Is the DPDP deadline 13 or 14 May 2027? Why sources disagree by 1 day

Search for the DPDP compliance deadline and you will find 2 answers. Some sources say 13 May 2027. Others say 14 May 2027. The same split runs through the earlier deadline: 13 or 14 November 2026 for Consent Manager registration.

Neither camp is inventing anything. The disagreement traces to a genuine ambiguity in how the notification date itself is recorded, and once you see it, the whole thing becomes simple to reason about.

The Rules never state a calendar date

This is the fact that most explainers skip. Rule 1 of the DPDP Rules 2025 does not say "these obligations begin on 13 May 2027". It sets periods that run from publication:

"Rules 1, 2 and 17 to 21 shall come into force on the date of their publication in the Official Gazette."

"Rules 3, 5 to 16, 22 and 23 shall come into force eighteen months after the date of publication of this Gazette."

Corrigenda G.S.R. 892(E) of 10 December 2025 corrected the closing words of Rule 1(3) and Rule 1(4) to read "in the Official Gazette", so that is the operative wording today. The periods, 1 year and 18 months, were not touched, and no computed date moves.

The Act side commencement notification, G.S.R. 843(E), is drafted the same way, using "one year from the date of publication of this gazette" for the group containing section 6(9) and section 27(1)(d). No corrigendum on file amends that notification, so the Act side still reads "of this gazette" where Rule 1 now reads "in the Official Gazette".

So every calendar date you have ever seen for DPDP compliance is a computation, not a quotation. The computation needs an input the text does not supply: the date of publication. It also needs a convention for counting a period from that date, which the text does not state either. The publication date is where the 2 answers in circulation come from.

The publication date is recorded 2 ways

The third row matters most. The 14 May 2027 figure is not a blogger's arithmetic error. It follows the Government's own public statement of the notification date, published by the Press Information Bureau. Anyone who tells you 14 May 2027 is simply computing from the date the Government itself announced.

Equally, the date the instrument states for itself is 13 November 2025: it is on the masthead of issue No. 760, in the heading of G.S.R. 846(E), and repeated in the December 2025 corrigenda, which describe that notification as dated the 13th November, 2025. That is the date this site computes from, and it is why our pages say 13 May 2027.

What this actually means for planning

The honest answer is that the framework's own text gives you a period and the record of its start carries a 1 day ambiguity. That has 3 practical consequences.

1. Plan to the earlier date. If your programme is built to be ready on 13 May 2027, the 1 day question never affects you. If it is built to land on 14 May 2027, you have made a 1 day ambiguity into a compliance risk for no benefit.
2. Do not quote either date as settled law. Say "computed from the notification, approximately mid May 2027" in board papers, and cite the period rather than the date. The Rules state 18 months; that is the durable fact.
3. Watch for an official confirmation. A clarificatory notification, a Board direction or a MeitY FAQ stating the operative dates would settle this. No such confirmation appears in the official sources on file as at 24 August 2026, so every calendar date on this site, including 13 May 2027 and 13 November 2026, is labelled interpretation until officially confirmed.

Why we chose the printed date

2 reasons, both about which document controls.

Both records sit on the same document. The masthead and the notification heading read 13 November 2025, while the file code stamped on the issue embeds 14112025. We take the date the instrument states for itself, because it is the only one of the 2 that the document asserts as its own date, and because the corrigenda published in December 2025 refer back to the notification as dated the 13th November, 2025. No official source on file explains what the date inside the file code records, so treat this choice as our interpretation rather than a settled rule about which record controls.

Consistency also matters more than the individual choice. The Act side notification, Gazette issue No. 757, carries the same split: masthead 13 November 2025, CG code embedding 14112025. Computing the Act group and the Rules group from different bases would produce a timeline that contradicts itself. We take the printed date for both, and we say so on every page that shows a computed date.

The corrigenda issued on 10 December 2025 did reach Rule 1: items (i)(a) and (i)(b) change the closing words of Rule 1(3) and Rule 1(4) from "of this Gazette" to "in the Official Gazette". The 1 year and 18 month periods are unchanged, so no computed date moves. What the corrigenda do add is that an official instrument published in December 2025 twice describes G.S.R. 846(E) as dated the 13th November, 2025, which supports the printed date without settling the date of publication in terms.

The wider lesson about DPDP dates

If a source states a DPDP deadline without saying what it computed from, you cannot check it, and a 1 day gap between 2 sources usually traces to nothing more than the choice of publication date set out above.

The test to apply to any DPDP date you read: does the source name the period from the text, and does it name the publication date it used? If it does neither, it is repeating a number rather than reading the law.

What to do

Settle the dates that apply to your organisation with the compliance plan, which shows the commencement basis beside every action. For the current status of each provision, see what is in force today, and for the full chronology, the DPDP timeline. The original documents, including both Gazette issues and the corrigenda, are listed on the official documents page.