[Analysis] Consent Manager under the DPDP Act – Registration Conditions | Thirteen Obligations | 13 November 2026

  • Blog|Company Law|
  • 16 Min Read

Consent Managers under section 6(7) to (9), Rule 4 and the First Schedule: the nine conditions for registration with the Board, the thirteen categories of obligation, the no-read constraint, the seven-year record retention requirement, and the 13 November 2026 commencement date.

  • By Taxmann
  • |
  • Last Updated on 16 November, 2026
The Consent Manager is the one concept in the DPDP framework with no direct parallel in the GDPR or most other data protection statutes. It is an intermediary, registered with the Data Protection Board, that aggregates consent management across multiple Data Fiduciaries onto a single platform and acts in a fiduciary capacity towards the Data Principal. Registration under section 6(9), together with the Board’s jurisdiction over registration breaches under section 27(1)(d) and Rule 4 itself, commenced on 13 November 2026. Part A of the First Schedule sets nine conditions for registration, including a minimum net worth of Rs. 2 crore and independent certification of the platform; Part B prescribes thirteen categories of obligation, one of which is that the Consent Manager must not be able to read the personal data flowing through its own platform.

Table of Contents

  1. What is a Consent Manager?
  2. When did the registration requirement take effect?
  3. Who can register as a Consent Manager?
  4. What obligations does a registered Consent Manager carry?
  5. Why must the Consent Manager be unable to read the data?
  6. How long must consent records be kept?
  7. What happens if a Consent Manager breaches its obligations?
  8. What does a Consent Manager change for a Data Fiduciary?
  9. How does this compare with the Account Aggregator model?
  10. What evidence should a Consent Manager maintain?
  11. Quick answers

1. What is 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 to enable a Data Principal to give, manage, review and withdraw her consent through an accessible, transparent and interoperable platform (Glossary).

Sections 6(7), (8) and (9) build the framework. Under section 6(7), the Data Principal may give, manage, review or withdraw her consent to the Data Fiduciary through a Consent Manager. Section 6(8) establishes accountability: the Consent Manager shall be accountable to the Data Principal and shall act on her behalf. Section 6(9) requires every Consent Manager to be registered with the Board, subject to technical, operational, financial and other conditions as may be prescribed. Rule 4 and the First Schedule prescribe those conditions and the obligations in detail (para 4.7).

Taxmann’s Digital Personal Data Protection describes the function in a way that makes the design intuitive. The Consent Manager is an intermediary that aggregates consent management across multiple Data Fiduciaries onto a single platform, giving the Data Principal a unified view of her consent relationships. Its illustration: a Data Principal who has given consent separately to a bank, an insurer and a lending app could, through a single Consent Manager dashboard, see all three consents in one place and withdraw the one given to the lending app without logging into that app separately (para 4.7).

That is the user-facing promise. The regulatory architecture behind it is more demanding than the dashboard suggests, and the rest of this article is about what the Rules actually require.

One structural point before the detail. The Board is not a conventional regulator under this Act; it does not issue regulations or set standards, and the only licence it grants is the registration of Consent Managers (para 1.5.1). The Consent Manager is therefore the single category of entity that must obtain the Board’s permission before operating.

2. When did the registration requirement take effect?

On 13 November 2026, which is Phase 2 of the three-phase commencement schedule under Notification No. G.S.R. 843(E), dated 13 November 2025 (para 1.6):

Phase Effective from Relevance to Consent Managers
Phase 1 13 November 2025 Section 2 definitions, including section 2(g), and sections 18 to 26 establishing the Board, came into force. Rules 1, 2 and 17 to 21 took effect
Phase 2 13 November 2026 Section 6(9) on Consent Manager registration, section 27(1)(d) on the Board’s jurisdiction over breaches of registration conditions, and Rule 4 took effect
Phase 3 13 May 2027 The substantive regime, including section 6(1) to (8) and (10), sections 11 to 17 on Data Principal rights, and section 27 except clause (d) of sub-section (1)

The book reads the twelve-month gap between Phase 1 and Phase 2 as deliberate lead time. For Consent Managers specifically, the registration requirement under Rule 4 took effect from 13 November 2026, after a twelve-month lead time intended for building the registration-compliant technical and governance infrastructure the First Schedule requires before the obligation became enforceable (para 1.6).

