Rule 4 of the Digital Personal Data Protection Rules, 2025, on Consent Managers, is now in force. What a Consent Manager is, who may register as one, what businesses must do about them, and why 13 May 2027 remains the date that matters for most businesses.

From 13 November 2026, Rule 4 of the Digital Personal Data Protection Rules, 2025 and the First Schedule to the Rules are in force. Together they set out who may register with the Data Protection Board of India as a Consent Manager under the DPDP framework, and the obligations a Consent Manager owes once registered. This is the second of the three phases in which the Rules commence. The third, and for most businesses the one that matters, begins on 13 May 2027.

This note explains what a Consent Manager is under the DPDP Act, the conditions for registration, the continuing obligations of a registered Consent Manager, and what the framework requires of ordinary businesses that collect consent.

The Digital Personal Data Protection Act, 2023 allows an individual (a Data Principal) to give, manage, review and withdraw consent either directly with a business or through a Consent Manager. Section 2(g) defines a Consent Manager as a person registered with the Board who acts as a single point of contact enabling a Data Principal to give, manage, review and withdraw consent through an accessible, transparent and interoperable platform. Under section 6(8), a Consent Manager is accountable to the Data Principal and acts on that person’s behalf. Section 6(9) requires every Consent Manager to be registered with the Board.

In practical terms, a Consent Manager is a single dashboard through which an individual can see the consents they have given to several businesses, and withdraw any of them, without approaching each business separately. The Consent Manager does not hold or read the personal data itself. It carries the consent, and the record of it, between the individual and the businesses that are onboarded on its platform.

Where the law sits

  • Sections 2(g), 6(7), 6(8) and 6(9) of the Act create the role, make the Consent Manager accountable to the Data Principal and require registration with the Board.
  • Rule 4 of the DPDP Rules, 2025 sets out the procedure for applying to the Board, the Board’s power to register or reject, and the Board’s power to inquire into non-compliance.
  • Part A of the First Schedule lists the conditions for registration.
  • Part B of the First Schedule lists the obligations of a registered Consent Manager.

Who may register as a Consent Manager

Part A of the First Schedule sets nine conditions for registration. In summary, the applicant must:

  1. be a company incorporated in India;
  2. have sufficient technical, operational and financial capacity to fulfil its obligations;
  3. be sound in its financial condition and in the general character of its management;
  4. have a net worth of not less than ₹2 crore;
  5. show adequate volume of business, capital structure and earning prospects;
  6. have directors, key managerial personnel and senior management with a general reputation for fairness and integrity;
  7. have a memorandum and articles of association that require compliance with the conflict-of-interest and related obligations in Part B, and that permit those provisions to be amended only with the Board’s approval;
  8. show that its operations will be in the interests of Data Principals; and
  9. have its platform certified by an independent certifier as consistent with the standards published by the Board, with appropriate technical and organisational measures in place.

The application is made to the Board with the particulars and documents the Board specifies. The Board may register the applicant, or reject the application with reasons.

Rule 4 came into force on 13 November 2026, so applications can now be made to the Data Protection Board. In practice, an applicant works through six steps.

  1. Check eligibility against Part A of the First Schedule. The applicant must be a company incorporated in India with a net worth of at least ₹2 crore, a sound financial condition and management, and adequate technical, operational and financial capacity. Its directors, key managerial personnel and senior management must have a record of fairness and integrity.
  2. Build the platform to the Board’s standards. The platform through which people give, manage, review and withdraw consent must meet the technical and data-protection standards and assurance framework published by the Board.
  3. Obtain an independent certification. Part A requires an independent certification that the platform conforms to those standards and that appropriate technical and organisational measures are in place.
  4. Amend the memorandum and articles of association. They must require the company to follow the Consent Manager obligations in Part B, require policies that ensure it does so, and provide that these provisions can be amended only with the Board’s prior approval.
  5. Apply to the Data Protection Board. The application is made with the particulars, information and documents the Board specifies. After such inquiry as it considers fit, the Board registers the applicant or rejects the application with reasons.
  6. Comply from the first day of registration. A registered Consent Manager must meet the continuing obligations in Part B, set out below. Check the Board’s website for its current application requirements before filing.

Part B of the First Schedule imposes continuing obligations. The most significant are these.

  • Enabling consent. The Consent Manager must enable a Data Principal to give consent to processing by a Data Fiduciary onboarded on its platform, either directly or through another onboarded Data Fiduciary that already holds the data with consent.
  • Data it cannot read. Personal data shared through the platform must not be readable by the Consent Manager.
  • Records for seven years. It must keep a record of consents given, denied or withdrawn, of the notices that accompanied each request, and of any sharing with a transferee Data Fiduciary. The Data Principal must have access to that record, in machine-readable form on request, and the record must be kept for at least seven years, or longer where agreed or required by law.
  • Fiduciary duty and conflicts. It must act in a fiduciary capacity towards the Data Principal, avoid conflicts of interest with Data Fiduciaries, their promoters and key managerial personnel, and have measures to ensure that its own directors and senior management do not hold roles or material interests that create a conflict.
  • Transparency of ownership. It must publish details of its promoters, directors, key managerial personnel, senior management, shareholders holding more than two per cent, and bodies corporate in which its promoters or senior personnel hold more than two per cent.
  • No sub-contracting. It may not sub-contract or assign its obligations under the Act and the Rules.
  • Security and audit. It must take reasonable security safeguards against personal data breach, maintain effective audit mechanisms, and report the outcome of audits to the Board.
  • Change of control. It may not transfer control of the company, by sale, merger or otherwise, without the Board’s prior approval.

