Built for files a professional is bound to keep confidential.

Every page of gevox.in and every call to the Gevox server travels over HTTPS. Browsers are told to refuse a plain, unencrypted connection to Gevox for the next two years, so a fake copy of the site cannot be slipped in on a café or office network.

Both the website and the server send strict security headers: other sites may not show Gevox inside a frame to trick your clicks, browsers may not guess what a file is, and the camera, microphone and location are switched off.

• HTTPS only, enforced for two years on every subdomain
• Content Security Policy on the website and the server
• Framing by any other site refused
• Camera, microphone and location disabled

When you sign in, you receive a digitally signed pass. The Gevox server does not take it on trust. On every single request it checks the signature against the published keys, checks that the pass was issued for Gevox, and checks that it has not expired.

Sign-up, sign-in, password reset and the client intake form sit behind a CAPTCHA, so automated bots cannot hammer them. Actions that send email, run scans or generate documents have per-account limits. Passwords are held by the authentication provider as one-way hashes; Gevox’s own code never stores one.

• Signature, audience and expiry verified on every server call
• CAPTCHA on sign-up, sign-in, reset and intake
• Per-account limits on scans, documents and email
• Passwords never stored by Gevox’s code

Every client of a professional lives in its own workspace. The rule that keeps workspaces apart is written into the database as row-level security, on every one of its 55 tables. So even a mistake in the application cannot hand one client’s records to another account: the database refuses.

On top of that, every server endpoint that reads or changes client data first confirms that the person asking owns that workspace. Inside a firm, administrators and partners see the firm’s clients, and an associate sees only the clients assigned to them.

• Row-level security on 55 of 55 database tables
• Ownership checked on every endpoint that touches client data
• Firm roles: admin, partner, associate
• Associates limited to the clients assigned to them

Client documents go into private storage, in a folder only the owning account can reach. Each upload is capped at 25 MB, must be an allowed type, and has its first bytes checked against the type it claims, so a program renamed to look like a PDF is refused.

When you send a client the intake link, Gevox creates a 256-bit random key, shows it to you once, and keeps only its SHA-256 fingerprint. Whoever reads the database cannot rebuild the link from it. The link expires, works once, and you can revoke it at any time.

• Private storage, a separate folder per account
• Allowed types only, content checked, 25 MB cap
• Intake links stored only as a SHA-256 hash
• Links expire, work once, and can be revoked

Your account and every client record, document and file are stored in Mumbai, in Amazon Web Services’ ap-south-1 region, run by our database provider Supabase and encrypted at rest and in transit.

The application server that processes your requests runs in the United States, and the website is delivered through a global network. We do not hide that: every provider, what it touches and where it is, is listed on the sub-processors page as a cross-border transfer. Payments go through Razorpay in India, and Gevox never sees a full card number.

Every night the database is copied, checked, and encrypted before the copy is stored, with a key held offline and never on any server. The last 14 copies are kept. Files uploaded to client lockers are not yet part of this copy.

• Database and files: Mumbai, AWS ap-south-1
• Encrypted at rest and in transit
• Nightly encrypted database copy, last 14 kept
• Request processing in the United States, disclosed
• Every sub-processor listed with its location

Gevox’s findings and documents come from fixed checks and fixed templates. The same input gives the same output, which is what lets a professional check a result and defend it. The Document Analyser reads uploaded documents on Gevox’s own server with fixed checks; nothing is sent to an outside AI service.

In the practitioner product no AI model sees client content. Two optional features of the separate business workspace use an AI model provider, are marked as doing so, and the provider does not train on what is sent. The website scanner is fenced in: before it visits any address, and again for every request and redirect along the way, it confirms the address is on the public internet, so it can never be turned on private or internal systems.

• Same input, same output, every time
• Document Analyser runs on Gevox’s server, no third party
• No AI on client content in the practitioner product
• Scanner blocks private and internal addresses

Compliance work has to stand up later, in front of a client, an auditor or the Data Protection Board. Every Evidence Vault record is sealed with a SHA-256 fingerprint of its exact contents when it is saved, so any later change to it shows.

Every export of client data and every erasure (account exports and deletions, client erasures, document deletions, evidence, file and report exports) is written to a security log: who, from where, and when. The log is kept for one year, as Rule 6 of the DPDP Rules 2025 expects, and then de-identified. Payment confirmations are accepted only when the payment provider’s signature checks out, and each one is recorded before anything acts on it.

• SHA-256 seal on every evidence record
• Every export and erasure logged: who, where, when
• Log kept one year, then de-identified
• Payment events verified by signature, logged first