--- title: "Rule 4: Registration and obligations of Consent Manager" url: https://dpdp.myndsolution.com/wiki/rules/rule-4-registration-and-obligations-of-consent-manager/ description: "Rule 4 of the Digital Personal Data Protection Rules, 2025 (Registration and obligations of Consent Manager). Official text verbatim, comes into force on 13…" kind: rule updated: 2026-09-09 official_source: https://egazette.gov.in/WriteReadData/2025/267650.pdf text_type: official-text-plus-interpretation publisher: MYND Integrated Solutions license: Official Government of India texts are reproduced verbatim (public domain / open government data). Interpretation is CC BY 4.0, MYND Integrated Solutions. disclaimer: Not legal advice. Official text prevails over any interpretation. html_version: https://dpdp.myndsolution.com/wiki/rules/rule-4-registration-and-obligations-of-consent-manager/ --- # Rule 4: Registration and obligations of Consent Manager *The Digital Personal Data Protection Rules, 2025, G.S.R. 846(E) dated 13 November 2025. Comes into force on 13 November 2026.* ## Official text - **(1)** A person who fulfils the conditions for registration of Consent Managers set out in Part A of First Schedule may apply to the Board for registration as a Consent Manager by furnishing such particulars and such other information and documents as the Board may publish in this behalf on its website. - **(2)** On receipt of such application, the Board may make such inquiry as it may deem fit to satisfy itself regarding fulfilment of the conditions set out in Part A of First Schedule, and if it— - **(a)** is satisfied, register the applicant as a Consent Manager, under intimation to the applicant, and publish on its website the particulars of such Consent Manager; or - **(b)** is not satisfied, reject the application and communicate the reasons for the rejection to the applicant. - **(3)** The Consent Manager shall have obligations as specified in Part B of First Schedule. - **(4)** If the Board is of the opinion that a Consent Manager is not adhering to the conditions and obligations under this rule,it may, after giving an opportunity of being heard, inform the Consent Manager of such non-adherence and direct the Consent Manager to take measures to ensure adherence. - **(5)** The Board may, if it is satisfied that it is necessary so to do in the interests of Data Principals, after giving the Consent Manager an opportunity of being heard, by order, for reasons to be recorded in writing, — - **(a)** suspend or cancel the registration of such Consent Manager; and - **(b)** give such directions as it may deem fit to that Consent Manager, to protect the interests of the Data Principals. - **(6)** The Board may, for the purposes of this rule, require the Consent Manager to furnish such information as the Board may call for. ## Made under - [s. 6 Consent](https://dpdp.myndsolution.com/wiki/act/section-6-consent/) ## Interpretation in plain English (not legal advice) > This is a plain-English interpretation of the official text, prepared by the DPDP Wiki editorial team. It is not the law and not legal advice, and it may be incomplete or wrong. Always rely on the official text of the Act, the Rules and the notifications, and take advice from a qualified professional for your situation. This rule sets out how a person can become a registered Consent Manager. A Consent Manager is an entity that helps a Data Principal (the individual to whom the personal data relates) manage their consent. To apply, a person must meet the conditions listed in Part A of the First Schedule and submit the required information and documents to the Board.\n\nThe Board will review the application and make any necessary inquiries. If the Board is satisfied that the applicant meets the conditions, it will register the Consent Manager, notify them, and publish their details on its website. If the Board is not satisfied, it will reject the application and explain the reasons for the rejection. Once registered, the Consent Manager must follow the obligations listed in Part B of the First Schedule.\n\nThe Board actively monitors Consent Managers. If the Board believes a Consent Manager is failing to meet its conditions or obligations, it can direct the Consent Manager to take corrective measures after giving them a chance to be heard. The Board can also ask the Consent Manager to provide specific information at any time.\n\nIn more serious cases, the Board has the power to suspend or cancel a Consent Manager's registration to protect the interests of Data Principals. Before doing this, the Board must give the Consent Manager an opportunity to be heard and must record its reasons in writing. The Board can also issue specific directions to the Consent Manager to ensure Data Principals are protected. ### Key points - A person meeting the conditions in Part A of the First Schedule can apply to the Board to register as a Consent Manager. [(1)] - The Board will register the applicant and publish their details if satisfied, or reject the application with reasons if not satisfied. [(2)] - A registered Consent Manager must comply with the obligations set out in Part B of the First Schedule. [(3)] - The Board can direct a Consent Manager to fix any non-adherence after giving them an opportunity to be heard. [(4)] - The Board may suspend or cancel a registration and issue directions to protect Data Principals, provided it gives a hearing and records reasons in writing. [(5)] - The Board can require a Consent Manager to furnish information at any time. [(6)] ### Common misreadings - A Consent Manager's registration cannot be cancelled without them first having an opportunity to be heard by the Board. - The Board does not automatically approve applications; it may make inquiries to satisfy itself that the conditions are met before granting registration. *Interpretation prepared 2026-09-09 from the official text only; the official text prevails.* --- Cite as: DPDP Rules, 2025, r. 4. Official source: https://egazette.gov.in/WriteReadData/2025/267650.pdf