Research / Consent

Consent Managers are here. The hard questions are not answered.

The Data Protection Board began registering Consent Managers on 13 November 2026. On paper the idea is simple: one place where a person can give, review and withdraw consent across every business they deal with. In practice, the questions we raised in early 2025 are still open. Who pays for it, how does it scale, and what does it actually change for the businesses that remain responsible for the data?

Consent 8 minute read

This article updates our February 2025 analysis, Consent Manager under DPDPA: challenges and alternatives, now that the DPDP Rules are final and registration is open.

The short version

  • Consent Managers can now register with the Board, but the law leaves the hard questions open: who pays, how one connects to thousands of businesses, and why a person would use one instead of dealing with each business directly.
  • A Consent Manager adds a route for consent. It does not remove a business's own consent records, requests or grievances, which stay with the Data Fiduciary.
  • Build your own consent platform for May 2027, and make sure it can accept consent from a registered Consent Manager when your customers start using one.

What a Consent Manager is meant to do

The DPDP Act describes a Consent Manager as a person registered with the Data Protection Board who acts as a single point of contact for a Data Principal to give, manage, review and withdraw consent, through an accessible, transparent and interoperable platform.

The DPDP Rules, 2025 fill in who can register. Rule 4 and Part A of the First Schedule require a company incorporated in India with a net worth of at least ₹2 crore, adequate technical, operational and financial capacity, and sound management. Part B sets out what a registered Consent Manager must do, including keeping records of consents and ensuring it cannot read the personal data it helps share. Rule 4 came into force on 13 November 2026.

What the law does not say. It does not say who pays a Consent Manager, how one should connect to the businesses its users deal with, or what happens to a person's consents if they stop using one. The word "platform" is not defined either. These are not small gaps. They decide whether the model works.

Three sides, three sets of problems

The easiest way to test the idea is to look at it from each party's position in turn.

For the individual, it can add confusion instead of removing it. A person does not choose which Consent Managers a business supports. If their bank works with one and their insurer with another, they need two, and the single point of contact is gone. Integration with every business they deal with will take years, and a badly built app will frustrate people and lose their trust quickly. If there is a fee, few will pay it when they can manage consent with each business directly for free.

For the Consent Manager, the business case is thin. Connecting to hundreds of thousands of businesses needs serious investment and a common technical standard that has not yet been widely adopted. Registration brings net worth, audit and record-keeping obligations close to those of a regulated financial intermediary. If neither individuals nor businesses pay, it is hard to see how a Consent Manager sustains itself. If one or two players come to dominate, that invites more regulation and public concern about concentration.

For the business, there is no saving. A Data Fiduciary still needs its own consent platform, because most customers will continue to deal with it directly. Supporting Consent Managers means more integrations, and when consent arrives by two routes, keeping a single source of truth becomes harder. Many businesses will also be wary of connecting to a third party that holds records about their customers, however well regulated.

Many to many: why scale is the real test

Take only India's listed companies, around 7,500 by a rough 2024 count, and ignore the millions of other businesses that process personal data. Each one would need to connect to every Consent Manager its customers choose, because the design has no central exchange sitting between them.

People Consent Managers Businesses CM 1CM 2CM 3 BankInsurerRetailerTelecomHospital
Many people, several Consent Managers, many businesses. With no central exchange, every business must connect to every Consent Manager its customers choose.

Compare this with central KYC. When a customer updates their KYC record, the change flows through CERSAI to the institutions that need it. One update, one hub. Consent Managers have no equivalent hub, so every connection is built and maintained separately, at a cost that runs into years and significant investment.

The shape of the market matters too. A single dominant Consent Manager would attract heavy regulation. Three or four, as in telecom, would bring rules on portability between them. Either way, Consent Managers could end up more tightly regulated than the businesses they serve.

Who pays?

The Act does not say, and the answer shapes everything else. The open questions are practical ones:

  1. Does the individual pay, or the business? Neither has an obvious reason to.
  2. What happens if a subscription lapses? If a card expires, do the consents managed through it stay valid, move, or end?
  3. What happens to consents given directly? A person can still deal with each business without a Consent Manager, so two sets of records will exist side by side.
  4. How is data passed to several businesses at once? And who answers for it if something goes wrong in between?

