DPDP consent

Consent only counts if the notice did its job first.

Under the Act, consent is one of two grounds for processing, and it is the one that needs the most proof. Each consent request comes with a notice that tells people what you want and why, in a language they can read, with a way out that is as easy as the way in.

Back to DPDP services

02 · Notice contents

What the notice must tell people

Section 5 sets the core; rule 3 adds the detail.

Stands on its own
Readable without opening your terms, policy or anything else.
Itemised data
A list of the personal data items, not a phrase like 'information you provide'.
Purposes and what they enable
Each purpose, with a specific description of the goods, services or uses it makes possible.
How to withdraw
A link to your website or app, any other means, and withdrawal as easy as consenting.
How to use rights
The route for access, correction, erasure, grievance and nomination.
How to complain to the Board
That she can complain to the Board, and how.

The notice must come with or before the request for consent. A notice shown after the tap cannot inform a choice already made.

03 · Language

Language and contact rules

English or any language in the Eighth Schedule to the Constitution.

  • Both the notice and the consent request must be available in English or in any language listed in the Eighth Schedule to the Constitution, at the person's option.
  • The option has to be real: a working language choice, not a promise to translate on request.
  • The consent request must give contact details for the Data Protection Officer, where there is one, or another person authorised to respond on rights.
  • Use clear and plain language throughout. Rule 3 asks for a fair account, not a legal summary.

Translation is a content job, not a plug-in

Machine translation of a legal notice can change its meaning. Have each language version reviewed, and keep every version under the same version control.

04 · Withdrawal

Withdrawal as easy as giving

Same effort, same place, and processors stop too.

  1. Put withdrawal where consent was given. One tap to agree and an emailed letter to withdraw is not comparable ease.
  2. Say what withdrawal will change. The consequences are hers to bear, and processing done before withdrawal stays lawful.
  3. Stop processing within a reasonable time and make your processors stop, unless the Act or another law requires or permits it to continue.
  4. Erase data held only on that consent, unless a law requires you to keep it.
  5. Log the withdrawal against the original consent record, so you can prove both.

The Act's own example: a shopper who withdraws consent can be stopped from placing new orders, but an order already paid for still has to be delivered.

05 · Older data

Data collected before the Act

Send a notice; keep processing until consent is withdrawn.

Where a person consented before the Act's notice provisions took effect, section 5(2) asks for a notice as soon as reasonably practicable. It covers the data and purposes, how to withdraw and use rights, and how to complain to the Board. Processing may continue until she withdraws. Email, an in-app message or another effective channel will do. Expect some people to withdraw once they are told they can, and make sure the systems behind the notice can act on it.

06 · Good and bad screens

A consent screen, done badly and done well

Illustrative screens for a telehealth app.

Weak

One box, everything in it

  • A single pre-ticked box: 'I agree to the Terms and Privacy Policy'
  • Purposes described as 'to improve our services and for our partners'
  • Contact-list access requested at sign-up with no link to consultations
  • Notice offered only as an English PDF link
  • Withdrawal by letter to a postal address

Strong

Separate, plain, reversible

  • Notice on the same screen, listing each data item, shown before any choice
  • Separate unticked choices: consultations (needed), SMS reminders (optional), research use (optional)
  • No contact-list request, because consultations do not need it
  • A language switcher covering English and the languages its users speak
  • A 'Manage consents' page in the app, one tap to withdraw each choice

The weak screen also fails the Act's own illustration: a telemedicine app's consent does not stretch to the phone's contact list.

07 · Mistakes

Common consent and notice mistakes

Each one weakens the proof section 6(10) asks you to hold.

  • Consent folded into the terms. Agreeing to terms of service is not a specific, informed choice about each purpose.
  • Consent where a legitimate use fits. Asking for consent you do not need creates a withdrawal you cannot honour.
  • A notice that is only a link. Rule 3 wants a notice that stands on its own, not a pointer to the privacy policy.
  • Withdrawal harder than sign-up. Buried settings and support tickets fail the comparable-ease test.
  • No consent log. Without per-person, per-purpose records, nothing can be proved.
  • Processors left running. Withdrawal must reach every vendor processing on that consent.
  • Asking for more than the purpose needs. Consent to unnecessary data does not hold for that data.

Sources: The Digital Personal Data Protection Act, 2023 (No. 22 of 2023), sections 4 to 7; the Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E)), rules 1 and 3.

Questions about consent and notice

Is our privacy policy the notice?

No. The notice must stand on its own at the moment you ask.

A privacy policy can sit behind it, but rule 3 wants a notice people can understand without reading anything else, listing the data, the purposes and the ways to withdraw, use rights and complain.

Can we refuse service if someone declines an optional consent?

Not for data the service does not need.

Consent must be unconditional and limited to necessary data. You can decline to provide a feature that genuinely needs the data, but not make an unrelated use a condition of the service.

Do we need consent for everything?

No. Some processing runs on a legitimate use.

Section 7 lists legitimate uses, such as data a person volunteers for a purpose, employment and legal obligations. The guide on processing without consent covers them and their limits.

When do the notice rules take effect?

Rule 3 applies eighteen months after the Rules were published.

Rule 3 comes into force eighteen months after the Rules were published in November 2025, so around May 2027. Notices, language versions and consent logs take time to build, so start with the data map now.

Fix consent once, at the point it is given.

A DPDP readiness assessment reviews your notices, consent screens, language options and withdrawal paths against the Act and rule 3. Counsel should confirm how the law applies to your contracts.