Data protection & DPDP compliance

DPDP Consent Notice Sec 5: Format and Sample Clauses

By Adv. K J Muhammed Aslam · Advocate, Ernakulam (Bar Council of Kerala)

Published 4 November 2026

Every Data Fiduciary’s DPDP compliance starts at the same document: the Section 5 notice that precedes Section 6 consent. Get the notice wrong and consent fails, processing becomes unlawful, and breach, rights, and penalty exposure compound downstream. This guide gives the required items, the consent tests, layered multilingual design, withdrawal mechanics, and the legacy re-noticing programme to run before May 2027. It is general information, not legal advice.

[Verified against the notified DPDP Rules, 2025 (G.S.R. 846(E), 13 November 2025): Rule 3 requires the notice to be presented and understandable independently of any other information (standalone), to give in clear and plain language an itemised description of the personal data and the specified purpose(s) and the goods, services or uses enabled, and to give the communication link and means for withdrawal of consent, exercise of rights and complaints to the Board. Rule 3 enters into force with the 18-month tranche — May 2027.]

What must the notice contain — Section 5 items?

Section 5 requires notice of the personal data proposed to be processed, the specified purpose, and the manner in which the principal may exercise rights — withdrawal of consent and grievance redressal — with accessibility in English and Eighth Schedule languages. In practice each notice states: who the fiduciary is with grievance contact; precisely which data for precisely which purpose; retention linked to purpose; sharing with named processor classes; rights and how to exercise them; and withdrawal mechanics. One purpose, one notice layer — bundled multi-purpose notices defeat the specificity test.

Test Meaning Drafting consequence
Free No coercion, no take-it-or-leave bundled conditions beyond necessity Separate consent for optional processing (marketing, analytics) from core service consent
Specific Tied to the specified purpose, not open-ended Purpose strings name the use (order fulfilment, fraud screening), never “improving our services” alone
Informed Given after the Section 5 notice Notice precedes the consent control in every journey, with version linkage
Unconditional No denial of unrelated service for refusing optional consent Withholding marketing consent never blocks checkout or care
Unambiguous Clear affirmative action Unticked opt-in controls; pre-ticked boxes and implied consent fail

Consent is limited to necessary data for the purpose, withdrawal is as easy as giving, and the fiduciary bears the burden of proving consent was validly obtained — which makes consent logs, notice versions, and timestamped records evidential necessities, not admin extras.

How should notices be designed — layered and multilingual?

The first layer carries purpose, data, and the consent control in under a screen; deeper layers hold retention tables, sharing schedules, rights procedures, and contact details. Language discipline matters most in Kerala-facing journeys: English plus Malayalam at minimum, plain wording tested on non-lawyers, consistent terminology across app, web, paper forms, and call-centre scripts. Children’s journeys need a separate parental layer under Section 9, linked from the main notice rather than buried in it — see the children-data companion. The phased compliance anchor for all of this is the DPDP countdown toward May 2027.

How do withdrawal and grievance hooks work inside the notice?

Withdrawal sits beside the consent record it reverses: a one-action path in the same channel, propagating to processors with confirmation, stopping the specified processing except retention the law requires, and logging the event. Grievance redressal under Section 13 gets a named contact, acknowledgment discipline, and escalation to the Board stated as a right — the principal-rights workflow companion maps the fiduciary-side SLA. Consent Managers, where principals use them, plug into this same propagation path: Consent Managers explained.

How do we migrate legacy databases before May 2027?

Inventory every base by source, purpose, and consent evidence; retire purpose-less and proof-less piles by deletion rather than re-noticing risk; re-notice live cohorts with fresh Section 5 notices in priority order — children’s data first, then marketing and analytics bases, then processor-shared data with amended data processing agreements; and freeze new collection on compliant journeys immediately so the legacy pile stops growing. Budget the programme across quarters: mapping, notice drafting, journey rebuild, processor amendments, and evidence testing each take a cycle.

Primary sources

General information — not legal advice. Office at High Court Junction, Ernakulam; practice before the High Court of Kerala.

FAQ

Common questions

What must a Section 5 DPDP notice contain?
The personal data to be processed, the specified purpose, the manner of exercising rights including withdrawal and grievance redressal — in clear, plain language, itemised per purpose, and available in English plus Eighth Schedule languages the principal understands. Each purpose gets its own notice layer.
What makes consent valid under Section 6?
Consent must be free, specific, informed, unconditional, and unambiguous through a clear affirmative action, limited to necessary personal data for the specified purpose. The fiduciary bears the burden of proving consent, and withdrawal must be as easy as giving it.
Is a privacy policy the same as a DPDP notice?
No. A privacy policy describes general practices; a Section 5 notice is a per-purpose, pre-consent disclosure tied to specific processing with rights and withdrawal mechanics. Policies support notices but cannot substitute for them.
How do we handle withdrawal technically?
Expose a one-action withdrawal path in the same channel consent was given, propagate it to processors and sub-processors, stop the specified processing except legally required retention, and log the event with timestamps. Test the path quarterly.
What do we do about customers acquired before May 2027?
Inventory legacy bases, map each cohort to a specified purpose, and re-notice with fresh Section 5 notices seeking Section 6 consent before the substantive horizon — prioritising children's data, marketing bases, and processor-shared data. Undocumented legacy consent is the highest-risk pile.
Which languages must the notice use?
English plus the Eighth Schedule languages relevant to the principal base — Malayalam for Kerala-facing businesses at minimum — in plain non-legalistic wording. Layered design keeps the first layer short with details one tap deeper.

Contact

3rd Floor, Lalan Towers (KGL Builders), Vanchi Square, High Court Junction, Ernakulam, Kerala 682031 · Monday – Saturday, 10:00 – 18:30 (by appointment)

A note before you read on. In keeping with the Bar Council of India Rules, this website provides information about Adv. K J Muhammed Aslam, and general legal information, only to those who seek it of their own accord. It is not an advertisement or solicitation, and nothing here is legal advice. By continuing, you acknowledge you are visiting voluntarily. Full disclaimer.