Built for how India regulates data
Not a global product retrofitted with a compliance checklist — data residency and consent handling are part of the architecture, not an add-on.
| Claim | Backing |
|---|---|
| Data stored in India | Database, file storage, OCR and embedding generation all run in AWS ap-south-1 (Mumbai). |
| Per-account isolation | Every document, chat session, guardrail and usage record is scoped by account — no shared or cross-account visibility. |
| Answers grounded in your content | Retrieval-augmented generation over the account's own library, not open-ended model knowledge. |
| Consent-aware by design | Configurable notice + consent checkbox on lead capture, with a permanent per-lead record of exactly what was agreed to — built against India's DPDP Act. |
| Powered by AWS Bedrock & Anthropic Claude | Enterprise-grade LLM infrastructure, not a hobbyist API wrapper. |
| Scoped, revocable API access | Server keys are hashed at rest, IP-allowlistable, individually rotatable with immediate effect. |
Data residency
Your database, file storage, OCR processing and embedding generation all run in AWS
ap-south-1
(Mumbai) — not routed through infrastructure outside India.
DPDP-aligned consent
Every widget can carry a privacy-policy link and a required consent checkbox, and a permanent snapshot of exactly what a visitor agreed to is stored against their lead — built against India's Digital Personal Data Protection Act, not GDPR-first tooling retrofitted after the fact.