DPDP data breach notification, step by step
Breach handling is the requirement most likely to be tested without warning, and the one where preparation shows most clearly. It carries a statutory maximum of up to ₹200 crore, and in this assessment a must-do gap here caps your readiness band however well you score elsewhere.
Reviewed 16 September 2026Educational self-assessment content, not legal advice
What you owe, and to whom
Two audiences, two different communications. Affected people need to be told without delay, in concise, clear and plain language they can act on. The Data Protection Board needs an immediate account and then a fuller one.
- To affected people: what happened and when, the likely consequences for them, what you are doing about it, what they should do to protect themselves, and who to contact.
- To the Board, immediately: the nature, extent, timing and location of the breach, and its likely impact.
- To the Board, within 72 hours: updated and detailed information, remedial measures taken, the circumstances and who appears to have caused it, and confirmation that affected people were informed.
- An extension beyond 72 hours is possible only on a written request to the Board.
Why 72 hours is a detection problem
The clock starts when you become aware. Most organisations that miss the window do not miss it because of the paperwork, they miss it because nobody could say by hour 60 which people and which records were affected. That answer comes from logs, monitoring and an inventory prepared long before the incident.
The Rules expect you to be able to detect, investigate and reconstruct a breach, and to keep logs for that purpose. Build for the reconstruction, and the notification writes itself.
- A named incident owner and a deputy, with contact routes that work outside office hours.
- A plan that includes who decides that a breach is notifiable, because that decision needs an owner.
- Log retention and monitoring good enough to scope which records were affected.
- A breach register, including incidents you concluded were not notifiable and why.
- At least one rehearsal a year against a realistic scenario, with the timing recorded.
After the notification
Mitigation and root cause are also part of the record. The Board weighs what action was taken and how promptly when deciding a penalty, and repetition counts against you. A documented fix, dated, is worth keeping.
What we assess: Breach handling
- A breach response plan with named roles
- The Board is informed without delay, with a detailed report within 72 hours
- Affected people are informed without delay in plain language
- DPDP reporting is aligned with CERT-In's 6-hour reporting
- A breach register and post-incident review
- Breaches can be detected, not just reported
DPDP 72 hour breach reporting, and the clock behind it
The 72 hours does not start when you finish investigating. It starts when you become aware of the breach, which in practice is the moment someone in your organisation could reasonably have known. That is why personal data breach reporting in India is a detection problem long before it is a drafting problem.
Work backwards from the report you will have to file. It needs the nature and extent of the breach, when and where it happened, its likely impact, what you did about it, and confirmation that the affected people were told. Every one of those answers comes from logs, an inventory and a plan that existed before the incident.
- Hour 0: someone notices. Your plan names who decides whether this is notifiable, and that person is reachable out of hours.
- Early hours: scope it. Which systems, which records, which people. If the CERT-In directions also apply to your organisation, they carry their own, shorter reporting window, and that clock is already running.
- Hour 6 to 24: tell the Board what you know, and start telling affected people in plain language.
- Hour 24 to 72: file the fuller report, with remedial action and root cause.
- After: record it in the breach register, including incidents you decided were not notifiable, and why.
What to tell affected people
The communication to people is not the communication to the regulator. It should be short, in plain language, and written so someone can act on it: what happened, which kinds of their data were involved, what it might mean for them, what you are doing, what they should do, and a named contact who will answer.
Draft this template now, while nothing is on fire. Teams that write it during an incident write it badly, and a badly worded notification creates its own problem.
Frequently asked questions
What is the DPDP breach notification timeline?
Affected people must be told without delay. The Data Protection Board must be told without delay with initial details, followed by a fuller report within 72 hours of becoming aware, extendable only on a written request.
What is the penalty for failing to report a data breach in India?
Up to ₹200 crore under the Schedule to the Act for failing to notify the Board or affected people. Failing to take reasonable security safeguards carries a separate head of up to ₹250 crore.
Do I have to report every personal data breach?
The obligation attaches to a personal data breach as defined in the Act, which is broad. Record the incidents you conclude are not notifiable, and the reason, rather than deciding informally.
Who should report the breach inside a company?
Whoever your plan names. The point is that the decision has a single owner who can be reached out of hours, with a deputy, rather than being made by whoever notices first.
What is the DPDP data breach notification deadline?
Affected people must be told without delay. The Data Protection Board must be told without delay with initial details, and a fuller report follows within 72 hours of becoming aware, extendable only on a written request the Board allows.
Does DPDP breach reporting replace CERT-In reporting?
No. They are separate duties under separate instruments, with their own timelines, and the CERT-In window is the shorter of the two. Where both apply to one incident, both clocks run, which is why the decision needs a single named owner. Confirm the current CERT-In position with your adviser.
Do I have to report a breach if no harm was caused?
The duty attaches to a personal data breach as the Act defines it, which is broad and does not turn on a harm threshold. Where you conclude an incident is not notifiable, record the reasoning rather than deciding informally.
Related guides
- The DPDP Rules 2025 and what they addDPDP Rules 2025 explained: notice wording, consent managers, security safeguards, breach reporting, erasure, children and transfers, with commencement dates.Read the guide
- DPDP Act penalties, and what they actually meanDPDP Act penalties by head: up to ₹250 crore for security failures, ₹200 crore for breach reporting and children, ₹50 crore for the rest. All are maximums.Read the guide
- DPDP compliance checklistFree DPDP compliance checklist for 2026: 73 requirements across 13 areas, mapped to the Act and Rules, with priority and evidence columns you can score.Read the guide
- DPDP Act 2023 requirements for businesses, in plain EnglishDPDP Act 2023 requirements explained for Indian businesses: scope, data fiduciary duties, consent, notice, rights and penalties, and what is in force in 2026.Read the guide
See your readiness in five minutes.
Start with the quick check. You can move to the full assessment at any time without losing your answers.
The DPDP-AID Readiness Check is a free self-assessment tool for educational and self-learning purposes. It is not legal advice. Disclaimer
A free self-assessment tool for educational use. Not legal advice.