1. Home
  2. Tools
  3. Rule 7 breach report template

Template

Rule 7 breach report template

A working outline for the Board intimation, the 72-hour detailed report and the notice to each affected person. It is not an official Board form.

Updated 4 Nov 2026

Short answer

Rule 7 requires a Data Fiduciary to intimate each affected Data Principal and the Board without delay after becoming aware of a personal data breach. Within 72 hours of becoming aware, or longer if the Board allows on a written request, it must give the Board a detailed report covering the facts, cause, mitigation, findings on who caused it, remedial steps and the intimations made to Data Principals. This template mirrors those contents; it is not an official Board form, so adapt it with counsel.

A working outline that mirrors Rule 7. It is not an official Board form. Fields ending in a colon are for you to fill in. Adapt it with counsel.

Personal data breach: intimations and detailed report (template)

About this document

This is a working template that mirrors the contents listed in Rule 7 of the Digital Personal Data Protection Rules, 2025. It is not an official Board form.

Check the current Rules and any Board directions before you file.

Part A. Intimation to the Board (without delay)

Data Fiduciary (legal name):

Contact for this incident (name, email, phone):

Date and time you became aware of the breach:

Date and time of this intimation:

Short description of the breach:

Part B. Intimation to each affected Data Principal (without delay)

Send in plain language through the person's user account or registered contact.

What happened: the nature, extent and timing of the breach:

Likely consequences for you:

What we have done and are doing to reduce the risk:

Steps you can take to protect yourself:

Who to contact (name or role, email, phone):

Part C. Detailed report to the Board (within 72 hours of becoming aware)

Facts and circumstances of the breach:

Events leading to the breach and its cause:

Measures taken or proposed to mitigate the risk:

Findings on the person who caused the breach, if known:

Remedial steps taken to prevent a recurrence:

Report on the intimations given to affected Data Principals:

Date this report is submitted:

If submitted after 72 hours, reference of the Board's permission on your written request:

Part D. Evidence appendix (internal)

Incident reference (sample format: INC-2041):

Systems and data stores affected:

Number of affected Data Principals (estimate):

Types of personal data involved:

Timeline of events, with times:

Logs retained and where they are kept:

Decisions and approvals, with names and times:

What Rule 7 asks for, and when

  1. 01Without delay: each affected Data Principal

    In plain language, through their user account or registered contact: the nature, extent and timing of the breach, likely consequences, mitigation, safety steps they can take, and a contact.

  2. 02Without delay: the Board

    An intimation to the Data Protection Board on becoming aware of the breach.

  3. 03Within 72 hours: the detailed report

    Facts and circumstances, cause, mitigation, findings on who caused it, remedial steps, and a report on the intimations to Data Principals. The Board can allow longer on a written request.

Read the full Rule 7 explainer and the 72-hour playbook.

How to use the template

Fill in names, contacts and approvers before any incident, so the template is ready. When a breach happens, start the evidence log at once and send both intimations without delay.

Then complete the detailed report within 72 hours. Keep every draft and decision with its time.

Other duties may apply

CERT-In's directions of 28 April 2022 under s.70B of the IT Act require reporting specified cyber incidents to CERT-In within 6 hours, a separate duty from Rule 7 that this template does not cover. Check your sector regulator's directions alongside DPDP.

What this template is not

Not an official Board form

This is a working template, not an official Board form, and no Board members have been appointed yet. It is educational, not legal advice and not a certification. Check the current Rules and adapt it with counsel.

How TruePrivacy helps

Breach management records the incident, runs a risk assessment before notifying, and keeps a clock per audience: the Board without delay (TruePrivacy uses a 24-hour working target), the detailed report within 72 hours, and each affected Data Principal without delay.

It sends individual notifications and closes with a post-incident review whose actions can create entries in the risk register.

Sources

  • Digital Personal Data Protection Act, 2023 (Act No. 22 of 2023)
  • Digital Personal Data Protection Rules, 2025, G.S.R. 846(E), 13 November 2025

Updated 4 Nov 2026. Educational information, not legal advice.

Questions, answered

Educational, not legal advice.

All DPDP FAQs
What goes in the Rule 7 detailed report?

The facts and circumstances of the breach, its cause, mitigation, findings on who caused it, remedial steps, and a report on the intimations made to affected Data Principals.

When is the detailed report due?

Within 72 hours of becoming aware of the breach, or longer if the Board allows on a written request.

Is this an official DPDP breach reporting form?

No. It is a working template, not an official Board form. Check the current Rules and any Board directions before you file.

What must we tell affected people?

In plain language, through their user account or registered contact: the nature, extent and timing of the breach, likely consequences, mitigation, safety steps they can take, and a contact (Rule 7).

Your DPDP plan, starting today

Core obligations for data fiduciaries begin on 13 May 2027.

13 May 2027

Core obligations begin