DPDP Rules 2025Updated 22 November 202610 min read

DPDP Data Breach Notification: The 72-Hour Rule Explained

Rule 7 requires every personal data breach to be reported to affected individuals and the Data Protection Board, with a detailed Board report within 72 hours. No materiality threshold applies.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Provision
Rule 7(1) and 7(2); Act section 8(6)
In force from
13 May 2027
Initial Board intimation
Without delay
Detailed Board report
Within 72 hours of becoming aware
Extension
Longer period if the Board allows on written request
Materiality threshold
None: every breach
Penalty for failure to notify
Up to ₹200 crore
Parallel CERT-In timeline
6 hours for specified cyber incidents

Quick answer

Under Rule 7 of the DPDP Rules, 2025, on becoming aware of any personal data breach, a Data Fiduciary must without delay inform each affected Data Principal and send the Board a description of the breach. Within 72 hours of becoming aware, or longer if the Board allows, it must file a detailed report. There is no materiality threshold. Rule 7 applies from 13 May 2027.

  • Every personal data breach is reportable under Rule 7; unlike the GDPR, there is no risk or materiality threshold.
  • The Board gets two reports: an immediate description without delay, then detailed information within 72 hours of becoming aware.
  • Each affected Data Principal must be told without delay, through her user account or registered communication mode, in plain language.
  • The 72-hour report must include causes, mitigation, findings on who caused the breach, remedial measures and a report on user intimations.
  • Failure to notify a breach can attract a penalty of up to ₹200 crore, separate from up to ₹250 crore for weak safeguards.

Who this is for: CISOs and incident response teams, Data Protection Officers, Legal counsel, Customer communications teams, Data Processors and SaaS vendors

What does the DPDP 72-hour breach rule require?

Section 8(6) of the DPDP Act requires a Data Fiduciary, in the event of a personal data breach, to intimate the Board and each affected Data Principal. Rule 7 sets the form and timing. It applies from 13 May 2027.

There are three notifications:

ToWhenRule
Each affected Data PrincipalWithout delay, to the best of the fiduciary's knowledge7(1)
The Board: initial descriptionWithout delay7(2)(a)
The Board: detailed reportWithin 72 hours of becoming aware, or a longer period the Board allows on written request7(2)(b)

All three are triggered "on becoming aware of any personal data breach". The Act defines a personal data breach broadly: any unauthorised processing, or accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access to personal data, that compromises its confidentiality, integrity or availability.

There is no materiality threshold. Rule 7 does not say "likely to result in harm" or "significant". A misdirected email with one customer's invoice is, on the text, a reportable breach. This is the single biggest difference from GDPR Article 33, which requires regulator notification unless the breach is unlikely to result in a risk to individuals.

The 72-hour clock runs from awareness, not from confirmation of scope or root cause.

What to tell affected Data Principals (Rule 7(1))

Rule 7(1) requires the fiduciary to intimate each affected Data Principal in a concise, clear and plain manner and without delay, through her user account or any mode of communication registered by her with the fiduciary. The message must contain:

  1. (a) a description of the breach, including its nature, extent and the timing of its occurrence;
  2. (b) the consequences relevant to her that are likely to arise;
  3. (c) the measures implemented and being implemented by the fiduciary, if any, to mitigate risk;
  4. (d) the safety measures she may take to protect her interests; and
  5. (e) business contact information of a person able to respond to her queries on the fiduciary's behalf.

Practical implications:

  • "User account" is defined broadly in Rule 2(1)(c) to include profiles, handles, email addresses and mobile numbers. Use in-app notification plus email or SMS to the registered contact.
  • "To the best of its knowledge" means you send what you know now and update later. Do not hold the message until the investigation ends.
  • Personalise consequences. A user whose password hash leaked needs different advice from one whose delivery address leaked. Segment by data elements affected.
  • Staff the contact. The person named under (e) will receive the queries; brief them before sending.

Pre-approve message templates now, with placeholders for each element, so the legal review on the day is minutes, not days.

