India’s Consent Manager Framework Starts: What the DPDP Data Privacy System Means

India’s Consent Manager Framework Starts: What the DPDP Data Privacy System Means

India has started the registration framework for Consent Managers under the Digital Personal Data Protection (DPDP) Act, 2023. The framework took effect on 13 November 2026. On 14 November, the Ministry of Electronics and Information Technology (MeitY) announced an online portal where eligible Indian companies can apply to become registered Consent Managers.

This is a step in the phased implementation of India’s data protection system. It is not a new app that every citizen must install. It is a registration route for eligible companies that want to provide a service for managing consent related to personal data.

Consent Manager Framework: Key Facts

LawDigital Personal Data Protection Act, 2023
Framework effective date13 November 2026
Portal announced14 November 2026
Registration portaldpbi.gov.in
Applicant typeCompanies incorporated in India
Minimum net worth₹2 crore
Other key DPDP provisions scheduled13 May 2027

Table of Contents

A Consent Manager is an entity registered with the Data Protection Board of India. It provides a platform through which a person, called a Data Principal under the law, can give, manage, review and withdraw consent relating to personal data.

The framework aims to make consent processes accessible, transparent and interoperable. In simple terms, a registered Consent Manager is intended to help people manage permissions across services through a structured platform. It must be accountable to the people whose consent it manages.

How Is the Framework Intended to Work?

When a person uses a digital service, the organisation may need to process personal data for a stated purpose. A Consent Manager platform is intended to help the person record and manage consent choices. The person should be able to review those choices and withdraw consent through the service where the law and applicable process allow it.

A Consent Manager is not the same as a data controller or a general customer support agent. It has a specific role under the DPDP framework and must be registered by the Board. Registration and oversight are important because the service may handle sensitive records of consent decisions.

Infographic 1: What a Consent Manager Does

Four Core Actions

Give consent

Record a person’s permission for a stated data use.

Manage consent

Keep choices organised through an accessible platform.

Review consent

Allow a person to check recorded choices.

Withdraw consent

Provide a route to withdraw a consent choice.

The exact user experience will depend on registered services and the applicable legal requirements.

Who Can Apply to Become a Consent Manager?

MeitY says companies incorporated in India may apply. They must have adequate technical, operational and financial capacity. The announced minimum net worth requirement is ₹2 crore.

Meeting the minimum financial requirement does not guarantee registration. The Data Protection Board will assess applications against the applicable requirements. Qualifying companies may be registered. The Board is expected to make the list of registered Consent Managers publicly available on its website.

How Does the Registration Process Work?

  1. Visit the official Data Protection Board portal.
  2. Review the current Consent Manager registration framework and application requirements.
  3. Check that the company is incorporated in India and meets the minimum net worth requirement.
  4. Prepare evidence of technical, operational and financial capacity.
  5. Submit the application through the official portal.
  6. Respond to any assessment or clarification request from the Board.
  7. Check the Board’s official information for the registration decision and public list.

Applicants should use the official portal and current framework documents. They should not rely on third-party summaries for legal requirements or assume that a submitted application means the company is registered.

Infographic 2: DPDP Implementation Timeline

Two Important Dates

13 November 2026

Consent Manager framework

Registration framework takes effect.

13 May 2027

Other key provisions

Specified Data Principal rights, Data Fiduciary obligations and Board inquiry and penalty processes are scheduled to commence.

These are separate implementation stages. Do not assume that every DPDP obligation starts on the same date.

What Should Individuals Know?

People do not need to apply for Consent Manager registration as individual users. The registration route announced by MeitY is for eligible companies. Individuals should still take care when sharing personal information online.

  • Read the purpose stated in a consent notice before agreeing.
  • Check which information a service wants to collect.
  • Do not approve a request that is unclear or unrelated to the service.
  • Keep a record of important privacy choices where possible.
  • Use official information to check whether a company is registered as a Consent Manager.
  • Never share passwords, banking PINs or one-time passwords with someone claiming to manage consent.

What Should Businesses Prepare?

Organisations that collect or use personal data should understand their role under the DPDP Act and Rules. The Consent Manager framework does not replace an organisation’s own legal responsibilities. Businesses should review their data practices and keep their notices clear.

  • Map the personal data the organisation collects and uses.
  • Record the purpose for each category of data.
  • Review consent notices for clarity and plain language.
  • Limit data collection to what is needed for the stated purpose.
  • Review access controls, security safeguards and retention practices.
  • Track official commencement dates and seek qualified legal advice.

