Short answer: Data breach notification under DPDP means telling every affected Data Principal and the Data Protection Board about a personal data breach without delay, then filing a detailed report with the Board within 72 hours of becoming aware of it. These duties come from Section 8(6) of the Act and Rule 7 of the DPDP Rules, 2025, and apply to most Data Fiduciaries from 13 May 2027.
Section 8(6) of the Digital Personal Data Protection Act, 2023 requires a Data Fiduciary to intimate the Data Protection Board of India and each affected Data Principal when a personal data breach occurs, in the form and manner prescribed. Rule 7 of the DPDP Rules, 2025 prescribes it. 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.
Two points catch teams out. First, the definition has no materiality threshold, so a small incident can still be reportable. Second, the 72-hour clock starts when you become aware of the breach, not when your investigation ends. For the full timeline of when each Rule applies, see our DPDP Rules 2025 timeline.
| Who You Notify | When | What It Must Cover |
|---|---|---|
| Each affected Data Principal | Without delay, after becoming aware |
|
|
Data Protection Board First intimation |
Without delay | A description of the breach, including its nature, extent, timing, location and likely impact. |
|
Data Protection Board Detailed report |
Within 72 hours of becoming aware, or a longer period allowed by the Board on written request |
|
Rule 7 sets one fixed deadline, the 72-hour report. The schedule below is our suggested internal plan, not wording from the Rules. It is built so that the "without delay" notices go out early and the detailed report is mostly written by the time the deadline approaches.
| Window | Goal | Actions |
|---|---|---|
| Hours 0 to 4 | Detect and triage | Log the time you became aware; open an incident record; assign an incident lead; preserve logs and evidence; confirm whether personal data is involved. |
| Hours 4 to 12 | Contain and scope | Stop the exposure by revoking keys, isolating systems or closing the affected storage bucket; identify affected systems, data types and Data Principals; check whether a processor is involved; start the CERT-In reporting clock if applicable. |
| Hours 12 to 24 | Notify without delay | Legal confirms reportability; send the first intimation to the Board; notify affected Data Principals in plain language through an appropriate registered channel or account; establish a contact point for questions. |
| Hours 24 to 60 | Investigate and remediate | Establish the root cause and responsible party; apply fixes; monitor for misuse; prepare the detailed report as findings become available. |
| Hours 60 to 72 | File | Compile the report; attach records of Data Principal notifications; obtain legal and DPO or privacy lead sign-off; submit the report to the Board; request an extension in writing if the investigation is incomplete. |
Do not wait for a complete investigation before sending the first notices. Delay because "we are still investigating" is not a safe position, and the Rule expects supplementary updates as facts emerge.
Write it for a non-expert, in clear and plain language, and send it through the channel the person uses with you, such as their user account or registered email or mobile number. Include:
Avoid blame, jargon and legal hedging. A clear notice reduces complaints, and a vague one can generate them.:
The last item is easy to forget. You need a record of who was told, when, through which channel and with what text, which is why notification tooling should log its own activity.
The Board will judge you on two things: whether you had reasonable security safeguards in place under Section 8(5), and whether you notified correctly. Both depend on evidence. Rule 6 expects logging, monitoring and review to detect unauthorised access, and retention of relevant logs and personal data for one year to support investigation.
That is why real-time audit trails and breach monitoring are practical requirements, not extras. They help in four ways:
If audit logs are scattered across applications and retained for different periods, reconstruction takes days. A single, consistent trail takes hours.
Failing to notify the Board and affected Data Principals can attract a penalty of up to ₹200 crore, and failing to maintain reasonable security safeguards up to ₹250 crore. Penalties are caps, set by the Board after considering factors such as gravity, duration and mitigation. The full schedule is in our guide to DPDP Act penalties and breach notification.
A breach-readiness checklist
Pixl is an AI-powered DPDP compliance platform with Discover, De-ID and Consent engines, deployable on-premise or in the cloud. The Discover engine maintains the data inventory that lets you scope an incident, the De-ID engine masks and tokenises data so less is exposed if a breach occurs, and the Consent engine keeps a signed, tamper-proof ledger with a full audit trail. The operations layer adds audit and reporting, producing inspection-ready records. To see the controls against your own systems, book a demo.
You must notify affected Data Principals and the Board without delay, and file a detailed report with the Board within 72 hours of becoming aware of the breach, or within a longer period the Board allows on written request.
When you become aware of the breach, not when the investigation is complete or the cause is confirmed.
The Act's definition has no materiality threshold, and the notification duty applies to a personal data breach. Build a process that reports promptly, and take legal advice on borderline cases.
No. CERT-In's cyber incident reporting directions are separate, with their own timeline, so a single incident can trigger both.
These operational improvements are one of the primary reasons companies are investing in finance automation technologies in 2026.
Ready to transform? Commence your Digital Transformation journey now!
Get Started