DPDP
Notice (DPDP)
Versioned notices subjects actually see — and how publish freezes them.
Notice
A notice is what people see: titles, descriptions, purpose labels, and company framing.
In Erasure, notice content lives in consent configuration. Until you publish, it is a draft. Publishing creates an immutable consent version (snapshot + content hash).
Why versioning matters
If notice wording changes, history must not rewrite what earlier subjects saw.
| State | Behaviour |
|---|---|
| Draft | Editable in console; not served to SDK |
| Published version | Frozen; version number increments |
| SDK load | Published snapshot only |
Operator workflow
- Edit notice fields in Consent.
- Review purposes and required vs optional.
- Publish.
- Inspect versions history when you need to know what was live.
Optional: export publish evidence after a publish for internal records.
What Erasure does not do
- Auto-generate counsel-approved legal language
- Localize notices for every Indian language out of the box without you configuring copy
- Guarantee that your notice text is sufficient under DPDP—that is a legal decision
What to do next
Consent · Withdrawal · concept Consent