DPDP
Withdrawal
Changing optional consent. New receipts, same browser scope.
Withdrawal
Consent frameworks generally expect withdrawal to be as practical as giving consent. Erasure supports optional purpose withdrawal and preference updates as new receipts, not silent edits.
What subjects can do (v1)
On the same browser / installation:
| Mechanism | Behaviour |
|---|---|
| Preference modal | Manage optional purposes; withdraw optional |
| Hosted preferences | /preferences?key=pk_live_… |
| SDK | client.withdrawOptional(), client.showPreferences() |
| Optional chip | Accord.init({ privacyControl: true, … }) re-entry |
Required purposes stay on. Each change creates a new append-only receipt.
What this is not
- Not multi-device "same person everywhere" identity
- Not automatic stop-processing across your entire estate (use webhooks + your own systems)
- Not legal confirmation that your withdrawal path meets every duty