Consent Manager registration under DPDP: 9 conditions and 13 obligations
By Abhijeet Singh · Primary sources verified by dpdprules.orgPublished · Last reviewed 11 min read
Jump to sourcesWhat are the registration conditions and obligations for a Consent Manager under DPDP?
The short answer
Consent Manager registration under Rule 4 requires the applicant to satisfy 9 conditions in Part A of the First Schedule, and a registered Consent Manager must follow the 13 obligations in Part B. At 26 October 2026, section 6(9), Rule 4 and the First Schedule scheme were not in force. Their computed date is 13 November 2026, interpretation until officially confirmed. Item 2 requires sufficient capacity to fulfil the Consent Manager's obligations and says this includes technical, operational and financial capacity; those 3 examples do not close the condition. Other conditions include incorporation in India, net worth of at least 2 crore rupees, governance tests and independent platform certification. The obligations cover the consent channel, unreadable data contents, records kept for at least 7 years or longer where agreed or legally required, access and transparency, security, fiduciary conduct, conflicts, audits and transfer of control. Section 2(g), already in force, defines a Consent Manager as a person registered with the Board who operates a single point of contact platform for a Data Principal to give, manage, review and withdraw consent. This site reads the First Schedule as commencing with Rule 4. Sections 6(7) and 6(8) have a computed date of 13 May 2027. The Gazette date and counting uncertainties could move these readings by up to 2 days, to 15 November 2026 and 15 May 2027 at the latest. Every computed date is interpretation until officially confirmed.

