What a DPDP-compliant onboarding flow looks like, step by step
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.
Ask at the moment of need
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.
This is a mock. The screens shown are illustrative, not a real app.
Related Articles
Collecting personal data from your own customers?
These are the rights your business has to honour. See where you stand with a two-minute self-check — no sign-up, no data stored.
Run the compliance self-check →