India data residency
LiveStorage and processing default to AWS ap-south-1 (Mumbai). Model inference leaves India — that is disclosed, not hidden.
- ✓Storage and application default to AWS ap-south-1 (Mumbai)
- ✓Organisation data-residency default of India
- ✓Model inference and error monitoring processed outside India, by named sub-processors
- ✓Sub-processor list published unauthenticated and derived from live configuration
What it is.
Storage and the application default to the AWS Mumbai region, and the default data-residency setting on an organisation is India. Your documents live there.
The part that matters for a localisation assessment is the exception, so we will state it plainly rather than in a footnote: model inference goes to third-party APIs — Anthropic, OpenAI for embeddings and part of the multi-agent path, and Google for the other part — and that content is processed outside India. Error monitoring likewise. The current vendor list is published on our privacy policy page and is generated from live configuration. If your obligation is that nothing leaves India, the hosted product does not meet it and the on-premise, air-gapped deployment is the honest answer, because there every one of those vendors is hard-disabled.
Three steps.
End to end.
The default region is AWS ap-south-1 (Mumbai) and the default residency setting is India. Nothing to configure.
Model inference and error monitoring reach sub-processors outside India, all of them disclosed.
Run it air-gapped on your own infrastructure, where every model vendor and every telemetry path is disabled by a hard gate in the code.
What you get.
- ✓Storage and application default to AWS ap-south-1 (Mumbai)
- ✓Organisation data-residency default of India
- ✓Model inference and error monitoring processed outside India, by named sub-processors
- ✓Sub-processor list published unauthenticated and derived from live configuration
- ✓Air-gapped self-hosting as the option where no outbound processing is acceptable
Quick answers.
That depends on your obligation and it is not ours to declare satisfied. Storage is in India; inference is not. Take the sub-processor list and the DPA to your compliance counsel and let them decide — anyone who tells you a SaaS product is automatically compliant is selling you something.
Not as a self-serve setting. Region choice on a self-hosted deployment is yours because you run it.
We are not printing a retention figure we cannot evidence. Ask us and you will get the real answer.
More in Platform & Deployment.
Tax invoices numbered consecutively within the financial year, with the CGST/SGST or IGST split, or zero-rated under LUT.
A read-only Indian legal-data API — clause benchmarks, judgment search, statute search — metered per key.
Right-click any PDF or Gmail attachment → "Scan with LexVio".
Air-gapped install via Helm chart. No outbound telemetry when AIR_GAPPED=true.