DPDP Act 2023Updated 22 November 202611 min read

DPDP Consent Requirements: Free, Specific, Informed and Unambiguous

What valid consent means under section 6 of the DPDP Act and Rule 3: the five qualities, clear affirmative action, necessity, withdrawal parity and proof of consent.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Provision
DPDP Act, section 6; notice under section 5 and Rule 3
Five qualities
Free, specific, informed, unconditional, unambiguous
Form
Clear affirmative action
Withdrawal
Ease comparable to giving consent (s.6(4); Rule 3(c)(i))
Burden of proof
On the Data Fiduciary
Languages
English or any language in the Eighth Schedule to the Constitution
Applies from
13 May 2027

Quick answer

Under section 6 of the DPDP Act, consent must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, and limited to the personal data necessary for the specified purpose. It must follow a Rule 3 notice. It must be as easy to withdraw as to give. The Data Fiduciary bears the burden of proving it. These requirements apply from 13 May 2027.

  • Valid consent has five qualities, free, specific, informed, unconditional and unambiguous, and needs a clear affirmative action such as a tap or a tick.
  • Consent covers only the data necessary for the specified purpose; extra data requests bundled into it do not count.
  • Withdrawal must be as easy as giving consent, and processing must stop within a reasonable time afterwards.
  • Any part of a consent that infringes the Act, such as a waiver of the right to complain, is invalid.
  • The Data Fiduciary must be able to prove that notice was given and consent obtained, so consent logs are essential.

Who this is for: Product managers and UX designers, Frontend and mobile engineers, Marketing and growth teams, Privacy and compliance teams, Consent Managers and the fiduciaries onboarding them

Section 6(1) of the DPDP Act requires consent to be:

QualityWhat it means in practice
FreeNot obtained by coercion or pressure; a real choice exists
SpecificTied to a specified purpose, not "any purpose we choose"
InformedGiven after a notice that meets section 5 and Rule 3
UnconditionalNot made a condition of something unrelated to the purpose
UnambiguousLeaves no doubt that the person agreed

On top of these, consent must be given through a clear affirmative action. It must signify agreement to processing for the specified purpose, and be limited to the personal data necessary for that purpose.

The Act's own illustration

The Act gives the example of a telemedicine app that asks a user to consent to processing her data for telemedicine services, and also to access her phone contact list. She agrees to both. Because the contact list is not necessary for telemedicine, her consent is valid only for the telemedicine processing.

The lesson for product teams is direct: over-collection does not become lawful because the user ticked a box.

Consent is one of two lawful grounds. The other is the list of legitimate uses in section 7, such as employment purposes, legal obligations and medical emergencies. If no section 7 ground fits, you need consent.

What makes consent invalid?

Infringing terms are void

Section 6(2) says that any part of a consent which infringes the Act, the Rules or any other law in force is invalid to that extent. The Act illustrates this with a consent that includes agreement not to complain to the Board. That part is invalid, while the rest of the consent can stand.

Common clauses that will not survive:

  • waivers of the right to complain to the Board or to exercise rights;
  • consent to "any purpose" or "future purposes we may determine";
  • consent to process data that the purpose does not need.

Patterns that fail the five qualities

  • Pre-ticked boxes, or silence: not an affirmative action.
  • Bundling: one "I agree" covering service delivery, marketing and third-party sharing. This is not specific, and is arguably conditional.
  • Service denial for unrelated data: refusing the service unless the user also consents to unnecessary processing. This is not unconditional.
  • Browsewrap: "by continuing to use this site you agree". This is ambiguous and lacks a clear affirmative action.
  • Dark patterns: a hidden "decline", confusing toggles, or repeated nagging until the user accepts. These undermine free and unambiguous consent.

Consent from children and guardians

For a child (under 18) or a person with disability who has a lawful guardian, consent must be verifiable consent given by the parent or guardian. Rules 10 and 11 set out how to verify it. See verifiable parental consent.

Notice comes first: section 5 and Rule 3

Consent is only "informed" if it follows a proper notice. Section 5 requires a notice with every consent request, and Rule 3 sets the minimum content. The notice must:

  • (a) be presented and understandable independently of any other information. A link to a 30-page policy is not enough.
  • (b) give, in clear and plain language, a fair account of the details needed for specific and informed consent, at minimum:
    • an itemised description of the personal data; and
    • the specified purposes, with a specific description of the goods, services or uses enabled.
  • (c) give the link to the website or app, and describe any other means, by which the person can:
    • withdraw consent, with ease comparable to giving it;
    • exercise her rights under the Act; and
    • complain to the Board.