The registration obligation has therefore been in force since 13 November 2026, six months ahead of 13 May 2027, when the rest of the substantive regime commences. The book treats the two as separate planning dates for organisations that are, or rely on, Consent Managers (para 1.9.2). The commencement notification and Rule 4 are on Taxmann.com | Research under Indian Acts and Rules.

3. Who can register as a Consent Manager?

Part A of the First Schedule sets out nine conditions for registration (para 4.7.1):

# Condition
1 The applicant must be a company incorporated in India
2 It must have sufficient technical, operational and financial capacity
3 Its financial condition and management must be sound
4 Its net worth must not be less than Rs. 2 crore
5 Its business volume, capital structure and earnings prospects must be adequate
6 Its directors, key managerial personnel and senior management must have a general reputation and record of fairness and integrity
7 Its memorandum and articles of association must contain provisions requiring adherence to the conflict-of-interest and related obligations under the First Schedule, and such provisions may be amended only with the Board’s previous approval
8 The proposed operations must be in the interests of Data Principals
9 The applicant must hold an independent certification that its interoperable platform is consistent with such data protection standards and assurance framework as may be published by the Board

The book reads the cumulative effect plainly: these conditions ensure that Consent Managers are financially stable, well-governed and technically certified entities. The Rs. 2 crore net worth requirement, combined with the independent certification requirement and the Board’s approval over amendments to constitutional documents, creates a regulatory barrier to entry intended to filter out entities that lack the capacity to handle the fiduciary responsibilities of the role (para 4.7.1).

Condition 7 is the one with the longest tail. Requiring the conflict-of-interest obligations to sit in the memorandum and articles, amendable only with the Board’s prior approval, converts a regulatory condition into a constitutional one. A Consent Manager cannot quietly reorganise its way out of the obligation through a shareholder resolution.

Condition 9 is the one with the most practical uncertainty, because the standards and assurance framework against which the platform is certified are those “as may be published by the Board”. The certification requirement is therefore anchored to standards and a framework that the Board publishes, so an applicant’s project plan has to track what the Board has issued at the time of application, and the engineering work should not wait for it.

4. What obligations does a registered Consent Manager carry?

Part B of the First Schedule prescribes thirteen categories of obligation (para 4.7.2). The first four are set out in detail in the book:

Obligation Requirement
1 Enable Data Principals to give consent either directly to a Data Fiduciary onboarded onto the platform, or through another Data Fiduciary onboarded onto the platform that maintains the personal data with the Data Principal’s consent
2 Ensure that the manner of making available or sharing personal data is such that the contents are not readable by the Consent Manager
3 Maintain records of consents given, denied or withdrawn; notices preceding or accompanying consent requests; and sharing of personal data with transferee Data Fiduciaries
4 Maintain those records for at least seven years, or for a longer period if agreed with the Data Principal or required by law, and give the Data Principal access to the records and, on request, make them available in machine-readable form

The remaining nine are (para 4.7.2):

Obligation Requirement
5 Develop and maintain a website or application as the primary means of access
6 Not sub-contract or assign any of its obligations
7 Take reasonable security safeguards
8 Act in a fiduciary capacity in relation to the Data Principal
9 and 10 Avoid conflicts of interest with Data Fiduciaries, including measures to ensure that no conflict arises from directors, key managerial personnel or senior management holding interests in Data Fiduciaries
11 Publish information about promoters, directors, key managerial personnel, senior management and significant shareholders
12 Maintain effective audit mechanisms, with periodic reporting to the Board
13 Not transfer control of the company except with the Board’s previous approval

Obligation 1 deserves a sentence of explanation, because its two routes are not obvious from the text. The illustrations in the First Schedule describe a scenario involving an individual, two banks and a Consent Manager platform: the individual may either directly consent to one bank accessing her data, or route consent through a second bank that holds her data, instructing it to share with the first (para 4.7.2). The platform therefore has to support both direct consent and consent-mediated sharing between onboarded Data Fiduciaries.

