The short version
- A Consent Manager is a company registered with the Data Protection Board. It works for the individual.
- A consent platform is software a business runs to meet its own consent obligations. It works for the business.
- A Data Fiduciary needs a consent platform before May 2027. It does not need to appoint, buy or become a Consent Manager.
On 13 November 2026, the Data Protection Board of India opened registration for Consent Managers. Within days, the phrase was everywhere: in vendor decks, in RFPs, in LinkedIn posts. We now get asked the same question in almost every demo: "Are you a Consent Manager?"
It is a fair question, and it deserves a straight answer. That answer starts with understanding that the law uses "Consent Manager" for something very specific, and it is not the software you buy to collect and manage consent inside your business.
If you are a Data Fiduciary working towards May 2027, getting this distinction right will save you from buying the wrong thing, or waiting for something you do not need.
What the law means by a Consent Manager
A Consent Manager is a company registered with the Data Protection Board that works for the individual, not for the business.
The DPDP Act defines it as a single point of contact that lets a Data Principal give, manage, review and withdraw consent through an accessible, transparent and interoperable platform. Think of it as one dashboard where a person can see every company holding their consent and switch any of them off.
The closest comparison in India is the Account Aggregator in financial services. It sits between the individual and many institutions, and it acts on the instruction of the individual.
Three things follow from the Rules:
- It is a regulated entity. An applicant must be a company incorporated in India, with a net worth of at least ₹2 crore and a platform that has been independently certified. The Board can suspend or cancel a registration.
- It owes its duty to the Data Principal. The Rules say a Consent Manager acts in a fiduciary capacity towards the individual. It must avoid conflicts of interest with Data Fiduciaries, including their promoters and key managerial personnel.
- It carries its obligations itself. It must keep consent records for at least seven years and cannot sub-contract its core obligations.
One more point matters a great deal. Using a Consent Manager is a choice that belongs to the Data Principal. The Act says an individual may route consent through one. Nothing in the law requires a Data Fiduciary to appoint, buy or become one.
As of this writing, the registration window has only just opened and the registered Consent Manager ecosystem does not yet exist in practice.
What a consent platform is
A consent platform is software a Data Fiduciary runs to meet its own consent obligations under the Act.
It is often called a consent management platform, or CMP, which is exactly where the confusion begins. The names are almost identical. The roles are not.
A consent platform works for the business. It is the system of record that lets you prove, for every customer and every purpose, that you asked properly and that you respected the answer. In practice it does the following:
- Presents notices and collects consent at every touchpoint: web, app, branch, call centre, paper
- Stores each consent record with its purpose, language, timestamp and version of the notice
- Lets individuals review and withdraw consent through a privacy portal
- Tells downstream systems whether they may process a record before they do so
- Handles requests and grievances from Data Principals
- Keeps the audit trail you will need if the Board ever asks
A consent platform needs no registration with the Board. It is a product, licensed and deployed like any other enterprise software, on your premises or in your cloud. The legal obligations stay with you as the Data Fiduciary. The platform is how you carry them out.
Side by side
The simplest test is to ask who each one works for.
| Attribute | Consent Manager | Consent platform |
|---|---|---|
| What it is | A regulated entity | A software product |
| Works for | The Data Principal (the individual) | The Data Fiduciary (the business) |
| Registration with the Board | Mandatory | Not required |
| Who can be one | An Indian company with net worth of ₹2 crore or more and a certified platform | Any vendor, or your own in-house build |
| Scope | One individual across many businesses | One business across all its customers |
| Relationship with fiduciaries | Must avoid conflicts of interest with them | Sold to and operated by them |
| Mandatory for a fiduciary? | No. It is the individual's choice to use one | The Act does not name a tool, but you cannot evidence consent at scale without one |
| Where it runs | On the Consent Manager's own infrastructure | On your premises or in your cloud |
Why the confusion costs you
Mixing up the two leads to three mistakes we see regularly.
Waiting for Consent Managers before doing anything. Some teams have paused their consent work until registered Consent Managers appear. That is a mistake. Your obligations to give notice, obtain consent and honour withdrawal apply from 13 May 2027 whether or not a single customer ever uses a Consent Manager.
Writing "must be a registered Consent Manager" into an RFP. It is tempting to add this as a mandatory vendor criterion. It rules out the very products that solve the problem, and it asks for a registration that says nothing about whether the vendor can manage consent inside your systems.
Assuming a registered Consent Manager makes you compliant. It does not. A Consent Manager carries a consent decision from the individual to you. What you do with that decision, across your CRM, your core systems, your marketing tools and your vendors, is still your job.
There is also a structural point worth thinking about. A Consent Manager must avoid conflicts of interest with Data Fiduciaries. A consent platform earns its revenue from Data Fiduciaries. When one company claims to be both, it is reasonable to ask how those two duties are kept apart.
So what do you actually need?
You need a consent platform now, and you need it to be ready for Consent Managers later.
The order matters. Before May 2027, a Data Fiduciary should be able to do the following without anyone else's help:
- Give a clear notice, in the customer's language, at every point where personal data is collected
- Record consent against a specific purpose, and keep that record
- Send notices to existing customers whose data you already hold
- Check consent before any downstream system processes the data
- Act on a withdrawal everywhere, including with your vendors and processors
- Give each Data Principal a place to review consent and raise requests or grievances
- Produce the evidence for any of the above when asked
None of these depend on a Consent Manager. All of them depend on a working consent platform connected to your real systems.
The one thing to plan for is the day a customer does choose a Consent Manager. On that day, a consent or a withdrawal will arrive from outside your own channels, and your systems need to accept it and act on it as if it came through your own app.
How the two work together
The Consent Manager and the consent platform are two ends of the same pipe, not competitors.
Here is how a withdrawal will travel once the ecosystem is live:
- A customer opens their Consent Manager and withdraws consent for marketing from your company.
- The Consent Manager sends that instruction to you through its interoperable interface.
- Your consent platform receives it, updates the consent record and logs the event.
- The platform pushes the change to every system that relies on that consent: CRM, campaign tools, vendors.
- Those systems stop processing for that purpose, and you hold the evidence that they did.
Steps 1 and 2 belong to the Consent Manager. Steps 3 to 5 belong to you, and they are where most of the real work sits. A fiduciary with no consent platform would receive the instruction and have nowhere to put it.
This is why the useful question for a vendor is not "are you a Consent Manager?" It is "will your platform accept instructions from any registered Consent Manager my customers choose?"
Five questions to ask any vendor
These questions separate the two roles quickly in any sales conversation.
- Are you selling me a product, or are you a registered entity? If the answer is "both", ask which legal entity does which.
- Who do you owe your duty to? A consent platform vendor works for you. A Consent Manager works for your customer. Both are legitimate. They are not the same.
- Where do my consent records live? With a platform, they should sit in your environment and under your control.
- Will you accept instructions from any registered Consent Manager? You do not choose which one your customers use, so your platform cannot play favourites.
- What happens downstream when consent changes? Collecting consent is the easy part. Ask to see a withdrawal reach your CRM and your vendors.
Where Atlas Privacy Manager stands
Atlas Privacy Manager is a consent platform. It is not a registered Consent Manager, and we would rather say that plainly than blur the line.
Atlas works for the Data Fiduciary. It manages the notice and consent lifecycle, gives your customers a Privacy Portal to review and withdraw consent, validates consent before downstream processing, records processing activities, and handles requests and grievances. Notices are supported in English and all 22 scheduled Indian languages. It deploys on your premises or in your own cloud, so your consent records stay with you.
Atlas is also built to integrate with Consent Managers. As registered Consent Managers come online and the interoperability standards are published, a consent or withdrawal arriving through one of them will be treated like any other: recorded, pushed to your systems and evidenced.
We think that is the right place for a platform to sit. Your customers will choose their own Consent Manager. Your job, and ours, is to make sure that whichever one they choose, their decision is respected everywhere it needs to be.
To see how this works in practice, read more about consent management in Atlas or write to us at sales@frslabs.com.