Your Challenge Our Progress

Jamtech Logo ×

What Is a Consent Manager? DPDP Act Explained for Indian Businesses

A consent manager is a company registered with India's Data Protection Board that lets people give, review and withdraw consent across businesses from one platform.

Ajay Shukla
By Ajay Shukla
Consent manager dashboard where a user reviews and withdraws DPDP consent given to three businesses

A consent manager is a company registered with the Data Protection Board of India that lets a person give, review and withdraw consent across many businesses through one platform. The DPDP Act, 2023 created the role. Registration opened on 13 November 2026. Most companies are not consent managers; they are the businesses that ask for consent.

That last point causes most of the confusion. Vendor pages, sales decks and social posts use "consent manager" for several different things. This guide separates the legal role from the software that businesses install, explains who has to act and by when, and ends with a test you can run on any consent system.

What is a consent manager under the DPDP Act?

Under the Digital Personal Data Protection Act, 2023 (the DPDP Act), a consent manager is a person registered with the Board who acts as a single point of contact, so that a Data Principal can give, manage, review and withdraw consent through an accessible, transparent and interoperable platform. The Ministry of Electronics and Information Technology (MeitY) used almost the same wording when it announced the registration framework on 14 November 2026.

Three terms from the Act come up in every discussion. A Data Principal is the individual the personal data is about. A Data Fiduciary is any organisation that decides why and how that data is processed, such as a bank, a retailer, a hospital or a SaaS company. The Board is the Data Protection Board of India, which registers consent managers and handles complaints.

Why did India create consent managers?

Consent today is scattered. A person who has agreed to a lender, an insurer and a shopping app has agreed three separate times, on three separate screens, and has to visit three separate privacy pages to change their mind. Most people never do.

A consent manager gives that person one place to see and change those choices. Picture someone opening a single dashboard, seeing three active consents and withdrawing one. The consent manager passes the instruction to the Data Fiduciary concerned, which has to act on it.

India has used the same idea in finance for several years. Account Aggregators, regulated by the Reserve Bank of India, let people share financial data between institutions through a single consent layer, a model FinTech and banking teams already know. The DPDP Act applies the idea to personal data more broadly. The two frameworks have different regulators and different rules, so treat the comparison as an analogy and not as a template.

When did consent manager registration start in India?

When did consent manager registration start in India

Registration opened on 13 November 2026. The date comes from the Digital Personal Data Protection Rules, 2025 (the DPDP Rules), which were notified on 13 November 2025 and switch on in phases. Section 6(9) of the Act, which requires every consent manager to register with the Board, and Rule 4 of the Rules, which sets out how, both took effect one year after notification. MeitY's release, reported by ANI on 14 November 2026, said applications go through the Board's portal at dpbi.gov.in.

The phases are:

  • 13 November 2025: definitions and the constitution of the Board.

  • 13 November 2026: consent manager registration (Section 6(9) and Rule 4).

  • 13 May 2027: the main duties for companies that handle personal data, individual data rights, and the Board's inquiry and penalty processes.

The third date matters most to ordinary businesses, and it is about six months away as of this update.

Who can register as a consent manager?

Only a company incorporated in India with a net worth of at least ₹2 crore can apply, according to the MeitY announcement. Net worth here means total assets minus total liabilities as shown in the company's books. The Rules also set conditions on technical, operational and financial capacity and on the fitness of the management. These sit in the First Schedule, and anyone planning to apply should read that text directly instead of relying on a summary.

The ₹2 crore floor suggests what the role is for: a neutral intermediary that holds consent choices on behalf of many people and many organisations. It is not aimed at a company that only wants to manage consent from its own customers.

Does my business need to register as a consent manager?

No. A business that collects personal data is a Data Fiduciary, and Data Fiduciaries do not register as consent managers. Your duties are to give a clear notice, ask for consent for specific purposes, record what people chose and honour withdrawals. You would register only if you planned to run the intermediary service for other organisations.

Section 6 of the Act lets a Data Principal manage consent through a consent manager, so you should expect some choices to arrive that way once the role is running. The Act does not make a business appoint one.

What is the difference between a consent manager and a consent management platform?

A consent manager is a registered legal role. A consent management platform (CMP) is a software product that one organisation installs to collect and record consent from its own users. The two share a word and a goal, which is why they get mixed up.

Consent manager

Consent management platform

What it is

A registered entity under the DPDP Act

A category of software

Registration

With the Data Protection Board, ₹2 crore minimum net worth