Obligation 6 is more restrictive than it first appears. A prohibition on sub-contracting or assigning any obligation means the Consent Manager cannot outsource the consent ledger, the notice repository or the data-routing layer to a third party and treat the obligation as discharged. It must perform them itself.

Obligation 13 pairs with registration condition 7. Together they mean that neither the governing documents nor the control of the company can change without the Board’s prior approval, which places the Consent Manager’s corporate structure under continuing regulatory supervision rather than one-time scrutiny at the point of registration.

Taxmann.com | Research | Subscribe Now!

5. Why must the Consent Manager be unable to read the data?

Because Obligation 2 of Part B says so, and the book treats it as the critical technical constraint on the whole model.

The Consent Manager must ensure that the manner of making available or sharing personal data is such that the contents are not readable by it. The book spells out what that means in engineering terms: the Consent Manager facilitates the flow of consent and data between the Data Principal and Data Fiduciaries, but must not have the ability to read the personal data that flows through its platform. The technical architecture must enforce this through encryption, access restrictions or other mechanisms that render the data opaque to the Consent Manager (para 4.7.2).

The design consequence is significant and worth stating directly. An architecture in which personal data is decrypted on the Consent Manager’s servers, even transiently and even for a legitimate routing purpose, does not satisfy Obligation 2. The platform must route consent artefacts and data-sharing instructions without itself decrypting or reading the underlying personal data (para 4.7.2).

That constraint also shapes what a Consent Manager can and cannot build commercially. A platform that cannot read the data cannot analyse it, cannot derive insight from it and cannot monetise it. Combined with Obligation 8, which requires the Consent Manager to act in a fiduciary capacity in relation to the Data Principal, and Obligations 9 and 10 on conflicts of interest, the Rules push the business model towards charging for the consent infrastructure rather than for anything derived from the data passing through it.

6. How long must consent records be kept?

At least seven years, and potentially longer.

Obligations 3 and 4 of Part B require the Consent Manager to maintain records of consents given, denied or withdrawn, the notices preceding or accompanying consent requests, and the sharing of personal data with transferee Data Fiduciaries, and to maintain them for at least seven years, or for a longer period if agreed with the Data Principal or required by law. The Consent Manager must give the Data Principal access to those records and, on request, make them available in machine-readable form (para 4.7.2).

Three elements of that obligation are easy to under-build. The notice records are part of it, not just the consent records, which means the Consent Manager must version and retain the notice that accompanied each consent request. The sharing records are part of it, which means the ledger must capture each transfer to a transferee Data Fiduciary, not merely the consent that authorised it. And the machine-readable export is an obligation on request, which means the export has to exist as a product feature rather than as an engineering project undertaken when the first request arrives.

The reason the notice records matter beyond the Consent Manager’s own compliance is section 6(10). Where consent is the basis of processing and a question arises in a proceeding, the Data Fiduciary is obliged to prove that a notice was given and consent was obtained in accordance with the Act and the Rules. The burden is on the Data Fiduciary; the Data Principal does not need to prove that she did not consent (para 4.6). Where consent was routed through a Consent Manager, the Consent Manager’s records are the evidence that discharges that burden, which is a dependency a Data Fiduciary should examine before onboarding.

The book’s broader guidance on consent infrastructure applies with equal force here. The consent record must be immutable, so that it is not possible for anyone within the organisation to alter, delete or backdate a consent record after the fact, and it must include the notice version that was in effect at the time of consent, because proving that consent was obtained in accordance with the Act and the Rules requires demonstrating that the notice met the requirements of section 5 and Rule 3. A consent record that cannot be linked to the specific notice under which it was obtained is incomplete evidence. The book’s recommendation is to treat consent infrastructure as financial accounting records are treated: designed for integrity, subject to access controls, backed up and periodically tested for completeness (para 4.6).

7. What happens if a Consent Manager breaches its obligations?

Two of the Board’s five powers under section 27(1) are directed specifically at Consent Managers (para 14.2):

Clause Trigger Board’s power
27(1)(c) A complaint by a Data Principal regarding breach of Consent Manager obligations Inquire and impose penalty
27(1)(d) Receipt of an intimation of breach of Consent Manager registration conditions Inquire and impose penalty

Clause (d) commenced on 13 November 2026 alongside the registration requirement itself, while clause (c) commences with the rest of section 27 on 13 May 2027 (para 1.6).

