CMP vs Consent Governance vs DPDP Consent Manager: How to Choose Your Stack
How a cookie CMP, consent governance and a DPDP Consent Manager differ, when you need each, and how to choose the stack you actually need.

I hear the same story from privacy teams. A team buys a cookie banner and treats the job as done. A month later the DPO still has to produce a consent record: which notice the person saw, which purpose they agreed to, and whether a later "no" reached the campaign tool. Then someone asks whether the company should become a Consent Manager.
I see three layers there, on two official clocks. Under the Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E), 13 November 2025), Rule 4, on registering Consent Managers, applies from about 13 November 2026. Rules 3 and 5 to 16, including the notice duty, apply from about 13 May 2027. Section 6(10) of the Act puts the burden of proving notice and consent on the Data Fiduciary.
If you are the CISO, DPO or counsel choosing the stack, I'll show you what each layer does, when you need one, two or all three, and where the shortlists live.
TL;DR
- A cookie or web consent management platform is a capture surface. It asks for a first choice on a website or app, and it should block optional cookies and tags until that choice is made. The file it leaves you is a banner or SDK log.
- Consent governance is the record behind that choice: the versioned notice, the purpose, the withdrawal path, a preference centre if you need one, and proof a later "no" reached the systems that still have the data.
- A Consent Manager is a Board-registered role, not a product SKU. Under section 2(g) of the Act it is "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."
- Most Data Fiduciaries need the first two layers, and a way to honour an artefact sent by the third. Buying a banner does not register you as a Consent Manager, and licensing a record does not either.
- Buy or become a registered Consent Manager when that is the business you intend to run for Data Principals. If a partner only asked whether you can work with one, the job is to receive and honour the artefact on your own record.
The three layers, in plain language
A cookie or web CMP sits on a property you operate. It presents a banner or an in-app prompt, records accept, reject or close, and should stop optional cookies and tags until there is a choice. That is a real job. It is also a narrow one. The log lives on the site or the SDK. It does not, by itself, tell you which notice version a person saw on a branch form, or whether a later withdrawal reached a campaign tool.
Consent governance is the record you keep as the Data Fiduciary. It holds the notice, the purpose, the choice and the proof together, across web, app, phone and paper if you collect there. When the person changes their mind, the record has to carry that change to every system and processor still using the data. Section 6(4) of the Act gives the Data Principal the right to withdraw consent at any time, "with the ease of doing so being comparable to the ease with which such consent was given." Section 6(10) puts the burden of proving notice and consent on you if a question arises in a proceeding. A banner log is rarely that file.
A DPDP Consent Manager sits in a different place in the statute. It is an intermediary the Data Principal uses. Section 6(7) lets a person give, manage, review or withdraw consent to a Data Fiduciary through a Consent Manager. Section 6(9) requires every Consent Manager to be registered with the Board. You honour the artefact that comes back to you. You do not become a Consent Manager by buying a CMP, and you do not become one by buying a governance platform.
This is a DPDP chooser. If you also have duties under EU or US law, put those choices on the same record so a person is not managing two files for one relationship.

