Templates & playbooksUpdated 22 November 20269 min read

Designing Consent and Withdrawal UX for DPDP

UX and engineering patterns for DPDP-compliant consent and withdrawal: affirmative action, per-purpose choices, symmetric withdrawal under Rule 3(c)(i), and consent records.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Consent standard
Section 6, DPDP Act
Withdrawal standard
Rule 3(c)(i): ease comparable to giving
Notice standard
Rule 3
Consent Manager rule
Rule 4, in force 13 Nov 2026
Core rules in force
13 May 2027
Children
Verifiable parental consent (Rule 10)

Quick answer

DPDP consent must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action under section 6. Rule 3(c)(i) requires withdrawal with ease comparable to giving consent. In UX terms that means unticked per-purpose choices, no bundling with terms, equal-weight accept and reject options, and a withdrawal control reachable in as few steps as the original consent. These rules apply from 13 May 2027.

  • Consent requires a clear affirmative action; pre-ticked boxes and continued browsing do not count.
  • Each purpose needs its own choice so that consent is specific, as section 6 requires.
  • Withdrawal must be comparable in ease to giving consent: measure the steps and keep them symmetric.
  • After withdrawal, processing and processor processing must stop within a reasonable time.
  • Store consent as versioned, timestamped events linked to the notice shown.
  • Registered Consent Managers, live since 13 November 2026, offer an alternative channel for consent.

Who this is for: Product designers and UX researchers, Frontend and mobile engineers, Product managers for sign-up and settings, Privacy engineers, Growth teams

Section 6 of the DPDP Act sets the substantive standard. Consent must be:

ElementUX implication
FreeNo forced consent as a condition of an unrelated service; no penalty for refusing
SpecificOne choice per purpose, not a single "I agree to everything"
InformedShown with a Rule 3 notice that is understandable on its own
UnconditionalNo hidden conditions attached to the choice
Unambiguous, by clear affirmative actionA tap, click or toggle that the user performs; nothing pre-selected
Limited to necessary dataAsk only for data the purpose needs

Section 6 also lets a Data Principal withdraw consent at any time, makes the ease of withdrawal comparable to that of giving consent, and requires the fiduciary to cease processing, and cause its processors to cease, within a reasonable time after withdrawal. Processing done before withdrawal remains lawful.

Rule 3(c)(i), in force from 13 May 2027, requires the notice itself to provide the communication link and other means to withdraw consent with the ease of doing so being comparable to that with which such consent was given. That turns a principle into a testable design requirement.

Sign-up and onboarding

  • Separate account creation (often relying on data voluntarily provided for that purpose) from optional purposes such as marketing and personalisation.
  • Show optional purposes as unticked checkboxes or toggles, each with a one-line description.
  • Do not combine "I accept the Terms" with any data consent.

Banners and modals on the web

  • Layer 1: plain-language purposes, with Accept all, Reject all and Choose given equal visual weight.
  • Layer 2: per-purpose toggles defaulting to off, each listing the data used and vendors involved.
  • Do not set tracking before the user acts.

Just-in-time prompts

Ask for permission at the moment the feature needs it, for example location when the user opens store finder, with a notice explaining that specific use. This produces more specific, informed consent than an upfront bundle.

Messaging channels

For WhatsApp, SMS and email marketing, use an explicit opt-in, confirm it in the first message, and include a one-word or one-tap opt-out in every message.

Patterns to avoid

Pre-ticked boxes, "by continuing you agree", consent walls that block the core service for an unrelated purpose, confirmshaming copy and colour schemes that hide the reject option.

Designing withdrawal with comparable ease

Make Rule 3(c)(i) measurable: count the steps and the discoverability of each path.

How consent was givenComparable withdrawal
One tap on a bannerPersistent "Privacy choices" link on every page that reopens the same toggles
A checkbox at sign-upA toggle in Account > Privacy, reachable in two taps from the home screen
WhatsApp "YES" replyReply "STOP", or tap an opt-out button in the message
Email opt-inOne-click unsubscribe in every email, no login needed
Via a Consent ManagerWithdraw on the Consent Manager's platform
In a store, on a tabletSame option in the app, website or by asking at any store

Rules of thumb

  • No extra authentication beyond what giving consent required, unless needed to identify the account.
  • No retention flows that demand a reason or present several pages of offers before honouring the request.
  • Confirmation on screen and, where useful, by message, showing exactly what was withdrawn.
  • Per-purpose withdrawal: a user leaving marketing should not have to close her account.

Testing

Run moderated usability tests where participants must withdraw a specific consent. Track success rate and time; compare with the time it took to give consent. Keep the results as evidence.

Back-end architecture for consent and withdrawal

A good interface on top of a weak back end still fails the law. The back end must enforce choices and prove them.

Consent record schema

consent_event
  event_id          uuid
  principal_id      internal ID (not raw email)
  purpose_key       e.g. "marketing.whatsapp"
  action            given | withdrawn | renewed
  notice_version    e.g. "notice-2027-05-v3"
  channel           web | ios | android | whatsapp | store
  ui_surface        e.g. "signup-step-2"
  timestamp_utc     ISO 8601
  actor             self | parent | guardian | consent_manager
  evidence_ref      pointer to request log or CM artefact