On quantum, the Schedule to the Act does not create a separate penalty head for Consent Managers. Breach of any provision of the Act or the Rules other than those specifically enumerated carries a penalty of up to Rs. 50 crore (para 14.4). As with any penalty under the Act, section 33(1) engages the power only where the Board determines the breach to be significant, and section 33(2) requires the amount to be calibrated against seven factors including the nature, gravity and duration of the breach, the mitigation action taken and its timeliness, and the likely impact of the penalty on the person (para 14.4).

A Data Principal’s route to the Board is also conditioned. Section 13(1) confers the right to readily available means of grievance redressal provided by the Data Fiduciary or Consent Manager in respect of any act or omission regarding the performance of its obligations or the exercise of her rights (para 9.3). Rule 14(3) requires the Data Fiduciary and the Consent Manager to prominently publish on their website or application a reasonable period not exceeding ninety days for responding to grievances, and to implement appropriate technical and organisational measures to ensure the effectiveness of the system in responding within that period (para 9.3). And section 13(3) requires the Data Principal to exhaust that opportunity before approaching the Board (para 9.3).

So a Consent Manager carries its own grievance mechanism, its own published response period and its own first-tier dispute resolution duty, separately from those of the Data Fiduciaries onboarded onto its platform. Rule 14(1) applies to it too: the Consent Manager, where applicable, must prominently publish the details of the means by which a Data Principal may make a request for the exercise of rights, together with the particulars required to identify her (para 9.1).

8. What does a Consent Manager change for a Data Fiduciary?

Less than organisations sometimes hope, and in one respect more.

Section 6(7) makes the Consent Manager a channel through which the Data Principal may give, manage, review or withdraw consent. It does not transfer the Data Fiduciary’s obligations. Section 8(1) states the allocation of accountability in terms that leave no room: a Data Fiduciary shall be responsible for complying with the provisions of the Act and the Rules in respect of any processing undertaken by it or on its behalf by a Data Processor, irrespective of any agreement to the contrary. As the book puts it, the Data Fiduciary may delegate the processing; it cannot delegate the accountability (para 2.4).

Applied here, three obligations stay exactly where they were. The notice obligation under section 5 and Rule 3 remains the Data Fiduciary’s. The burden of proving valid notice and consent under section 6(10) remains the Data Fiduciary’s. And the obligation under section 6(6) to cease processing within a reasonable time of withdrawal, and to cause its Data Processors to cease, remains the Data Fiduciary’s, whichever channel the withdrawal arrived through (paras 4.5 and 4.6).

What does change is the operational dependency. If a withdrawal can arrive through a Consent Manager platform rather than through the organisation’s own interface, the organisation’s systems must be able to receive, recognise and act on it, and to do so within a reasonable time. The book notes that the phrase “within a reasonable time” is not defined and will be interpreted contextually: for automated processing systems, where cessation can be achieved through a configuration change, a reasonable time may be hours or days, while for complex multi-vendor processing chains requiring coordination across multiple Data Processors it may be longer. What is not reasonable is an indefinite delay, or a cessation that occurs only after the Data Principal escalates the matter to the Board (para 4.5).

Where that integration, and the record-keeping around it, has to be designed and documented rather than assumed, including compliance SOPs and automation of compliances, Taxmann Advisory provides implementation support.

9. How does this compare with the Account Aggregator model?

Closely, and the comparison is the fastest way for anyone in financial services to understand the design.

The book draws the parallel directly: the DPDP Act’s Consent Manager framework draws conceptual parallels with the Reserve Bank of India’s Account Aggregator framework, which enables consent-based financial data sharing through regulated intermediaries. Both models interpose a registered intermediary between the data subject and the data holder. Both require the intermediary to act in a fiduciary capacity. And both prohibit the intermediary from reading the data that flows through its platform (para 4.7.2).

Two differences follow. The DPDP framework extends the model beyond financial data to all categories of personal data. And it places the intermediary under the Data Protection Board’s supervision rather than a sectoral regulator’s (para 4.7.2).

