Complied AIComplied AI

What makes consent and notice valid under the DPDP Act?

Section 5 of the DPDP Act sets what a notice must say, section 6 sets the test for valid consent, and section 7 lists the legitimate uses that need no consent. Rule 3 notice contents, withdrawal and Consent Managers explained.

In this guide
Answer firstVerified 19 November 2026

Under the Digital Personal Data Protection Act, 2023, consent is valid only if it is free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, under section 6(1). A section 5 notice must come before or with the request, and rule 3 of the DPDP Rules, 2025 sets its contents. Withdrawal must be as easy as giving consent. These provisions apply from 13 May 2027. Consent Manager registration began on 13 November 2026.

DPDP consent rules apply from 13 May 2027. Notification G.S.R. 843(E) of 13 November 2025 brings sections 5, 6(1) to 6(8), 6(10) and 7 of the Digital Personal Data Protection Act, 2023 into force eighteen months after publication. Rule 3 of the DPDP Rules, 2025, which sets notice contents, is in the same eighteen-month group under rule 1(4).

One part is already live. Section 6(9), which requires Consent Managers to register with the Data Protection Board, and rule 4, which sets how they register, came into force one year after publication, on 13 November 2026.

ProvisionIn force fromAuthority
Consent Manager registration, section 6(9)13 November 2026G.S.R. 843(E)
Consent Manager rules, rule 413 November 2026Rule 1(3)
Notice, consent, legitimate uses, sections 5 to 713 May 2027G.S.R. 843(E)
Notice contents, rule 313 May 2027Rule 1(4)

What must a DPDP notice contain?

A section 5 notice must accompany or precede every request for consent and tell the Data Principal what data is collected and why, how to withdraw consent and use her grievance rights, and how to complain to the Board. Section 5(3) adds that she must be able to read the notice in English or any language in the Eighth Schedule to the Constitution.

Rule 3 sets the form. The notice must:

  1. be presented and understandable on its own, apart from any other information the Data Fiduciary gives (rule 3(a));
  2. give, in clear and plain language, an itemised description of the personal data and the specified purpose of processing, with a description of the goods, services or uses that processing enables (rule 3(b));
  3. give the link to the website or app, and any other means, through which the Data Principal can withdraw consent, exercise her rights and complain to the Board (rule 3(c)).

For users who consented before the Act came into force, section 5(2) requires the same notice as soon as reasonably practicable. Processing can continue until the user withdraws consent.

Consent is valid under section 6(1) only when it is free, specific, informed, unconditional and unambiguous, with a clear affirmative action, and limited to the personal data necessary for the specified purpose. Any part of a consent that breaches the Act, the rules or another law is invalid to that extent under section 6(2).

A worked example. A food delivery app asks for a user's name, phone number, delivery address and phone contacts at signup. The first three are needed to deliver orders. The contacts are not. If the app makes access to contacts a condition of using the service, that part of the consent fails the "necessary" test in section 6(1). The app should ask for the contacts separately, say what they are for, and still deliver food to a user who says no.

Section 6(10) puts the burden on the Data Fiduciary to prove that a notice was given and consent obtained. Logs that show which notice version a user saw and when they agreed are the practical answer to that burden.

A Data Principal may withdraw consent at any time under section 6(4), and section 6(5) requires the ease of withdrawal to be comparable to the ease with which consent was given. If consent took one tap in an app, withdrawal cannot need an email to a support address and a week's wait. Rule 3(c)(i) repeats the same standard for the notice.

Withdrawal does not undo processing done before it, under section 6(4). The Data Principal bears the consequences, such as losing a feature that needed the data. Under section 6(6), the Data Fiduciary and its Data Processors must stop processing within a reasonable time unless a law allows processing without consent.

A Consent Manager is a person registered with the Data Protection Board who lets a Data Principal give, manage, review and withdraw consent through an accessible, transparent and interoperable platform, under section 6(7) to 6(9). It acts on behalf of the Data Principal and is accountable to her.

Rule 4 and the First Schedule to the DPDP Rules, 2025 set the registration conditions. Under Part A, item 4, the applicant must be a company incorporated in India with a net worth of at least ₹2 crore. Using a Consent Manager is optional for a Data Principal. A Data Fiduciary may still collect consent directly.

What are DPDP section 7 legitimate uses?

Section 7 lists the uses for which a Data Fiduciary may process personal data without consent. Because no consent is requested, the section 5 notice that goes with a consent request does not arise.

  • Data the person voluntarily gave for a specified purpose, where she has not said she does not consent (section 7(a)).
  • Subsidies, benefits, services, certificates, licences or permits by the State (section 7(b)).
  • State functions under law, or in the interest of sovereignty, integrity or security of India (section 7(c)).
  • A legal obligation to disclose information to the State (section 7(d)), or compliance with a judgment or order (section 7(e)).
  • A medical emergency, an epidemic or other threat to public health, or a disaster or breakdown of public order (sections 7(f) to 7(h)).
  • Employment purposes, or safeguarding the employer from loss or liability (section 7(i)).

Section 7(a) is the one most businesses rely on. The illustration in the Act is a buyer who gives her phone number to a pharmacy to get a payment receipt. The pharmacy can use the number for the receipt without separate consent. Sending her promotional messages is a different purpose and needs consent. Our guide to Data Principal rights covers what she can demand afterwards, and MeitY notifications on the Act appear in the MeitY updates feed.

Practical checks

Common questions

Our signup form has a pre-ticked box saying the user agrees to marketing. Is that valid consent?

No. Section 6(1) of the DPDP Act requires consent signified by a clear affirmative action. A box the user did not tick is not an action by the user. The marketing consent should be a separate, unticked option.

Can we refuse service to a user who will not consent to us sharing data with advertisers?

Not if that data is unnecessary for the service. Section 6(1) limits consent to personal data necessary for the specified purpose, and the illustration to section 6(1) treats consent as limited to what the service needs. Ask for advertising consent separately.

Can our privacy notice just link to the full privacy policy?

No. Rule 3(a) of the DPDP Rules, 2025 requires the notice to be understandable on its own, independent of any other information. It must itemise the personal data and state each purpose. A link to a longer policy can sit alongside it.

How fast must we stop processing after a user withdraws consent?

Within a reasonable time. Section 6(6) of the DPDP Act requires the Data Fiduciary, and its Data Processors, to cease processing within a reasonable time after withdrawal, unless the Act or another law permits processing without consent. The Act does not set a fixed number of days.

Do we need consent to process our employees' data?

Often no. Section 7(i) of the DPDP Act treats processing for the purposes of employment, or to safeguard the employer from loss or liability, as a legitimate use. Processing outside that purpose, such as a staff photo used in advertising, still needs consent.

Who has to prove that a user gave consent?

The Data Fiduciary. Section 6(10) of the DPDP Act puts the burden on the Data Fiduciary to prove that a notice was given and consent obtained, where that is in question in a proceeding. Keep timestamped records of each notice version and each consent.

What does a company need to become a Consent Manager?

Registration with the Data Protection Board under section 6(9), which rule 4 started on 13 November 2026. Part A of the First Schedule to the DPDP Rules, 2025 requires the applicant to be a company incorporated in India with a net worth of at least ₹2 crore.

Publication method

How this guide was prepared

This guide is published by the Complied AI research desk. Its source list and stated position were checked against the official records shown below on 19 November 2026.

Automation, including AI, may assist research, drafting and structure. It does not replace the official record or amount to an independent professional review. Read our editorial standards and corrections policy.

Verification path

Official sources used

Keep reading

Related guides

Search Complied AI

Laws and sections by number or title, due dates, pages, and updates.