Security & trust
A compliance platform is only as credible as its own security posture. This page summarizes the architecture decisions that protect tenant data — the same ones we help you evidence.
Tenant isolation at the database layer
Every tenant-scoped table enforces PostgreSQL Row-Level Security with FORCE ROW LEVEL SECURITY. Isolation is a database property, not an application promise — and automated cross-tenant isolation tests run in CI.
Encryption everywhere
TLS 1.2+ in transit end to end. AES-256 at rest, with application-level envelope encryption for sensitive fields — per-tenant data keys, so offboarding can cryptographically shred a tenant's data.
Data minimization by design
We store configuration and control state, not your customers' personal data. PII discovery records category labels and counts only. Data principal contacts on DSR tickets are envelope-encrypted.
No passwords, read-only access
Sign-in is SSO-only (Google / Microsoft) — we never store passwords. Future connectors use read-only scopes and short-lived credentials (STS AssumeRole, GitHub App installation tokens).
Tamper-evident evidence
Evidence objects are content-hash addressed, version-locked and hash-chained per control. A nightly job re-verifies random samples; any retroactive alteration breaks the chain.
We run on our own product
Alvionix operates as tenant zero: our own DPDP obligations — notice, consent records, grievance redressal via support@complianceedge.in — are tracked in the same DSR module we sell.
Responsible disclosure: report vulnerabilities to support@complianceedge.in. We acknowledge within 48 hours.