DPDP Consent Managers in India: 2026 Business Guide
India’s Digital Personal Data Protection (DPDP) framework is entering an important phase. With the Consent Manager registration provisions becoming effective in November 2026, businesses need to understand how these platforms will work, what responsibilities they carry and whether their existing consent practices need to change. A customer signs up for an online service, shares personal information and agrees to receive updates. A few months later, the customer changes their mind and wants to withdraw consent for a particular use of their information.
Where should that request go? How will the customer know which businesses have received their consent? And how can they manage different permissions without having to contact every organisation separately? These are some of the practical issues that Consent Managers are intended to address under India's Digital Personal Data Protection framework. For businesses, this development is worth understanding now. Consent Managers introduce a structured mechanism through which individuals can manage their consent, while also creating new expectations around transparency, interoperability and accountability. This article explains the concept, the legal framework, the registration requirements and what businesses should consider as the DPDP regime moves forward in 2026.
1. What Is a Consent Manager Under the DPDP Act?
A Consent Manager is a registered entity that provides individuals with a single point of contact to give, manage, review and withdraw consent for the processing of their personal data. The concept is recognised under Section 2(g) of the Digital Personal Data Protection Act, 2023.
In simple terms, a Consent Manager acts as an intermediary between an individual and the businesses that process that individual's personal data. It provides an accessible, transparent and interoperable platform through which consent-related choices can be managed. Consider a customer who uses a banking application, an online shopping platform and a healthcare service. Each organisation may collect and process different categories of personal data for different purposes.
A Consent Manager can help the individual manage consent through a common platform, rather than relying entirely on separate consent-management processes maintained by each organisation. However, a Consent Manager is not simply a consent pop-up, a cookie banner or a software tool that records whether someone clicked an acceptance button. It is a regulated entity with specific registration conditions and legal responsibilities.
2. Why Has the DPDP Framework Introduced Consent Managers?
Consent is an important part of the DPDP framework. However, giving consent and having meaningful control over that consent are two different things. In many digital services, individuals encounter multiple consent requests. They may accept a privacy notice while registering, agree to additional processing when using a service and later struggle to identify how to withdraw a particular permission. A Consent Manager is intended to make this process more accessible and organised.
The framework seeks to support individuals in:
- Giving consent through a common platform.
- Reviewing the permissions they have provided.
- Managing consent across participating Data Fiduciaries.
- Withdrawing consent when they no longer wish to permit a particular use.
- Accessing records of consent-related activity.
For businesses, this could mean greater visibility into how consent is obtained and managed. It may also require organisations to review how their systems communicate consent decisions and maintain related records. The underlying objective is straightforward: individuals should have a more practical way to exercise control over their personal data.
3. What Is the Legal Framework Governing Consent Managers?
Consent Managers are primarily governed by the Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025. Three provisions are particularly relevant.
Section 2(g): Definition of a Consent Manager
This provision defines a Consent Manager as a person registered with the Data Protection Board of India who enables Data Principals to give, manage, review and withdraw consent through an accessible, transparent and interoperable platform.
Section 6(7) to Section 6(9): Consent Management
These provisions recognise the role of Consent Managers in enabling individuals to manage their consent, establish their accountability towards Data Principals and require registration with the Board.
Rule 4 and the First Schedule of the DPDP Rules, 2025
Rule 4 provides the registration framework and sets out the obligations that registered Consent Managers must follow. The First Schedule contains the eligibility conditions and operational requirements.
The provisions should be read together. The Act establishes the legal concept, while the Rules explain how registration and ongoing compliance are expected to work.
4. When Do the Consent Manager Provisions Come Into Effect?
The commencement timeline is especially important for businesses planning their compliance activities. The DPDP Act and Rules follow a phased implementation approach. Not every provision becomes operational on the same date.
The DPDP Rules, 2025 were notified on 13 November 2025. Under Rule 1:
- Rules 1, 2 and 17 to 21 came into force upon publication.
- Rule 4, dealing with Consent Manager registration and obligations, comes into force one year after publication.
- Rules 3, 5 to 16, 22 and 23 are scheduled to come into force eighteen months after publication.
Accordingly, Rule 4 became effective on 13 November 2026. Section 6(9) of the Act, which requires Consent Managers to be registered with the Board, also follows the one-year commencement timeline. However, this should not be confused with the commencement of the entire consent framework. Sections 6(1) to 6(8) and 6(10), including the substantive provisions concerning consent and withdrawal, are scheduled for commencement after eighteen months from 13 November 2025.
This distinction matters. As of November 2026, the Consent Manager registration framework is effective, but most of the wider operational obligations under the Act and Rules are scheduled for May 2027. Businesses should therefore distinguish between provisions that are already in force and those for which preparation is necessary ahead of their scheduled commencement.
5. Who Can Register as a Consent Manager in India?
Not every company offering privacy-related software or digital consent services can automatically operate as a registered Consent Manager. The First Schedule, Part A of the DPDP Rules, 2025 specifies conditions that an applicant must satisfy.
The main requirements include:
1. Incorporation in India
The applicant must be a company incorporated in India.
2. Adequate technical, operational and financial capacity
The applicant must demonstrate that it has the resources and systems required to fulfil its responsibilities as a Consent Manager.
3. Minimum net worth of ₹2 crore
The applicant must have a net worth of at least ₹2 crore.
4. Sound financial position and management
The company's financial condition and the general character of its management must be satisfactory.
5. Adequate business prospects
The expected volume of business, capital structure and earning prospects must be adequate for the proposed operations.
6. Reputation and integrity of management
Directors, key managerial personnel and senior management must have a general reputation and record of fairness and integrity.
7. Appropriate constitutional documents
The company's Memorandum of Association and Articles of Association must contain provisions supporting compliance with specified conflict-of-interest requirements.
8. Operations in the interests of Data Principals
The proposed operations must serve the interests of the individuals whose consent is being managed.
9. Independent certification of the platform
The applicant's interoperable platform must be independently certified against the applicable data protection standards and assurance framework published by the Board. Appropriate technical and organisational measures must also be in place.
These conditions indicate that registration is not intended to be a simple formality. Applicants must demonstrate that their business structure, financial position, management and technology are suitable for handling consent-management responsibilities.
6. How Does the Consent Manager Registration Process Work?
Under Rule 4, an eligible applicant may apply to the Data Protection Board of India for registration as a Consent Manager. The application must include the particulars, information and documents that the Board may publish for this purpose. After receiving an application, the Board may conduct an inquiry to assess whether the applicant meets the conditions specified in Part A of the First Schedule.
The process broadly involves:
- The applicant reviews the prescribed eligibility conditions.
- It prepares the required company, financial, management and technical information.
- It submits an application to the Board in the prescribed manner.
- The Board examines the application and may make further inquiries.
- If satisfied, the Board registers the applicant and publishes its particulars.
- If the Board is not satisfied, it may reject the application and communicate the reasons.
Registration is therefore subject to the Board's assessment. A company should not describe itself as a registered Consent Manager merely because it has developed a consent-management platform or submitted an application. The Board may also issue directions where a registered Consent Manager fails to comply with the prescribed conditions. In appropriate cases, its registration may be suspended or cancelled after following the prescribed process.
7. What Are the Key Obligations of a Registered Consent Manager?
Registration brings continuing responsibilities. The First Schedule, Part B of the DPDP Rules, 2025 sets out the obligations that registered Consent Managers must follow. Some of the most important requirements are explained below.
Enabling consent management
A Consent Manager must enable individuals using its platform to give consent to the processing of their personal data by Data Fiduciaries onboarded onto that platform. The platform must also support the management and review of consent.
Maintaining records of consent
The Consent Manager must maintain records of:
- Consent given, denied or withdrawn.
- Notices provided before or alongside consent requests.
- Sharing of personal data with a transferee Data Fiduciary.
These records help create a traceable history of consent-related activity.
Providing access to records
Individuals must be able to access their records through the platform. On request, the relevant information must also be made available in machine-readable form, in accordance with the prescribed requirements.
Retaining records for at least seven years
The Rules require Consent Managers to maintain the specified records for at least seven years, or for a longer period where agreed with the Data Principal or required by law.
Maintaining an accessible website or application
A Consent Manager must develop and maintain a website, an application or both as the primary means through which individuals access its services.
Protecting personal data
The Consent Manager must take reasonable security safeguards to prevent personal data breaches. Importantly, the Rules also require the platform to be designed so that the contents of personal data being made available or shared are not readable by the Consent Manager.
Avoiding conflicts of interest
A Consent Manager must act in a fiduciary capacity towards the Data Principal and avoid conflicts of interest with Data Fiduciaries. The Rules also address conflicts that may arise through directorships, financial interests, employment, beneficial ownership or material financial relationships involving the Consent Manager's directors and senior management.
Maintaining transparency and audit mechanisms
The Consent Manager must publish specified information about its promoters, directors, senior management and certain shareholding interests. It must also maintain effective audit mechanisms to review its technical and organisational controls, continued eligibility and compliance with its obligations. These requirements make independence, transparency and accountability central to the role of a Consent Manager.
8. Does Every Business Need to Appoint a Consent Manager?
This is an important question for organisations planning their DPDP compliance strategy. The Act recognises that a Data Principal may give, manage, review or withdraw consent through a Consent Manager. The language of Section 6(7) provides an option for individuals; it does not create a general requirement for every business to appoint or become a Consent Manager.
A Consent Manager is a separate registered entity. A business that collects or processes personal data does not automatically become one. However, businesses should consider how they will interact with registered Consent Managers where individuals choose to use their services. For example, an e-commerce company may receive a consent-related instruction through a platform used by its customer. A financial services organisation may need to understand how consent is communicated when personal information is shared between participating entities. The exact technical and operational arrangements will depend on the applicable standards, platform requirements and the legal obligations in force. Businesses should not assume that simply signing up with a Consent Manager transfers their responsibility for personal data processing to that platform.
9. What Should Businesses Do to Prepare in 2026?
Even where a business does not intend to register as a Consent Manager, it should understand how the new framework may affect its consent-management processes. A useful starting point is to review how personal data is collected, why it is collected and how consent-related instructions are recorded.
The following steps can help.
Review existing consent practices
Examine the consent requests presented through websites, applications, registration forms and customer-facing platforms. Check whether the purpose of processing is clearly explained and whether the organisation can identify the consent associated with a particular activity.
Map personal data and processing activities
Identify the categories of personal data collected, the systems in which they are stored and the departments or service providers that process them. This will help the organisation understand where consent-related instructions may need to be implemented.
Review technology and system integration
Businesses should assess whether their existing systems can communicate with external consent-management platforms where required. The assessment may involve APIs, identity verification, consent-status updates, audit trails and internal access controls. The final technical requirements should be evaluated against the standards and directions issued by the Board.
Strengthen record-keeping
A business should be able to identify what consent was obtained, the purpose for which it was obtained and the relevant changes or withdrawals recorded over time. Clear records can help organisations investigate customer complaints and demonstrate how consent-related instructions were handled.
Review vendor and service-provider arrangements
Where customer information is processed through third-party platforms, businesses should examine contractual arrangements, responsibilities and information-sharing processes. This is particularly relevant where several service providers participate in a single customer-facing transaction.
Assign internal responsibility
Legal, compliance, IT, information security and business teams should understand their respective responsibilities. Consent management should not be treated as an isolated IT project. It involves legal interpretation, customer communication, system design and operational processes.
Monitor regulatory developments
Businesses should keep track of directions, standards, registration details and other guidance issued by the Data Protection Board and the Ministry of Electronics and Information Technology. The implementation framework may require organisations to revisit their systems as further regulatory details become available.
10. What Risks Should Businesses Watch Out For?
The introduction of Consent Managers may improve transparency, but it does not remove the practical risks associated with personal data processing. Businesses should pay particular attention to the following areas.
Unclear consent records: If an organisation cannot establish which consent was obtained and for what purpose, it may face difficulties responding to disputes or demonstrating compliance.
Delayed implementation of withdrawal instructions: A withdrawal instruction must be handled through an appropriate process. Organisations should consider how instructions received through external platforms will reach the relevant systems and teams.
Weak system integration: If the consent-management platform and the business's internal systems do not communicate correctly, an instruction may not be reflected consistently across different processing activities.
Over-reliance on third-party platforms: Using a Consent Manager does not mean a business can stop reviewing its own data practices. The organisation must understand its independent responsibilities under the applicable law.
Conflicts of interest and inadequate security: For entities seeking registration as Consent Managers, governance, independence and security arrangements are central to maintaining regulatory confidence.
A consent-related issue may begin as a customer request, but poor handling can create wider legal, operational and reputational concerns.
11. Consent Managers and the Future of Data Protection Compliance in India
Consent Managers represent an important development in India's approach to personal data governance. They introduce a structured mechanism through which individuals can manage consent across participating organisations. At the same time, the registration and operational requirements indicate that these platforms are expected to meet defined standards of independence, security and accountability.
For businesses, the development should be viewed as part of a broader shift towards more transparent data practices. The practical challenge will be ensuring that consent is not treated merely as a one-time acceptance during registration. Organisations will need to consider how consent is communicated, recorded, reviewed and acted upon throughout the customer relationship.
The transition will also depend on interoperability. A consent instruction has limited practical value if the systems responsible for processing personal data cannot recognise and implement it correctly. Businesses that review their processes early will be better positioned to respond as the wider DPDP framework becomes operational.
Conclusion
Consent Managers are an important part of the evolving data protection framework in India. Their introduction gives individuals a structured way to manage consent while placing specific registration, governance and security responsibilities on the entities operating these platforms. For businesses, the important takeaway is that consent management cannot be treated as a one-time compliance exercise. Organisations should understand their data flows, review how consent is recorded and prepare their systems to handle consent-related instructions appropriately.
The wider DPDP framework is being implemented in phases. Businesses should therefore follow the applicable commencement dates carefully and avoid treating future obligations as though they are already in force. Preparing early, reviewing internal processes and obtaining appropriate legal guidance can help organisations approach the transition with greater clarity.
How Lexcuriam Can Help
Lexcuriam LLP advises businesses, startups and institutions on data protection, regulatory compliance, corporate governance and legal risk management. Our team can assist organisations in reviewing their data-handling practices, assessing DPDP compliance requirements, examining privacy policies and contractual arrangements, and preparing internal governance processes for the evolving regulatory framework. For legal guidance on DPDP compliance and data protection governance in India, connect with Lexcuriam LLP.
Frequently Asked Questions
A Consent Manager is an entity registered with the Data Protection Board of India that enables individuals to give, manage, review and withdraw consent for the processing of their personal data through an accessible, transparent and interoperable platform.
Rule 4 of the DPDP Rules, 2025 and Section 6(9) of the DPDP Act follow a one-year commencement timeline from 13 November 2025. Accordingly, these provisions became effective on 13 November 2026.
The applicant must have a net worth of at least ₹2 crore, along with the other financial, operational, management and technical conditions prescribed under the First Schedule of the DPDP Rules, 2025.
No. The applicant must be a company incorporated in India and must satisfy the prescribed registration conditions. It must also obtain the required independent certification of its interoperable platform and secure registration from the Board
The Act does not impose a general requirement on every business to appoint a Consent Manager. Section 6(7) allows individuals to manage their consent through one. Businesses should, however, assess how they may need to interact with registered platforms when individuals choose to use them.
No. A Consent Manager facilitates consent management. It does not automatically take over the legal responsibilities of a Data Fiduciary. Each organisation must assess and fulfil its own obligations under the applicable provisions of the DPDP framework.
The First Schedule requires a Consent Manager to retain the specified records for at least seven years, or for a longer period as agreed with the Data Principal or as required by law.
The Data Protection Board may issue directions requiring corrective measures. Where necessary, and after following the prescribed process, it may suspend or cancel the Consent Manager's registration and issue directions to protect Data Principals.
