What does consent under the DPDP Act mean?
Consent under the DPDP Act is a person's free, specific, informed, unconditional and unambiguous agreement, given by a clear affirmative action, to the processing of her personal data for a specified purpose (Section 6(1)). It covers only the data necessary for that purpose, can be withdrawn at any time, and the business must be able to prove it. Consent is one of only two grounds for processing personal data; the other is the list of legitimate uses in Section 7 (Section 4(1)).
Sections 5 and 6 apply from 13 May 2027, along with Rule 3 of the DPDP Rules 2025 on notices. The one exception is Section 6(9), on registering Consent Managers, which applies from 13 November 2026.
What are the five qualities of valid consent in Section 6(1)?
Section 6(1) lists five qualities, plus a clear affirmative action. A consent request should pass all of them:
| Quality | What it means in practice | A request that fails it |
|---|---|---|
| Free | The person chooses without pressure or a forced trade-off | "Agree to marketing or you cannot create an account" |
| Specific | Tied to a specified purpose, not "any purpose we choose" | "We may use your data to improve our business" |
| Informed | Given after a notice that meets Section 5 and Rule 3 | A checkbox with no notice before or with it |
| Unconditional | Not tied to giving up a right or accepting unrelated terms | Consent that also waives the right to complain to the Board |
| Unambiguous, with a clear affirmative action | The person does something that clearly means yes | A pre-ticked box, or silence treated as agreement |
Section 6(1) adds a data-minimisation test: consent is limited to the personal data necessary for the specified purpose. The Act's own illustration is a telemedicine app that asks for consent to its telemedicine service and to access the user's mobile phone contacts. Because the contacts are not necessary to provide telemedicine, her consent covers only the telemedicine service.
What makes part of a consent invalid under Section 6(2)?
Any part of a consent that infringes the DPDP Act, the Rules or any other law in force is invalid to that extent (Section 6(2)). The rest of the consent can still stand. In the Act's illustration, a person consents to an insurance company processing her data to issue a policy and, in the same consent, waives her right to complain to the Data Protection Board. The waiver is invalid; the consent to issue the policy is not.
The practical lesson: do not use a consent form to take away rights the Act gives, such as access, correction and erasure (Sections 11 and 12) or grievance redressal (Section 13). Those clauses will not hold.
How must a consent request be written?
Section 6(3) requires every request for consent to be in clear and plain language, to give the person the option to read it in English or any language in the Eighth Schedule to the Constitution, and to give the contact details of a Data Protection Officer (where applicable) or another person authorised to respond to her.
Section 5(1) adds that every request must come with, or after, a notice. Rule 3 of the DPDP Rules 2025 sets its content: it must be understandable independently of any other information, give an itemised description of the personal data and the specified purpose of each use, and give a link to withdraw consent, exercise rights and complain to the Board. For the full list, see what a DPDP privacy notice must say.
How does withdrawal of consent work under the DPDP Act?
A person may withdraw consent at any time, and withdrawing must be as easy as giving it was (Section 6(4)). Rule 3(c)(i) requires the notice to give the link or other means to do this. What happens next is set by three provisions:
| Question | Answer | Provision |
|---|---|---|
| Does past processing become unlawful? | No. Processing based on consent before withdrawal stays lawful | Section 6(5) |
| Who bears the consequences? | The person who withdraws, for example losing a service that needs the data | Section 6(5) |
| When must processing stop? | Within a reasonable time, for you and every Data Processor working for you | Section 6(6) |
| Are there exceptions? | Yes, where the Act or another law requires or authorises processing without consent | Section 6(6) |
| What happens to the data? | Erase it, and make your Data Processors erase it, unless a law requires you to keep it | Section 8(7) |
The Act gives two illustrations. An online shopper who withdraws consent after paying for an order can be stopped from placing new orders, but the seller must still process her data to deliver the goods she has paid for. And a company whose vendor emails its bills must stop, and make the vendor stop, emailing bills to a customer who withdraws consent to receive them that way.
Who must prove consent was given, and how?
The Data Fiduciary. Where consent is the basis of processing and it is questioned in a proceeding, the Data Fiduciary must prove that it gave the notice and obtained consent in line with the Act and Rules (Section 6(10)). The Act does not prescribe a format for that proof, so in practice keep, for every consent: who gave it, which purposes they agreed to, the version and language of the notice they saw, the time and channel, and any later withdrawal.
Section 5(2) also covers your existing database: for consent given before the Act commenced, you must send a notice as soon as reasonably practicable, and you may keep processing until the person withdraws. See record of processing activities for how to map which purposes rest on consent.
Where do Consent Managers fit in?
A Consent Manager is a company registered with the Data Protection Board that lets a person give, manage, review and withdraw consent through one interoperable platform (Sections 2(g) and 6(7) to 6(9)). It acts on the person's behalf and is accountable to her (Section 6(8)). Using one is the person's choice; the Act does not require every business to use one. Rule 4, on their registration, applies from 13 November 2026. See Consent Managers under the DPDP Act.
When is consent not needed, and when is a parent's consent needed?
Consent is not needed for a purpose that fits one of the nine legitimate uses in Section 7, such as data a person voluntarily gives you for a specified purpose (Section 7(a)) or employment purposes (Section 7(i)). See legitimate use under the DPDP Act.
For a child (anyone under 18), Section 9(1) requires verifiable consent of the parent or lawful guardian before processing her data, and Rule 10 requires appropriate technical and organisational measures to make sure of it. Section 9(3) bars tracking, behavioural monitoring and targeted advertising directed at children, subject to the exemptions in the Rules. See children's data under the DPDP Act.
Example: fixing a sign-up form
This is a made-up example. "FitThali" is a fictional Jaipur meal-subscription app with 40,000 customers. Its sign-up screen has one pre-ticked box: "I agree to the Terms, to receive offers on WhatsApp, and to share my details with partner gyms." It also asks to read the phone's contacts.
Mapping the form against Sections 6 and 7 gives this:
| Purpose | Old approach | Fixed approach | Why |
|---|---|---|---|
| Delivering meals the customer orders | Inside the bundled box | Section 7(a), no tick box | She gives her address to get the meals delivered |
| Offers on WhatsApp | Inside the bundled box, pre-ticked | Separate, unticked option | Needs consent: specific, free, clear affirmative action (Section 6(1)) |
| Sharing details with partner gyms | Inside the bundled box | Separate, unticked option | A different purpose and recipient needs its own consent |
| Reading phone contacts | Required to continue | Removed | Not necessary for meal delivery (Section 6(1) and the telemedicine illustration) |
| Clause waiving complaints to the Board | In the Terms | Deleted | Invalid under Section 6(2) |
FitThali puts a short Rule 3 notice above the two options, adds a "Manage consent" link to the app menu so withdrawing takes the same two taps as agreeing, logs each choice with the notice version, and lists which vendors must be told to stop when someone withdraws (its WhatsApp messaging provider, for one). It also plans a Section 5(2) notice to its 40,000 existing customers.
How do you get consent right, step by step?
- List every purpose for which you use personal data, and decide for each whether it rests on consent or a Section 7 legitimate use.
- For consent-based purposes, cut the data to what each purpose needs (Section 6(1)).
- Write a notice that meets Section 5 and Rule 3, in plain language, with the DPO or contact person's details (Section 6(3)).
- Ask separately for each purpose, with nothing pre-ticked and no service held back for an unrelated purpose.
- Remove any clause that waives a right under the Act (Section 6(2)).
- Build a withdrawal route as easy as the consent route, and a process to stop processing and tell your Data Processors (Sections 6(4) and 6(6)).
- Record every consent and withdrawal so you can prove it (Section 6(10)), and set the erasure point for each purpose (Section 8(7)).
- Check for children's data and plan verifiable parental consent (Section 9, Rule 10), and send Section 5(2) notices to existing users.
What are the common mistakes and myths about DPDP consent?
- Myth: "Accepting our terms is consent." Consent must be specific to a purpose and limited to necessary data; a blanket clause in long terms rarely meets Section 6(1).
- Mistake: pre-ticked or bundled boxes. They lack a clear affirmative action for each purpose.
- Myth: "Withdrawal means we must stop everything instantly." Section 6(6) says within a reasonable time, and only for processing that rests on that consent.
- Mistake: forgetting your vendors. Section 6(6) makes you cause your Data Processors to stop too.
- Myth: "Every use of data needs consent." Section 7 lists nine legitimate uses that do not.
- Mistake: no record. Without proof, Section 6(10) works against you. The Schedule sets no separate penalty for Section 6, so a breach falls under the residual row of up to ₹50 crore; children's duties under Section 9 go up to ₹200 crore. See DPDP penalties.
GRC-Flow's consent manager gives you a consent banner, consent by QR code or link, and a record of each choice with its notice version, and lists the vendors to tell when someone withdraws. To see where your website stands today, run the free DPDP website check. No tool can guarantee compliance; a person reviews every result.
This guide is general information about the DPDP Act and Rules, not legal advice.
Frequently asked questions
What is valid consent under the DPDP Act?
Section 6(1) says consent must be free, specific, informed, unconditional and unambiguous, with a clear affirmative action, and must signify agreement to processing for a specified purpose. It covers only the personal data necessary for that purpose. It must also follow a notice that meets Section 5 and Rule 3 of the DPDP Rules 2025.
Is a pre-ticked checkbox valid consent under the DPDP Act?
It is very unlikely to be. Section 6(1) requires a clear affirmative action by the person. A box that is already ticked records no action by her, so it does not show that she agreed.
How quickly must a business stop processing after consent is withdrawn?
Within a reasonable time, under Section 6(6). The Data Fiduciary must stop, and make its Data Processors stop, unless the Act or another law requires or authorises the processing without consent. Section 8(7) then requires erasure, unless a law requires the data to be kept.
Does withdrawing consent make past processing unlawful?
No. Section 6(5) says withdrawal does not affect the legality of processing done on the basis of consent before it was withdrawn. The consequences of withdrawing, such as losing access to a service that needs the data, are borne by the person.
Do you always need consent to process personal data under the DPDP Act?
No. Section 4(1) allows two grounds: consent, or one of the legitimate uses listed in Section 7, such as data a person voluntarily gives for a specified purpose (Section 7(a)) or employment purposes (Section 7(i)). If a purpose fits neither, you need consent.
Sources
- The Digital Personal Data Protection Act, 2023 (India Code)
- Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E), Gazette text)
- PIB: Digital Personal Data Protection Rules, 2025
This guide explains the law in general terms and is not legal advice. Check specific situations with a qualified lawyer.