The two Board reports: immediate and 72-hour

Initial intimation, Rule 7(2)(a): without delay. A description of the breach, including its nature, extent, timing and location of occurrence and the likely impact. Location appears here but not in the Data Principal notice, so record which systems, regions and vendors are involved.

Detailed report, Rule 7(2)(b): within 72 hours. Within 72 hours of becoming aware, or within a longer period the Board allows on a written request:

ItemContent
(i)Updated and detailed information on the description
(ii)Broad facts on the events, circumstances and reasons leading to the breach
(iii)Measures implemented or proposed to mitigate risk
(iv)Any findings regarding the person who caused the breach
(v)Remedial measures taken to prevent recurrence
(vi)A report on the intimations given to affected Data Principals

Points that catch teams out:

  • Item (vi) means individual notifications should be largely done, or at least under way and tracked, within 72 hours. Build the Data Principal notification pipeline to run in parallel with the investigation.
  • Item (iv) asks for findings about the person who caused the breach, so preserve evidence and logs that support attribution.
  • Extensions require a written request to the Board. Make it before the 72 hours expire, explaining what is outstanding and why.

The Board functions as a digital office under Rule 20, so expect digital submission.

When does the 72-hour clock start?

Rule 7 uses "on becoming aware" as the trigger and measures the 72 hours from when the fiduciary became aware of the breach. The Rules do not define "aware".

A defensible internal standard:

  • Aware = the point at which someone with responsibility for security or privacy has a reasonable basis to believe a personal data breach has occurred. Not when every detail is confirmed.
  • Record that moment in the incident ticket with a timestamp and the evidence available at that time.

Processors are the hidden risk. If your cloud host, CRM vendor or AI API provider suffers a breach, your clock effectively depends on how fast they tell you. Rule 6(1)(f) requires security provisions in processor contracts; use them to require breach notice within a short, fixed window, for example 24 hours, with the details you need for Rule 7(2)(a).

Clock synchronisation matters for evidence. CERT-In's 2022 Directions require systems to synchronise clocks to NIC or NPL NTP servers or traceable sources. Consistent timestamps across logs make your awareness timeline credible.

Do not let a debate about whether something is "really" a breach consume the window. Because there is no materiality threshold, the safer path is to treat confirmed unauthorised access to personal data as a breach and notify, then update as facts develop.

How Rule 7 fits with CERT-In and GDPR

A single incident can trigger three regimes with different clocks.

RegimeTriggerDeadlineRecipient
CERT-In Directions (28 April 2022)Specified cyber incidents6 hours of noticingCERT-In
DPDP Rule 7Any personal data breachWithout delay; detailed report within 72 hoursBoard and each affected Data Principal
GDPR Articles 33 and 34Personal data breach of EU-scope data72 hours where risk; individuals where high riskSupervisory authority and, where high risk, individuals

Build one incident runbook with three branches:

  1. Hour 0 to 6: classify the incident against the CERT-In list and file if required. In parallel, decide whether personal data is involved.
  2. Without delay: send the Rule 7(2)(a) description to the Board and start Data Principal notifications.
  3. By hour 72: file the Rule 7(2)(b) report and, if EU data is involved and the risk test is met, the GDPR Article 33 notification.

Use one evidence base, one timeline and one root-cause document for all three. Inconsistent accounts to different regulators are a credibility risk. The breach response playbook has an hour-by-hour plan.

Penalties and how to prepare before May 2027

The Act's Schedule provides two separate penalty lines that a breach can trigger:

  • Up to ₹200 crore for failing to give the Board or affected Data Principals intimation of a breach.
  • Up to ₹250 crore for failing to take reasonable security safeguards to prevent the breach.

These are per instance and decided by the Board after inquiry. A fiduciary that is breached despite good safeguards, and notifies properly, is in a far better position than one that does neither.