Enforcement

  • A consent service answers is_permitted(principal, purpose) at runtime; jobs and tags call it, rather than caching consent in many places.
  • Withdrawal publishes an event that downstream systems and processors consume: tag manager, CRM, email platform, ad audiences, data warehouse jobs.
  • Define and monitor a service level for propagation, consistent with ceasing processing within a reasonable time.

Retention

Keep consent events as evidence. Rule 8(3) requires personal data, traffic data and processing logs to be retained for at least one year from processing; consent evidence will often need to be kept longer, for as long as you may need to show that processing was lawful.

Consent for children and persons with disabilities

When the user is under 18, consent must come from a parent and be verifiable. Rule 10 requires technical and organisational measures to ensure verifiable consent of the parent before processing a child's personal data, with due diligence that the person identifying as the parent is an identifiable adult.

UX flow

  1. Ask the user's age or date of birth neutrally, without hinting at the "right" answer.
  2. If under 18, route to a parent flow: the child declares the parent, or the parent creates the account.
  3. Verify the parent using reliable identity and age details already held (Rule 10(1)(a)), or details voluntarily provided, including a virtual token from an authorised entity such as a Digital Locker service provider (Rule 10(1)(b)).
  4. Record actor = parent and the verification method on the consent event.
  5. Give the parent the same symmetric withdrawal controls.

Guardians of persons with disability

Rule 11 requires due diligence that a lawful guardian is appointed by a court, a designated authority under section 15 of the RPwD Act, 2016, or a local level committee under section 13 of the National Trust Act, 1999. Capture the appointment evidence in the consent record.

More detail: age verification and DigiLocker tokens.

Rule 4, in force since 13 November 2026, lets companies registered with the Data Protection Board act as Consent Managers: platforms through which a Data Principal can give, manage, review and withdraw consent across onboarded Data Fiduciaries. No Consent Manager registration should be assumed until the Board publishes it.

What changes for your UX

  • If you onboard onto a Consent Manager, users can grant and withdraw consent there. Your systems must accept those signals and treat a withdrawal on the Consent Manager's platform exactly like one in your own app.
  • The Consent Manager must keep records of consents given, denied and withdrawn, and of notices, for at least seven years, and must not be able to read the personal data shared through it.
  • Your own interface must still offer withdrawal; the Consent Manager is an additional channel, not a replacement.

Engineering

Model the Consent Manager as another channel and actor in the consent event schema, with an artefact reference. Subscribe to its withdrawal notifications and test end-to-end propagation.

See Consent Managers explained.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Remove pre-ticked boxes and implied consent

    Require a clear affirmative action for every optional purpose.

    Section 6

  2. Split consent by purpose

    Offer separate choices for marketing, personalisation, analytics and sharing.

    Section 6

  3. Give accept and reject equal weight

    Use the same size, colour and position for both options.

    Section 6

  4. Provide a persistent withdrawal control

    Place a privacy choices link or setting reachable in as few steps as consent.

    Rule 3(c)(i)

  5. Measure withdrawal ease in testing

    Compare steps and completion time for giving and withdrawing consent.

    Rule 3(c)(i)

  6. Propagate withdrawal to processors

    Push withdrawal events to vendors and downstream jobs and monitor propagation.

    Section 6

  7. Log versioned consent events

    Store purpose, action, notice version, channel, actor and timestamp.

    Section 6

  8. Route under-18 users to verifiable parental consent

    Verify the parent is an identifiable adult before processing.

    Rule 10

  9. Accept Consent Manager signals

    Treat consents and withdrawals via a registered Consent Manager as authoritative.

    Rule 4

Answers

Frequently asked questions

What does 'withdrawal as easy as giving consent' mean in practice?

Rule 3(c)(i) requires the ease of withdrawal to be comparable to the ease of giving consent. If consent took one tap on a banner, withdrawal should be a comparably simple action from a persistent control, not an email or a multi-page cancellation flow. Measure the steps and keep them symmetric.

Are pre-ticked checkboxes allowed under DPDP?

No. Section 6 requires consent to be signified by a clear affirmative action. A pre-ticked box records the designer's choice, not the user's. Use unticked boxes or toggles defaulting to off, and do not treat scrolling or continued use as consent.

Can I make consent a condition of using my app?

Only for data genuinely necessary to provide the service, and then you may not need consent at all if section 7(a) applies. Consent for unrelated purposes, such as marketing or selling data, must be free and unconditional, so blocking the core service unless the user agrees to them is defective.

How quickly must I stop processing after withdrawal?

Section 6 requires the fiduciary to cease processing, and cause its processors to cease, within a reasonable time. The Act does not fix a number of hours. Set an internal service level, propagate withdrawal events automatically, and monitor that tags, jobs and vendors actually stop.

Do I need to keep a record of consent?

Practically, yes. If a Data Principal or the Board questions whether consent was given, the fiduciary must be able to show it. Record the purpose, action, notice version, channel, actor and timestamp for every consent and withdrawal, and keep the records for as long as you may need to prove lawful processing.

Does a Consent Manager replace my consent screens?

No. A registered Consent Manager is an additional, interoperable channel through which users can give, manage, review and withdraw consent. You must still give notice and offer withdrawal in your own product, and you must honour withdrawals made through the Consent Manager.

Legal references and sources

  • Digital Personal Data Protection Act, 2023 — Section 6 (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 3(c)(i) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 4 and First Schedule (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 10 (official text)

This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.

About the author

Suhas Bhairav

Suhas Bhairav

Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.