Skip to content

Trust

Where the ledger lives, and who can reach it.

You are handing us your client’s books. That deserves a straight answer rather than a badge wall, so this page says what is in place today and nothing more.

In place today

What the system actually does.

Each record states one control as a buyer can read it, and names the part of the product it comes from. Nothing here describes work that is planned.

  1. India data residency

    Client ledgers and uploaded documents are held in object storage in India, in Google Cloud’s Mumbai region. AI features run on Gemini in Mumbai through OpenRouter, with zero data retention. If your engagement terms need the residency stated in writing, ask and we will put it in the agreement.

    Evidence

    Google Cloud asia-south1 (Mumbai); OpenRouter zero data retention

  2. Role-based access

    Firm admin, senior auditor and junior auditor each see only what their role permits, enforced on the server rather than hidden in the interface.

    Evidence

    Backend require_roles enforcement; frontend RoleGuard

  3. Every action is logged

    Who opened what, who reviewed a flag, who proposed an adjustment from one, and when — each recorded against the user who did it.

    Evidence

    Audit trail logging in the backend

  4. Session-based authentication

    Sign-in uses httpOnly cookies with short-lived access tokens and refresh rotation. No token is exposed to page scripts.

    Evidence

    Cookie-based JWT auth, access plus refresh

  5. Client portal is deliberately narrow

    Your client signs in to send documents and to download the reports your firm has chosen to share. The findings queue, review notes and working papers are not shown there, and nothing reaches a client unless the firm decided to share it.

    Evidence

    Portal endpoints scoped to document upload and firm-shared reports; separate portal identity

  6. Tenant isolation

    Every record is scoped to a firm. Another practice using the platform cannot see your work.

    Evidence

    Firm-scoped multi-tenancy across the data model

Compliance

Compliant, and resident in India.

Quantom is SOC 2 compliant, encrypts client data with 256-bit encryption, and keeps it resident in India.

Certifications held
SOC 2

A clearer practice

Read the controls against your own file.

Bring the questions your firm has to answer about client data, and see where each one lands in the working system.

Book a Raukon walkthrough