DPDP Act guide · 3 controls
Notice & Consent Under the DPDP Act
Much of the processing under the DPDP Act rests on consent, and consent only counts if a clear notice comes first. People must also be able to withdraw consent as easily as they gave it.
Privacy notice Sec 5, Rule 3
You have a clear privacy notice that tells people what data you collect, why, what rights they have, how to raise a grievance, and how to complain to the Data Protection Board.
Why it matters
Consent is only valid if a proper notice comes first. A weak notice undermines every consent you hold.
How to close the gap
Write a standalone privacy notice that lists the data you collect, why, people's rights, the grievance contact and how to complain to the Board. Show it before you collect data.
Evidence that shows it's in place
- Current privacy notice
- Screens showing where the notice appears at collection
- Language versions offered
Consent capture and records Sec 6, Sec 7
People give consent by actively agreeing to something specific they understand, never by default, and you keep a record of it.
Why it matters
If you can't show valid consent, the processing that relies on it may not be lawful.
How to close the gap
Replace pre-ticked boxes with clear opt-in for each purpose, and store a record of who agreed to what and when.
Evidence that shows it's in place
- Consent screens or forms
- Consent log schema or sample records
- Legitimate-use basis register for non-consent processing
Consent withdrawal Sec 6(4), 6(6)
Withdrawing consent is as easy as giving it, and once someone withdraws, you and your vendors stop using their data within a reasonable time.
Why it matters
People must be able to withdraw as easily as they agreed. Complaints here go straight to the Board.
How to close the gap
Add a one-click way to withdraw consent, and a process that tells your systems and vendors to stop using that person's data.
Evidence that shows it's in place
- Withdrawal mechanism screenshots
- Procedure to propagate withdrawal to processors
- Consent manager integration (if used)
An Example
An online store shows one pre-ticked box at checkout: "I agree to the terms, privacy policy and marketing emails." Under the Act that is not valid consent for marketing, because it is bundled and not a clear affirmative action. Splitting it into an unticked marketing box, with a short notice beside it and an unsubscribe link in every email, fixes it.
Common Mistakes
- Pre-ticked boxes, or one checkbox that covers several unrelated purposes.
- A privacy notice hidden in the website footer instead of shown when data is collected.
- Easy sign-up but hard withdrawal, such as needing to email support to unsubscribe.
- Recording that someone consented, but not what they were told or when.
- Asking for consent where another basis applies, then having nothing to fall back on when consent is withdrawn.
Questions People Ask
What makes consent valid under the DPDP Act?
Section 6 says consent must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, and limited to the data needed for the stated purpose.
Can we process personal data without consent?
Yes, for the legitimate uses listed in Section 7, such as data a person gave voluntarily for a specified purpose, certain employment purposes, and legal obligations. Most marketing and analytics still needs consent.
Which languages must the notice be in?
People must be able to read the notice in English or in any language listed in the Eighth Schedule to the Constitution (Section 5(3)).
What is a consent manager?
A person registered with the Data Protection Board that lets people give, manage, review and withdraw consent through one accessible platform (Section 6(7) and Rule 4).
Last checked: , against the DPDP Act 2023 and the DPDP Rules 2025. This is general guidance, not legal advice.