Data protection & DPDP compliance

DPDP Consent Managers Explained: Should You Register

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

Published 30 October 2026

India’s DPDP framework creates an intermediary most privacy laws lack: the Consent Manager — a Board-registered entity through which individuals grant, review, and withdraw consent across businesses from one dashboard. Rule 4 with the First Schedule, timed around November 2026 in the phased rollout, governs registration and duties. For most Kerala businesses the question is not registration but interoperation; for a few intermediaries it is a business opportunity. This guide explains both decisions. It is general information, not legal advice.

Under the notified DPDP Rules, 2025 (G.S.R. 846(E), 13 November 2025), registration conditions and duties sit in Rule 4 read with the First Schedule — Part A (conditions for registration, including incorporation in India and a minimum net worth of ₹2 crore) and Part B (Consent Manager obligations) — and Rule 4 comes into force one year after the Rules’ publication, on 14 November 2026.

Consent under Sections 5 and 6 of the DPDP Act is per-purpose, informed, and withdrawable — but individuals face dozens of fiduciaries with incompatible consent screens. The Consent Manager answers by intermediating: the principal acts once through the Manager, which records and transmits consent states to participating fiduciaries, and withdrawal propagates the same way. The Act anchors the concept in Section 2(g); the phased timeline places Manager registration around November 2026, ahead of the May 2027 substantive-compliance horizon, so consent architecture must be Manager-compatible before enforcement bites. The timeline anchor for the whole series is the DPDP compliance position toward May 2027.

What duties does the First Schedule impose?

At the level the Act and notified summaries disclose: eligibility and registration with the Board; operation that is transparent to principals about what is recorded and transmitted; secure, tamper-evident consent records with audit trails; prompt effect to withdrawal; cooperation with Board audits and inquiries; and confinement of principal data to intermediation — no secondary use. Each limb’s exact thresholds, formats, and audit mechanics live in the notified Rule 4 and First Schedule text and must be read there, not inferred from this summary.

Where does liability fall — Manager, Fiduciary, or both?

The table below is an interpretive allocation — confirm these lines in the Manager–Fiduciary contract.

Failure Answers
Consent never recorded or wrongly transmitted Manager, for intermediation breach
Defective notice or purpose creep in processing Fiduciary, under Sections 5, 6, and 8
Withdrawal ignored downstream Fiduciary for continued processing; Manager if transmission failed
Security failure of consent records The party whose safeguards failed, under Section 8(5) and Rule 6

Penalty exposure follows the Schedule to the Act — up to the stated crores per contravention class — with Section 33 factors weighing cooperation and mitigation. The Board-inquiry and appeal mechanics are mapped in the penalties companion to this series. Contracts between Managers and Fiduciaries must allocate logging, breach-cascade notice within Rule 7-compatible hours, audit rights, and deletion duties expressly.

Should my firm register, build, or integrate?

Register only where intermediation is the business: health-data networks, fintech rails, large consumer platforms with cross-fiduciary consent traffic. Build proprietary consent infrastructure where consent journeys are a competitive differentiator and volumes justify audit overhead. Integrate — the common Kerala SME answer — where a registered Manager or consent-platform vendor supplies interoperable consent endpoints while the business keeps its notices, records, and grievance redressal. The decision tree turns on consent volume, sector sensitivity (health, finance, children’s data), and engineering capacity — assessed in 2026, not after enforcement.

Expose consent states as structured, versioned records tied to notice versions; align notice content with the consent-notice drafting guide; log grants, reviews, and withdrawals with timestamps and identity verification references; rehearse withdrawal propagation end-to-end with processors under data processing agreements; and pilot one Manager-interoperable journey before re-platforming. Data processing agreements and impact assessments that carry this load are covered in the processor-contracts companion.

Primary sources

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

FAQ

Common questions

What is a Consent Manager under the DPDP Act?
A Board-registered intermediary through which a Data Principal may give, review, and withdraw consent across Data Fiduciaries — a single consent dashboard. The Act defines the concept in Section 2(g); registration conditions and duties sit in Rule 4 with the First Schedule, timed around November 2026 in the phased rollout.
Does every business need to become a Consent Manager?
No. Most businesses remain Data Fiduciaries and simply interoperate with Consent Managers where customers use them. Registration suits intermediaries — health-data networks, fintech account-aggregator-style players, large platforms — that want to offer consent management as a service.
Who is liable if consent recorded through a Manager is defective?
Liability follows function: the Manager answers for its intermediation duties (authentic recording and transmission), while the Fiduciary remains responsible for its own notice, purpose limitation, and processing compliance under Section 8. Contracts must draw this line expressly.
What is the First Schedule duty set in brief?
Registration eligibility, transparent operation, secure consent records, honoring withdrawal promptly, audit cooperation, and non-use of principal data beyond intermediation. Exact conditions must be read in the notified Rule 4 text, not summarised here.
How should hospitals, fintechs, and edtech prepare before November 2026?
Map consent flows, expose machine-readable consent endpoints, align notice formats with Rule 3 requirements, and pilot Manager-interoperable journeys with one vendor before committing architecture. The consent-notice drafting companion to this guide carries the notice detail.
How is this different from account aggregators?
Account aggregators move financial data on consent under RBI's framework; Consent Managers intermediate data-protection consent across sectors under the DPDP Board. The design rhyme is real — interoperable, revocable, logged consent — but the regulator, scope, and liability regime differ.

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.