Explore what each module does for your team below — and how it all writes to the one audit trail that has your back when a regulator calls.
Under the DPDP Act, consent must be free, specific, informed — and withdrawable as easily as it was given. Every decision is recorded precisely: tied to a specific purpose, dated, and never simply overwritten when something changes.
What DPDP §6(4) actually requires here — and where we found the same gap in our own product first: read the post →
Most rights-request tools are just ticketing systems: the request gets logged, someone gets emailed, and the data stays exactly where it was. Consent Tree executes it: the person’s records are hard-deleted from the platform’s own stores, the deletion is dispatched to each system you have connected, and the destruction itself is written into the audit chain. A request cannot be marked complete at all if that execution path isn’t configured.
PostgreSQL — a parameter-bound delete against the table and column you nominate, returning the row count the database itself reports.
Amazon S3 and S3-compatible stores — every object under the subject’s prefix deleted in batches, with the deleted count returned.
Salesforce, HubSpot, Zoho and Freshdesk — deletion through each vendor’s own API. Razorpay publishes no deletion API, so its connector says so and flags a manual filing rather than reporting a success it cannot achieve.
Every consent event, erasure, notice publication and policy change becomes a linked record, each one bound to the one before it. Alter any past record, and that break is visible immediately.
Then we go one step further: periodically, the current state of that record is stamped by an independent outside authority — a neutral third party who can attest “this existed, unchanged, at this moment.” Even a skeptical auditor can verify your history without taking our word for it, or yours.
How the hash-chained, Ed25519-signed trail actually works, and why that's a different claim from “we log everything”: read the post →
for entry in ledger: # each record commits to its predecessor assert sha256(entry.body + entry.prev_hash) == entry.hash # and the head is attested by an independent TSA, # so history can’t be quietly rewritten later assert tsa_verify(ledger.head.hash, ledger.head.tsa_token)
When someone disputes “I never consented to this,” you don’t produce a database entry — you produce a receipt that’s independently verified by a party that isn’t you. That is the difference between an assertion and evidence.
Impact assessments, control catalogs and policy approvals — structured, assigned, and gated so the right role signs off before anything counts as “done.”
New to the terms? Consent Manager, Significant Data Fiduciary and Data Protection Board, plainly defined with section numbers: read the glossary →
Guided Data Protection Impact Assessments built from a structured screening, risk register and control catalog — not a freeform document you fill in from scratch.
A controls library aligned to RBI's cybersecurity framework, monitored continuously, and mapped to the 12-pillar compliance scorecard.
Draft → review → approve → publish for privacy policies, with version history and forced re-consent on material changes.
Sign-off on governance actions is restricted to your DPO and admins. Task assignment, ownership and due-date tracking built in.
The DPDP Act expects notices to be available in the languages of the Eighth Schedule. We translate notices and consent flows into 22 Indian languages using a self-hosted translation model that runs on our own infrastructure — no third-party API, nothing leaves our systems.
Shipped: notices & consent flows in 22 Indian languages, translated locallyOur scanner loads your public pages like a stranger would and reports what it finds — before consent is given, after it’s refused, and everywhere in between.
70+ tracker and pixel signatures detected before consent is given — the classic case of analytics firing before the banner even loads.
Detects manipulative banner design: buried reject buttons, pre-ticked boxes, consent walls.
Checks whether Google's Consent Mode is set up correctly, and whether Global Privacy Control (GPC) — the browser signal for "don't track me" — is actually honoured.
Grades whether your privacy policy substantively covers DPDP/GDPR duties, or just gestures at them.
The scorecard, the scanner, the audit feed and the task queue meet in an operations center designed for DPOs — with an AI assistant that answers from your tenant’s real data, in plain language.
A weighted compliance posture score across twelve pillars, with a configuration assistant that recommends the highest-impact next fix.
Shipped: compliance scorecard with next-best-fix recommendationsA single source of truth for data assets, with visual lineage tracing how personal data flows between systems and purposes.
Shipped: unified data inventory + visual lineageAn AI assistant trained on the platform's own documentation and your organization's context — for DPOs and end-users alike.
Shipped: AI guidance assistant, grounded in your own documentation