Security, Data Residency & Tenant Isolation
Accie is architected with strict regional data boundaries, hardware-level tenant isolation, and DPDP-aligned data residency.
1. Multi-Tenant Architectural Isolation
Every customer account on Accie is treated as a cryptographically separate tenant boundary:
- Postgres Row-Level Security (RLS): Database tables enforce tenant isolation at the query execution level, keyed to the verified organization ID from your authentication token.
- Object Storage Isolation: Uploaded scans and JSON payloads are stored under private, tenant-scoped paths in AWS / Cloudflare object storage. Access is permitted strictly via short-lived signed URLs (15-minute TTL).
- Zero Cross-Tenant Access: Organization identifiers supplied in request payloads are never trusted without cryptographic session signature verification.
2. India Data Residency (DPDP Aligned)
All production services, database clusters, and machine learning inference pipelines for Accie Extract reside within AWS Asia Pacific (Mumbai, ap-south-1) and MeitY-empanelled regional data centers:
- No document bytes or extracted financial records leave the sovereign territory of India during transmission, processing, or storage.
- Tax and financial documents remain compliant with the Digital Personal Data Protection (DPDP) Act 2023 and RBI data localization guidelines.
3. Encryption in Transit and at Rest
| Layer | Standard | Implementation |
|---|---|---|
| In Transit | TLS 1.3 / HTTPS | Mandatory HTTPS with HSTS; TLS 1.2+ minimum cipher suites across all endpoints. |
| At Rest | AES-256-GCM | Object storage, Postgres volumes, and audit logs encrypted with AWS KMS keys. |
| Webhook Delivery | HMAC-SHA256 | Every event signed with your secret key via X-Accie-Signature header. |
4. Data Retention & Automated Purge
You retain absolute ownership of your data. Accie enforces automatic data retention schedules:
- Original source PDFs and document images are purged automatically after your retention window (configurable from 7 to 90 days).
- Account closure triggers automated cryptographic deletion of all stored document objects within 30 days.