Trust Center
Your clients' data, treated the way a CA firm would demand.
Ganav was built controls-first, for people who are personally accountable for other people’s money and private information. Here’s exactly how we protect it, where it lives, and the commitments we make.
Data isolation & residency
- A separate tenant per firm — always. Your own database and your own encryption keys, never shared with another firm. (Full detail: Tenancy & Architecture.)
- Data residency — India-first. Ganav is hosted on Microsoft Azure in India and run by BLS Software, a Microsoft Indirect Reseller. Firms with residency or contractual mandates can have their tenant on a dedicated Azure VM, or in an Azure subscription in the firm’s own name — still installed, monitored and updated by us, so there is never a server of your own to look after. Even the AI layer offers an India-hosted provider (Sarvam AI) so document text can be processed within India.
- Encryption everywhere it counts. Secrets and PII (GSTIN, PAN, Aadhaar, UAN, bank details) are stored AES-256-GCM encrypted, with the master key held outside the database. Employee PII is masked by default and revealing it needs a dedicated, audited permission.
- Backups & retention per tenant, on your schedule, with policy-driven archival to cold storage.
- Audit independence by architecture. Ganav Audit runs as a separate application and database that cannot open the accounting tenant — client books reach it only as a signed snapshot the firm’s key has verified.
How we protect data in use
- AI PII maskinggovernment IDs in document text are tokenized before any AI provider sees them, and the masking fails closed. (Text IDs are masked; vision/image OCR pixels are a disclosed, accepted exposure.)
- Maker–Checker governance + segregation of duties on every financial mutation.
- Immutable audit trailevery action recorded, insert-only, including denied and auto-approved ones.
- Real authentication controlsJWT with genuine token revocation, standards-based 2FA (TOTP), role-based access with continuous role-health checks.
Availability & operations
- Uptime targets: 99.5% (Cloud Professional) / 99.9% (Dedicated VM).
- Backups: daily on Cloud Professional and above; dedicated backups on the Dedicated VM and Azure-in-your-name tiers.
- Change management: governed, versioned database migrations from signed release batches; updates rolled per tenant with pre-swap startup validation, a binary snapshot and one-command rollback, a configuration doctor, and a version-drift guard. The running build is visible in the product.
Compliance posture (honest, current-state)
- DPDP Act, 2023 (India) readiness. Ganav’s architecture provides strong building blocks for India’s Digital Personal Data Protection Act: tenant isolation, encryption at rest, PII masking, audited access to personal data, and immutable logs. To be fully DPDP-compliant as an operator you still need: a published Privacy Policy, a consent/notice mechanism, a named grievance/Data-Protection contact, a data-retention & erasure process, and breach-notification procedures.
- GST/IT compliance of the product itself (as an accounting tool) is covered on the Governance & Compliance page.
Sub-processors & third parties (disclose)
List every third party that could touch customer data, for transparency:
| Sub-processor | Purpose | Data it may see |
|---|---|---|
| Anthropic (Claude) | AI document extraction (text + vision) | Document text with government IDs tokenized; image pixels for vision OCR |
| Sarvam AI (India-hosted) | AI document extraction (text) | Document text with government IDs tokenized |
| Microsoft 365 / Google (Gmail) | Staff email send for client queries (per-user OAuth) | Email content the staff member sends |
| BLS Connect (Ganav’s messaging platform) → Meta (WhatsApp Business API) | The WhatsApp Business channel — client bills in, staff replies out, published documents sent | Message text, media the client or staff send, the client’s phone number, delivery/read status |
| Cloud hosting provider | Cloud infrastructure | Encrypted data at rest / in transit |
| Payment gateway | Billing | Billing details (not accounting data) |
Support telemetry (disclose)
To support you, each Ganav instance reports to Ganav’s support desk: a heartbeat with the running build and its configuration posture, and error captures (correlation ID, message, stack trace, the route or job that failed). This is diagnostics, not your ledger — it does not include journal contents, documents, or party data. Support tickets you raise from inside the product carry whatever you attach to them.