The person must be able to read the request in English or any language listed in the Eighth Schedule to the Constitution.

Consent obtained before the Act

For consent given before commencement, section 5 requires the fiduciary to give a notice as soon as reasonably practicable. It can continue processing until the person withdraws consent. Plan a re-notice campaign for your existing user base ahead of 13 May 2027.

Full detail: privacy notice requirements under Rule 3.

Withdrawal: as easy as giving consent

Section 6(4) lets the Data Principal withdraw consent at any time. The ease of withdrawal must be comparable to the ease with which consent was given. Rule 3(c)(i) requires the notice to say how.

What happens after withdrawal

  • Consequences: under section 6(5), the consequences of withdrawal are borne by the Data Principal. For example, a feature that depends on the data may stop working. Withdrawal does not make earlier processing unlawful.
  • Stop processing: under section 6(6), the fiduciary must, within a reasonable time, stop processing and cause its Data Processors to stop. The exception is processing that the Act or another law permits without consent.
  • Erasure: section 8(7) requires erasure once consent is withdrawn, unless retention is required by law. Rule 8(3) separately requires personal data, traffic data and logs to be kept for at least one year from processing. Reconcile the two in your retention design.

Withdrawal parity in UX

If consent was given byWithdrawal should be available by
One tap on a mobile promptOne or two taps in app settings
Ticking a box on the webA toggle in account settings, plus a link in emails
An OTP on a call-centre flowThe same call-centre flow, or an IVR or SMS option
A Consent Manager platformThe same Consent Manager platform

See consent withdrawal UX for patterns.

Proving consent: burden of proof and consent logs

Under section 6(10), where a question arises in a proceeding about consent, the Data Fiduciary must prove that a notice was given and consent was obtained in line with the Act and Rules. If you cannot show it, you should expect the consent to be treated as not obtained.

A minimal consent record schema

consent_id, principal_id, notice_version, notice_language,
purposes[], data_items[], channel (web/app/ivr/consent_manager),
action (granted/denied/withdrawn), ui_evidence (screen/version hash),
timestamp_utc, ip/device (where justified), processor_fanout_status

Engineering practices

  • Version notices. Store every Rule 3 notice text and hash, and link each consent event to the exact version shown.
  • Purpose-level granularity. Record one row per purpose, not one blanket flag.
  • Event-sourced history. Keep the full sequence of grants and withdrawals, not just the current state.
  • Propagation. Push withdrawal events to processors, and record their acknowledgement, to evidence section 6(6).
  • Retention. Consent records are personal data too. Keep them as long as you may need to prove consent, and protect them under Rule 6.

Consent Managers must keep a record of consents given, denied and withdrawn, and the notices that went with them, for at least seven years (First Schedule, Part B, item 4(c)). That is a useful benchmark even for fiduciaries that do not use one.

Section 6(7) lets a Data Principal give, manage, review and withdraw consent through a Consent Manager registered with the Board. Registration under Rule 4 opened on 13 November 2026. No registrations are reported in this guide, so check the Board's website for registered entities.

What a Consent Manager must do (First Schedule, Part B)

  • enable consent either directly to an onboarded fiduciary, or routed through another onboarded fiduciary that holds the data (the B1/B2 bank illustration);
  • ensure that shared personal data is not readable by the Consent Manager itself;
  • keep records of consents, notices and sharing for at least seven years, and provide them in machine-readable form on request;
  • act in a fiduciary capacity towards the Data Principal, avoid conflicts of interest and not sub-contract its obligations.

What it means for a Data Fiduciary

  • Consent received through a Consent Manager is still subject to section 6. The five qualities and the necessity test do not change.
  • Withdrawals arriving through the Consent Manager must stop processing within a reasonable time, exactly as direct withdrawals do.
  • Integration work includes onboarding, consent artefact verification, and webhooks for withdrawal events.

See Consent Managers explained and Consent Manager obligations.