Under Rule 4, the Board may inquire into a breach of these conditions or obligations and, after giving the Consent Manager an opportunity to be heard, direct it to take measures to remedy the breach, or suspend or cancel its registration.

What the Consent Manager framework means for businesses

A business is not required to use a Consent Manager. Consent may continue to be collected directly, through a website, an app or a form.

A business must, however, be ready to deal with consents and withdrawals that reach it through a Consent Manager. Where an individual withdraws consent through a Consent Manager, the business must stop processing that person’s data within a reasonable time, and must cause its processors to stop as well, unless processing without consent is permitted by the Act or another law.

Three practical consequences follow.

  1. Systems must be able to receive a withdrawal from outside. A consent record that sits only in a marketing tool, with no way of being updated from an external signal, will not serve.
  2. Contracts with processors must provide for withdrawal. Agencies, cloud providers and other vendors must be bound to stop processing when consent is withdrawn.
  3. Records of consent matter. Where a business relies on consent, the Act places on it the burden of proving that notice was given and consent obtained. That proof is easier to give where consent is recorded, dated and linked to the notice the person saw.

The two are often confused. A consent management platform (CMP) is software a business buys to collect and record consent on its own website or app, such as a cookie banner or a preference centre. It acts for the business. A Consent Manager under the DPDP Act is a registered entity that acts for the individual, across many businesses, and owes duties to that individual. A business may use a CMP without any registration. Only a company registered with the Board may hold itself out as a Consent Manager.

A practical point on timing

Registration of Consent Managers is a function of the Data Protection Board. The Board was established on 13 November 2025, and the Ministry of Electronics and Information Technology invited applications for the posts of Chairperson and Members in May 2026. Until appointments are made, it is not clear how quickly applications for registration will be processed. Businesses should not read this as a reason to delay their own compliance, since their obligations do not depend on the Board’s composition.

The date that matters: 13 May 2027

From 13 May 2027, the main obligations of businesses as Data Fiduciaries take effect: standalone notices under Rule 3, valid and withdrawable consent, reasonable security safeguards under Rule 6, intimation of personal data breaches under Rule 7, erasure and retention under Rule 8, a published contact person under Rule 9, verifiable parental consent for anyone under eighteen, and the grievance and rights procedures under Rule 14. The penalties in the Schedule to the Act, which extend to ₹250 crore for each instance of breach, apply from the same date.

A proposal in January 2026 to shorten the transition period to twelve months was not notified. The Government confirmed the November 2026 and May 2027 dates in a written answer in the Lok Sabha in August 2026.

What to do now

For a business that has not yet begun, the following order of work is practical in the six months that remain.

  1. Make a list of the personal data the business holds, where it is stored and which vendors receive it.
  2. Identify, for each use of personal data, whether it rests on consent or on one of the legitimate uses in section 7.
  3. Rewrite notices and consent flows to meet Rule 3, and plan a notice to existing customers whose consent was taken before the Act.
  4. Make sure consent records can be updated when a withdrawal arrives from a Consent Manager, and that the update reaches every processor.
  5. Review contracts with processors, and add terms on security, breach notice, withdrawal and deletion.
  6. Write a breach response plan that covers both the 72-hour report to the Board and the six-hour report to CERT-In.

Frequently asked questions

When does the Consent Manager framework under the DPDP Rules come into force?
Rule 4 and the First Schedule came into force on 13 November 2026, one year after the Rules were notified.

Is it mandatory for a business to use a Consent Manager?
No. A business may continue to collect consent directly. It must, however, act on consents and withdrawals that reach it through a registered Consent Manager.

What is the minimum net worth to register as a Consent Manager?
The applicant must be a company incorporated in India with a net worth of not less than ₹2 crore, and must meet the other conditions in Part A of the First Schedule.

Can a Consent Manager see the personal data it carries?
No. The First Schedule requires that personal data shared through its platform is not readable by the Consent Manager.

How long must a Consent Manager keep consent records?
For at least seven years, or for a longer period if agreed with the Data Principal or required by law.

Who regulates Consent Managers?
The Data Protection Board of India, which registers them and may suspend or cancel registration for breach.

A self-assessment of twenty-five questions is available in the Firm’s DPDP Readiness Scorecard. The obligations are summarised on the Data Protection Desk page.

Alagh & Kapoor Law Offices

Disclaimer

The Bar Council of India does not permit advocates to solicit work or advertise in any manner. By clicking “I agree”, you acknowledge that:

  • you are seeking information about Alagh & Kapoor Law Offices of your own accord, and there has been no solicitation, advertisement or inducement by the firm or its members;
  • the information on this website is for general information only and is not legal advice; and
  • using this website does not create a lawyer–client relationship.

The firm is not liable for any consequence of action taken on the basis of this website’s content. All content on this website is the intellectual property of Alagh & Kapoor Law Offices.