Is the compliance tool itself safe?
It is the first question a CISO should ask, and the one most privacy vendors answer last. A platform that indexes every piece of personal data you hold is either your best-protected system or your largest new risk. Here is how we build for the former.
How the platform is protected
Read-only and agentless
Connectors hold read permissions and install nothing on your systems. A compliance scanner should not become the most privileged thing in your estate.
No egress by default
Telemetry and error reporting are disable-able by configuration and verifiable by egress inspection. Unset means zero outbound traffic — no beacons to any vendor cloud.
Least-privilege access governance
Role-based access with entitlement inventory, recertification campaigns and four-eyes grant and revoke on the data that matters most.
Pseudonymisation where it counts
The consent ledger is pseudonymised by design, so the record proving compliance is not itself a fresh store of identifiable data.
Tamper-evident logging
Hash-chained evidence and a log vault with integrity verification, so what you present in an audit can be shown not to have been edited afterwards.
Sovereign by architecture
Self-hosted and in-India by design. With sovereign mode on there is no cross-border processing and no foreign sub-processor anywhere in the data path.
Certification status
Stated plainly, including what we have not finished. We would rather lose a deal to an honest answer than win one and be found out in diligence.
- DPDP-native product designIn place
- Indian OEM and IPIn place
- Air-gapped / on-premise deploymentIn place
- Data residency in IndiaIn place
- Class-I Local SupplierIn progress
- CERT-In empanelled VAPTIn progress
- ISO 27001On roadmap
- SOC 2 Type IIOn roadmap
Bring your security questionnaire
We would rather work through it on the first call than at the end of a procurement cycle.