A panel states that Rule 4 and section 6(9) are not in force at 26 October 2026 and gives the computed 13 November 2026 date as interpretation until officially confirmed. The image says a Consent Manager helps a person give, manage, review and withdraw consent, must register with the Board under Rule 4, and is a registered company operating a consent platform rather than merely a Data Fiduciary's consent banner. Status as at 26 October 2026: Rule 4 and section 6(9) are not in force yet. Their computed date is 13 November 2026, potentially 15 November 2026 at the latest, interpretation until officially confirmed.
Most of the DPDP framework's cast has familiar ancestors in global privacy law. The Consent Manager is less familiar: consent infrastructure operated as a registered, supervised business. At 26 October 2026, section 6(9), Rule 4 and the First Schedule scheme are not in force; their computed date is 13 November 2026, interpretation until officially confirmed. This article maps the institution from the primary text: the definition, the section 6 channel, and what registration under Rule 4 with the First Schedule demands. A companion piece answers the narrower commercial question, whether you need to register as a Consent Manager; for most businesses the answer is no.
The definition in section 2(g)
The Act defines the term once, in the definitions section:
"“Consent Manager” means a person registered with the Board, who acts as a single point of contact to enable a Data Principal to give, manage, review and withdraw her consent through an accessible, transparent and interoperable platform"
4 practical elements carry the weight. Registered with the Board: registration with the Data Protection Board of India is part of the definition, so under section 2(g) an unregistered service does not meet the Act's defined term. A single point of contact: the Data Principal uses the platform as the contact point for participating Data Fiduciaries. Give, manage, review and withdraw: the definition covers the life of a consent, not only its capture. Accessible, transparent and interoperable: the platform is meant to work across the Data Fiduciaries onboarded onto it.
Software is not a Consent Manager merely because it records consent choices. A consent banner or preference centre used by a Data Fiduciary does not by itself meet section 2(g): the defined term requires Board registration and the single point of contact platform described there. The same company could occupy more than 1 role if the legal conditions for each are met; the labels are not interchangeable.
The consent channel in section 6
Section 6, the consent section, gives the institution its function in 3 subsections. Subsection (7) opens the channel: the Data Principal may give, manage, review or withdraw her consent to the Data Fiduciary through a Consent Manager. The word is may: an optional route for the individual, not a mandatory intermediary for every consent in India.
Subsection (8) fixes the direction of loyalty:
"The Consent Manager shall be accountable to the Data Principal and shall act on her behalf in such manner and subject to such obligations as may be prescribed."
For this statutory role, the Consent Manager is accountable to the Data Principal and acts on her behalf; subsection (8) does not make a Data Fiduciary the beneficiary of that statutory duty. Subsection (9) then makes registration compulsory and conditional:
"Every Consent Manager shall be registered with the Board in such manner and subject to such technical, operational, financial and other conditions as may be prescribed."
Both subsections end in as may be prescribed. The DPDP Rules 2025 are the prescription: Rule 4 and the First Schedule.
Rule 4: registration with the Board
Rule 4 builds the machinery around the First Schedule. A person who fulfils the conditions in Part A may apply to the Board for registration, furnishing the particulars and the other information and documents the Board may publish on its website. After such inquiry as it deems fit to satisfy itself that the Part A conditions are fulfilled, the Board either registers the applicant under intimation to the applicant and publishes its particulars on its website, or rejects the application and communicates the reasons for the rejection to the applicant.
Registration is where the ongoing supervision attached to the Part B obligations begins. Under Rule 4(3) the registered Consent Manager carries those obligations. Where the Board considers the conditions and obligations are not being adhered to, it may, after giving an opportunity of being heard, inform the Consent Manager of the non adherence and direct it to take measures to ensure adherence; where satisfied that it is necessary in the interests of Data Principals it may, again after giving the Consent Manager an opportunity of being heard, by order for reasons to be recorded in writing, suspend or cancel the registration and give the Consent Manager such directions as it may deem fit to protect the interests of the Data Principals; and it may, for the purposes of this rule, require the Consent Manager to furnish such information as it may call for.
Part A: what it takes to register
Part A sets 9 conditions. Rule 4(2) lets the Board make the inquiry it considers fit to satisfy itself that every condition is fulfilled. Part A gives 1 quantitative eligibility threshold: the net worth floor in item 4. It gives no numeric formula for sufficient capacity in item 2.
| Item | What Part A requires |
|---|---|
| 1 | The applicant is a company incorporated in India. |
| 2 | The applicant has sufficient capacity to fulfil its Consent Manager obligations. The text says this includes technical, operational and financial capacity. This site's reading is that these are named examples, not a closed list. |
| 3 | Its financial condition and the general character of its management are sound. |
| 4 | Its net worth is not less than 2 crore rupees. |
| 5 | Its likely business volume, capital structure and earning prospects are adequate. |
| 6 | Its directors, key managerial personnel and senior management have a general reputation and record of fairness and integrity. |
| 7 | Its memorandum and articles require adherence to Part B items 9 and 10, require policies and procedures for that adherence, and allow those provisions to be amended only with the Board's previous approval. |
| 8 | Its proposed operations are in the interests of Data Principals. |
| 9 | An independent certification covers both limbs: the interoperable platform is consistent with the data protection standards and assurance framework the Board may publish, and appropriate technical and organisational measures are in place to follow them and effectively observe the disclosures in Part B item 11. |
The word including matters in item 2. Technical, operational and financial capacity are inside the test, but the condition remains sufficient capacity to fulfil the obligations as a whole. Item 9 is also wider than platform certification alone because its second limb reaches the measures behind the platform and the item 11 transparency duties.
Part B: the operating obligations
Part B lists 13 obligations. Together they describe the consent flow, the record, the service and the company behind it.
| Item | What Part B requires |
|---|---|
| 1 | Enable the Data Principal to give consent to an onboarded Data Fiduciary either directly or through another onboarded Data Fiduciary that holds her personal data with her consent. |
| 2 | Make personal data available or share it in a manner where "the contents thereof are not readable by it". |
| 3 | Keep a platform record of consent given, denied or withdrawn, the related notices, and sharing with a transferee Data Fiduciary. |
| 4 | Give the Data Principal access to that record; on her request and in accordance with the terms of service, provide its information in machine readable form; keep it for at least 7 years, or longer where the Data Principal and Consent Manager agree or the law requires. |
| 5 | Maintain a website or app, or both, as the primary means for accessing the service. |
| 6 | Do not subcontract or assign performance of any obligation under the Act and Rules. |
| 7 | Take reasonable security safeguards to prevent personal data breach. |
| 8 | Act in a fiduciary capacity in relation to the Data Principal. |
| 9 | Avoid conflicts of interest with Data Fiduciaries, including in respect of their promoters and key managerial personnel. |
| 10 | Have measures against conflicts arising from a director, key managerial personnel or senior management holding a directorship, financial interest, employment or beneficial ownership in a Data Fiduciary, or having a material pecuniary relationship with one. |
| 11 | Publish the named company leadership; each person holding more than 2 per cent of the shareholding of the company registered as the Consent Manager; every body corporate in which its promoter, director, key managerial personnel or senior management holds more than 2 per cent as at the first day of the preceding calendar month; and other information the Board directs in the interests of transparency. The words every body are the corrigendum wording. |
| 12 | Maintain effective audit mechanisms covering technical and organisational controls, continued fulfilment of registration conditions, and adherence to obligations; report audit outcomes to the Board periodically and whenever else it directs. |
| 13 | Do not transfer control by sale, merger or otherwise without the Board's previous approval and without fulfilling the conditions it may specify. |
The illustration for item 1 uses banks. The individual either grants a requesting bank access to a statement held in her digital locker, or routes consent through her own bank and instructs it to send the statement. Item 2 then supplies the distinctive data blindness rule: the Consent Manager moves the permission without being able to read the personal data contents.
When each piece commences
The commencement picture is split, and every calendar date here is computed, interpretation until officially confirmed. Section 6(9), the registration duty, sits in the 1 year group of notification G.S.R. 843(E), which computes to 13 November 2026. Rule 4 is on its own matching track: corrected Rule 1(3) brings it into force 1 year after publication in the Official Gazette, computing to the same 13 November 2026. Rule 1(3) does not name the Schedules; the First Schedule says it is linked to Rule 4, so this site presents it as commencing with that rule, which is itself interpretation. The rest of section 6, including the subsection (7) channel and the subsection (8) accountability duty, sits in the 18 month group, computing to 13 May 2027.
There are 2 uncertainties around that arithmetic. The printed Gazette issues are dated 13 November 2025, while their identifiers and the eGazette listing for G.S.R. 843(E) use 14 November 2025. The instruments also state periods without saying how they are counted. Together those points could move this site's readings by up to 2 days, to 15 November 2026 and 15 May 2027 at the latest. Those later dates are also interpretation until officially confirmed.
Who registers a Consent Manager when Rule 4 commences
Rule 4 makes the Board the registering authority. Under Rule 4(1) an applicant meeting the Part A conditions applies to the Board, and under Rule 4(2) the Board "may make such inquiry as it may deem fit" and, if satisfied, registers the applicant and publishes its particulars on its website, or, if not, rejects the application and communicates its reasons. Section 2(g), already in force, makes registration with the Board part of the definition, so an unregistered service does not meet the Act's defined term.
The Board exists as a body. Notification G.S.R. 844(E) established the Data Protection Board of India on 13 November 2025, and sections 18 to 26 of the Act, which constitute it, have been in force since that date. Who sits on it is a separate question. A MeitY circular of 6 May 2026 invited applications for 1 post of Chairperson and 4 posts of Member to prepare a panel of names for a Search cum Selection Committee. MeitY's published document library, as enumerated on 24 October 2026 and kept on file, held 1,605 records, including 19 that mention the DPDP framework. The same 6 titles named the Board, and no title named an appointment made, judged on the held copies of the circular and its advertisement and on the record titles for the rest.
That is a bounded statement about what was located, not a certified negative. MeitY's library is not the Gazette of India, and no eGazette search stands behind it. The Board status article tracks the later official records and the limits of each search.
So 2 pieces meet on the computed 13 November 2026 date, interpretation until officially confirmed: section 6(9) and Rule 4 become operative, while Rule 4(1) still requires the applicant to furnish the particulars, information and documents the Board may publish on its website. Each period runs from publication of its own instrument, G.S.R. 843(E) for section 6(9) and G.S.R. 846(E) for Rule 4, so a later appointment changes neither period. This site takes no position on how an application would be handled before the Board is functional. A business planning to apply can prepare against Part A now; that is practical guidance, not a present legal duty or a prediction that registration will be available on the first day.
Who actually needs to care
3 audiences. Businesses that want to become Consent Managers, most plausibly around financial data sharing, health or digital locker style services: Part A is the entry checklist, Part B the product specification, and the window opens with Rule 4. Data Fiduciaries that expect to receive consent through registered Consent Managers: section 6(7) lets the Data Principal give her consent to the Data Fiduciary through this channel, so integration is worth planning, and the role identifier confirms which side of the flow you sit on. And individuals, for whom the institution eventually means one dashboard for consents across services; the rights explorer covers the rights you will be able to exercise directly once sections 11 to 14 are in force, on a computed 13 May 2027, interpretation until officially confirmed.
The practical next step is to read Rule 4 and the First Schedule in the official text, and to let the company compliance plan tell you whether any of this lands on your own action list.
Related tool
Role and Actor Checker
Work out your likely role for a processing activity, such as Data Fiduciary or Data Processor.
Open
Related tool
Compliance Plan
Generate 1 company level action plan and see the work for your role first.
Open
Related tool
Individual Rights Assistant
Understand your rights as an individual and the channels a Data Fiduciary must offer.
Open
Section 6, official text →Rule 4, official text →First Schedule, official text →Do you need a Consent Manager? →Is the Data Protection Board operational? →