DPDP consent management: what a valid consent record must contain

Under the DPDP Act, consent must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, and as easy to withdraw as it was to give. If consent is ever questioned, the business must prove that it gave a proper notice and that consent was given (Section 6(10)). So consent management is really record-keeping: what the person saw, what they agreed to, when, and whether they later withdrew.

Do you need consent at all?

Not always. Section 4 allows processing personal data on one of two grounds: the person's consent, or one of the "certain legitimate uses" listed in Section 7. Check the second list before you add a consent checkbox, because consent comes with a right to withdraw it at any time.

The legitimate uses that matter most to a small business are:

Anything outside these, such as marketing emails, analytics that identify individuals, sharing data with partners, or reusing data for a new purpose, needs consent.

What makes consent valid?

Section 6(1) sets five qualities: consent must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action. It must also be limited to the personal data necessary for the purpose. In the Act's example, a telemedicine app asks for consent to provide its service and to read the user's phone contacts. The user agrees to both, but because contacts aren't necessary for telemedicine, the consent is valid only for the service.

In practice that means:

What must the notice say?

Every request for consent must come with, or be preceded by, a notice (Section 5(1)). Rule 3 of the DPDP Rules, 2025 says the notice must:

  1. be understandable on its own, not buried in your terms and conditions or dependent on other documents;
  2. give, in clear and plain language, an itemised description of the personal data, the specified purpose of processing it, and a specific description of the goods or services it enables;
  3. give the link (and any other means) through which the person can withdraw consent as easily as they gave it, exercise their rights under the Act, and complain to the Board.

People must also be able to read the notice and the consent request in English or any of the 22 languages in the Eighth Schedule to the Constitution (Sections 5(3) and 6(3)). The request must name a contact: your Data Protection Officer where you have one, or another person authorised to answer questions.

For customers who consented before the Act took effect, you must send them this notice as soon as reasonably practicable. You may keep processing their data until they withdraw (Section 5(2)).

What should a consent record contain?

The Act doesn't prescribe a record format. It does put the burden of proof on you: if consent is questioned in a proceeding, you must prove that the notice was given and that consent was given in line with the Act and Rules (Section 6(10)). A record that answers that needs, at minimum:

FieldWhy you need it
Who: a customer ID or an opaque identifierLinks the record to the person without copying more personal data than needed
Which notice, and which version and languageProves what the person was actually shown. Keep every past version unchanged, ideally with a hash of its text
Each purpose agreed to, separatelyConsent is per purpose; "marketing: yes, analytics: no" must be recorded as two decisions
The action taken and whereThe checkbox, button or form, and the website or app it was on, showing a clear affirmative action
Date and timeWhen consent started, so processing before a withdrawal stays lawful (Section 6(5))
Withdrawal: date, time and channelWhen processing for that purpose had to stop
For a child: how the parent's consent was verifiedSection 9(1) requires verifiable consent of the parent; a self-declared tick is not enough

Keep the records append-only: a withdrawal is a new entry, not an edit. Store the minimum of identifying data in them. An IP address with the last part removed is usually enough to show where a request came from.

How must withdrawal work?

Withdrawing must be as easy as consenting was (Section 6(4)). If someone consented with one tick on your website, withdrawal can't require a signed letter. A link in every email, plus a setting in the account or on the same web page, is a reasonable minimum.

After a withdrawal, you must stop processing within a reasonable time and make your vendors (Data Processors) stop too, unless a law requires or allows you to continue (Section 6(6)). You must also erase the data, and have your processors erase it, unless a law requires you to keep it (Section 8(7)). Processing done before the withdrawal stays lawful, and the person bears the consequences of withdrawing (Section 6(5)). In the Act's example, a shop may stop taking new orders from someone who withdraws, but must still deliver what they already paid for.

What changes for children's data?

A child under the Act is anyone under 18. Before processing a child's personal data, you need the verifiable consent of a parent or lawful guardian (Section 9(1)), verified as Rule 10 of the DPDP Rules sets out. You may not track or behaviourally monitor children, or target advertising at them (Section 9(3)). Breaching the children's-data obligations carries a penalty of up to ₹200 crore, against up to ₹50 crore for most other breaches of the Act, including notice and consent failures.

Do you need a Consent Manager?

Usually not. A Consent Manager is a company registered with the Data Protection Board that lets people give, review and withdraw consent across many businesses from one place (Sections 6(7)–6(9)). The Rules on registering Consent Managers apply from November 2026. Your business doesn't have to become one. It does need to be ready to receive consents and withdrawals that arrive through one, and to record them like any other.

Don't confuse this with a consent management platform: the software your own business uses to show notices, collect choices and keep the records described above. You can build that yourself or buy it.

What should a small business do first?

  1. List every form, checkout and sign-up where you collect personal data, and the purpose of each field.
  2. Decide the ground for each purpose: a legitimate use under Section 7, or consent.
  3. Rewrite the notice to meet Rule 3: standalone, itemised data, specific purposes, and links to withdraw, exercise rights and complain to the Board. Offer it in the languages your customers use.
  4. Split bundled checkboxes into one unticked box per optional purpose.
  5. Start recording consent with the fields in the table above, and keep every notice version.
  6. Build withdrawal that is as easy as consenting, and make sure it reaches your email tool, CRM and other vendors.
  7. Send the new notice to existing customers (Section 5(2)).

The notice and consent obligations apply in full from 13 May 2027. CyberLetics' consent ledger does steps 3 to 6 for you. It publishes versioned notices with the Rule 3 fields and translations, records each choice per purpose with its notice version, logs withdrawals, verifies guardian consent for children, and issues each person a checksummed consent receipt. The free website scan is a quick first check of what your site exposes today.

Sources

This page summarises the primary sources below. It is guidance, not legal advice; check the current text before you rely on a specific obligation, date or figure.

Is your website leaking personal data?

Run the free CyberLetics scan: eight public checks, a score out of 100 and plain-language fixes. No signup.

security Scan my site free