Is a Consent Manager mandatory under DPDP Act 2023? Understanding legal requirements in India Is a Consent Manager mandatory under DPDP Act 2023? Understanding legal requirements in India

Is a Consent Manager Mandatory Under DPDP? (2026 Guide)

For businesses, the more important question is not simply whether they have appointed a Consent Manager. It is whether they have a reliable way to obtain valid consent, explain how personal data will be used, honour withdrawal requests and maintain evidence of consent.

The Digital Personal Data Protection (DPDP) Act, 2023 recognises a statutory role called a Consent Manager. However, this does not mean that every business must hire or integrate with one. Businesses can manage their own consent processes, including through internal systems or a Consent Management Platform (CMP), subject to the applicable legal requirements.

This guide explains whether businesses are legally required to use a registered Consent Manager, what Sections 6(7), 6(9) and 6(10) provide, how a Consent Manager differs from a CMP, and when using one may make practical sense.

Important: DPDP Act commencement status

As of 16 November 2026, Section 6(9), which requires Consent Managers to be registered, and Rule 4 of the DPDP Rules, 2025, which sets out the registration framework, have commenced. Sections 6(7) and 6(10), along with Rule 3 on detailed notice requirements, are scheduled to commence on 13 May 2027. The distinction is important when interpreting the provisions discussed below.

Contents hide

1. Do Indian Businesses Need to Hire a Consent Manager?

No. The DPDP Act does not impose a general requirement on every business in India to hire, appoint or integrate with a registered Consent Manager.

The Act recognises Consent Managers as an intermediary through which individuals, known as Data Principals (the people whose personal data is being processed), can manage their consent. However, the Act does not make using this intermediary a universal condition for a business to process personal data.

A business can design and operate its own consent processes or use a third-party CMP. The important distinction is that the business remains responsible for meeting the legal requirements applicable to its processing activities. Using consent-management software does not, by itself, establish compliance.

A statutory Consent Manager is a separate role under the Act. An entity operating in that role must meet the prescribed registration conditions and be registered with the Data Protection Board of India (DPBI).

Key takeaway: Businesses need a suitable way to manage consent and meet their applicable legal responsibilities. They are not universally required to purchase the services of a registered Consent Manager.

2. Is a Consent Manager Mandatory Under the DPDP Act?

No. The Act does not generally require a Data Fiduciary to appoint or use a registered Consent Manager. Three provisions help explain the distinction.

Section 6(7): Individuals may use a Consent Manager

Section 6(7) states that a Data Principal may give, manage, review or withdraw consent to a Data Fiduciary through a Consent Manager.

The word may is significant. It provides an additional mechanism for individuals to exercise control over their consent. It does not state that every business must appoint a Consent Manager or route all consent interactions through one.

Commencement: Section 6(7) is scheduled to come into force on 13 May 2027. It should therefore be described as an enacted provision with a future commencement date, rather than an already operative requirement as of 16 November 2026.

Section 6(9): Consent Managers must be registered

Section 6(9) provides that every entity acting as a statutory Consent Manager must be registered with the Board in the prescribed manner and subject to the applicable technical, operational, financial and other conditions.

Rule 4 of the DPDP Rules, 2025 sets out the registration procedure and obligations. The First Schedule specifies the eligibility and operational conditions, including that the applicant must be a company incorporated in India and have a net worth of at least ₹2 crore.

This registration requirement applies to organisations operating as statutory Consent Managers. It does not require every business that collects or processes personal data to register as a Consent Manager.

Commencement: Section 6(9) and Rule 4 came into force on 13 November 2026.

Section 6(10): Data Fiduciaries must be able to prove consent

Section 6(10) addresses the burden of proof where consent is the basis for processing personal data and a question arises in a proceeding. It places the obligation on the Data Fiduciary to prove that the required notice was given and that consent was obtained in accordance with the Act and Rules.

This provision is important because a business cannot assume that appointing a third-party Consent Manager automatically transfers its responsibility to demonstrate consent.

Commencement: Section 6(10) is scheduled to come into force on 13 May 2027. The provision should not be presented as already operational as of 16 November 2026.

What this means for businesses: The Act provides for registered Consent Managers, but does not make their services compulsory for every Data Fiduciary. Businesses should prepare systems to meet their applicable obligations and retain appropriate evidence of consent.

