Guide
DPDP Act time limits and deadlines 2027: every clock in one table
Every DPDP Act and Rules time limit for 2027 in one table: 72-hour breach report, logs, erasure, grievances, SDFs, Consent Managers, with rule numbers.
Quick answer: Core DPDP duties start on 13 May 2027. The only fixed hour count in the Act and Rules is 72 hours, and it applies to the detailed breach report to the Data Protection Board. Everything else is a period in months or years, or "without delay". Telling affected people and the first notice to the Board have no hour count, and access, correction and erasure requests have no fixed response deadline.
People often ask for "the DPDP deadline" as if there were one. There are many clocks, in different rules, with different triggers. This page puts every fixed period from the DPDP Act, 2023 and the 2025 Rules in one table, with the rule number so your legal team can check each line against the Gazette text.
The three dates that start the clocks
The Act and Rules come into force in three steps. Which date applies to you depends on the duty.
The dates 13 November 2026 and 13 May 2027 are computed from the Gazette date of 13 November 2025 printed on the notifications. Some official file records show 14 November 2025, so check the Gazette text before relying on a single day.
Every DPDP time limit, by topic
| Time limit | What it applies to | Where | Note |
|---|---|---|---|
| Breach | |||
| Without delay | Tell each affected Data Principal | Rule 7(1) | No hour count is set for individuals. |
| Without delay | First notice to the Board: what happened, when, where, likely impact | Rule 7(2)(a) | No hour count is set for this notice either. |
| Within 72 hours | Detailed report to the Board | Rule 7(2)(b) | Or a longer period the Board allows on a written request. This is the only 72-hour clock. |
| Data kept and erased | |||
| One year | Keep logs and personal data for security (detect, investigate, remedy) | Rule 6(1)(e) | Unless another law requires a longer period. |
| At least one year from processing | Keep personal data, traffic data and logs for the Seventh Schedule purposes, including processing by a Data Processor | Rule 8(3) | A separate duty from Rule 6(1)(e). It still applies after the account is deleted. Erase afterwards unless another law requires longer retention. |
| Three years of inactivity | Erase data of e-commerce entities (2 crore or more registered users), online gaming intermediaries (50 lakh or more) and social media intermediaries (2 crore or more) | Third Schedule | Counted from the last approach, or the Rules' commencement if later. Exceptions apply for access to the user account and to virtual tokens. |
| At least 48 hours before erasure | Warn the Data Principal that data will be erased | Rule 8(2) | Applies to the Third Schedule entities above. |
| Rights and grievances | |||
| Not more than 90 days | Published period for responding to a grievance | Rule 14(3); s.13 | The ceiling is clear. The Rule's drafting is imperfect, so read the Gazette text. Use the grievance route before going to the Board (s.13(3)). |
| No fixed period | Requests for access, correction or erasure | ss.11, 12 | Neither the Act nor the Rules set a response deadline. |
| At any time | Withdrawal of consent | s.6(4) | Processing must stop within a reasonable time after withdrawal (s.6(6)). |
| Large companies (Significant Data Fiduciaries only) | |||
| Once in every 12 months | Impact assessment and audit, with a report to the Board | Rule 13(1), (2) | Applies only after notification as a Significant Data Fiduciary. |
| Consent Managers | |||
| At least seven years | Keep consent and sharing records | First Schedule, Part B, item 4(c) | Minimum period. |
| Enforcement | |||
| Six months, extendable by up to three months at a time | Board inquiry to be completed | Rule 19(9) | The Board can extend in blocks of up to three months. |
| 60 days | Appeal to the Appellate Tribunal (TDSAT) | s.29(2), (3) | Read the Act for the full appeal procedure. |
RBI, SEBI, CERT-In and other sector regulators set their own time limits. They are not covered here. Check your own regulator's rules.
Download this table as a one-page PDF Free, no sign-up.
Three common mix-ups
1. 72 hours is not for individuals
Telling affected people (Rule 7(1)) and the first notice to the Board (Rule 7(2)(a)) are both "without delay". Only the detailed report to the Board (Rule 7(2)(b)) has the 72-hour limit, and the Board can allow a longer period on a written request. For the full breach workflow, see our guide to reporting a DPDP data breach.
2. There are two one-year rules
Rule 6(1)(e) is a security rule: keep logs and personal data for one year so you can detect, investigate and remedy unauthorised access. Rule 8(3) is a separate minimum: keep personal data, traffic data and logs for at least one year from the date of processing, for the Seventh Schedule purposes. It also covers a Data Processor acting for you. See our retention and erasure mapping guide.
3. No deadline for rights requests
Neither the Act nor the Rules set a response deadline for access, correction or erasure requests (ss.11, 12). The only cap is on the grievance process: the published response period must not exceed 90 days (Rule 14(3)).
Status check, 17 October 2026
As of 17 October 2026, we found no official notification of any Significant Data Fiduciary, any appointed Data Protection Board Chairperson or Member, an open Consent Manager registration process, or any change to the commencement dates. This is a search finding, not an official statement. We will re-check on and after 13 November 2026. Compare dates in your own plan with our DPDP compliance timeline.
Frequently asked questions
What is the time limit to report a data breach under the DPDP Act?
Is the 72-hour limit for telling affected individuals?
When do the DPDP Act duties start?
Is there a deadline to respond to access, correction or erasure requests?
How long must logs be kept under the DPDP Rules?
Sources
- DPDP Act, 2023 (MeitY)
- DPDP Rules, 2025, G.S.R. 846(E) (MeitY)
- DPDP Rules, 2025 (eGazette)
- Correction notification, G.S.R. 892(E) (eGazette)
- Commencement notification, G.S.R. 843(E) (India Code)
This guide is for education and is not legal advice (see our disclaimer). Rule and section references follow the English Gazette text, as corrected by G.S.R. 892(E). Laws and notifications change, so check the current text and speak to a qualified lawyer before you act. Last checked: 17 October 2026. Version 1.0.
Guidance, not legal advice. dpdpactindia.in is an independent resource, not affiliated with the Government of India. Confirm specifics against the enacted Act and Rules.