Skip to main content

On-demand webinar coming soon...


On-demand webinar coming soon...

Blog

Understanding Consent Manager Registration and CMP Requirements Under India's DPDPA

India's DPDPA introduces registered Consent Managers, a distinct legal role from the consent management platforms businesses use to manage customer choices.


Harry Chambers
Regulatory Content Strategist
November 18, 2026

OneTrust logo over an abstract blue and teal background of layered curved waves

India's Digital Personal Data Protection Act (DPDPA) has introduced a new concept into privacy compliance: the Consent Manager. For organizations already using a Consent Management Platform (CMP), this raises a practical question: does operating in India require a registered Consent Manager?

The short answer is no. Businesses aren't generally required to use a registered Consent Manager under the DPDPA. They remain responsible for meeting their applicable consent obligations, whether they manage these processes directly or use technology to support them.

The distinction matters when evaluating compliance requirements, existing technology, and how customer choices are honored across systems.

Key Takeaways

  • A DPDPA Consent Manager is a registered intermediary acting on behalf of individuals, while a CMP supports an organization's consent management processes.
  • Businesses aren't generally required to use a registered Consent Manager to comply with the DPDPA.
  • Registration as a Consent Manager introduces specific obligations involving governance, independence, transparency, record retention, and regulatory oversight.
  • Effective consent management requires organizations to connect collection and withdrawal mechanisms with accurate records and downstream processing.

 

Section 2(g) of the DPDPA defines a Consent Manager as: "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."

A Consent Manager acts on behalf of data principals, the individuals whose personal data is being processed, and remains accountable to them.

For example, an individual dealing with several service providers might use a registered Consent Manager to manage consent across participating organizations, rather than interacting separately with each one.

This creates a unique legal role under the DPDPA, subject to registration with the Data Protection Board of India and specific regulatory obligations.

A Consent Management Platform (CMP) is technology that supports an organization's consent processes, including presenting notices, collecting choices, maintaining records, and applying consent across relevant systems.

Both approaches involve consent management, but their roles and responsibilities differ.

 

AspectDPDPA Consent ManagerConsent Management Platform
NatureRegistered legal intermediarySoftware solution
RegistrationRequired with India's Data Protection BoardNo registration required solely to provide CMP software
ServesData principalsOrganizations managing consent
PurposeEnables individuals to give, manage, review, and withdraw consent across participating data fiduciariesSupports consent collection, records, withdrawal, and enforcement
ObligationsSpecific regulatory, governance, and operational requirementsSupports the organization's applicable compliance responsibilities
ScopeInteroperable consent management on behalf of individualsDepends on the organization's processing activities and technology

 

Consider an e-commerce business collecting personal data during customer registration.

Its CMP might present a notice, record consent, and help connect a subsequent withdrawal to relevant processing systems. A registered Consent Manager, meanwhile, would provide an independent mechanism for the individual to manage consent involving participating data fiduciaries.

The distinction affects both technology decisions and legal accountability.

Registration as a Consent Manager introduces requirements extending beyond consent collection technology.

Under the DPDPA and DPDP Rules described in the supplied regulatory materials, these include:

  • Incorporation and governance: Applicants must be companies incorporated in India, with corporate documents containing specified compliance provisions. Amendments to those provisions require Board approval.
  • Record retention: Consent records must be maintained for at least seven years, or longer where agreed with the data principal or required by law.
  • Independence: Measures must prevent specified conflicts of interest involving directors, senior management, and relationships with data fiduciaries.
  • Transparency: Registered Consent Managers must disclose information about leadership, promoters, certain shareholding interests, and additional information required by the Board.
  • Changes in control: Transfers of control through mergers, sales, or other arrangements require prior Board approval, subject to applicable conditions.

These obligations create legal and operational considerations that differ significantly from providing consent management software. Registration affects corporate governance, regulatory oversight, and the ongoing responsibilities of the entity undertaking the role.

No. The DPDPA does not generally require data fiduciaries to appoint or use a registered Consent Manager.

Businesses remain responsible for their own applicable consent requirements. Under the DPDPA, consent generally must be free, specific, informed, unconditional, unambiguous, and expressed through clear affirmative action. Individuals must also be able to withdraw consent as easily as they provide it.

The law separately recognizes certain legitimate uses for processing personal data.

For organizations, the immediate questions concern how these requirements apply in practice. Which processing activities require consent? How are individuals informed? Where are choices recorded? What happens when consent is withdrawn?

CMPs and broader consent management technologies support these processes without automatically assuming the legal role of a registered Consent Manager.

Consider a customer who registers for an online service and agrees to a particular use of their personal data.

The business presents the relevant notice and records consent. Later, the customer withdraws that permission through their account settings.

The customer-facing experience captures the withdrawal, but the relevant processing systems also need to reflect the change.

If the business maintains customer information across account management, CRM, and marketing systems, the withdrawal needs to reach the environments where the affected processing occurs.

The underlying consent management infrastructure therefore needs to connect the customer's identity, the relevant purpose, the updated consent state, and the systems responsible for acting on it.

Records also matter. Organizations need appropriate evidence of the original consent and how the subsequent withdrawal was handled.

This distinction between the customer-facing experience and downstream operations is central to effective consent management. A clear interface supports informed choice, while connected records and enforcement workflows help ensure that the organization's subsequent processing reflects that choice.

A useful starting point is understanding the organization's legal role and its existing consent workflows.

Privacy, legal, and technology stakeholders should examine five questions:

  1. Which processing activities require consent? Identify relevant purposes and determine where legitimate uses apply.
  2. How do individuals provide and withdraw consent? Review notices, collection experiences, and withdrawal mechanisms.
  3. Where are consent records maintained? Establish how consent is associated with individuals, purposes, and relevant processing activities.
  4. What happens after withdrawal? Identify the downstream systems and operational owners responsible for reflecting the change.
  5. Does the intended operating model involve a registered intermediary? Distinguish between using technology to support the business's responsibilities and engaging an entity acting as a registered Consent Manager.

These questions help organizations evaluate whether existing processes and technology support their obligations, and where operational changes are necessary.

The distinction between registered Consent Managers and CMPs helps organizations make better-informed decisions about their consent management approach. Registration establishes a specific legal role, while consent management technology supports the day-to-day responsibilities of organizations processing personal data.

The practical priority is ensuring that consent choices remain accurate and actionable throughout the processing lifecycle. That means understanding where consent is required, connecting withdrawals to the systems responsible for processing, and maintaining records that demonstrate how those choices were handled.

A clear view of these dependencies helps identify gaps in existing workflows and establish which capabilities deserve attention first.

For a broader understanding of how consent fits alongside privacy notices, individual rights, and governance requirements, explore OneTrust's India DPDPA Compliance Guide: Requirements, Rights, Consent, and Governance. The guide provides further context for assessing DPDPA obligations and preparing an operational compliance program.