Skip to main content
DPDP-AID Readiness Checkby

DPDP consent requirements, and what a notice must say

Consent and notice are where most businesses touch the DPDP regime first, because they are visible on the product surface. They are also where legacy practice fails most often: a pre-ticked box, consent bundled into terms of service, or a notice that no one could act on.

Reviewed 16 September 2026Educational self-assessment content, not legal advice

Consent must be free, specific, informed, unconditional and unambiguous, and given by a clear affirmative action. It signifies agreement to processing for the specified purpose, and it is limited to the personal data necessary for that purpose.

The limits do real work. Consent bundled with unrelated terms is not specific. Access conditioned on consent that is not needed for the service is not free. Silence, inactivity or a pre-ticked box is not a clear affirmative action. Asking for more data than the purpose needs makes the surplus unlawful even if the person clicked yes.

  • Ask separately for each distinct purpose, and record which purpose each person agreed to and when.
  • Do not condition a service on consent that the service does not require.
  • Keep the request available in English and the languages the Act's schedule lists.
  • Withdrawal must be as easy as consent was to give, and reachable from the same place.
  • After withdrawal, stop processing and erase, unless a law requires the data to be kept.

What a notice must contain

The Rules require a notice to stand on its own, be understandable without reading anything else, and use clear and plain language. It must give an itemised description of the personal data collected and the specified purpose, described with the goods, services or uses it enables.

It must also tell the person how to withdraw consent, how to exercise their rights and how to complain to the Data Protection Board, in a way they can act on rather than merely read.

What we assess: Notice

  • A standalone, itemised notice covering data collected, purpose and related services
  • The notice explains how to withdraw, exercise rights and complain to the Board
  • People whose data was collected before the Act have been sent a notice
  • The notice is available in English and Eighth Schedule languages

More on notice

The Act creates the consent manager: a registered intermediary, accountable to the data principal, through which consent can be given, managed, reviewed and withdrawn. These provisions commence on 13 November 2026.

For most businesses the practical implication is interoperability, not immediate integration. Consent records need to be structured enough that they can be reconciled with an external record of the same consent later.

Where this usually goes wrong

The common pattern is a notice that is compliant in text and unusable in practice: a withdrawal link that goes to a support inbox no one owns, or a preferences page that changes marketing but not processing. Test the route, not the wording.

DPDP notice requirements, item by item

A notice is not a privacy policy. A privacy policy is a long document that covers everything you do; a notice is the short, specific thing a person sees at the moment they are asked to agree, and it has to stand on its own without the reader following a link to understand it.

The DPDP privacy notice requirements are short enough to check against your live product this week. Take your signup screen and ask whether each of these is present and usable.

  • An itemised description of the personal data you are collecting, not a category like "your details".
  • The specified purpose, described with the goods, services or uses that purpose enables.
  • How to withdraw consent, as a route the person can actually take.
  • How to exercise their rights, including who to contact and what identifiers to give.
  • How to complain to the Data Protection Board.
  • Availability in English and the other languages the Act's schedule lists.

Withdrawal must be as easy as giving consent was. The common failure is not the wording, it is the plumbing: a withdrawal link that reaches a support inbox nobody owns, or a preferences page that changes marketing but leaves the underlying processing running.

Once consent is withdrawn you must stop processing for that purpose and erase the personal data, including at your processors, unless a law requires you to keep it. Withdrawal does not undo processing that was lawful before it happened, and it does not oblige you to delete records you are legally required to retain, but it does oblige you to know which of those applies.

  • Test the route end to end, as a user, at least once a quarter.
  • Fan the withdrawal out to processors and get confirmation back.
  • Record what was stopped, what was erased and what was kept, with the reason for anything kept.

If you cannot show what someone agreed to, you cannot show that consent was valid. Records are what turn a claim into evidence, and they are the part of DPDP consent management most often left until the audit. Each consent record should tie a person to a moment, a notice version and a set of purposes.

Frequently asked questions

What makes consent valid under the DPDP Act?

Consent must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, limited to the personal data necessary for the specified purpose, and as easy to withdraw as it was to give.

Is a pre-ticked consent box allowed under the DPDP Act?

No. Consent needs a clear affirmative action, so silence, inactivity or a pre-ticked box does not count.

What must a DPDP notice contain?

An itemised description of the personal data collected, the specified purpose with the goods, services or uses it enables, and how to withdraw consent, exercise rights and complain to the Data Protection Board. It must be understandable on its own in clear and plain language.

What happens when a person withdraws consent?

Processing for that purpose must stop and the personal data must be erased, including by processors, unless retention is required by law. Withdrawal does not undo processing that was lawful before it.

What are the DPDP consent requirements in one sentence?

Consent must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, limited to the personal data the stated purpose needs, and as easy to withdraw as it was to give.

Do I need a consent manager to meet the DPDP notice requirements?

No. A consent manager is a registered intermediary, and registration is for entities that want to operate that infrastructure. Most businesses need consent management inside their own product, not registration.

Is my existing privacy policy enough?

Usually not on its own. A privacy policy explains everything you do; the Rules expect a standalone notice, understandable without reading anything else, shown when consent is taken. Most sites need both.

See your readiness in five minutes.

Start with the quick check. You can move to the full assessment at any time without losing your answers.

The DPDP-AID Readiness Check is a free self-assessment tool for educational and self-learning purposes. It is not legal advice. Disclaimer

A free self-assessment tool for educational use. Not legal advice.