DIMEAI Consent Manager
Consent Manager
for Data Fiduciaries.
A module you run in your own stack. Every consent and every withdrawal becomes an append-only, hash-chained record, signed twice, with a receipt for the person.
Sections 5, 6 and 7 of the DPDP Act.
The Consent Manager is built around three ideas in the Digital Personal Data Protection Act, 2023. It does not replace legal advice; it gives you the records.
Section 5: notice
Tell the person what is collected and for which purposes before you ask. Here, notices are versioned, and a notice goes live only after a second person approves it (maker-checker).
Section 6: consent
Consent is asked purpose by purpose and is never pre-ticked. Withdrawal is as easy as giving consent, and it is recorded as its own record. SMS and OTP are never treated as consent.
Section 7: other grounds
Not everything rests on consent. Legacy, declaration and legitimate-use records are kept alongside consent records, so one place shows the basis for each purpose.
Records you can check yourself.
The Consent Manager runs inside your own stack. Your signing keys stay in your own secrets manager.
Append-only, hash-chained
Every consent and every withdrawal is added to a chain. Nothing is edited in place.
Signed twice
Each record is signed with ECDSA P-256 and with ML-DSA-65.
Offline verification
Anyone holding the public keys can verify the chain without calling a server.
Receipts
The person gets a receipt for each consent and each withdrawal.
Versioned notices
Each record points to the exact notice version that was shown.
Erasure of sealed proofs
The tenant dashboard supports erasure of sealed proofs, and export.
Five steps, from notice to proof.
Publish the notice
Write the notice and its purposes in the tenant dashboard. A second person approves it before it goes live. Each change is a new version.
Ask, purpose by purpose
The person sees each purpose with nothing pre-ticked. The same choices work in the web widget, the Android and iOS consent panel, and in assisted counter and call-centre sessions.
Record and sign
The choice becomes an append-only record, linked to the one before it and signed with ECDSA P-256 and ML-DSA-65. The person receives a receipt.
Change or withdraw
A withdrawal is added as its own record at the moment it happens. The earlier consent record stays in the chain.
Verify, export, erase
Verify the chain offline with the public keys, export records and receipts from the dashboard, and erase sealed proofs when required.
Where people give consent
- Web widget, bound to a passkey and the browser fingerprint
- Android and iOS consent panel
- Assisted counter and call-centre sessions
Each rung adds something you can check.
| Rung | What it adds |
|---|---|
| 1. Record | An append-only entry for the choice: the person, the purpose, the notice version shown, and whether it was a consent or a withdrawal. |
| 2. Hash chain | The entry is linked to the one before it, so a removed or changed entry breaks the chain. |
| 3. Two signatures | The entry is signed with ECDSA P-256 and ML-DSA-65. The signing keys sit in your own secrets manager. |
| 4. Receipt | The person receives a receipt for what they chose. |
| 5. Offline verification | Anyone with the public keys can check the chain and the signatures without calling a server. |
Data Fiduciaries that need consent they can show.
Government
Departments and agencies that serve people at counters, over the phone and online, and need one record across all of them.
D2C
Consumer brands that ask for consent on a website and in an app, purpose by purpose, and need to honour withdrawal.
BFSI
Banks, lenders, insurers and other regulated firms that need signed records they can verify offline.
One place to run it.
Overview and person view
Active consents, withdrawals and the latest events, then one person's timeline with the data types, proof and browser fingerprint behind each consent.
Notices
Draft, version and publish notices. Two admin logins; turn on a second approver (maker-checker) when you want one.
Records and receipts
Look up consent and withdrawal records and the receipts issued.
Erasure and export
Erase sealed proofs and export records.
Not SMS, not OTP
The Consent Manager never treats an SMS or OTP as consent.
Illustration with demo data
| Event | Purpose | Data types | Proof | Browser fingerprint | Evidence |
|---|---|---|---|---|---|
| Granted 10:42:07 | KYC verification | KYC, Mobile number | Passkey | fp 7c2e…91, tier HIGH | sha256 9f3a…c21e ES256 · ML-DSA-65 |
| Verified 10:42:08 | KYC verification | KYC, Mobile number | Checked before processing | Not applicable | sha256 4be0…7d93 ES256 · ML-DSA-65 |
| Withdrawn 11:15:31 | Marketing SMS | Mobile number | Session-bound | fp 7c2e…91, tier HIGH | sha256 c7a1…02fb ES256 · ML-DSA-65 |
GET /consents/verify?purpose=kyc returns 200 granted. Every grant and withdrawal is hash-chained, and you can export the ledger for audit. The data itself is never stored here: only its type.
Give consent, then withdraw it.
See a sample notice, make your choices, receive a receipt, and then withdraw. It takes about a minute, and the demo asks for no personal data.
Open the live demoTry it free for 7 days.
Sign up with your company email and choose DPDP Consent Manager. We send a verification link first, and the trial needs no card. Your 7 days start the day we send your trial access. After the trial, DPDP Consent Manager is $999 per month, billed monthly by invoice.
Frequently asked questions
What is the DIMEAI Consent Manager?
It is a Consent Manager for Data Fiduciaries: a module you run in your own stack that records every consent and every withdrawal as a signed, hash-chained record, purpose by purpose, and gives the person a receipt.
Where does it run, and who holds the signing keys?
You run it in your own stack. The signing keys are held in your own secrets manager, not by DIMEAI.
How are consent records protected against change?
Each record is appended to a hash chain and signed with ECDSA P-256 and ML-DSA-65. Records are never edited in place, and anyone holding the public keys can verify the chain offline.
Is consent ever collected by SMS or OTP?
No. Consent is given through the web widget, the Android or iOS consent panel, or an assisted counter or call-centre session. SMS and OTP are never treated as consent.
Are the consent boxes pre-ticked?
No. Consent is asked purpose by purpose and nothing is ticked in advance.
How does withdrawal work?
Withdrawal is its own record, added to the chain at the time the person withdraws. The earlier consent record is kept, not overwritten.
Can records be erased?
Yes. The tenant dashboard supports erasure of sealed proofs, as well as export.
Can I try it?
Yes. Choose DPDP Consent Manager in the free trial form. The trial runs for 7 days from the day we send you your trial access.