Section 8(6) of the DPDP Act 2023 requires every Data Fiduciary to notify the Data Protection Board — and affected individuals — of a personal data breach. The DPDP Rules 2025 make this a two-part obligation to the Board: an initial intimation "without delay," followed by detailed particulars within 72 hours of becoming aware (or a longer period the Board allows). Affected individuals must also be told "without delay." Here's everything you need to know.
Quick Answer: What Is the 72-Hour Breach Rule?
Under Section 8(6) of the DPDP Act 2023 and Rule 7 of the DPDP Rules 2025, a Data Fiduciary must intimate the Data Protection Board and affected individuals "without delay" on becoming aware of a personal data breach, then give the Board detailed particulars within 72 hours (or a longer period it allows). Rule 7 comes into force on 13 May 2027. Failing to notify can attract a penalty of up to ₹200 Crore.
What Counts as a Personal Data Breach?
Section 2(u) of the Act defines a personal data breach as any unauthorised processing of personal data, or any accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access to personal data, that compromises its confidentiality, integrity or availability. Reporting one is among the core obligations every business must meet. Common examples:
- A hacker gains access to your customer database
- An employee accidentally emails a spreadsheet of customer data to the wrong person
- You lose a laptop or phone containing unencrypted customer data
- A cloud storage bucket containing customer records is misconfigured as public
- A WhatsApp message with customer details is sent to the wrong contact
- An ex-employee downloads the customer list before leaving
The breach doesn't have to be a sophisticated cyberattack. Any incident that results in customer data being accessed by someone not authorised to see it qualifies.
The 72-Hour Clock: When Does It Start?
The 72-hour clock starts from the moment you become aware of the breach — not from when the breach occurred. If a breach happened three days ago but you discovered it today, the 72-hour clock started today.
This "aware" standard does not reward not knowing. Rule 6(1)(c) requires logs and monitoring that allow unauthorised access to be detected, and Rule 6(1)(e) requires those logs to be kept for one year. A business without them has not met the security safeguards duty in Section 8(5), which carries its own penalty of up to ₹250 Crore under the Schedule (see the penalties guide).
Who Must Be Notified?
Two separate notification obligations:
1. The Data Protection Board
Rule 7(2) sets out two reports to the Board.
Without delay: a description of the breach, including its nature, extent, timing and location, and its likely impact.
Within 72 hours of becoming aware (or a longer period the Board allows on a written request):
- Updated and detailed information on that description
- The broad facts about the events, circumstances and reasons that led to the breach
- Measures taken or proposed to reduce the risk
- Any findings about the person who caused the breach
- Remedial measures taken to prevent it happening again
- A report on the notices given to affected individuals
2. Affected Individuals (Data Principals)
Every person whose data was compromised must be notified without delay, in concise, clear and plain language, through their account or a registered mode of communication. The notification must describe the nature, extent and timing of the breach, its likely consequences, the measures you've taken to mitigate it, what the individual can do to protect themselves, and your contact point — enough for them to take protective action (e.g., "your email and phone number were exposed — be alert for phishing attempts").
What If You're Not Sure It's a Breach?
If you discover an incident but are not certain it is a "breach", the cautious course is to send the Board its first intimation anyway, noting that the investigation is ongoing. Rule 7(2) is built for this: the first intimation is due without delay and needs only what you know at that point, and the detailed report follows within 72 hours. If the investigation shows no personal data was compromised, say so in that report.
Penalties for Missing the Deadline
Failing to give the Board or affected individuals notice of a breach under Section 8(6): a penalty that may extend to ₹200 Crore (Schedule, item 2). This is separate from the penalty of up to ₹250 Crore for failing to take reasonable security safeguards under Section 8(5) (item 1). Both are maximums. Under Section 33(2), the Board must consider the nature and gravity of the breach, whether the business acted to reduce its effects and how quickly and how well it did so, and whether the penalty is proportionate.
Why Do Breach Notifications Miss the 72-Hour Deadline?
Most late breach notices are not caused by a business ignoring the rule. The deadline is usually lost in the first few hours, before anyone has decided that the incident is a breach at all. The causes below are the ones a business can fix in advance. Rule 7 comes into force on 13 May 2027, eighteen months after the DPDP Rules were published on 13 November 2025, so there is time to put the fixes in place before it applies.
1. The clock started earlier than the team thought
The 72 hours run from the moment the business becomes aware of the breach (Rule 7(2)(b)). They do not run from the end of an investigation, from the day a manager was told, or from the next working day. Many teams start counting when the owner hears about the problem. By then a staff member may have noticed something odd a day earlier and said nothing, or mentioned it on a team chat.
The Rules do not define the exact moment of "becoming aware". The safe working assumption is that the clock starts when the first credible report reaches anyone in the business who is responsible for the data. Write that time down straight away.
2. The first notice waited for the full report
Rule 7 asks for two things from the Board, at two different times:
- Without delay: a description of the breach, covering its nature, extent, timing, location and likely impact (Rule 7(2)(a)).
- Within 72 hours: the detailed report. This covers updated details, the facts and reasons behind the breach, steps taken to reduce the risk, any findings about who caused it, steps to stop it happening again, and a report on the notices sent to affected people (Rule 7(2)(b)).
A common mistake is to treat 72 hours as the only deadline, and to hold back the first notice until the investigation is complete. The first notice only needs what you know at that point. The 72-hour report is where the investigation's findings go. Affected individuals must also be told "without delay" (Rule 7(1)). That duty runs alongside the Board notice, not after it.
3. A vendor knew first and told you late
Many breaches happen at a supplier: a cloud host, a billing or accounting software provider, a payroll firm, a marketing agency. The DPDP Act calls these suppliers Data Processors. The duty to notify still rests with your business. Section 8(1) makes the business (the Data Fiduciary) responsible for processing done on its behalf by a Data Processor, whatever any agreement says.
The Act and Rules do not give the supplier its own deadline for telling you. That gap is closed by your contract. Section 8(2) allows a Data Processor to be engaged only under a valid contract, and Rule 6(1)(f) expects that contract to include reasonable security safeguards. Add a clause that requires the supplier to tell you about any incident involving your customers' data promptly, within a fixed number of hours, and to name who at the supplier will tell you.
4. Nobody owned the decision
When an incident is found, someone has to decide, quickly, whether it is a personal data breach and whether to notify. If that person is not named in advance, the question passes from the IT person to the accountant to the owner, and the hours run out. The Act's definition is broad. A personal data breach includes any unauthorised processing, or any accidental disclosure, sharing, use, alteration, destruction or loss of access to personal data, that compromises its confidentiality, integrity or availability (Section 2(u)). A simple decision rule helps: if customer or employee data may have reached the wrong person, been changed, or been lost, treat it as a breach and start the notices. If the investigation later shows nothing was compromised, say so in the 72-hour report.
5. The business could not see what happened
A business cannot describe a breach it has no record of. Rule 6(1)(c) requires logs and monitoring that make it possible to detect unauthorised access, and Rule 6(1)(e) requires those logs to be kept for one year. Without them, the 72-hour report has no facts to rely on, and the team spends the time rebuilding events from memory.
6. A second, shorter clock was missed: CERT-In
Separate from the DPDP Act, CERT-In's directions of 28 April 2022, issued under Section 70B(6) of the Information Technology Act, 2000, require service providers, intermediaries, data centres, body corporate and Government organisations to report listed cyber incidents to CERT-In within 6 hours of noticing them or being told about them. The list includes data breaches, data leaks and unauthorised access to IT systems or data. Reports go by email to incident@cert-in.org.in or by phone on 1800-11-4949. These directions are already in force, while Rule 7 applies from 13 May 2027.
The two are separate reports to separate authorities on separate clocks. A team that is focused on the 72-hour Board report can easily miss the 6-hour CERT-In report. Decide in advance whether your business falls within the CERT-In directions. If it does, put the 6-hour report first on your incident sheet.
When the Board decides a penalty, Section 33(2)(e) of the Act requires it to consider whether the business acted to reduce the effects of the breach, and how quickly and how well it did so. A prompt, honest first notice, followed by a complete 72-hour report, is part of the record the Board will look at.
Causes and fixes at a glance
| Why the deadline is missed | What to put in place now | Where it comes from |
|---|---|---|
| The clock is counted from the wrong moment | Record the time of the first credible report, not the time the owner hears of it | Rule 7(2)(b) |
| The first notice waits for the investigation | Send the Board a short first notice without delay; keep the findings for the 72-hour report | Rule 7(2)(a) and (b) |
| Customers are told after the Board, or not at all | Prepare the customer notice in advance and send it alongside the Board notice | Rule 7(1) |
| A supplier reports the incident late | Add a contract clause with a fixed reporting window and a named contact at the supplier | Section 8(1), 8(2); Rule 6(1)(f) |
| No one is authorised to decide | Name one decision-maker and a backup, and agree the decision rule in writing | Section 8(4), 8(6) |
| No record of what happened | Keep access logs and monitoring for at least one year | Rule 6(1)(c), (e) |
| The CERT-In 6-hour report is missed | Check whether the CERT-In directions apply to you; if so, make it the first report on the list | CERT-In directions, 28 April 2022, para (ii) |
| The detailed report cannot be finished in 72 hours | Ask the Board in writing for a longer period, before the 72 hours end | Rule 7(2)(b) |
A short readiness check
Go through these with your team, or with your CA, before May 2027:
- Is one person named to decide whether an incident is a breach, with a backup when they are away?
- Does every staff member know to report anything unusual at once, and to whom?
- Does every supplier that handles customer data have a contract clause requiring prompt incident reporting to you?
- Is a first notice to the Board drafted, with blanks for the nature, extent, timing, location and likely impact?
- Is a plain-language customer notice drafted, covering the five points Rule 7(1) asks for?
- Are access logs kept for a year, so the 72-hour report can be based on facts?
- Have you checked whether the CERT-In 6-hour report applies to your business?
Building Your Breach Response Plan Now
The time to plan for a breach is before it happens. Prepare:
- Detection: What monitoring do you have in place? (Security alerts, access logs, anomaly detection)
- Escalation: Who in your team gets called when a potential breach is detected? Who makes the notification decision?
- Documentation: A breach log template that captures incident details
- DPB Notification: A draft notification form ready to complete
- Customer Notification: A template WhatsApp/SMS/email to send to affected customers
- Containment: Steps to limit the damage (disable compromised accounts, rotate credentials, revoke access)
Your Breach-Response Checklist
When a breach is discovered, nobody has time to re-read this article. Work the sequence below — it's also the one-page PDF at the top of this post, formatted for pinning next to the server rack or billing desk.
- Note the awareness time. The legal clocks run from the moment you become aware — record it immediately.
- Contain. Revoke compromised access, isolate affected systems, stop the leak before you explain it.
- Start the incident log. What happened, what data, how discovered, who is acting — timestamped as you go.
- Notify affected customers without delay. Nature, extent and timing of the breach, likely consequences, your mitigation, their safety steps, and a contact person, in concise, clear and plain language, through their account or the contact details they registered with you. Using the language they normally deal with you in is good practice.
- Send the Board its initial intimation without delay — in parallel, not after, the customer notices.
- File detailed particulars with the Board within 72 hours — cause, extent, mitigation, remediation. Need longer? Request it in writing before the deadline.
- Keep proof of every notification sent — the timeline you can reconstruct is the compliance you can prove.
- Fix the root cause and update the plan — the Board's view of a repeat incident will be far harsher.
How EasyDP Handles Breach Notification
EasyDP's compliance dashboard includes a breach-reporting workflow. When you log a breach incident, the system:
- Starts the 72-hour countdown timer
- Generates a draft DPB notification from your business and incident details
- Identifies which customers are affected based on your EasyDP data records
- Drafts customer notifications in their preferred languages
- Logs every action with timestamps for your audit trail
The goal: when a breach happens at 2 AM, you're not scrambling to figure out what to do. The process is already defined.
References & Sources
- Ministry of Electronics & IT, Government of India — The Digital Personal Data Protection Act, 2023 (Section 8(6), breach intimation; the Schedule).
- The Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E)) — Rule 7, "Intimation of personal data breach."
- India Code — Digital Personal Data Protection Act, 2023 (Act No. 22 of 2023), official consolidated text.
- Indian Computer Emergency Response Team (CERT-In), MeitY — Directions under Section 70B(6) of the IT Act, 2000, No. 20(3)/2022-CERT-In, 28 April 2022 (para (ii), 6-hour reporting; Annexure I).
This article is general information about the DPDP Act 2023 and DPDP Rules 2025, not legal advice. Section and rule references are cited from the official text; verify against the current notified version for your specific situation. Commencement dates stated as of October 2026.