Consent and notice under the DPDP Act: what Rule 3 requires and when consent is valid.
The notice is where most compliance programmes start and where many go wrong. This guide covers what it must say, how consent has to be taken and withdrawn, and when you do not need consent at all.
By Advocate Joginder Poswal · Updated November 2026
In short. Before you ask for consent, you must show a notice that a user can understand on its own. It lists each item of personal data, the exact purpose and the service it enables, and gives a link to withdraw consent, exercise rights and complain to the Board. Consent must be a clear affirmative act, limited to the data you need, and as easy to withdraw as it was to give. If you rely on consent and are challenged, you carry the burden of proving it. Rule 3 applies from 13 May 2027.
Consent or legitimate use: decide first
Section 4 allows personal data to be processed on one of two grounds: consent, or a legitimate use under Section 7. Working out which ground covers each activity is the first step, because the notice and consent machinery applies only to the first.
Section 7 lists nine legitimate uses. The ones a private business meets most often are:
- Section 7(a): data a person voluntarily gives for a specified purpose, where they have not said they object to its use. A customer who shares a delivery address to receive an order is the typical case.
- Section 7(e): compliance with a judgment, decree or order.
- Section 7(f) to (h): medical emergencies, health services during an epidemic, and safety during a disaster or breakdown of public order.
- Section 7(i): employment purposes, or protecting the employer from loss or liability, such as preventing corporate espionage or keeping trade secrets confidential.
The rest concern State functions, subsidies and legal disclosures to the State. Anything not covered by Section 7 needs consent. Marketing, profiling, product analytics beyond what the service needs, and sharing with partners for their own use almost always fall on the consent side.
What the notice must contain
Section 5(1) requires every request for consent to be accompanied or preceded by a notice. Rule 3 then sets the standard. The notice must:
- Stand on its own. Rule 3(a) says it must be understandable independently of any other information you provide. A one-line banner pointing to a forty-page policy does not meet this.
- Itemise the data. Rule 3(b)(i) asks for an itemised description of the personal data. "Name, mobile number, delivery address, order history" is itemised. "Information you provide to us" is not.
- State the specific purpose and describe the goods or services to be provided or the uses to be enabled by the processing, under Rule 3(b)(ii).
- Give a link to your website or app, and describe any other means, by which the user can withdraw consent, exercise their rights under the Act, and complain to the Data Protection Board, under Rule 3(c).
- Be available in the user's language. Section 5(3) gives the user the option to read it in English or in any of the languages in the Eighth Schedule to the Constitution.
Rule 3(b) also requires the notice to be in clear and plain language and to give a fair account of the processing. That is a test of substance. A notice that is technically complete but written so that nobody can follow it invites the argument that consent was never informed.
When consent is valid
Section 6(1) requires consent to be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, for the specified purpose, and limited to the personal data necessary for that purpose. Each word does work:
- Clear affirmative action rules out pre-ticked boxes and consent assumed from silence or from continuing to browse.
- Specific rules out one consent covering every purpose the business might have later.
- Unconditional makes it hard to justify refusing a service because the user declined processing the service does not need.
- Limited to necessary data means the consent cannot be used to collect more than the stated purpose requires.
The Act's own illustration makes the last point concrete. A telemedicine app asks a user to consent to processing for its medical service and to access her phone contact list, and she agrees to both. Because the contact list is not needed for telemedicine, the Act treats her consent as limited to the medical service. Ticking yes did not make the contact list fair game.
Section 6(2) adds that any part of a consent which infringes the Act or any other law is invalid to that extent. A clause in which the user waives the right to complain to the Board, for example, has no effect.
Section 6(3) requires the consent request itself to be in clear and plain language, offered in English or an Eighth Schedule language, and to give the contact details of your Data Protection Officer or another person authorised to respond.
Withdrawal
Under Section 6(4) a user can withdraw consent at any time, and withdrawing must be as easy as giving consent was. Rule 3(c)(i) repeats the point: the ease of withdrawal must be comparable to the ease of giving consent. If consent took one tap in the app, withdrawal cannot require an email to a support address and a wait.
Withdrawal does not undo the past. Section 6(5) keeps processing done before withdrawal lawful and puts the consequences of withdrawing on the user. If a feature cannot work without the data, the user loses that feature.
After withdrawal, Section 6(6) requires you, within a reasonable time, to stop processing and to make your Data Processors stop as well, unless a law requires or authorises continued processing. Section 8(7) separately requires erasure once consent is withdrawn, subject to the retention rules explained in the guide on data principal rights.
Consent Managers
Sections 6(7) to 6(9) allow a user to give, manage, review and withdraw consent through a Consent Manager, a platform registered with the Data Protection Board that acts for the user. Rule 4 and the First Schedule govern registration. A Consent Manager must be a company incorporated in India with a net worth of at least two crore rupees, run an interoperable platform, act in a fiduciary capacity towards users, and keep records of consents for at least seven years.
Rule 4 came into force one year after the Rules were published, on 13 November 2026, so registration is already open. Using a Consent Manager is optional for a business. Whether integrating with one makes sense depends mostly on scale and on whether your users are likely to expect it.
Users who signed up before the Act
Section 5(2) deals with consent obtained before the Act commenced. You must give those users a notice as soon as it is reasonably practicable, and you may continue processing until they withdraw. In practice this means a notice campaign to your existing base, by email or in-app, ahead of 13 May 2027. It is a good moment to stop processing anything you could not justify in a fresh notice.
Proving consent
Section 6(10) puts the burden on the Data Fiduciary. If there is a dispute, you must prove that notice was given and consent was obtained in line with the Act. That turns consent into a record-keeping exercise. For each user you should be able to show which version of the notice they saw, in which language, what they agreed to, when, and through which screen. Keep every version of the notice text on file. A database flag that says "consented" proves very little on its own.
Common mistakes
- Treating the existing privacy policy as the notice.
- Bundling consent for marketing or data sharing with acceptance of the terms of service.
- Pre-ticked boxes, or "by continuing you agree" banners.
- A withdrawal route that is harder than the sign-up route.
- Asking for consent for processing that is really a legitimate use, then having nothing to fall back on when the user withdraws.
- Offering the notice only in English when the product serves users in other languages.
- Keeping no record of which notice version each user saw.
Frequently asked questions
Not usually. Rule 3(a) requires the notice to be understandable on its own, with an itemised list of data, the specific purpose and a link for withdrawal, rights and complaints. A long general policy linked from a footer rarely meets that test.
Section 6(1) requires a clear affirmative action. A box ticked before the user does anything is not the user's action, so it is unlikely to qualify.
English or any language in the Eighth Schedule to the Constitution, at the user's option, under Sections 5(3) and 6(3).
Yes, for the legitimate uses in Section 7, such as data voluntarily given for a specified purpose, employment purposes, medical emergencies and compliance with court orders.
Section 5(2) requires a notice to those users as soon as reasonably practicable. Processing may continue until they withdraw.
Related reading
- DPDP Data Principal Rights: handling access, correction, erasure and grievance requests.
- Children's Data Under the DPDP Act: verifiable parental consent for users under 18.
- DPDP Act Compliance for Indian Startups: the full set of obligations and the timeline to 13 May 2027.
- DPDP Data Breach Notification: who has to be told after a breach, and by when.
- DPDP Compliance: all guides on the Act in one place.
Enrolment: Bar Council of Punjab & Haryana | No.: PH/9616/2023
This page is informational and does not constitute legal advice. References are to the Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E), 13 November 2025). How these apply depends on the data and operations of each organisation.
