By Adv. K J Muhammed Aslam · Advocate, Ernakulam (Bar Council of Kerala)
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.
What makes consent valid — the Section 6 tests?
| 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
- Digital Personal Data Protection Act, 2023 — Sections 5, 6, 8, 13 (India Code)
- DPDP Rules, 2025 — Rule 3 (notice particulars) (notified text: G.S.R. 846(E), 13 November 2025; in force with the 18-month tranche)
- DPDP Act commencement note — GSR 843(E)/846(E) phased timeline (Gazette)
General information — not legal advice. Office at High Court Junction, Ernakulam; practice before the High Court of Kerala.
FAQ
