DPDP Rules 2025Updated 22 November 20269 min read

DPDP Consent Managers Explained: What Changed on 13 Nov 2026

Rule 4 of the DPDP Rules came into force on 13 November 2026. Here is what a Consent Manager is, what is live now, and what still waits for 13 May 2027.

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

Rule 4 in force
13 November 2026
Act provisions live
Sections 6(9) and 27(1)(d), from 13 Nov 2026
Registered with
Data Protection Board of India
Minimum net worth
₹2 crore
Consent record retention
At least 7 years
Fiduciary obligations start
13 May 2027
Registered Consent Managers
Check the Board's website for published particulars

Quick answer

A Consent Manager is a Board-registered, India-incorporated company that runs an interoperable platform through which people give, manage, review and withdraw consent to Data Fiduciaries. Rule 4 and the First Schedule came into force on 13 November 2026, so companies can now apply to the Data Protection Board for registration. The fiduciary-side obligations they plug into, such as Rule 3 notices and Rule 14 rights, start on 13 May 2027.

  • Rule 4 of the DPDP Rules and section 6(9) of the Act came into force on 13 November 2026, opening Consent Manager registration.
  • Applicants must meet nine First Schedule Part A conditions, including Indian incorporation and net worth of at least ₹2 crore.
  • Registered Consent Managers must meet thirteen Part B obligations, including data-blind sharing and seven-year consent records.
  • The Board can direct, suspend or cancel a Consent Manager after giving it an opportunity of being heard.
  • Data Fiduciaries do not have to use a Consent Manager; it is an optional channel, and their own obligations start on 13 May 2027.

Who this is for: Companies planning to become Consent Managers, Banks, fintechs and account aggregator ecosystem players, Data Fiduciaries evaluating consent infrastructure, Product and platform architects, Investors in consent and identity infrastructure

A Consent Manager is a person registered with the Data Protection Board who acts as a single point of contact for a Data Principal to give, manage, review and withdraw her consent through an accessible, transparent and interoperable platform. The DPDP Act creates the role; Rule 4 and the First Schedule of the DPDP Rules, 2025 set out how to register and what a registered Consent Manager must do.

Think of it as consent infrastructure that sits between people and the organisations that want to process their data:

  • The Data Principal sees, in one place, which fiduciaries she has consented to, for what, and can withdraw.
  • The Data Fiduciary is onboarded onto the platform and sends consent requests through it.
  • The Consent Manager records consents, notices and sharing events, but under Part B item 2 must ensure that the personal data being shared is not readable by it.

The First Schedule illustration uses banks. Two banks, B1 and B2, are onboarded onto a platform P. In one case, X gives consent to B1 directly and shares a bank statement held in her digital locker. In the other, X routes her consent through B2 to B1 and digitally instructs B2 to send her statement to B1.

A Consent Manager acts in a fiduciary capacity towards the Data Principal (Part B item 8). It works for the individual, not for the companies that pay to be onboarded.

What changed on 13 November 2026

Rule 1(3) brought Rule 4 into force one year after the Rules were published, on 13 November 2026. MeitY's commencement notification for the Act brought section 6(9), which requires every Consent Manager to be registered with the Board, and section 27(1)(d), covering the Board's role where a Consent Manager breaches its conditions, into force on the same date.

From that date:

  1. Applications are open. Under Rule 4(1), a person meeting the Part A conditions may apply, furnishing the particulars, information and documents the Board publishes on its website.
  2. The Board decides. Under Rule 4(2), the Board may inquire, then either register the applicant and publish its particulars on its website, or reject the application with reasons.
  3. Part B obligations bind registrants. Rule 4(3) makes the thirteen Part B obligations applicable to every registered Consent Manager.
  4. Supervision is live. Rule 4(4) to 4(6) let the Board direct corrective measures, suspend or cancel registration, issue protective directions, and call for information.

No registered Consent Manager is assumed on this page. Check the Board's website for the list of particulars it publishes under Rule 4(2)(a) before relying on any provider's claim of registration.

What is live now versus what waits for 13 May 2027

The one-year head start for Consent Managers means the infrastructure layer is switched on before the obligations it serves.

Live since 13 Nov 2026Waits for 13 May 2027
Registration applications to the Board (Rule 4(1))Rule 3 notice requirements for Data Fiduciaries
Board inquiry, registration or rejection (Rule 4(2))Rule 14 rights publication, including by Consent Managers
Part A conditions and Part B obligations (First Schedule)90-day grievance ceiling for fiduciaries and Consent Managers (Rule 14(3))
Board directions, suspension, cancellation (Rule 4(4)–(5))Rule 6 security, Rule 7 breach, Rule 8 retention for fiduciaries
Board calls for information (Rule 4(6))Remaining Act sections, including the penalty regime for fiduciaries
Act sections 6(9) and 27(1)(d)Rule 10 verifiable parental consent

In practical terms, November 2026 to May 2027 is the window for Consent Managers to register, certify their platforms, and onboard Data Fiduciaries, so that by the time fiduciaries must give Rule 3 notices and honour rights, the consent rails already exist.

For a Data Fiduciary, nothing about using a Consent Manager became mandatory on 13 November 2026. What changed is that a regulated option now exists to evaluate.

Who can register as a Consent Manager?

