DPDP
Consent (DPDP)
How Erasure supports purpose-bound consent collection with durable proof.
Consent
Under DPDP-shaped work, teams must collect personal data for stated purposes and be able to show what people agreed to.
Erasure’s Consent product (Anumati) turns a banner into:
- Configured purposes and notice copy
- A published immutable version
- Append-only receipts when subjects choose
How Erasure supports this
| Need | Product behaviour |
|---|---|
| Purpose-bound collection | Configure required and optional purposes |
| Consistent notice | Draft → Publish freezes a version |
| Proof of choice | Receipt stores choices + version reference |
| Live integration | Browser SDK loads published config only |
What you do in Erasure
- Create a project.
- Configure purposes and notice.
- Publish.
- Create a publishable key and install the SDK.
- Confirm receipts after subjects interact.
See Publish your first consent form and Consent (concept).
Limits (honest)
- Erasure does not write your legal notice for you.
- Draft config is never what the SDK serves.
- Receipts are operational proof inside the product—not a sealed legal archive.
What to do next
Read Notice for how versioning works, or implement via First 30 minutes.