Infographic 3: A Simple Digital Privacy Checklist

Before You Share Personal Data

  • Do I understand why the information is needed?
  • Is the organisation clearly identified?
  • Can I review the privacy notice?
  • Can I change or withdraw consent through the stated process?
  • Am I using the genuine website or app?
  • Have I avoided sharing passwords and OTPs?

MASA World Editorial Insight

Digital privacy depends on clear choices, responsible organisations and effective oversight. A Consent Manager framework can help people manage consent, but public trust will depend on how registered services work in practice. People need simple information. Businesses need clear processes. Regulators need transparent registration and accountability.

For now, readers should follow official MeitY and Data Protection Board updates. Companies considering registration should study the framework before applying. Users should not assume that every app is already connected to a registered Consent Manager.

Frequently Asked Questions

MeitY says the registration framework took effect on 13 November 2026.

The announced route is for eligible companies incorporated in India, not ordinary individual users.

What is the minimum net worth requirement?

The announcement sets a minimum net worth of ₹2 crore for applicant companies.

Where can companies apply?

Eligible companies can use the Data Protection Board portal at dpbi.gov.in.

When are other key DPDP provisions scheduled to start?

The announcement schedules specified rights, obligations and Board processes for 13 May 2027.

A Consent Manager is intended to help a person give, review and withdraw consent through a clear digital process. In the data protection framework, consent must be meaningful and linked to a specific purpose. A person should be able to understand what information is requested and why it is needed. A consent record should not become a blanket permission for unrelated uses.

The framework places importance on a person’s ability to manage consent over time. This includes access to information about the request, the ability to make a choice and a route to withdraw consent. The organisation processing the data remains responsible for meeting its legal duties. Using a Consent Manager does not remove that responsibility.

  • Identify the organisation asking for the data.
  • Read the stated purpose and check whether it is specific.
  • Check what categories of personal data are requested.
  • Look for the retention period or information about how long data may be kept.
  • Understand how to withdraw consent or raise a grievance.
  • Do not approve a request simply because it appears inside a familiar app.

What Businesses and Developers Should Prepare

Organisations should map the personal data they collect and the purposes for which they use it. They should review privacy notices, consent screens, data retention practices and access controls. A clear interface should explain choices in plain language. It should not hide important information in long blocks of legal text or use confusing buttons that pressure people into agreeing.

Developers should test how consent choices move between systems. They should check whether a withdrawal is communicated to the relevant data controller and whether records are updated. Security controls should protect consent records from unauthorised access or alteration. Teams should also plan how to respond when a person asks for information or raises a complaint.

Privacy compliance involves more than collecting consent. Organisations may have duties relating to security safeguards, data accuracy, retention, breach response, grievance handling and children’s data. The applicable duties depend on the law, the organisation’s role and the circumstances of processing. A Consent Manager cannot make an unlawful data practice lawful simply by recording a click.

Individuals should be cautious about sharing identity documents, financial details or sensitive information through unverified links. Businesses should not describe themselves as registered or approved unless they can confirm that status through the official process. The regulatory framework may develop through rules, notifications and implementation guidance, so readers should check current official publications.

Practical Questions for the Next Stage

As the system develops, people will need to know which Consent Managers are registered, how to identify them and how complaints are handled. Businesses will need clear technical standards and reliable records. Public awareness will matter because consent tools only work when people understand the choices they are making. Clear communication and secure design are essential to public trust.

Official Sources

A person may agree to share contact details so a service can send account updates. That choice should not automatically be treated as permission to use the same details for unrelated advertising. A person may also agree to a service that needs location information for a specific feature. The request should explain why location is needed and whether the feature can work without it.

These examples show why purpose and clarity matter. A consent request should make the choice understandable at the time it is presented. Organisations should avoid bundling unrelated purposes into one confusing request. They should also make it practical for a person to change a choice later.

Questions to Ask About a Privacy Notice

  • Who is responsible for deciding how the data is used?
  • What data is collected and for what stated purpose?
  • Is the data shared with another organisation?
  • How can a person correct information or withdraw consent?
  • Where can a complaint be submitted?

People should not feel pressured to accept a request they do not understand. If a service makes a feature conditional on data sharing, the reason should be clear. Organisations should provide support for people who need help understanding digital choices.

Scroll to Top