3. Does the DPDP Act Require Businesses to Hire, Appoint or Integrate with a Consent Manager?

No. These terms describe different commercial or technical arrangements. They are not separate statutory obligations imposed on every Data Fiduciary under the DPDP Act.

Term What it means Is it generally mandatory?
Hire a Consent Manager Engage a registered Consent Manager to provide its services. No general requirement for every business.
Appoint a Consent Manager Formally designate or engage an intermediary to support consent-related processes. No general appointment requirement under the Act.
Onboard with a Consent Manager Enable the business to participate in a Consent Manager’s ecosystem or service. No universal onboarding requirement.
Integrate with a Consent Manager Connect business systems so consent-related instructions and information can be exchanged. No universal integration requirement.

A business can manage its consent processes through its own website, mobile application, internal systems or an ordinary CMP. It should assess whether the chosen arrangement supports the requirements applicable to its processing activities.

There is also an important distinction between using software to manage consent and operating as a statutory Consent Manager under the DPDP Act. They are not automatically the same thing.

For example, an e-commerce company may use a CMP to display consent notices, record customer choices and manage withdrawal requests. This does not, by itself, make the CMP provider a statutory Consent Manager requiring registration with the DPBI.

Do not confuse the two roles:

A CMP is a technology solution used by a business to manage its consent workflows. A statutory Consent Manager is a registered intermediary recognised under Section 6 of the DPDP Act. A software provider does not become a registered Consent Manager merely by offering consent-management features.

4. Consent Manager vs CMP: Does Your Business Need Both?

A common source of confusion under the DPDP Act is the difference between a registered Consent Manager and a Consent Management Platform (CMP). Although both involve consent management, they serve different purposes and operate in different roles.

A statutory Consent Manager is an intermediary recognised under Section 2 of the DPDP Act. It acts as a single point of contact through an accessible, transparent and interoperable platform, enabling Data Principals (individuals whose personal data is being processed) to give, manage, review and withdraw consent in relation to participating Data Fiduciaries.

An ordinary CMP, on the other hand, is a software solution that helps a business manage its own consent processes across its website, mobile application and other digital channels. It may provide consent notices, preference controls, consent records and withdrawal workflows.

Key differences between a Consent Manager and a CMP

Basis Registered Consent Manager Ordinary CMP
Primary purpose Provides individuals with a mechanism to manage consent through an intermediary. Helps businesses manage consent within their own digital operations.
Acts for Acts on behalf of the Data Principal and is accountable to the Data Principal. Typically supports the Data Fiduciary’s consent-related processes.
Main role Enables consent to be given, managed, reviewed and withdrawn through its platform in relation to onboarded Data Fiduciaries. Supports consent collection, preference management, recordkeeping and related workflows.
Registration Must be registered with the DPBI to operate as a statutory Consent Manager under Section 6(9). Does not automatically require DPBI registration merely for providing CMP software.
Scope Can facilitate consent management across participating Data Fiduciaries onboarded onto its platform. Usually manages consent within the business’s own website, app or connected systems.
Legal responsibility Must comply with the statutory Consent Manager framework and its prescribed obligations. Supports the business but does not replace the Data Fiduciary’s legal responsibilities.

Can a business use both?

Yes. The two arrangements are not necessarily alternatives. A business can use an ordinary CMP for its internal consent operations and separately participate in a registered Consent Manager’s ecosystem where the relevant arrangements support it.

For example, an e-commerce company may use a CMP to display privacy notices, collect customer consent, maintain consent records and manage withdrawal requests across its website and mobile application.

It may also choose to work with a registered Consent Manager so that customers can exercise consent-related choices through that intermediary. This would depend on the Consent Manager’s platform, the business’s onboarding and the required technical and operational integration.

The CMP supports the company’s internal consent operations, while the registered Consent Manager provides an additional mechanism for individuals to manage consent through its platform.

Important: A software provider does not become a statutory Consent Manager simply because its product collects or records consent. Its actual role matters. An entity operating as a statutory Consent Manager must meet the registration requirements under the DPDP Act and Rules.

5. Can Businesses Manage Consent Without a Consent Manager?

Yes. The DPDP Act does not generally require businesses to route all consent-related activities through a registered Consent Manager.

A business can manage its consent processes through its own website, mobile application, internal systems or an ordinary CMP. The important consideration is whether the chosen arrangement can support the requirements applicable to the business under the Act and Rules.

