What a DPDP-compliant onboarding flow looks like, step by step
Reviewed by Confidential Dispatch Editorial Team · Updated 21 Jul 2026 · 2 min read
This is a mock. The screens shown are illustrative, not a real app.
What a compliant onboarding flow looks like
The same app, step by step — asking for the right thing at the right moment, and leaving the choice with the person. Five points make it work.
Minimal signup
Only the data the core service needs — name and mobile — asked for up front, with a one-line reason attached.
The location permission appears when a feature first needs it, not bundled into signup. Context is what makes the choice meaningful.
A genuine decline
“Not now” carries the same weight as “Allow.” Refusing is a real, equal option — not a greyed-out afterthought.
Optional stays optional
Marketing consent is separate, off by default, and refusable — and the app works exactly the same if it’s declined.
Withdrawal in one place
A settings screen lets any consent be switched off as easily as it was granted. Withdrawal is one reachable screen, not a support ticket.
Every article is checked against the current law and the judgments it cites before it is published.
Updated 21 July 2026 · Not legal advice.