Side-by-side: what each layer actually does
| Cookie or web CMP | Consent governance | DPDP Consent Manager | |
|---|---|---|---|
| Job | Capture a first choice on a website or app, and block optional cookies and tags until that choice is made | Keep the notice, the purpose, the choice and the proof together, and carry a later withdrawal to every system that still has the data | Act as a Board-registered single point of contact so a person can give, manage, review and withdraw consent across many companies |
| Who operates it | You, on your own site or SDK | You, as the Data Fiduciary, on your own record | A person registered with the Board, accountable to the Data Principal |
| Typical surfaces | Banner, cookie scan, tag manager | Versioned notice, preference centre, withdrawal path, exportable record | The Consent Manager's own platform, which relays an artefact to you |
| Evidence it produces | A banner or SDK log of accept, reject or close | Notice version, purpose, time, channel, and proof a "no" reached CRM, campaign tools and processors | The artefact you received, and what you did with it on your record |
| DPDP provision | A capture surface for consent. It does not, on its own, meet the notice or proof duties in Rule 3 and section 6 | Section 6 consent and withdrawal; Rule 3 notice; section 6(10) burden of proof | Section 2(g) and sections 6(7) to 6(9); Rule 4 registration, from about 13 November 2026 |
| Enough on its own? | Only if a website is your only channel and a banner log is all you will be asked for | For most Fiduciaries, yes, if you also have a capture surface and a way to honour a Consent Manager artefact | No, not for your own notice, record or withdrawal path. You still have to honour the artefact and keep your proof |
Read the table as a stack. The layers do not stand in for one another. The rest of this post is about when one, two or all three show up in the same programme.
What a cookie or web CMP is, and where it stops
A cookie or web CMP is the tool most teams buy first, because a website is the first place a lawyer or a customer sees a consent prompt. In a good setup it scans the site, classifies cookies and tags, presents a banner the person can actually use, and holds optional scripts until there is a choice. The better ones keep a log you can export and let you run a later change on that same property.
That is the job, and it is worth doing well. It is also where the tool stops. A CMP does not write the Rule 3 notice you owe on an app, a call or a paper form. The notice has to be "presented and be understandable independently of any other information," in "clear and plain language," with "an itemised description of such personal data" and the specified purpose. A CMP does not, on its own, carry a withdrawal into CRM or a campaign tool. It does not register you with the Board as a Consent Manager.
If the only personal data you process on a site is strictly necessary for the page to work, a CMP may be all you need on that property today. The moment you collect for marketing, for an account, or on a second channel, you will be asked for a record the banner log cannot produce.
For a shortlist of cookie and web CMPs used in India, start with consent management platforms for India. The two-way split between a cookie consent manager and a DPDP Consent Manager is in Cookie consent manager vs DPDP Consent Manager. This post does not retell those bake-offs.
What consent governance adds
Consent governance is the layer that makes a later question answerable. It keeps one record per Data Principal, stamps the notice version the person saw, records the purpose they agreed to, and has a path for withdrawal that reaches the systems and processors still holding the data. A preference centre, if you run one, sits on the same record, so a person can change channel or frequency without a second, disconnected file.
The legal pressure for this layer is already in the Act and the Rules, even though the notice clock in Rule 1 runs to about 13 May 2027. Section 6(4) makes withdrawal as easy as giving consent. Section 6(6) requires the Data Fiduciary, within a reasonable time, to cease processing and to cause its Data Processors to cease, unless another ground still applies. Section 6(10) is the line I come back to in every review: if a question arises, you have to prove the notice and the consent. I have sat with teams who could show a banner screenshot and could not show which notice version a person had actually been given. That gap is what this layer is for.
You still need a capture surface. Governance does not replace the banner on the website, and it does not replace a prompt in the app. It is the system of record those surfaces write to, and the system that has to talk to a Consent Manager if an artefact arrives.
A later post will compare consent governance platforms for DPDP in India. This one stops at the job: the record, the notice, the withdrawal, the evidence, and a way to honour an artefact.
What a DPDP Consent Manager is
A Consent Manager is not a feature in a privacy suite. It is a statutory role. The definition in section 2(g) is the one that matters: a person registered with the Board, acting as a single point of contact so a Data Principal can give, manage, review and withdraw consent. Section 6(8) makes the Consent Manager accountable to the Data Principal. Section 6(9) and Rule 4 set the registration itself. Under Rule 1(3), Rule 4 applies one year after publication in the Official Gazette, from about 13 November 2026.
I am not naming anyone as Board-registered in this post. Registration is the Board's process, and the list, when the Board keeps one, is the Board's to publish. Rule 4 says the Board, if satisfied, "register the applicant as a Consent Manager, under intimation to the applicant, and publish on its website the particulars of such Consent Manager." Until you are reading that list, treat vendor claims of readiness as a demo question, not as registration.
NeGD empanelment is a separate process from Board registration. If a partner is talking about empanelment, start with our note on NeGD-empanelled Consent Managers. For the role itself, see the role of a Consent Manager under the DPDP Act and Consent Manager under the DPDP Act. For a shortlist of tools in that category, use Consent Manager tools. This post does not repeat those bake-offs.
What you, as a Data Fiduciary, actually have to do with this layer is narrower than the conversation often becomes. Section 6(7) lets a Data Principal deal with you through a Consent Manager. When that happens, your record has to accept the artefact, enforce it, and keep the proof. The burden in section 6(10) stays with you. Working with a Consent Manager does not take the notice duty, the withdrawal duty, or the proof duty off your books.
How to choose the stack
Use the situation you are actually in. If two of these apply, take the heavier of the two stacks, then confirm the interfaces: the banner writing to the record, and the record ready to honour an artefact.
We only have a website today
Start with a cookie or web CMP, and be honest about what the site collects. If the only personal data on the property is strictly necessary for the page to work, the CMP may be enough on that channel for now. If the site also collects for an account, for marketing, or for any purpose you will have to explain later, add the governance record early, even if the first capture surface is still the banner. You will need the notice version and a withdrawal path before May 2027, and it is cheaper to collect into the right record than to reconstruct it.
We collect on app, call centre and branch as well
You need the governance layer. A website banner will not cover a recorded call, an in-app prompt or a paper form at a branch. Put every channel on one record, with the notice version stamped for each. Keep a CMP or SDK where it belongs, on the web and in the app, as the capture surface for those properties. The question to ask in a demo is simple: if a person withdraws on the app, does the campaign tool and the branch CRM hear it, and can you export the proof?
Marketing wants a preference centre
A preference centre is part of the governance layer, not a second banner. It lets a person change purpose, channel or frequency without withdrawing from the relationship altogether. If marketing only wants a softer opt-down on email, you can start there, but the choices have to live on the same record as the original consent and the withdrawal path. Otherwise you will have a "no" in the preference centre and a "yes" still going to the campaign tool. A later post on preference-management platforms will cover that bake-off. The decision here is whether you need the layer at all, and the answer is yes once marketing is asking for it.
A partner asked if we work with a Consent Manager
That is an interop question, not a reason to register as one. Ask whether your record can receive an artefact from a Board-registered Consent Manager, write it to the same file as every other channel, and enforce it the same way. Ask what happens if the artefact arrives and a system has no API. Then say yes or no to the partner with evidence from a demo, not with a slide. If the partner was talking about NeGD empanelment, use the NeGD note and keep it distinct from Board registration under Rule 4.
We were told to 'just buy OneTrust / a CMP'
A large suite can include a banner, a preference portal and a record. It can also be sold as a CMP and leave the record and the Consent Manager question untouched. Buy the suite if it can show, in a trial, a versioned notice, a withdrawal that reaches your actual systems, and a way to honour an artefact. Do not treat the brand name as the layer. If all you need today is a website banner, a focused CMP will do that job at a lower cost. If you need the record, score the suite as a governance platform, not as a banner.
We thought we had to register as a Consent Manager
Most Data Fiduciaries do not. You register as a Consent Manager if you intend to be that intermediary for Data Principals, you meet the conditions in Rule 4 and the First Schedule, and the Board registers you. That is a business and a regulatory role. It is not the way you put your own house in order. For your own programme, keep the capture surface, keep the record, and be ready to honour an artefact. If being a Consent Manager is in fact the business you want to run, start with the Consent Manager tools shortlist, not with a CMP.
What the Rule 1(4) clocks mean for the buy
The Rules split the clocks, and the buy has to follow that split. Rule 1 of the Digital Personal Data Protection Rules, 2025, as corrected by G.S.R. 892(E) dated 10 December 2025, reads:
"Rule 4 shall come into force one year after the date of publication in the Official Gazette."
"Rules 3, 5 to 16, 22 and 23 shall come into force eighteen months after the date of publication in the Official Gazette."
The Gazette was published on 13 November 2025, so those lines fall about 13 November 2026 for Rule 4, and about 13 May 2027 for Rules 3 and 5 to 16, including the notice duty. The December 2025 corrigendum replaced "of this Gazette" with "in the Official Gazette" in both lines. It did not change the periods. On 12 November 2026, MeitY's documents library did not list a later instrument that moves either date.

