Consent you can prove — and withdrawal you can honour.

Consent without a receipt is opinion.

In a dispute — with a data principal, a regulator or an auditor — the burden of proof sits on the Data Fiduciary. Without a receipt, the record does not exist.

DPDP §6 requires consent to be free, specific, informed, unconditional and unambiguous — and §6(4) makes withdrawal as easy as giving consent.

Consent lives in eight tools and none of them talk to each other.

CMPs collect it. CRMs use it. Marketing overrides it. Downstream systems have no idea what the data principal actually agreed to. The withdrawal button on the site does not propagate.

• Consent purposes reconcile to approved RoPA purposes.
• Receipt written on every capture — value, purpose, version, timestamp.
• Ledger per data principal with full state history.
• Withdrawal propagates to downstream systems and vendors.
• Language and surface variants tracked on the receipt.

Capture, receipt, ledger, withdrawal — as one workflow.

Every consent event lands in the same ledger. The withdrawal path is designed alongside the capture path.

1. 01
   Capture

   Consent widget renders from approved RoPA purposes.
2. 02
   Receipt

   Signed receipt written with purpose, version, surface and timestamp.
3. 03
   Store

   Ledger per data principal with full state history.
4. 04
   Withdraw

   One-tap withdrawal per purpose from a public link.
5. 05
   Propagate

   Downstream systems and vendors notified — with confirmation.
6. 06
   Evidence

   Receipt retrievable per data principal on request.

A ledger a regulator can walk.

Every event on the record. Every withdrawal actioned. Every propagation confirmed.

You can answer 'did this person consent, and to what?' — every time.

No more reconstruction from log fragments. The receipt is the record.

Grounded in

DPDP §6

Receipt

Per event

Withdrawal

One tap