For example, a business may independently:

  • Display clear notices explaining what personal data it processes and the purpose of processing.
  • Provide individuals with an appropriate way to give or refuse consent where consent is the applicable legal basis.
  • Maintain records of consent choices and relevant changes.
  • Provide an accessible mechanism for individuals to withdraw consent.
  • Communicate relevant withdrawal instructions to its internal systems and Data Processors where required.
  • Retrieve relevant records and demonstrate how its consent processes operate.

What should a business’s internal consent system support?

Managing consent internally is possible, but simply displaying an acceptance button is not a complete consent management process. Businesses should assess whether their systems can handle the following activities.

1. Clear notice and consent collection

Individuals should receive the required information about the personal data being processed and the purpose of processing before consent is obtained, where consent is the applicable legal basis. The notice and consent process should meet the requirements that apply when the relevant provisions commence.

2. Consent records

The business should be able to identify when consent was obtained, what the individual agreed to and which processing purpose the consent relates to. Maintaining reliable records also helps the organisation investigate complaints and respond to compliance queries.

3. Consent withdrawal

Individuals should have an accessible way to withdraw consent. Under Section 6(4), once the provision commences, withdrawal must be as easy as giving consent. Businesses should plan their systems accordingly rather than treating withdrawal as a manual exception.

4. Downstream communication

If personal data is processed through multiple internal systems or shared with Data Processors, the business should have a process for communicating relevant withdrawal instructions and ensuring that processing is stopped where required, subject to applicable legal exceptions.

5. Evidence and audit readiness

The organisation should be able to retrieve relevant records and explain how consent was obtained, how preferences are managed and how withdrawal instructions are handled. These capabilities help support the Data Fiduciary’s compliance responsibilities.

Important commencement distinction

As of 16 November 2026, Section 6(10), which addresses the Data Fiduciary’s burden to prove consent in proceedings, and the detailed notice requirements under Rule 3 are scheduled to commence on 13 May 2027. The system capabilities described above are practical preparation points; they should not all be represented as provisions already in force.

The takeaway: A registered Consent Manager is not the only way to manage consent. Businesses can build or use their own systems, but those systems should be capable of supporting their applicable legal obligations.

6. When Should a Business Consider Using a Consent Manager?

Even though using a registered Consent Manager is not generally mandatory for businesses, there may be practical reasons to consider participating in one.

The decision should depend on the complexity of the business’s consent processes, the number of systems involved and whether customers would benefit from an additional way to manage their consent.

Here are some situations where evaluating a registered Consent Manager may make sense.

1. Your business processes personal data across multiple services

Businesses operating several websites, applications, brands or digital services may find it difficult to coordinate consent-related instructions across different systems.

A registered Consent Manager may provide an additional mechanism for individuals to manage their consent across participating Data Fiduciaries onboarded onto its platform.

2. Your customers want greater control over their consent

Some individuals may prefer managing consent through an intermediary rather than visiting each company’s website or application separately.

Supporting a registered Consent Manager could offer another route for customers to exercise their consent-related choices, provided the business participates in the relevant platform arrangements.

3. Your organisation operates across multiple digital platforms

E-commerce businesses, financial service providers and digital platforms may collect personal data through websites, mobile applications, customer portals and other channels.

If consent-related processes are fragmented across these channels, the organisation may evaluate whether participation in a registered Consent Manager’s platform would improve coordination.

4. Your existing consent management process is difficult to coordinate

If your organisation relies on disconnected systems, manual updates or separate consent records, it may be worth reviewing whether your existing setup is sufficient.

However, this does not automatically mean you need a statutory Consent Manager. Improving your internal CMP or consent infrastructure may be enough.

5. You want to prepare for the evolving consent ecosystem

With the Consent Manager registration framework in force, businesses can evaluate how registered Consent Managers may fit into their future consent management processes.

This is a planning consideration, not a legal requirement to onboard with a registered provider.

A practical point: Before choosing a Consent Manager, assess your existing CMP, consent records, withdrawal workflows and system integrations. If these already meet your needs, adopting another intermediary may add complexity without providing enough value.

7. Do Small Businesses, Startups and E-commerce Companies Need a Consent Manager?

No. The DPDP Act does not create separate mandatory Consent Manager requirements based on whether an organisation is a startup, small business, e-commerce company or large enterprise.

