Data Protection | DPDP Consent Manager
Consent Manager Under the DPDP Act: What Changed on 13 November 2026
On 13 November 2026, Rule 4 of the Digital Personal Data Protection Rules, 2025 and Section 6(9) of the DPDP Act came into force. The Data Protection Board of India can now register Consent Managers. In the weeks since, a familiar pattern has appeared in our DPDP compliance conversations: finance teams asking whether they have missed a registration deadline, and vendors telling them they have.
Most of that worry is misplaced. Rule 4 is not a general obligation. It creates a licensing regime for a small category of infrastructure companies, and the overwhelming majority of Indian businesses will never apply for it. What those businesses do need to understand is how the role affects them from May 2027, because a data fiduciary that cannot process a consent decision arriving through a Consent Manager will be unable to honour a statutory right.
The distinction matters commercially as well as legally. Several consent tools are now being marketed in India on the implication that buying them discharges a registration duty the buyer does not have. Anyone evaluating data privacy tooling in the next few months should be clear about what the statute actually creates.
Table of Contents
- Where the role comes from
- Who can actually register
- Consent Manager or consent management platform
- Which sectors will feel this first
- The engineering problem nobody has budgeted for
- What ordinary businesses should do now
- If you are considering registration
- What happens if you get it wrong
- Final Thoughts
- Frequently Asked Questions
Where the role comes from
The Consent Manager is defined in Section 2(g) of the DPDP Act, with its substantive provisions in Sections 6(7) to 6(9). The concept is straightforward. Instead of an individual managing dozens of separate consent relationships across every bank, retailer, hospital and app they have ever used, a Consent Manager provides one interface through which they can give, review, manage and withdraw consent across all of them.
The design is deliberately modelled on the account aggregator architecture that India already operates in financial services, and the comparison is instructive. An account aggregator moves financial data on instruction without reading it. A Consent Manager moves consent decisions on instruction, and the First Schedule requires that personal data passing through its platform is not readable by the Consent Manager itself.
Who can actually register
Part A of the First Schedule sets the eligibility conditions, and they are demanding by design. An applicant must be a company incorporated in India under the Companies Act 2013. It must demonstrate sufficient technical, operational and financial capacity to discharge its obligations. Its management must be sound in character and financial condition, the familiar fit-and-proper standard. It must have a net worth of not less than two crore rupees, calculated as total assets minus total liabilities as shown in its books of accounts.
Independence is the condition that disqualifies most interested parties. A Consent Manager cannot simultaneously act as a Data Fiduciary or Data Processor for the same individual whose consent it is carrying. A large platform cannot therefore register in order to manage consent for its own customer base, which is precisely what several organisations initially assumed the rule would permit.
The Part B operational conditions
Part B adds operational requirements. The platform must be interoperable with Data Fiduciaries generally rather than with a chosen few. Consent records must be retained for at least seven years. Obligations cannot be sub-contracted. The platform must be independently certified, and periodic audits must confirm that the registration conditions continue to be met.
Consent Manager or consent management platform
This is the single most useful distinction for a buyer to hold on to.
| Consent Manager | Consent management platform | |
|---|---|---|
| What it is | A statutory role under the DPDP Act | A software product category |
| Legal basis | Section 2(g), Sections 6(7) to 6(9), Rule 4, First Schedule | None |
| Registration | Must be registered with the Data Protection Board | No registration exists or is required |
| Net worth bar | Not less than two crore rupees | None |
| Scope | Carries consent across many Data Fiduciaries | Collects consent for one organisation |
| Can it read the data | No, expressly prohibited | Yes, it is the organisation's own tool |
| Who needs it | A narrow class of infrastructure providers | Most Data Fiduciaries, as an internal tool |
Both can be legitimate purchases. They solve different problems. A consent management platform helps you capture, timestamp, store and withdraw consent inside your own estate, which is work every Data Fiduciary has to do before May 2027. A Consent Manager is external infrastructure that individuals choose to use, and you will need to interoperate with it rather than buy it.
Which sectors will feel this first
The Consent Manager architecture will not land evenly. Its effect is largest wherever an individual holds many separate relationships that each rest on consent, and where switching or withdrawing has real consequences.
Financial services is the obvious case, partly because the account aggregator framework has already trained customers to expect a single consent dashboard, and partly because banks and NBFCs hold the deepest consent histories. Healthcare is the second, because patient data moves between hospitals, diagnostic labs, insurers and teleconsultation platforms, often with consent captured on paper at one end and nowhere at the other. Telecom, insurance and large consumer platforms follow, mainly on volume.
For business-to-business SaaS the direct exposure is smaller, since the personal data held is typically limited to client employees. The indirect exposure is not. If your enterprise customers are banks or hospitals, their readiness programmes will reach you as processor obligations, contractual warranties and security questionnaires long before the Board ever contacts you.
The engineering problem nobody has budgeted for
Interoperability sounds like a policy word, but the work it describes is technical and unfashionable. For an external withdrawal instruction to mean anything, your systems have to answer three questions on demand: which consents does this individual currently hold with us, which systems rely on each of them, and what happens downstream when one is revoked.
Most Indian organisations cannot answer the second question. Consent is captured at the point of collection, usually in a web form or an onboarding journey, and then the fact of consent travels no further than a boolean column. The data itself, meanwhile, has been copied into a warehouse, a CRM, a marketing automation tool and three analyst spreadsheets. Revoking consent in the source system changes nothing in any of those places.
Why consent stops travelling
Fixing that is a data lineage problem before it is a privacy problem, and it tends to need engineering time rather than legal time. Teams that start it in 2027 will be doing it badly and in a hurry.
What ordinary businesses should do now
Rule 4 commencing does not require you to register, to appoint a Consent Manager, or to redesign your consent flows this quarter. It does mean the architecture that individuals will use from May 2027 is now being built, and your systems will eventually have to talk to it.
- Confirm your own position. If you are not seeking to operate consent infrastructure for the public, Rule 4 registration does not apply to you.
- Treat vendor claims sceptically. Ask directly whether a supplier is registered with the Board, and recognise that as of now very few, if any, registrations have been granted.
- Make consent machine readable internally. Consent that exists only as a checkbox state in a legacy application cannot be reconciled against an external withdrawal instruction.
- Build withdrawal as a real workflow. A withdrawal has to propagate to downstream systems, analytics copies and processors, not just flip a flag on a user record.
- Record consent with its context. The notice version, timestamp, language and purpose all need to be retrievable, because a consent record without its notice proves very little.
- Review processor contracts for the obligation to act on withdrawal within a defined period.
If you are considering registration
A small number of Indian companies genuinely want this role, typically identity providers, account aggregators extending their mandate, and privacy infrastructure startups. For them the work is substantial and front-loaded.
What the application involves
Corporate structure usually needs attention first, since independence conditions may require separating the consent business from any fiduciary or processor activity in the same group. Audited financials must evidence the net worth threshold at the time of application. The platform needs independent certification, and an organisation with mature ISO 27001 controls and an ISO 27701 privacy extension will find that assessment considerably shorter than one starting from nothing.
Expect the Board to take time. Rule 4 came into force only in November 2026, the application channel is new, and each application has to be decided individually. Anyone planning a launch around a registration date should build in generous slack.
What happens if you get it wrong
Operating as a Consent Manager without registration from 13 November 2026 is a contravention, and the penalties regime under the Act is not nominal. The more common commercial risk, though, is quieter. Organisations that buy a product believing it discharges a statutory duty tend to stop work on the duty that actually applies to them, which is building defensible notice, consent and withdrawal processes before 13 May 2027.
Final Thoughts
If you want clarity on which obligations genuinely attach to your organisation, and a prioritised plan for the months remaining, our consulting team can take you through a DPDP readiness review. Get in touch for a consultation.
Frequently Asked Questions
Does my company have to register as a Consent Manager?
Only if you intend to operate as one. Rule 4 applies to companies providing consent infrastructure to individuals across multiple organisations. A bank, retailer, hospital or SaaS business acting as a Data Fiduciary does not register.
When did Rule 4 come into force?
On 13 November 2026, twelve months after the DPDP Rules 2025 were notified on 13 November 2025.
What is the minimum net worth to register?
Not less than two crore rupees, measured as total assets minus total liabilities in the applicant company's books of accounts, evidenced by audited financial statements.
Can a Consent Manager read the personal data it handles?
No. The First Schedule requires that personal data shared through the platform is not readable by the Consent Manager.
Is a consent management platform the same thing?
No. A consent management platform is software an organisation uses internally. A Consent Manager is a registered statutory role. Neither substitutes for the other.
Do individuals have to use a Consent Manager?
No. It is an option available to them from 13 May 2027, not an obligation. Organisations must be able to accommodate the choice when it is exercised.
How long must a Consent Manager keep consent records?
At least seven years, under Part B of the First Schedule.








