VEL

Trust centre

VEL runs on hosting that you control, and your business data stays in your own database. This page explains how VEL protects that data, and what you are responsible for.

Where data lives

In the MySQL database on your hosting account. GeekMidst does not receive a copy of your invoices or customers.

Sign-in security

Passwords are stored as one-way hashes. Accounts lock after repeated failures. Optional two-step codes, fingerprint/face passkeys (your biometrics never leave your device) and PIN auto-lock.

Web protections

CSRF tokens on every form, prepared database queries, output escaping, a strict content security policy, and private folders blocked from the web.

Access control

Super admin, admin and staff roles. Staff cannot change settings, manage users, delete records or see reports.

Audit log

Sign-ins, issued invoices, payments, deletions and settings changes are logged with the user and time.

Backups

Download a full database backup from the app whenever you like, and keep your hosting's automatic backups switched on.

Website analytics

This website counts visits itself, without cookies or third-party trackers. Raw IP addresses are not stored.

WhatsApp and email

VEL never sends messages by itself. It opens WhatsApp or your email app with a draft, and you choose whether to send it.

Offline copies

Pages you open in the app are kept on your device so they work offline, and are cleared when you sign out. Secrets such as SMTP and payment keys are stored encrypted.

Assistants

Kiyara and Mathi are rule-based and run inside VEL. They do not send your data to an external AI service.

Your responsibilities

  • Turn on SSL (HTTPS) for your domain.
  • Use strong, unique passwords, and turn on two-factor sign-in for admins.
  • Delete the install folder after installation.
  • Keep regular backups, and test restoring one.
  • Check the GST rates and invoice details you use with your tax advisor.

Report a security issue

If you find a vulnerability, please email info@geekmidst.com with the details, and give us a chance to fix it before you share it publicly.