Consent Manager SDK — Purpose-Level Consent with a Hash-Chained, Auditable Record
Every consent, change and withdrawal, written into a hash chain you can verify.
Each record is sealed with the hash of the one before it. Alter or drop a record and the chain stops verifying — so the ledger is something an auditor can check rather than something they have to trust.
Consent you can prove, not just collect
Not a cookie banner. A consent lifecycle with a record an auditor can check — and a clear line around what is not built yet.
Consent Banner
A drop-in banner with per-purpose toggles, an accept and a reject of equal weight, and a language selector driven by the notices you publish. Scripts you tag with a purpose stay inert until that purpose is granted, including ones injected later by a tag manager.
Purpose-Based Consent
Separate consent for each processing purpose — marketing, analytics, personalisation, essential. The user controls each one independently, and the decision is recorded per purpose rather than as a single yes.
Tamper-Evident Consent Ledger
Every consent action is recorded with its timestamp, a salted hash of the IP rather than the IP itself, the user agent, the exact notice version and hash that was shown, and the purposes chosen — then sealed into a SHA-256 chain. An admin endpoint re-verifies the whole chain on demand, and records export for auditors.
Rights-Request Intake
A public endpoint accepts access, correction, erasure, grievance and nomination requests, creates a ticket with the DPDP 90-day due date, and puts it in a queue your DPO works through in the dashboard. We do not ship a hosted end-user portal — the form on your site is yours to build and place.
Consent Withdrawal
One call withdraws every non-required purpose: local consent flips to denied, Consent Mode v2 is signalled, the withdrawal is written into the chain, and an HMAC-signed webhook fires to your backend. Webhook delivery is fire-and-forget today — there is no retry queue yet — and scripts already running in the page are not torn down, so your systems must act on the signal.
Browser SDK and REST API
A JavaScript SDK for the browser and REST endpoints for consent, withdrawal, rights requests and configuration. Native Android and iOS SDKs, a Flutter widget and a React Native module are not built.
How it works
Install, configure, collect, verify.
Add one async script tag carrying your site's public id. No backend change is needed to get the banner on the page.
Define your processing purposes, author the notice text in the languages you need, and publish a version. The banner pins the exact notice version and hash it showed.
Users decide per purpose. Consents, changes and withdrawals are appended to your site's chain as they happen, each sealed against the record before it.
Export consent records for an auditor, and re-verify the whole chain from the dashboard whenever you need to show the ledger has not been altered.
One dashboard for your DPDP work: consent records, rights requests and withdrawal logs live in the same Bachao.AI dashboard as the rest of your data-protection work — so your DPO is not reconciling two systems.
A cookie banner is not a consent manager
The gap is not the popup. It is what happens after the click — what was recorded, whether it can be proved, and how a withdrawal or a rights request is handled.
| Typical cookie banner | Bachao.AI Consent Manager | |
|---|---|---|
| Consent granularity | One accept or reject, for cookies | Per-purpose consent, each purpose independent |
| Proof of consent | A log row you have to trust | Hash-chained record, verifiable end to end |
| What is stored | Usually the raw IP | Salted IP hash, notice version and notice hash |
| Withdrawal | Often harder than giving consent | One call, recorded in the chain, webhook to your backend |
| Data principal rights | Out of scope | Access, correction, erasure, grievance, nomination — ticketed with the 90-day clock |
| Notice languages | Whatever the vendor translated | You author the notice in the languages you need |
Not packaged yet
Consent Manager is still being built, so there is no plan to sell you and no tier list worth printing. If it is close to what you need, talk to us — we will scope the work, tell you plainly what exists today, and quote only for that.
Frequently asked questions
Everything you need to know about DPDP consent management.
Are you a registered DPDP Consent Manager?
No — and nobody is yet. The DPDP Act 2023 creates a Consent Manager role that must be registered with the Data Protection Board, and reserves it for entities incorporated in India. That registration is not open, so no company holds a registration today and we do not claim one. Bachao.AI is India-incorporated, which is the eligibility condition, and we intend to apply when the Board opens registration. Until then, treat this as consent-management software — not a registered Consent Manager.
What’s the difference between a cookie banner and DPDP consent management?
A cookie banner asks for cookie consent — typically a single yes or no. The DPDP Act expects purpose-specific consent (marketing versus analytics versus personalisation), a record of what was shown and agreed to, withdrawal that is as easy as giving consent, and a route for data principal rights such as access, correction, erasure and grievance. A cookie popup handles none of that.
How long does integration take, and what platforms are supported?
For a website it is one script tag; the real work is defining your purposes and writing your notice text in the dashboard, which depends on how many purposes you have. What ships today is the browser SDK and the REST API. There is no npm package, no Flutter widget, no React Native module and no native Android or iOS SDK — if you need one of those, tell us and we will be straight about the timeline.
What happens when a user withdraws consent?
The SDK flips local consent to denied for every non-required purpose, signals denial through Consent Mode v2, and records the withdrawal server-side in the hash chain with the purposes withdrawn. If you have configured a webhook, an HMAC-signed notification is sent to your backend — fire-and-forget, with no retry queue yet. Scripts already loaded in the page are not removed, so acting on the signal is your systems’ job.
Is this enough for DPDP compliance on its own?
No, and we will not tell you otherwise. It covers consent capture, proof, withdrawal and rights-request intake. Data mapping, retention, breach notification, vendor contracts and your internal policies sit outside it. Installing an SDK is not compliance — it is one of the things compliance needs.
What languages does the banner support?
Whichever ones you author. A notice carries a language, a site can hold several, and the banner shows a language selector when more than one is published. We do not supply translations and we do not claim coverage of all 22 Eighth Schedule languages — the notice text is yours, which also means it says what your lawyers approved rather than what a vendor machine-translated.
Explore more products
Bachao.AI covers your entire security surface — from code to cloud to compliance.
Start keeping a consent record you can prove
Consent Manager registration is not open yet, and no vendor can honestly tell you otherwise. What you can do now is capture purpose-level consent properly and keep a ledger that verifies. Talk to us about a pilot on one site.