Step 01
Step 1
Open /settings → Consent; see every flag with its purpose, retention window, and current state.
ComplianceRetailpartial· marketing-claim · dpdp-self-serve-erasure
DPDP §12 self-serve erasure.
See every consent flag, change any of them, and start an account erasure in two taps.
The problem
Why this exists.
The Digital Personal Data Protection Act makes consent specific, purpose-bound, and withdrawable. Most apps treat it as a one-time signup checkbox.
We want every consent flag visible and switchable from one screen, with an honest erasure path that cascades across our entire data stack.
How it works · 3 steps
From input to outcome.
- Step 02
Step 2
Toggle a flag off — downstream features that need it pause; we never silently re-enable.
- Step 03
Step 3
Start erasure with a 7-day grace; the worker cascades across 30+ tables after the window.
Under the hood
The models and routes behind it.
Models called
No models cite this feature directly — backing logic is deterministic Python.
API routes
- POST /api/v1/consent
Compliance posture
- DPDP §6 — every flag declares purpose, retention, and right-to-withdraw.
- DPDP §12 — self-serve erasure is the fiduciary obligation, not a courtesy.
- Grievance contact [email protected] under DPDP §13; audit-trail captures every flag change.
What it's not
Erasure completes within the DPDP-prescribed window after a grace period — it is not instantaneous. The worker runs daily and cascades across thirty-plus tables.
Related · features & stories