Startup Compliance

DPDP Consent Manager Registration Opens: What Businesses Should Do Now

India’s Consent Manager registration framework is now live. Understand the November 2026 update and prepare your business for the next DPDP implementation phase.

MEMyFinancialAdvisory Editorial21 November 20264 min read
On this page
  1. What changed in November 2026?
  2. Keep the two implementation phases separate
  3. First decide which project your business is running
  4. A practical 30-day preparation checklist
  5. Week 1: Map one complete customer journey
  6. Week 2: Review the words customers actually see
  7. Week 3: Test requests across connected systems
  8. Week 4: Review vendors, access and evidence
  9. Questions to ask before buying a consent tool
  10. Your next step

India’s data-protection rollout has reached a new milestone. For founders and finance, operations and technology teams, this is a useful moment to turn a broad “privacy compliance” project into a practical work plan.

Updated: 21 November 2026. This article separates the announced regulatory change from suggested business preparation.

What changed in November 2026?

The Ministry of Electronics and Information Technology confirmed that the DPDP Consent Manager registration framework took effect on 13 November 2026. Eligible companies can apply through the Data Protection Board of India’s portal at dpbi.gov.in.

A registered Consent Manager helps individuals give, manage, review and withdraw consent through an accessible, transparent and interoperable platform. Applicants must be incorporated in India, have adequate technical, operational and financial capacity, and meet a minimum net worth requirement of ₹2 crore. The Board assesses applications and will publish registered entities on its website. Source: MeitY/PIB announcement, 14 November 2026.

Keep the two implementation phases separate

The same announcement places other key provisions covering individuals’ rights, Data Fiduciaries’ obligations, and the Board’s inquiry and penalty processes in the 13 May 2027 phase. The November milestone should therefore not be presented as the commencement of every operational DPDP requirement.

Rule 1 of the notified DPDP Rules separately provides a one-year commencement period for Rule 4 and an eighteen-month period for Rules 3, 5–16, 22 and 23. See the official Gazette notification.

First decide which project your business is running

There are two different planning questions: do you want to build a regulated consent-management business, or do you want to improve how your existing business handles personal data?

For the first, start with Rule 4, the First Schedule and the Board’s current application instructions. A net worth figure alone is not an approval, and filing an application is not the same as obtaining registration.

For the second, begin with your own systems and customer journeys. Before buying software, identify the problem it must solve, the teams that will operate it and the evidence it must produce. Treat any vendor’s claim of Board registration as something to verify against the official register.

A practical 30-day preparation checklist

The following is a suggested internal project plan, not a list of new statutory deadlines.

Week 1: Map one complete customer journey

Choose a real workflow, such as a website enquiry becoming a paying customer. Record the information collected, the purpose of each field, the systems it enters, the staff who can access it and the vendors that receive it. Include spreadsheets, support tickets and exports; these are easy to miss when reviewing only the main application.

Deliverable: a data-flow map with a named owner for each system.

Week 2: Review the words customers actually see

Collect screenshots of signup forms, enquiry forms, marketing preferences and privacy notices. Check whether a customer can understand what happens after submitting information. Flag vague descriptions, unnecessary fields and promises that your operations cannot currently fulfil. Have the proposed wording assessed against the applicable legal requirements before deployment.

Deliverable: a prioritised list of notice and form changes, with an owner and target date.

Week 3: Test requests across connected systems

Use a fictional test customer to trace what happens when a preference changes or someone asks a privacy question. Check whether the request reaches support, marketing tools and any relevant vendor. Record unresolved handoffs. A button that updates one database may leave several downstream copies untouched.

Deliverable: a tested workflow, an escalation contact and a log of remaining gaps.

Week 4: Review vendors, access and evidence

List the service providers involved in the chosen journey. Ask what records they can export, how access is controlled, how they support incident investigation and what happens when the contract ends. Agree who in your business maintains the evidence and checks progress each month.

Deliverable: a vendor action list and a short management review with clear decisions.

  • Can the supplier demonstrate the exact workflow you need using test data?
  • Can you retrieve understandable records without depending on a proprietary dashboard?
  • How are preference changes passed to your existing applications?
  • Which responsibilities remain with your employees and other vendors?
  • If the supplier claims to be a registered Consent Manager, where can you verify that claim?

Avoid treating a product label or a “compliance-ready” sales statement as proof that your whole business is ready. Ask for a demonstration, document the limitations and assign responsibility for the work the software does not perform.

Your next step

Appoint one accountable project owner and complete the first customer-journey map this week. That gives your legal, operations and technology teams a shared starting point for assessing applicability, prioritising changes and preparing for the next implementation phase.

This article provides general information and suggested preparation steps, not a legal opinion or a certification of compliance. Check current MeitY and Data Protection Board publications and obtain advice for your business’s specific processing activities.

Share this guideWhatsApp
ME

Written by

MyFinancialAdvisory Editorial

Editorial guidance prepared for business owners and reviewed before production publication.

Written against official sources, with the governing rule named wherever a figure or deadline is given. General guidance — not advice on your specific case.

Need a hand?

Get this handled, end to end.

Tell us your situation and we’ll map the documents, review points and next steps — AI-assisted checks, reviewed by qualified experts, tracked in your portal.