13 November Opens DPDP Consent Manager Registration. It Is Not Your Compliance Deadline.
Rule 4 switches on a year after notification. The duties that bind most Indian SaaS companies start six months later.
Search for "DPDP November 2026" and the results are full of countdown clocks. Several vendor blogs tell data fiduciaries to have consent-manager integrations running by 13 November. The primary text says something narrower. The DPDP Rules, 2025 were notified on 13 November 2025 as G.S.R. 846(E), and Rule 4, which covers the registration and obligations of consent managers, is the one rule that starts a year later.
That makes 13 November 2026 a milestone for a small group of companies that want to be consent managers. For everyone else it is a date to understand, not a date to panic about. This piece separates the two and lists what is worth doing in the six months before the larger deadline.
What actually switches on
The Rules were written with three start dates. A few administrative rules, including those about the Data Protection Board of India, took effect on notification in November 2025. Rule 4 follows after twelve months. The remaining rules, which hold the operational duties for data fiduciaries, start after eighteen months, on 13 May 2027.
| Date | What starts | Who it affects |
|---|---|---|
| 13 November 2025 | Short title, definitions, the Board and its procedure | Government; mostly institutional |
| 13 November 2026 | Rule 4: consent manager registration and obligations | Companies applying to be consent managers |
| 13 May 2027 | Notice, security safeguards, breach reporting, children’s data, erasure, rights handling | Data fiduciaries and processors |
One caution on sources. Commentaries disagree on small points, such as whether particular sections of the Act itself start in 2025 or 2026. The Rule 4 date is consistent across everything we read. Where a summary and the Gazette text differ, the Gazette text wins.
Who can be a DPDP consent manager
A consent manager is a registered intermediary. Under Section 6 of the Act, a Data Principal can give, manage, review and withdraw consent through one, and the consent manager is accountable to the Data Principal rather than to the company asking for consent.
The eligibility bar is deliberately high. Reporting on the Rules lists these conditions:
- An Indian-incorporated company with a net worth of at least Rs 2 crore.
- Adequate technical, operational and financial capacity, and directors and senior management of sound reputation.
- Articles of association that prevent conflicts of interest with data fiduciaries, and cannot be amended without the Board’s prior approval.
- An independent certification that the platform meets the Board’s technical standards and has adequate security and audit measures.
Once registered, a consent manager must be data-blind: personal data passing through its platform stays unreadable to it. It must keep records of consents, withdrawals, notices and data sharing for at least seven years, make them available to users in machine-readable form, audit itself and report the outcome to the Board. It cannot subcontract its obligations or change control without Board approval.
“Rule 4 decides who may stand between a person and a company that wants their consent. It does not decide what that company must build.”
Is integration mandatory? Read the claim carefully
Some commentary says fiduciaries must integrate with consent managers by 13 November. We could not find that in the Rules. Coverage that follows the text closely says working with a consent manager is optional. Read the Act and the Rules yourself before you accept either framing, and take legal advice for your own facts.
The practical pressure is different. Once consent managers are registered, a large customer, a bank or a health-data platform may ask to give consent through one. If you refuse, you may lose the customer. One speaker at a roundtable reported by Medianama put it as letting the customer go or working with the consent manager. That is a commercial risk, and it arrives on the customer’s schedule, not the statute’s.
What to do before 13 May 2027
The overlap between what a consent manager will ask of you and what the 2027 duties already demand is large. Work that pays off either way:
- Map every place consent is collected, and the purpose each consent covers. A consent given for one purpose cannot quietly serve another.
- Make withdrawal propagate. If a user withdraws, every system holding that data, including analytics, backups with a deletion queue, and processors, must learn about it. Test with a real withdrawal and trace where it stops.
- Store consent events as an append-only log with timestamp, notice version, purpose and channel. Make it exportable as structured data.
- Decide retention for that log. Consent managers carry a seven-year floor for their own records, and a log you can produce on request is easier to defend than one reconstructed from three databases.
- Keep a short list of processors and where each receives personal data, so notices and erasure requests can be routed.
None of this needs a vendor. Most of it needs a person who owns the question of where consent lives in the product. In a ten-person company that is usually the CTO, with a lawyer on call.
What to watch between now and May
Three things will move. First, whether the Board publishes registration forms, fees and technical standards, and when the first consent managers are approved. Second, whether the Government changes the May 2027 date. One source we read mentions a proposal to compress the eighteen-month window, but we found no confirmation that it was adopted, so plan for May 2027 and watch the Gazette. Third, how large buyers write consent-manager acceptance into their vendor questionnaires.
If the first registered consent managers appear in the weeks after 13 November, the useful question for engineering teams will be whether their consent log can answer a withdrawal request from outside the product. That is worth being able to answer before anyone asks.
Frequently asked questions
Related reading
Your AI Act Marking Deadline Is 2 December 2026, Not 2027. The Delay Covered High-Risk, Not Article 50.
The AI Act delay everyone read about moved the high-risk rules. It left the Article 50(2) marking duty in place, with a 2 December 2026 cut-off for systems shipped before August.
Stamp Duty on an Arbitral Award Is Due on Signing, Delhi High Court Says. Karnataka Disagrees.
Delhi High Court held that an arbitral award is chargeable to stamp duty when signed, and that a late deposit does not cure the defect. Karnataka reads the timing differently.
Cross-Border Card Authentication: RBI's 1 October Deadline Is a Switch, Not an OTP on Every Purchase
RBI's 1 October 2026 deadline obliges Indian card issuers to honour authentication requests from overseas merchants. It does not put an OTP on every foreign purchase.