Preparation steps for the next six months:

  1. Define "personal data breach" internally using the Act's definition, with examples relevant to your systems.
  2. Write templates for the Board initial description, the 72-hour report (items (i) to (vi)) and the Data Principal message (items (a) to (e)).
  3. Build a notification pipeline that can segment affected users by data elements and send through in-app and registered channels at scale.
  4. Update processor contracts with short breach-notice windows.
  5. Run a tabletop exercise with legal, security, support and communications, timed against 72 hours.
  6. Keep one year of logs under Rules 6(1)(e) and 8(3), so you can actually answer the 72-hour questions.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Adopt the Act's breach definition internally

    Train teams that any unauthorised processing or accidental loss of personal data is a breach, with no materiality filter.

    Act section 2; Rule 7

  2. Template the Data Principal notice

    Cover nature, extent, timing, likely consequences, mitigation, safety steps and a contact person.

    Rule 7(1)(a)–(e)

  3. Template the initial Board intimation

    Cover nature, extent, timing, location and likely impact, ready to send without delay.

    Rule 7(2)(a)

  4. Template the 72-hour Board report

    Cover updated description, causes, mitigation, findings on the perpetrator, remedial measures and user intimation report.

    Rule 7(2)(b)

  5. Record the awareness timestamp

    Log when the fiduciary became aware, with supporting evidence, in every incident ticket.

    Rule 7(2)(b)

  6. Require fast breach notice from processors

    Set a short contractual window and required content for processor breach notices.

    Rule 6(1)(f)

  7. Align with CERT-In six-hour reporting

    Classify incidents against the CERT-In list in the first hours and file where required.

    CERT-In Directions 2022

  8. Rehearse against the clock

    Run a timed tabletop exercise covering all three notifications and an extension request.

    Rule 7

Key dates

  1. Rule 7 breach intimation obligations apply

Answers

Frequently asked questions

How long do you have to report a data breach under DPDP?

You must notify the Data Protection Board and each affected Data Principal without delay. The detailed report to the Board is due within 72 hours of becoming aware of the breach, or within a longer period the Board allows on a written request. Rule 7 applies from 13 May 2027.

Do all data breaches need to be reported under DPDP?

Yes. Rule 7 applies on becoming aware of any personal data breach. There is no threshold based on risk, harm or number of people affected. This is stricter than the GDPR, where regulator notification is not required if the breach is unlikely to result in a risk to individuals.

What must a DPDP breach notice to users contain?

Under Rule 7(1), a description of the breach including its nature, extent and timing; the likely consequences for her; mitigation measures taken or under way; safety measures she can take; and business contact details of a person who can answer her questions. It must be concise, clear and plain.

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

Up to ₹200 crore per instance for failing to intimate the Board or affected Data Principals. If the breach also reflects a failure to take reasonable security safeguards, a separate penalty of up to ₹250 crore may apply. The Board decides amounts after an inquiry.

Can the 72-hour DPDP deadline be extended?

Yes. Rule 7(2)(b) allows a longer period if the Board allows it on a request made in writing. Make the request before the 72 hours expire, explaining what information is outstanding and why. The initial intimation must still be sent without delay.

Do I report to both CERT-In and the Data Protection Board?

Often yes. CERT-In's April 2022 Directions require specified cyber incidents to be reported within 6 hours of noticing. Rule 7 separately requires personal data breaches to be reported to the Board and affected individuals. One incident can trigger both.

Is a data processor's breach my responsibility under DPDP?

Yes. The Data Fiduciary remains responsible for processing done on its behalf, so a processor's breach of your data triggers your Rule 7 duties. Require processors by contract to notify you quickly with the details you need.

Legal references and sources

  • Digital Personal Data Protection Rules, 2025 — Rule 7(1)(a)–(e) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 7(2)(a)–(b) (official text)
  • Digital Personal Data Protection Act, 2023 — Section 8(6) (official text)
  • Digital Personal Data Protection Act, 2023 — Schedule (penalties) (official text)
  • CERT-In Directions under section 70B(6) IT Act — 28 April 2022 (official text)

This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.

About the author

Suhas Bhairav

Suhas Bhairav

Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.