Do not collapse the two dates into one programme date. Rule 4 is the registration process for Consent Managers. It is not the deadline for your own notice, and it is not a reason to pause the record you will need in May 2027. The notice, withdrawal and proof work is the May 2027 job. The November 2026 job, for a Data Fiduciary, is narrower: know how you will honour an artefact if a registered Consent Manager sends you one, and do not wait for someone else's registration before you start collecting into a record you can defend.
If your board has been told that "Consent Manager registration in November" is the compliance date, correct it now. Two clocks, two jobs.
Where Redacto fits
Full disclosure: we build Redacto.
Three customers, in their own words:
Surya N, Director, Product Management, TimePay: "As a product team, we had one worry: would privacy compliance hurt the onboarding journey? It didn't. Redacto's consent flows fit into our app with very little engineering effort, and we change notices from the console instead of shipping a new build. Our users get a clear choice at every step, and we get a consent record we can stand behind."
Prem Kumar, Data Protection Officer, Pine Labs Group: "Privacy across a group of businesses is hard because every team has its own systems and its own idea of what personal data it holds. Redacto gave us one view of where personal data is collected, why we collect it and where it goes. When a customer request or an audit question comes in, I answer it with evidence, not a round of emails."
Saif, Head, Infosec Compliance & Privacy, Razorpay: "Our vendor security and privacy reviews used to live in spreadsheets and long email threads. With Redacto, every assessment, every piece of evidence and every follow-up sits in one place. When a customer sends us a security questionnaire, we answer it from that same record. We focus on the vendors that actually carry risk, and the paperwork no longer runs the week."
These are our customers speaking, so weigh them that way and ask for a reference call.
By our own count we've done 40+ successful implementations.
Redacto Consent Governance is the record layer: versioned notices, a preference centre, withdrawal reach, and the evidence you keep when a question arises. Cookie Consent and DSAR & Grievance can be bought on their own. Used together, they share one record, so a withdrawal or an erasure request sees everything about the person. When a registered Consent Manager passes on a person's consent or withdrawal, it goes into the same file as every other channel, and the same downstream rules act on it. We are not a Board-registered Consent Manager.

Quote-based.
There isn't a public review base yet.
The honest limits follow from that. There is no public price, and there is no public review corpus, so you should ask for a quote, a trial and a reference call. If you only need a website cookie banner, you will be better served by a CMP. If your job is to be a Consent Manager, look at the Consent Manager shortlist, not at this product.
Final thoughts
The expensive mistake I still see is buying one label and hoping it covers three jobs. A banner is a capture surface. A governance platform is a record, a notice and a withdrawal path. A Consent Manager is a Board-registered role a Data Principal may use to deal with you. Most Fiduciaries need the first two, and a way to honour the third. Very few need to become the third.
Get the clocks right as well. Rule 4, about 13 November 2026, is the registration process for Consent Managers. Rules 3 and 5 to 16, about 13 May 2027, are when the notice and the rest of that operational bundle come into force. Build the record for the later date, and be ready to honour an artefact for the earlier one. Then use the shortlists this post points to, and make the vendor prove the layer you are actually buying.