Most privacy laws leave consent to the business that collects it. India's DPDP Act adds a new player: the Consent Manager, a registered company that gives individuals one place to give, review, manage and withdraw consent across many businesses. The rules for registering Consent Managers start about 13 November 2026, six months before most other obligations.
How the model works
Picture a dashboard, in an app or on the web, where you can see every business you have consented to share data with, what you agreed to, and a button to withdraw. That's the idea.
- The Data Principal (the individual) signs up with a Consent Manager of their choice.
- A Data Fiduciary (the business) integrates with the Consent Manager so that consent requests, and withdrawals, flow through it.
- The Consent Manager keeps a record of each consent, its purpose and its status, and must be data-blind: it handles consent artefacts, not the underlying personal data.
The design borrows from India's Account Aggregator framework in financial services, where RBI-licensed aggregators move consented financial data between institutions without being able to read it.
Who can be a Consent Manager
The DPDP Rules set conditions for registration with the Data Protection Board. In summary, a Consent Manager must:
- be a company incorporated in India with sound finances (the Rules set a minimum net worth) and fit-and-proper management;
- run an interoperable platform that lets individuals give, manage, review and withdraw consent;
- act in a fiduciary capacity towards individuals and avoid conflicts of interest with the businesses it serves;
- keep consent records for at least seven years;
- not subcontract its core obligations, and maintain strong security;
- publish its key terms and be audited.
The Board can suspend or cancel a registration for breaches.
What it means for businesses
Using a Consent Manager is optional for a business, and individuals can still give consent directly to the business. But if your customers start using Consent Managers, you will need to accept consent, and withdrawals, through them.
Practical steps:
- Know your consents. You can't integrate what you can't describe. List each purpose that relies on consent, the data it covers and where the consent is recorded today.
- Make consent granular. A single "I agree" checkbox maps poorly onto a dashboard of purposes. Split consent by purpose now.
- Make withdrawal work. When consent is withdrawn, through a Consent Manager or directly, processing must stop within a reasonable time, including at your processors. Test this end to end.
- Watch the register. From November 2026, track which Consent Managers register and which sectors they target, then decide whether to integrate early.
Open questions
The technical standards for interoperability between Consent Managers and businesses will shape how useful the model is. As with Account Aggregators, adoption may come sector by sector, likely starting where consent volumes are high, such as fintech, health and telecom.
Learn more
Consent is one of the core topics of our free Data Protection & Privacy Fundamentals course. For the wider picture, read India's DPDP Act in plain language and the DPDP Rules timeline.
Written and reviewed by the DigiTrust Asia editorial team. How we research, review and correct articles.
General information, not legal advice. Laws and official guidance change; check the current text before acting.
Learn privacy properly
Data Protection & Privacy Fundamentals is a free, law-neutral course with a final exam and certificate.
Create a free account