Last reviewed: 7 November 2026.
What counts as valid consent under the DPDP Act
Section 6 of the Act says consent must be free, specific, informed, unconditional and unambiguous, and given through a clear affirmative action. In plain terms, the person must actively say yes, knowing what they are agreeing to, and the yes must cover only the stated purpose and only the data needed for it.
A request for consent must come with a notice (Section 5). The notice should tell the person which personal data you want, why, how they can withdraw consent or use their rights, and how to complain to the Data Protection Board. The person must also be able to read the notice in English or in any language listed in the Eighth Schedule to the Constitution.
Ways to collect consent
The Act does not define "types" of consent. In practice, these are the common ways, and what to watch for with each.
| Method | Works when | Watch out for |
|---|---|---|
| Website checkbox | The box is unticked, the purpose is stated beside it, and the person ticks it themselves | Pre-ticked boxes, or one box covering several unrelated purposes |
| App toggle or button | Each purpose has its own switch, off by default | "Accept all" with no way to choose |
| Phone call or IVR | The caller states the purpose and the person confirms with an affirmative action, such as pressing a key | Keeping a record of the call or key press, and offering a way to withdraw |
| Signed paper form | The notice is printed on or with the form | Storing the form so you can prove consent later |
| Through a Consent Manager | The person manages consent for many companies in one place | You remain responsible for your own compliance |
What does not count as valid consent
- Silence, inactivity or a pre-ticked box.
- Consent bundled with terms the person cannot refuse, or made a condition for something unrelated to the data you ask for.
- An "Accept all" button with no meaningful choice over purposes.
- A vague purpose such as "to improve our services" with nothing more.
If a person refuses consent for data that is genuinely needed for the service, you may decline that service. You cannot refuse a service because the person declined an unrelated use of their data. More questions like these are answered on the Q&A page.
When you do not need consent
Section 7 lists "legitimate uses" where you may process personal data without asking for consent again. The main ones are:
- Data the person voluntarily gave you for a specified purpose, where they have not said they object to its use for that purpose.
- Government benefits, licences and similar services.
- Meeting a legal obligation or a court order.
- Medical emergencies and public health, and disasters.
- Purposes related to employment, including safeguarding the employer from loss or liability.
Do not treat this list as a general escape hatch. Each use is narrow. Using customer data for marketing, for example, is not a legitimate use that avoids consent. See the marketing checklist.
How to revoke (withdraw) consent
You have the right to withdraw consent at any time. The Act says withdrawing must be as easy as giving consent was. The consequences of withdrawing are your own, for example you may lose a service that depends on that data, but withdrawing does not make earlier processing unlawful.
- Find the contactLook in the company's privacy notice for a withdrawal link, account setting, or the contact person's email.
- Say clearly what you are withdrawingName the purpose, for example "marketing emails" or "use of my data for profiling".
- Keep proofSave the date and any reference number. A message you can copy is below.
- Expect action within a reasonable timeOnce you withdraw, the company must stop processing your data for that purpose, and make its processors stop too, unless the law requires it to keep the data.
- Escalate if ignoredUse the company's grievance process, then the Data Protection Board once that route opens. See how to report data misuse.
Consent records and governance (for businesses)
The Act puts the burden on you to show that consent was properly given. A simple governance routine covers most of what you need:
- Record every consentWho agreed, when, to what purpose, through which method, and which version of the notice they saw.
- Record every withdrawalWith the date, and the date you stopped processing.
- Keep purposes separateOne consent per purpose, not one for everything.
- Pass changes to your vendorsMake sure processors act on withdrawals.
- Review regularlyCheck old data and old consent records at least once a year, and clean up what you no longer need.
Whether a spreadsheet, a database or a dedicated consent platform is right depends on your size. What matters is that you can demonstrate and manage consent. The cookie banner generator and the privacy notice generator cover the website side, and the free DPDP Audit shows where you stand.
Consent Managers
A Consent Manager is a company registered with the Data Protection Board that lets a person give, review and withdraw consent across many organisations from one place. Using one is optional. Using a Consent Manager does not remove your own duties. Registration opened on 13 November 2026 through the Board's portal at dpbi.gov.in. See the latest update. See the glossary.
Children and consent
For anyone under 18, you need verifiable consent from a parent or lawful guardian, and you may not track or target children with ads. See Children's Data.