Food delivery apps show how people respond to a middle layer that costs money. A ₹100 sandwich ordered through an app that charges the restaurant 25–35% often ends up priced at around ₹150 plus ₹20 for delivery. Ordered directly, it is ₹100 plus ₹20. Given a free direct route that works, most people will take it. Consent is no different.

The Account Aggregator comparison

The Consent Manager model looks closely related to Account Aggregators, which grew out of the Data Empowerment and Protection Architecture (DEPA) and let a person approve the sharing of financial data between institutions. The comparison is useful, because it shows both what works and what is missing.

AttributeAccount AggregatorConsent Manager
Built onDEPA consent architectureThe DPDP Act and Rule 4 of the DPDP Rules, 2025
Overseen byReserve Bank of IndiaData Protection Board of India
Problem it solvesSharing verified financial data quickly, for example to assess a loanOne place to manage consent across many businesses
Can it read the data?No, it passes on data it cannot readNo, the personal data it helps share must not be readable by it
Who clearly benefitsLenders and borrowers, through faster, better-informed creditNot yet clear, since people can already deal with each business directly
Who paysSet by commercial arrangements in the networkNot addressed in the Act
Mandatory for a business?NoNo

Account Aggregators solve a real problem. A person applying for a loan at Bank A can let it fetch salary account data from Bank B through an Account Aggregator, approving the request in the app. That is data sharing for a clear purpose, and it saves real time and cost. Onboarding and KYC still sit with the bank itself.

Even so, they have struggled to scale. Only a small number of Account Aggregators operate for over a billion people, and in 2025 PhonePe, with hundreds of millions of users and strong backing, chose to give up its Account Aggregator licence, citing difficulty in getting enough data providers on board. If a model with a clear use case finds integration this hard, a model without one will find it harder.

Where consent intermediaries do make sense

We are not arguing that consent intermediaries have no place. They work where sharing data between organisations solves a problem the individual actually has.

Health. Moving X-rays, MRI scans, blood reports and discharge summaries between hospitals with the patient's consent saves time and repeat tests. The ABHA app from the National Health Authority already does part of this.

Insurance. Sharing health or claims history with an insurer can speed up claims, reward healthy habits or make it easier to switch provider, while the old provider is stopped from misusing what it holds.

Existing intermediaries. Account Aggregators could extend to new consent purposes after onboarding, building on networks that already exist rather than starting new ones.

Software agents. AI agents are starting to search, order and pay on people's behalf. In time they may manage consent for personal data too, working directly with businesses or with services such as DigiLocker. That could change the picture again, and it should not be dismissed.

What to do before May 2027

Whatever happens to Consent Managers, the core obligations stay with the Data Fiduciary. The Act and the Rules do not move disputes, processing, Data Principal requests or grievances to a Consent Manager. They remain yours, and the main DPDP obligations apply from 13 May 2027.

  • Run your own consent platform for capture, records and withdrawal, across every channel where you collect personal data.
  • Keep one record of consent per person, whichever route it arrives by.
  • Make sure your platform can accept consent from a registered Consent Manager, so you are ready when your customers start using one.
  • Do not pay for Consent Manager integrations before your customers ask for them.
  • Keep requests and grievances in your own workflow, with your own evidence.

The goal of the DPDP Act should be trust between businesses and the people whose data they hold, because trust is what brings people into the digital economy and keeps them there. Compliance for its own sake is a cost. The test for Consent Managers, as for everything else in the framework, is whether they build that trust. In their current form, the case is not yet made.

Where Atlas Privacy Manager stands

Atlas Privacy Manager is a consent platform for Data Fiduciaries. It captures consent at every touchpoint, keeps one record per person with full proof, pushes changes to your connected systems and handles requests and grievances through your own Privacy Center. It is built to work with registered Consent Managers as they come online, so consent that arrives through one ends up in the same record as consent given directly.

For the difference between the two roles, read Consent Manager vs consent platform: they are not the same thing. To see how this works in practice, learn more about consent management in Atlas or write to sales@frslabs.com.

Back to all research

See consent from every route land in one record

In a 30 minute demo we show consent captured directly, kept as one record with full proof, and enforced across connected systems, ready for Consent Managers when they arrive.

Trusted by 250+ customers worldwide

TTK Duruva Ujjivan Jana UIDAI Equitas Yes Bank