Consent implementation checklist before 13 May 2027

  1. Inventory consent-based processing. For each purpose, confirm that no section 7 legitimate use applies. If one does, document it instead of asking for consent.
  2. Unbundle purposes. Separate service delivery, marketing, personalisation, analytics and third-party sharing into distinct choices.
  3. Apply the necessity test. Remove data items that the purpose does not need from both the request and the collection.
  4. Rewrite notices to Rule 3 and translate them where you serve users in other languages.
  5. Remove dark patterns. Give equal prominence to "accept" and "decline", with no pre-ticked boxes and no forced continuation.
  6. Build withdrawal parity in every channel where consent is collected.
  7. Implement consent logging with notice versioning, and processor propagation.
  8. Re-notice existing users whose consent pre-dates the Act.
  9. Add age gating and Rule 10 parental consent where children may use the service.
  10. Test with the Board in mind. Can you prove, for a random user, which notice she saw and when she agreed?

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Unbundle consent by purpose

    Present separate choices for each specified purpose instead of a single blanket agreement.

    DPDP Act s.6(1)

  2. Apply the necessity test

    Collect only the personal data necessary for each purpose; drop extra fields from consent screens.

    DPDP Act s.6(1)

  3. Publish Rule 3 compliant notices

    Itemise the data, specify the purposes and link to withdrawal, rights and Board complaint routes.

    Rule 3

  4. Offer notices in Eighth Schedule languages

    Let users access the consent request in English or any Eighth Schedule language relevant to your audience.

    DPDP Act s.5, s.6(3)

  5. Match withdrawal effort to consent effort

    Provide withdrawal in the same channel and with similar steps as the original consent.

    DPDP Act s.6(4); Rule 3(c)(i)

  6. Propagate withdrawals to processors

    Stop processing within a reasonable time and cause processors to stop, recording their acknowledgement.

    DPDP Act s.6(6)

  7. Log consent with notice versions

    Store purpose-level consent events linked to the exact notice shown, so that you can carry the burden of proof.

    DPDP Act s.6(10)

  8. Strip invalid clauses

    Remove waivers of rights or of complaints to the Board, and open-ended purpose language, from terms and consent text.

    DPDP Act s.6(2)

  9. Re-notice legacy users

    Send Rule 3 notices to users whose consent was obtained before commencement.

    DPDP Act s.5

Key dates

  1. Consent Manager registration (Rule 4) in force

  2. Sections 5–6 consent and notice duties and Rule 3 apply

Answers

Frequently asked questions

What are the requirements for valid consent under the DPDP Act?

Section 6 requires consent that is free, specific, informed, unconditional and unambiguous, given through a clear affirmative action, and limited to the personal data necessary for the specified purpose. It must follow a Rule 3 notice and be as easy to withdraw as to give.

Are pre-ticked boxes valid consent under DPDP?

No. DPDP consent requires a clear affirmative action by the Data Principal. A pre-ticked box, silence, inactivity or a 'by continuing you agree' banner does not show unambiguous agreement, so it is unlikely to be valid consent under section 6.

Can I refuse service if a user does not consent to marketing?

Making a service conditional on consent to unrelated processing, such as marketing, conflicts with the requirement that consent be unconditional and limited to necessary data. Ask for marketing consent separately and keep the core service available to users who decline it.

How quickly must processing stop after consent is withdrawn?

Section 6(6) requires the Data Fiduciary to stop processing, and to cause its Data Processors to stop, within a reasonable time after withdrawal, unless processing is permitted without consent. The Act does not set a fixed number of hours, so design automated propagation and document your timelines.

Who has to prove consent was obtained under DPDP?

The Data Fiduciary. Section 6(10) places the burden of proof on the fiduciary to show that it gave a proper notice and obtained consent in line with the Act and Rules. Versioned notices and purpose-level consent logs are the practical way to meet it.

Do existing users need to give consent again under DPDP?

Not necessarily. For consent obtained before the Act commenced, section 5 requires a notice as soon as reasonably practicable, and processing may continue until the person withdraws consent. Send compliant Rule 3 notices to legacy users before 13 May 2027.

Is consent through a Consent Manager different?

The standard is the same. Consent given through a Consent Manager registered under Rule 4 must still meet section 6. The Consent Manager must keep consent and notice records for at least seven years and must not be able to read the personal data shared.

Legal references and sources

  • Digital Personal Data Protection Act, 2023 — Sections 5 and 6 (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 3 (notice) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 4 and First Schedule (Consent Managers) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rules 10 and 11 (verifiable consent) (official text)

This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.

About the author

Suhas Bhairav

Suhas Bhairav

Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.