None required

Who it serves

Data Principals, across many Data Fiduciaries

One organisation and its users

Typical features

One place to give, review and withdraw consent

Banners, notices, preference centres, logs

OneTrust describes a CMP as a tool that collects and records consent through cookie banners, mobile notices or preference centres, scans trackers, blocks tags until a valid choice is made, and passes signals to advertising and analytics partners (OneTrust, Consent & Preferences page, checked 16 November 2026). The regulations and standards that page lists are GDPR, CCPA/CPRA, LGPD, US state laws and advertising standards such as IAB TCF. It does not mention India's DPDP Act.

KavachOne's ConsentiQo page, checked on the same date, lists purpose-wise consent, 22 Indian languages, a cookie scanner, audit logs and a privacy centre, all framed around the DPDP Act. Those are the features of a consent management platform: a tool a business deploys on its own website or app. Whether a vendor is also registered with the Board as a consent manager is a separate fact, and it is reasonable to ask the vendor for it.

How do I check whether a vendor is a registered consent manager?

Ask for the registration details and verify them with the Board through dpbi.gov.in. If the vendor cannot give any, treat the product as a consent management platform. That is still a useful product. It just does not do the legal job of a consent manager.

Is a cookie banner enough for DPDP compliance?

No. A cookie banner covers data collected by trackers on a website. The DPDP Act covers digital personal data wherever it comes from: sign-up forms, mobile apps, KYC uploads, support tickets and offline records that are later digitised. Under Section 6, consent must be free, specific, informed, unconditional and unambiguous, and given by a clear affirmative action.

A banner on the homepage does nothing for a consent that was collected by a loan application form. This is the most common gap: the banner exists, and the back end behind it does not.

How will a business receive a withdrawal from a consent manager?

The Act calls the consent manager's platform interoperable, which means a business has to be able to receive instructions from it in a defined format. The technical details come from the Rules and anything the Board publishes later, so confirm what is current before you build.

What you can do now is keep the boundary clean. Give your consent log one place that accepts a change event, either a new grant or a withdrawal, with a person identifier, a purpose and a timestamp. Make it safe to receive the same event twice, because networks retry. Then use workflow automation to route the event to every system that uses the data. If your consent choices are spread across a CRM, a marketing tool and a database, this is the step that will hurt, and it is cheaper to fix before 13 May 2027 than after a complaint.

What does a usable consent record look like?

A consent record is the evidence that a specific person agreed to a specific use of their data. For any user, you should be able to answer five questions from it: who agreed, to which purpose, under which version of the notice, when and through which channel, and whether they have withdrawn since.

Here is a simple test. Pick one real user at random and try to answer all five questions from your own systems, without asking an engineer to run queries across several tables. If you cannot do it in a few minutes, the record is not ready for a regulator, a complaint or an audit.

Four design mistakes show up again and again in consent builds:

  • Consent stored as a single true or false column on the user table. A withdrawal overwrites the old value and the history is gone.

  • One checkbox covering several purposes, for example service emails, analytics and sharing with partners. The Act asks for specific consent, so each purpose needs its own record.

  • Notice text edited in place with no version number. Later, nobody can show what the user actually saw.

  • Withdrawal that works on the website but never reaches the CRM or the email tool, so messages keep going out.

The Act also says withdrawing consent must be as easy as giving it (Section 6(4)). That is a design requirement for your interface and for every system that stores or uses the data.

The usual fix is an append-only log, where every change is a new row with a timestamp and a notice version instead of an edit to an old one. The trade-off is more storage and a slightly harder schema. Given that the log is your evidence, most teams accept that.

What should an Indian business do before 13 May 2027?

Start with the parts that take longest. A reasonable order is:

  1. List the personal data you collect, where it enters your systems and why you need it. Each reason is a purpose.

  2. Write one plain-language notice per purpose, in the languages your users actually read.

  3. Replace bundled or pre-ticked checkboxes with one clear choice per purpose.

  4. Store consent as an append-only log with the five fields above.

  5. Build a withdrawal path that reaches every system holding the data, including exports and third-party tools.

  6. Decide how you will receive choices passed on by a registered consent manager.

  7. Ask a lawyer to review notices and retention periods against the Rules.

Teams without in-house engineering capacity for the consent log and the withdrawal flow often bring in API and integration developers. The legal review in step 7 stays with counsel either way.

Rules and technical specifications can change, and the Board may publish more detail after this update, so check dpbi.gov.in before you act. This article is general information and not legal advice.