However, the complexity of a business’s operations can influence whether using a registered Consent Manager is practically useful.

Here is how different types of businesses can approach the decision.

Small businesses and local businesses

A small business operating a single website or a straightforward digital service may not need to integrate with a registered Consent Manager.

It can manage its consent processes through its own website, internal systems or an ordinary CMP. Its priority should be understanding what personal data it processes, why it processes it and how applicable consent-related requests will be handled.

Startups and SaaS companies

Startups often process personal data through websites, mobile applications, subscription forms and customer accounts.

A startup can manage these processes internally or use a CMP. It may consider a registered Consent Manager if its business model involves multiple services, platforms or participating Data Fiduciaries.

However, adopting one simply because the company is a technology startup is unnecessary.

E-commerce companies

E-commerce businesses may process personal data through customer registrations, orders, payment-related processes, marketing subscriptions and mobile applications.

When consent-related activities are spread across several systems, coordinating customer choices can become more complicated.

An e-commerce company may evaluate whether integration with a registered Consent Manager would offer additional value. It should first assess whether its existing consent infrastructure is sufficient.

Banks and financial institutions

Banks and financial institutions may operate multiple digital channels and process personal data across different services.

They should evaluate Consent Manager integration in the context of their existing consent infrastructure, security requirements, operational processes and applicable sector-specific regulations.

A registered Consent Manager is not automatically mandatory simply because an organisation operates in the financial sector.

Healthcare and education organisations

Hospitals, clinics, educational institutions and digital health or learning platforms may process personal data through several digital touchpoints.

These organisations should pay particular attention to the nature of the information collected, the purposes of processing and the legal requirements applicable to their activities.

A Consent Manager may be worth evaluating where it offers an additional mechanism for individuals to manage consent. It is not a universal legal requirement for these sectors.

Large enterprises and businesses with multiple brands

Large organisations may operate several websites, applications, subsidiaries and customer-facing services.

Managing consent across these environments can require coordination between different teams and systems.

A registered Consent Manager may be useful as an additional consent management channel, particularly where customers interact with multiple participating Data Fiduciaries.

Remember: These are practical business recommendations, not legal classifications. The DPDP Act does not make Consent Manager adoption compulsory for any of these categories merely because of their size or industry.

8. What Happens If a Business Does Not Use a Consent Manager?

A business does not automatically violate the DPDP Act simply because it does not use or integrate with a registered Consent Manager.

The statutory Consent Manager framework provides an additional mechanism for individuals to manage consent. It does not make a registered Consent Manager the only permitted way for a business to manage its own consent processes.

Businesses must distinguish between two different situations:

  • Not using a registered Consent Manager.
  • Failing to meet the applicable requirements of the DPDP Act and Rules.

These are not the same.

Does not using a Consent Manager attract a penalty?

There is no standalone penalty simply for choosing not to hire or integrate with a registered Consent Manager, because the Act does not impose a general obligation on every Data Fiduciary to do so.

However, a business must still comply with the legal obligations applicable to it as and when the relevant provisions commence.

For example, Section 6(10) provides that where consent is the basis for processing personal data and a question arises in a proceeding, the Data Fiduciary must prove that the required notice was given and consent was obtained in accordance with the Act and Rules.

This provision is scheduled to commence on 13 May 2027. Businesses should therefore prepare to maintain reliable consent records and supporting evidence rather than assuming that an intermediary will establish compliance on their behalf.

Does using a Consent Manager protect a business from penalties?

No. Using a registered Consent Manager does not automatically make a business DPDP-compliant or transfer its legal responsibilities to the intermediary.

The Data Fiduciary remains responsible for its own obligations under the Act. A Consent Manager can provide an additional mechanism for consent management, but it should not be treated as a replacement for the organisation’s own compliance processes.

The takeaway: Not using a Consent Manager is not, by itself, a compliance failure. Failing to meet the applicable obligations of the DPDP Act is a different matter.

9. How to Decide Whether Your Business Needs a Consent Manager

Before integrating with a registered Consent Manager, assess whether your existing consent management process is sufficient.

The following checklist can help your organisation make a practical decision.