The book makes the same point when explaining Obligation 2 in practice: the architecture mirrors India’s Account Aggregator model in financial services, where the intermediary routes consent artefacts and data-sharing instructions between Data Principal and Data Fiduciary without itself decrypting or reading the underlying personal data (para 4.7.2).

For an organisation that has already built or integrated with an Account Aggregator, the engineering patterns transfer. The regulatory relationship does not: registration, the certification of the interoperable platform, the conflict-of-interest provisions in the constitutional documents, and prior approval for a transfer of control all run to the Board.

10. What evidence should a Consent Manager maintain?

Appendix A to the book groups the Consent Manager obligations separately, in section 12 of its Consolidated Requirements Register, and lists the evidence items against each (Appendix A, section 12):

Requirement Evidence to maintain
Incorporation, Part A conditions and registration with the Board under section 6(9), Rule 4(1) and the First Schedule, Part A Certificate of incorporation; net worth certificate or audited financial statements demonstrating the minimum Rs. 2 crore; Board registration certificate or acknowledgement; independent certification of platform interoperability and data protection standards; memorandum and articles of association containing the required provisions
Record-keeping and Data Principal access under the First Schedule, Part B, items 3 and 4 Platform records demonstrating consent given, denied or withdrawn; notice records linked to consent requests; data sharing records with transferee Data Fiduciaries; a record retention policy confirming minimum seven-year retention; Data Principal access mechanism documentation; machine-readable export functionality documentation
The no-read constraint under the First Schedule, Part B, item 2 Technical architecture documentation demonstrating that data is not readable by the Consent Manager; encryption or access restriction configurations; an independent security assessment or certification
Fiduciary capacity, conflicts, sub-contracting, security, disclosure and audit under the First Schedule, Part B, items 6 to 12 Conflict of interest policy and declarations from directors, key managerial personnel and senior management; the published disclosure on the website or application required by item 11; security safeguards documentation; the audit mechanism framework and completed audit reports submitted to the Board; a sub-contracting prohibition policy

Two items on that list are worth singling out because they are documents rather than processes, and they take time to produce. The independent certification of platform interoperability and data protection standards has to be obtained from a third party against a framework the Board publishes. And the memorandum and articles have to be amended to carry the conflict-of-interest provisions before registration, with any later change requiring the Board’s prior approval. Neither can be completed in the weeks before an application.

11. Quick answers

What is a Consent Manager under the DPDP Act?

Section 2(g) defines a Consent Manager as a person registered with the Data Protection 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. Under section 6(7) the Data Principal may deal with a Data Fiduciary’s consent through the Consent Manager, and under section 6(8) the Consent Manager is accountable to the Data Principal and acts on her behalf.

When did Consent Manager registration become mandatory?

13 November 2026. Under the Timelines Notification G.S.R. 843(E), dated 13 November 2025, section 6(9) on registration, section 27(1)(d) on the Board’s jurisdiction over breaches of registration conditions, and Rule 4 all commenced on that date, one year after Phase 1 and six months before the substantive regime commences on 13 May 2027.

What are the conditions for registering as a Consent Manager?

Part A of the First Schedule sets out nine conditions: incorporation in India; sufficient technical, operational and financial capacity; sound financial condition and management; net worth of not less than Rs. 2 crore; adequate business volume, capital structure and earnings prospects; directors, key managerial personnel and senior management of good reputation and record of fairness and integrity; memorandum and articles containing the conflict-of-interest and related obligations, amendable only with the Board’s previous approval; proposed operations in the interests of Data Principals; and an independent certification that the interoperable platform is consistent with the data protection standards and assurance framework the Board may publish.

What is the minimum net worth for a Consent Manager?

Rs. 2 crore, under condition 4 of Part A of the First Schedule. Appendix A to Taxmann’s Digital Personal Data Protection lists a net worth certificate or audited financial statements demonstrating the minimum as the evidence an auditor or the Board would expect.

Can a Consent Manager read the personal data on its platform?

No. Obligation 2 of Part B of the First Schedule requires the Consent Manager to ensure that the manner of making available or sharing personal data is such that the contents are not readable by it. The technical architecture must enforce this through encryption, access restrictions or other mechanisms that render the data opaque to the Consent Manager, which mirrors the Reserve Bank of India’s Account Aggregator model.

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 Obligations 3 and 4 of Part B of the First Schedule. The records must cover consents given, denied or withdrawn, the notices preceding or accompanying consent requests, and the sharing of personal data with transferee Data Fiduciaries. The Consent Manager must give the Data Principal access to them and, on request, make them available in machine-readable form.