Frequently Asked Questions

Q1. What is a consent manager in simple words?

A consent manager is a registered company that gives a person one place to give, check and withdraw consent for many businesses. The DPDP Act, 2023 created the role. It acts as a single contact point between the person and the organisations that hold their data, and it must be registered with the Data Protection Board.

Q2. Is a consent manager the same as a data fiduciary?

No. A Data Fiduciary is any organisation that decides why and how personal data is processed, such as a bank or an online store. A consent manager is a separate registered intermediary that helps people manage consent given to those organisations. One does not replace the other, and ordinary businesses are Data Fiduciaries only.

Q3. Who can register as a consent manager in India?

Only companies incorporated in India can register, and they need a net worth of at least ₹2 crore. MeitY announced these conditions on 14 November 2026. The Rules also look at technical, operational and financial capacity and at the fitness of the management, which the First Schedule of the DPDP Rules, 2025 sets out.

Q4. What is the net worth requirement for a DPDP consent manager?

The minimum net worth is ₹2 crore. Net worth means total assets minus total liabilities, as shown in the company's books of accounts. An applicant that falls below this figure does not meet the eligibility condition, so a startup planning to apply should check its latest accounts before filing on the Board's portal.

Q5. How do I register as a consent manager under the DPDP Act?

Apply online through the Data Protection Board's portal at dpbi.gov.in. Rule 4 of the DPDP Rules, 2025 sets the registration process, and the First Schedule lists the conditions the Board checks. Read both before filing, and keep your books of accounts ready, because the net worth condition is verified against them.

Q6. When did consent manager registration start?

Registration opened on 13 November 2026, one year after the DPDP Rules, 2025 were notified. Section 6(9) of the Act and Rule 4 took effect that day. MeitY announced the framework on 14 November 2026, and the Board accepts applications through dpbi.gov.in. Other duties for companies begin later, on 13 May 2027.

Q7. Does my company need to appoint a consent manager?

No, the Act does not require a business to appoint one. Using a consent manager is an option for the Data Principal, who can give, manage, review and withdraw consent through it. Your own duties stay the same: clear notice, specific consent, honest records and a working withdrawal path. Expect some consent choices to arrive through registered managers.

Q8. What is the difference between a consent manager and a consent management platform?

A consent manager is a registered legal role, while a consent management platform is software. The platform runs on one organisation's website or app and collects consent from its own users. A consent manager serves people across many organisations. A vendor can sell the first without being the second, so ask for registration details.

Q9. Is a cookie consent banner enough for DPDP compliance?

No. A banner only covers data collected by trackers on a website. The DPDP Act applies to digital personal data from forms, apps, uploads and support tickets as well. Each purpose needs its own notice and consent record, and withdrawal must reach every system that holds the data, not just the website.

Q10. Can a user withdraw consent through a consent manager?

Yes. Section 6 of the DPDP Act lets a Data Principal give, manage, review or withdraw consent through a consent manager. Withdrawal must also be as easy as giving consent (Section 6(4)). In practice, the Data Fiduciary needs a way to receive that instruction and apply it across its databases, CRM and marketing tools.

Q11. When do DPDP obligations for businesses start?

The main duties for companies start on 13 May 2027, based on MeitY's statement of 14 November 2026. These cover notice, consent, individual data rights and the Board's inquiry and penalty processes. Consent manager registration came earlier, on 13 November 2026, which is why vendors are talking about it now.

Q12. What is the legal basis for registering consent managers?

Section 6(9) of the DPDP Act requires every consent manager to register with the Board, and Rule 4 of the DPDP Rules, 2025 sets the process. Section 27(1)(d) lets the Board inquire into a registered consent manager's breach of its conditions. Check with a lawyer before offering the service.

Q13. What should a consent record contain?

A good record shows who agreed, to which purpose, under which notice version, when, through which channel, and whether the person has withdrawn since. Store each change as a new entry instead of editing an old one. That keeps the history intact if a regulator or customer asks what happened.

Q14. How can I check if a vendor is a registered consent manager?

Ask the vendor for its registration details and verify them with the Data Protection Board through dpbi.gov.in. A vendor that sells a banner or a preference centre to businesses is usually offering a consent management platform. That can still be useful, but it is a different product from the registered role.

Ready to grow your business with Jamtech?

Talk to our experts about your next digital project.

Get Free Consultation
Published on Nov 16, 2026 Updated on Nov 16, 2026
Chat on WhatsApp