Consent management readiness checklist

  • Do you know what personal data your website, application and other systems collect?
  • Can you explain why the data is collected and how it will be used?
  • Do your consent notices clearly communicate the relevant information?
  • Can you record and retrieve individual consent choices?
  • Can individuals withdraw consent through an accessible process?
  • Can your systems communicate withdrawal instructions to relevant internal teams and service providers where required?
  • Can you identify which processing activities and purposes are linked to a particular consent?
  • Can you retrieve records and supporting evidence when required?
  • Do you have a process to review and update your consent management practices?

How should you interpret the results?

Your business situation Practical recommendation
One website with straightforward consent requirements An internal system or ordinary CMP may be sufficient.
A startup with a single digital product Start with a reliable consent management process and evaluate additional integration as complexity grows.
Multiple websites or applications Review whether your existing systems can coordinate consent effectively.
Several brands or business units Consider whether a registered Consent Manager offers additional value.
Existing enterprise CMP Assess its capabilities before introducing another solution.
Customers need a mechanism to manage consent across participating organisations Evaluate integration with a registered Consent Manager.
Important: This checklist is a practical readiness assessment, not a statutory test for deciding whether a Consent Manager is mandatory. It does not replace a legal assessment of your processing activities.

If your existing system can support your applicable legal requirements, you may not need another intermediary.

If your consent processes are fragmented or customers would benefit from managing consent through an additional channel, evaluating a registered Consent Manager may be worthwhile.

For a broader understanding of the processes involved, read our guide to the Consent Management Process Under the DPDPA.

10. What Changed in November 2026? Consent Manager Registration Is Now Open

Although businesses are not generally required to appoint a Consent Manager, the regulatory framework for organisations wishing to operate as statutory Consent Managers has now entered its registration phase.

On 13 November 2026, Section 6(9) of the DPDP Act and Rule 4 of the DPDP Rules, 2025, which establish the registration framework for Consent Managers, came into force.

On 14 November 2026, the Ministry of Electronics and Information Technology (MeitY) announced the launch of the online registration portal at dpbi.gov.in. Eligible Indian companies can use the portal to apply for registration as statutory Consent Managers.

Who can apply to become a registered Consent Manager?

Under Rule 4 and Part A of the First Schedule to the DPDP Rules, 2025, applicants must satisfy the prescribed eligibility conditions. These include:

  • Being a company incorporated in India.
  • Having a net worth of at least ₹2 crore.
  • Having sufficient technical, operational and financial capacity to fulfil the obligations of a Consent Manager.
  • Meeting the prescribed requirements relating to financial soundness, management, business prospects and the integrity of directors and key managerial personnel.

Meeting the minimum net-worth requirement alone does not guarantee registration. Applicants must satisfy the applicable conditions, and registration is subject to the prescribed assessment and approval process.

Has the DPBI started granting registrations?

The launch of the portal means eligible companies can apply. It should not be interpreted as confirmation that registrations have already been granted.

As of 16 November 2026, public reporting indicated that appointments to the DPBI’s leadership and membership had not yet been finalised. Businesses should therefore distinguish between the commencement of the registration framework, the availability of the application portal and the actual grant of registration.

For the official announcement, refer to the MeitY and PIB announcement dated 14 November 2026.

Does this mean businesses must now onboard with a registered Consent Manager?

No. This is an important distinction.

The registration framework allows eligible entities to apply to operate as statutory Consent Managers. It does not create a general obligation for every Data Fiduciary to hire, appoint or integrate with one.

Businesses can continue evaluating their own consent management requirements and decide whether integration would provide practical value.

DPDP Act implementation timeline

The DPDP Act and Rules are being implemented in phases. The following dates are particularly relevant to the Consent Manager framework as of 16 November 2026.

Provision Commencement date Status as of 16 November 2026
Section 6(9) – Registration of Consent Managers 13 November 2026 In force
Rule 4 – Registration and obligations of Consent Managers 13 November 2026 In force
Section 6(7) – Data Principal’s use of a Consent Manager 13 May 2027 Scheduled to commence
Section 6(10) – Data Fiduciary’s burden of proving consent 13 May 2027 Scheduled to commence
Rule 3 – Notice requirements 13 May 2027 Scheduled to commence

The table covers provisions directly relevant to the topics discussed in this guide, not the complete commencement schedule for the Act and Rules.

This phased timeline is important when assessing the current legal position. A provision being included in the Act or Rules does not necessarily mean that it has already commenced.

For a more detailed explanation of the regulator and its responsibilities, read our guide to the Data Protection Board of India (DPBI).