Does using a Consent Manager reduce a Data Fiduciary’s obligations?

No. Section 8(1) makes the Data Fiduciary responsible for complying with the Act and the Rules in respect of any processing undertaken by it or on its behalf, irrespective of any agreement to the contrary. The notice obligation under section 5 and Rule 3, the burden of proving notice and consent under section 6(10), and the duty to cease processing within a reasonable time of withdrawal under section 6(6) all remain with the Data Fiduciary.

Who regulates Consent Managers in India?

The Data Protection Board of India. Registration is with the Board under section 6(9) and Rule 4. The Board may inquire and impose penalty on a Data Principal’s complaint about breach of Consent Manager obligations under section 27(1)(c), and on an intimation of breach of registration conditions under section 27(1)(d). A transfer of control of the company requires the Board’s previous approval under Obligation 13 of Part B of the First Schedule. The registration of Consent Managers is the only licensing function the Board performs.


This article draws on Chapter 4 of Taxmann’s Digital Personal Data Protection – An Essential Guide to India’s DPDP Law by CA Narasimhan Elangovan (2026 Edition), which examines the notice and consent framework, the evidentiary burden under section 6(10), and the Consent Manager framework with the nine registration conditions in Part A and the thirteen categories of obligation in Part B of the First Schedule. It also draws on Chapter 1 on the three-phase commencement schedule, Chapter 9 on the grievance framework applicable to Consent Managers, Chapter 14 on the Board’s powers, and Appendix A, section 12, on the evidence a Consent Manager should maintain. Law stated as updated till 15 September 2026.

The DPDP Act, 2023, the DPDP Rules, 2025 and the notifications of 13 November 2025 are available on Taxmann.com | Research under Indian Acts and Rules.

Related reading: lawful processing and consent under the DPDP Act · scope and key definitions · commencement dates for the DPDP Act · the notification of the DPDP Rules, 2025.

More in this series: the Data Protection Board of India · how a DPDP compliance audit is conducted · Significant Data Fiduciary obligations · personal data breach intimation under Rule 7 · handling Data Principal rights requests · Data Fiduciary, Data Processor or both · children’s data and verifiable parental consent · the SPDI Rules and the DPDP Act · the Record of Processing Activities (ROPA) · the incident response plan · data retention and erasure · the privacy notice under Rule 3 · the data processing agreement · data localisation and cross-border transfers · employee data and workplace monitoring · exemptions under the DPDP Act · legitimate uses under section 7.

Disclaimer: The content/information published on the website is only for general information of the user and shall not be construed as legal advice. While the Taxmann has exercised reasonable efforts to ensure the veracity of information/content published, Taxmann shall be under no liability in any manner whatsoever for incorrect information, if any.

Leave a Reply

Your email address will not be published. Required fields are marked *

Everything on Tax and Corporate Laws of India

To subscribe to our weekly newsletter please log in/register on Taxmann.com

Author: Taxmann

Taxmann Publications has a dedicated in-house Research & Editorial Team. This team consists of a team of Chartered Accountants, Company Secretaries, and Lawyers. This team works under the guidance and supervision of editor-in-chief Mr Rakesh Bhargava.

The Research and Editorial Team is responsible for developing reliable and accurate content for the readers. The team follows the six-sigma approach to achieve the benchmark of zero error in its publications and research platforms. The team ensures that the following publication guidelines are thoroughly followed while developing the content:

  • The statutory material is obtained only from the authorized and reliable sources
  • All the latest developments in the judicial and legislative fields are covered
  • Prepare the analytical write-ups on current, controversial, and important issues to help the readers to understand the concept and its implications
  • Every content published by Taxmann is complete, accurate and lucid
  • All evidence-based statements are supported with proper reference to Section, Circular No., Notification No. or citations
  • The golden rules of grammar, style and consistency are thoroughly followed
  • Font and size that's easy to read and remain consistent across all imprint and digital publications are applied