Part A of the First Schedule sets nine conditions. In summary:

  1. A company incorporated in India.
  2. Sufficient capacity, including technical, operational and financial capacity.
  3. Sound financial condition and general character of management.
  4. Net worth of not less than ₹2 crore, measured as total assets minus liabilities in the books.
  5. Adequate business volume, capital structure and earning prospects.
  6. Directors, key managerial personnel and senior management with a reputation for fairness and integrity.
  7. Memorandum and articles that require adherence to the conflict-of-interest obligations in Part B items 9 and 10, with policies to ensure adherence, amendable only with the Board's prior approval.
  8. Proposed operations in the interests of Data Principals.
  9. Independent certification that the interoperable platform meets the data protection standards and assurance framework the Board publishes, and that technical and organisational measures support the Part B item 11 disclosures.

The draft Rules set the net worth at ₹12 crore; the final figure is ₹2 crore. The independence conditions (items 6, 7 and 9) are often harder to meet than the financial ones, especially for groups that also operate Data Fiduciaries. See registration conditions for detail.

What a registered Consent Manager must do

Part B lists thirteen obligations. The ones with the biggest design impact:

  • Data-blind architecture (item 2). Personal data shared through the platform must not be readable by the Consent Manager. In engineering terms, the platform orchestrates consent and routes encrypted payloads or instructions; it does not hold decrypted content.
  • Consent ledger (items 3 and 4). A record of consents given, denied or withdrawn, the notices that preceded or accompanied each request, and each sharing event with a transferee fiduciary. The Data Principal must be able to access it, get a machine-readable copy on request, and the record must be kept for at least seven years.
  • Primary channel (item 5). A website or app, or both, as the primary means of access.
  • No outsourcing (item 6). No sub-contracting or assignment of obligations under the Act and Rules.
  • Security and fiduciary duty (items 7 and 8). Reasonable security safeguards, and acting in a fiduciary capacity towards the Data Principal.
  • Conflict controls and disclosures (items 9 to 11). Avoid conflicts with fiduciaries and publish promoters, directors, KMP, senior management and shareholdings above two per cent.
  • Audit and control (items 12 and 13). Audit mechanisms reporting to the Board, and no transfer of control without the Board's prior approval.

See Consent Manager obligations for item-by-item guidance.

Should a Data Fiduciary use a Consent Manager?

Using a Consent Manager is optional. A Data Fiduciary can collect and manage consent itself, provided it meets Rule 3 and the Act. The question is whether a registered platform reduces cost or risk for your use case.

Reasons to consider one:

  • Multi-party data flows. Where data moves between fiduciaries at the person's request, as in the bank illustration, a neutral platform with a consent ledger simplifies proof of consent.
  • Withdrawal at scale. A Consent Manager gives the individual one place to withdraw, which helps meet the "comparable ease" test.
  • Evidence. The seven-year record of notices, consents and sharing is useful evidence if a consent is challenged.

Reasons for caution:

  • Accountability does not transfer. The fiduciary remains responsible for its own processing, notices, security and rights handling from 13 May 2027.
  • Integration effort. Your consent state must stay in sync with the platform, including withdrawals that arrive through it.
  • Verify registration. Check the Board's published particulars, not a vendor's marketing.

Whichever route you choose, keep your own consent event log. See DPDP consent requirements.

Further reading on suhasbhairav.com

Key dates

  1. DPDP Rules published; Rule 4 scheduled for one year later

  2. Rule 4, First Schedule and Act section 6(9) in force; registration opens

  3. Fiduciary obligations, Rule 14 rights and the 90-day grievance ceiling apply

Answers

Frequently asked questions

What is a Consent Manager in the DPDP Act?

A Consent Manager is a company registered with the Data Protection Board that operates an accessible, transparent and interoperable platform through which a Data Principal can give, manage, review and withdraw consent to Data Fiduciaries. It acts in a fiduciary capacity towards the individual and must not be able to read the personal data shared through it.

When did Consent Manager registration start under DPDP?

Rule 4 of the DPDP Rules, 2025 and section 6(9) of the Act came into force on 13 November 2026, one year after the Rules were published. From that date, companies meeting the First Schedule Part A conditions can apply to the Data Protection Board using the particulars and documents it publishes on its website.

Is it mandatory to use a Consent Manager under DPDP?

No. A Data Fiduciary may obtain and manage consent directly, as long as it meets the notice and consent requirements of the Act and Rule 3. A Consent Manager is an optional, regulated channel. Using one does not shift the fiduciary's own accountability for processing.

What is the net worth requirement for a DPDP Consent Manager?

At least ₹2 crore, under item 4 of Part A of the First Schedule. Net worth means total assets reduced by liabilities as shown in the books of accounts. The January 2025 draft had proposed ₹12 crore.

How long must a Consent Manager keep consent records?

At least seven years, or longer if agreed with the Data Principal or required by law, under Part B item 4(c) of the First Schedule. The record covers consents given, denied or withdrawn, the notices preceding or accompanying requests, and sharing of data with transferee Data Fiduciaries.

Can the Data Protection Board cancel a Consent Manager's registration?

Yes. Under Rule 4(5), if it is necessary in the interests of Data Principals, the Board may, after giving the Consent Manager an opportunity of being heard and by a reasoned written order, suspend or cancel its registration and issue protective directions.

How do I check if a Consent Manager is registered?

Rule 4(2)(a) requires the Board to publish the particulars of each registered Consent Manager on its website. Check that published list directly rather than relying on a provider's own claims or marketing material.

Legal references and sources

  • Digital Personal Data Protection Rules, 2025 — Rule 4(1)–(6) (official text)
  • Digital Personal Data Protection Rules, 2025 — First Schedule, Parts A and B (official text)
  • Digital Personal Data Protection Act, 2023 — Section 6(7)–(9) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 1(3) (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.