A privacy platform is a concentration of exactly the data it protects. That deserves specifics, not a badge wall — so this page describes controls, not certifications-in-progress.
Every customer's data is kept separate from every other customer's by default, with dedicated-schema and fully-siloed database options for stricter requirements. This isolation is enforced by the database itself, not just application logic, and every table carrying a tenant key is checked for it by an automated guard that runs before any code can be pushed. No third-party audit of it has happened yet — a penetration test is scoped and not yet commissioned.
3 isolation modes — pooled, dedicated schema, fully siloedAccess is controlled by role everywhere in the product — down to which roles may approve a governance attestation. Multi-factor authentication is required for privileged accounts, end-to-end.
Shipped: platform-wide RBAC · TOTP MFAEvery request is checked to confirm the caller actually owns the record they're asking for — closing off the single most common way privacy platforms get breached. Every path is authenticated, and every API key is locked to the exact domain that issued it.
Shipped: JWTAuth + self-guards on partner routesEvery audit event is linked to the one before it, and independently timestamped by an outside authority on a regular basis. Our own operational actions land in the very same trail as yours — we don't get a separate, quieter record. How the chain actually works →
Shipped: audit chain + TSA anchoringAn eighteen-step gate runs before any code leaves a machine: secret scanning that hard-fails, static analysis, dependency and container vulnerability scanning, and a set of guards that enforce this platform's own data-protection rules. Load and dynamic-security suites run against a real database rather than a simplified stand-in — on demand today, not yet wired into every release, and we would rather say that than imply otherwise.
Shipped: 18-step pre-push gate · k6 load suites · ZAP DAST (on demand)Data is encrypted in transit and at rest. Retention windows are enforced automatically rather than manually, and purpose-limitation is checked in the backend — not left to the UI's good manners, where it would be easy to bypass.
Shipped: automated retention enforcement · backend purpose checksCompliance buyers get lied to constantly, so we keep a short list of things this site deliberately does not say:
When third-party attestations complete, they’ll appear here with report dates — not as logo wallpaper before then.
We say TLS in transit, encryption at rest, and SHA-256 hash chains with RFC 3161 anchoring — terms your security team can verify.
Every “Shipped:” chip across this site names the actual service or module behind the claim. If a capability is roadmap, it isn’t on this website.
Receipts, chain segments and TSA tokens export in open formats and verify with standard tooling — with or without us. Check an evidence pack yourself → The verifier runs entirely in your browser; the pack is never uploaded, and the signing key is published out of band so you don’t have to trust our API for it.
Security reports go straight to the engineering team, and we credit researchers who report in good faith. Write to cdpo@consentree.in — we read it.
If you report in good faith, we will not pursue you. We will not bring legal action against you, or support action by anyone else, for research that follows this page. That means: tell us before you tell anyone else and give us reasonable time to fix it; access only the data you need to demonstrate the issue, and never anyone else’s personal data; don’t degrade the service or run automated scanning that would; and don’t extract, keep or publish data you find. Work within those lines and you are covered — if you’re unsure whether something crosses one, ask us first and we’ll tell you.
We don’t run a paid bounty programme today, and we’d rather say so here than let you find out
after a weekend’s work. Our machine-readable contact is at
/.well-known/security.txt.