Skip to content

How Do You Report a Data Breach Under the DPDP Rules?

DPDP data breach notification: tell the Board and every affected person without delay, then send the Board a detailed report within 72 hours under Rule 7.

By the GRC-Flow team · Published · 7 min read

Key takeaways

  • Under Section 8(6) of the DPDP Act and Rule 7 of the DPDP Rules 2025, every personal data breach must be reported to the Data Protection Board and to each affected Data Principal.
  • Both the Board and the affected people must be told without delay; the Board must then receive a detailed report within 72 hours of the Data Fiduciary becoming aware of the breach, or longer if the Board allows.
  • There is no threshold or low-risk exemption: a small breach is reportable just like a large one.
  • Failing to notify can cost up to ₹200 crore, separate from the up to ₹250 crore penalty for weak security safeguards.

How do you report a data breach under the DPDP Rules?

You tell the Data Protection Board and every affected person without delay, then send the Board a detailed report within 72 hours. Section 8(6) of the DPDP Act and Rule 7 of the DPDP Rules 2025 set this duty for every Data Fiduciary. There is no size or risk threshold: every personal data breach counts.

What counts as a personal data breach?

A personal data breach is any unauthorised processing of personal data, or its accidental disclosure, acquisition, sharing, use, alteration or destruction, or loss of access to it, that compromises its confidentiality, integrity or availability. A misdirected email with a customer list, a stolen laptop, ransomware that locks a patient database and an exposed storage bucket can all qualify.

What is the DPDP breach notification timeline?

The DPDP breach notification timeline has three steps, two of them immediate:

WhoWhenWhat to send
Each affected Data PrincipalWithout delayA plain notice of what happened and what they can do
Data Protection BoardWithout delayA first intimation: the nature, extent, timing, location and likely impact of the breach
Data Protection BoardWithin 72 hours of becoming aware, or longer if the Board allowsA detailed report on the facts, cause, mitigation and notices sent

These duties apply from 13 May 2027, with the other business obligations in the DPDP Rules 2025. Other reporting duties, such as CERT-In's cyber incident directions or a sector regulator's rules, apply separately and can have their own deadlines.

What must you tell affected people?

The notice to affected people must be concise, clear and plain, sent through their user account or the contact they gave you, and cover:

  • what happened: the nature, extent, timing and location of the breach;
  • the consequences relevant to them that are likely to arise;
  • what you have done or are doing to reduce the risk;
  • the safety measures they can take to protect themselves;
  • the business contact of a person who can answer their questions.

What goes in the 72-hour report to the Board?

The detailed report to the Board updates your first intimation and covers:

  1. the broad facts of the events, circumstances and reasons that led to the breach;
  2. the measures taken or proposed to mitigate the risk;
  3. any findings about the person who caused the breach;
  4. the remedial steps taken to stop it happening again;
  5. a report on the notices sent to affected Data Principals.

What happens if you don't report a breach?

Failing to notify the Board and affected people can lead to a penalty of up to ₹200 crore. If the breach happened because reasonable security safeguards were missing, a separate penalty of up to ₹250 crore can apply. The Board weighs how quickly you acted when setting the amount, so a prompt, documented response matters. See the full schedule in DPDP Act penalties.

How do you get ready before a breach happens?

  • Write a breach playbook that names who decides, who drafts and who sends each notice.
  • Keep templates for the Data Principal notice, the first intimation and the 72-hour report.
  • Know where personal data lives, so you can tell quickly whose data was affected.
  • Require every Data Processor by contract to tell you about a breach straight away.
  • Keep logs that let you investigate: the Rules require processing logs to be kept for at least one year.
  • Run a drill and record what you learned.

How GRC Flow helps

GRC Flow's breach register tracks each incident against the 72-hour Board report, with an owner and the notices sent, as part of its DPDP registers. It can also draft a breach playbook from your own data inventory and vendor list, which a person reviews before it is used (see DPDP documents).

Frequently asked questions

What is the breach notification timeline under the DPDP Rules?

Inform the Data Protection Board and each affected Data Principal without delay. Then send the Board a detailed report within 72 hours of becoming aware of the breach, or within a longer period if the Board allows it on a written request.

Do all personal data breaches need to be reported under the DPDP Act?

Yes. Unlike GDPR, the DPDP Act and Rules have no risk threshold. Every personal data breach must be reported to the Board and to the affected Data Principals.

What must a breach notice to affected people contain?

A plain description of the breach (its nature, extent, timing and location), the likely consequences for them, what the Data Fiduciary is doing to reduce the harm, the safety measures they can take, and a contact who can answer their questions.

What is the penalty for not reporting a data breach under the DPDP Act?

Up to ₹200 crore for failing to notify the Board and affected Data Principals. If the breach happened because reasonable security safeguards were missing, a separate penalty of up to ₹250 crore can also apply.

Does a Data Processor report breaches to the Board?

The duty to notify sits with the Data Fiduciary. The Data Fiduciary should require its processors by contract to tell it about any breach straight away, so it can meet the timeline.

Sources

This guide explains the law in general terms and is not legal advice. Check specific situations with a qualified lawyer.