DPDP Act Breach Notification: The 72-Hour Reporting Requirement to the Data Protection Board

Summarise on:

In India’s evolving data protection landscape, the Digital Personal Data Protection (DPDP) Act, 2023 establishes rigorous requirements for organizations handling personal data. One of the key mandates under the DPDP Act is the 72-hour breach notification timeline, which requires organizations to report data breaches to the Data Protection Board within a short window of discovery.

This article provides an in-depth understanding of the 72-hour notification requirement, explains what you need to include in your breach report, and discusses best practices to ensure compliance and avoid penalties.

What Is the 72-Hour Breach Notification Requirement?

The DPDP Act requires that organizations notify the Data Protection Board whenever a data breach occurs that affects personal data. The crucial part of this requirement is the 72-hour timeline: businesses must report breaches to the Data Protection Board within 72 hours of discovering the incident.

While this is consistent with global standards such as the GDPR (General Data Protection Regulation) in the European Union, it is important to understand the nuances of DPDP breach reporting in India. The 72-hour notification period is not just a regulatory formality but a necessary action to mitigate risk and prevent further harm to data subjects.

Read also: DPDP Compliance Privacy Maturity Report

Understanding the Data Protection Board

Under the DPDP Act, the Data Protection Board plays a critical role in overseeing data protection issues in India. When a breach occurs, organizations must notify the Board as part of the compliance process.

This report must detail:

  • The nature of the breach
  • Categories of data involved
  • Impact on data subjects
  • Any actions taken to mitigate the breach

Failure to notify the Data Protection Board within 72 hours can result in severe penalties. It is crucial for organizations to follow the DPDP Act breach notification rules closely.

Read also: DPDP Compliance for Businesses in India

When Does the 72-Hour Clock Begin?

The 72-hour countdown begins when an organization becomes aware of a personal data breach. This means that the moment the breach is detected or suspected, organizations must act promptly to assess the situation and prepare the necessary documentation for submission.

While the DPDP Act provides some flexibility around the specific details that need to be provided within the first 72 hours, it’s crucial to act swiftly. The timing of the notification can affect the outcome of the breach, including:

  • How quickly corrective measures can be applied
  • The extent of any potential fines or penalties
  • The trust and reputation of the organization

Read also: Personal Data Search (PDS) for DPDP Compliance

What Information Must Be Included in the Notification?

According to the DPDP Act and its rules, breach notifications must be detailed and include the following:

  • Description of the breach: Including when and how it occurred.
  • Affected data types: Personal, sensitive, or critical data compromised in the breach.
  • Risk assessment: Explanation of the potential consequences for the affected individuals.
  • Measures taken: Immediate actions taken to contain and mitigate the breach (e.g., data recovery, security patching).
  • Contact details: A designated person or Data Protection Officer (DPO) who can provide further information.

This information helps the Data Protection Board understand the severity and scope of the breach and take appropriate action, such as advising affected individuals or enforcing corrective measures.

Read also: What is Data Minimization? Meaning & Importance

Penalties for Failing to Meet the 72-Hour Deadline

Failing to notify the Data Protection Board within the mandated 72-hour period can result in serious consequences. While the DPDP Act doesn’t specify the exact penalties for late reporting, similar regulations in other jurisdictions (like the GDPR) have shown that non-compliance can lead to:

  • Fines based on the severity of the breach
  • Legal repercussions including civil or criminal penalties
  • Reputational damage that may harm customer trust and business operations

Moreover, consistent breaches or non-reporting can attract higher scrutiny from regulators, leading to even more severe long-term consequences.

Read also: Data Minimization Under DPDP: What, Why & How

Comparing DPDP Breach Notification with Global Standards

India’s DPDP Act mirrors global data privacy laws like the GDPR in many respects, including its 72-hour breach notification requirement. GDPR has set the benchmark for timely breach reporting, and India’s DPDP Act follows this model, ensuring that organizations prioritize quick responses to personal data breaches.

Here’s a comparison:

AspectDPDP ActGDPR (EU)
Breach Notification PeriodWithin 72 hoursWithin 72 hours
Who to NotifyData Protection BoardRegulatory authorities
Who is AffectedIndividuals whose data is compromisedIndividuals whose data is compromised
PenaltiesSevere penalties for delayed reportingFines up to €20 million or 4% of global turnover

Adhering to this 72-hour rule not only ensures compliance but also strengthens your organization’s overall data governance strategy, showing that you are proactive and responsible in safeguarding personal data.

Read also: Shadow Data Processing & DPDP Audit Failures

Best Practices for Meeting the 72-Hour Deadline

To ensure you meet the 72-hour notification requirement under the DPDP Act, follow these best practices:

1. Create a Breach Response Plan

Your organization should have a data breach response plan that details roles, responsibilities, and timelines. This plan should include procedures for assessing a breach, notifying stakeholders, and reporting to the Data Protection Board.

2. Implement Continuous Monitoring Systems

Having automated systems in place to monitor and detect potential breaches is crucial. By detecting a breach early, you can start the 72-hour countdown right away and ensure quick reporting.

3. Designate a Data Protection Officer (DPO)

A Data Protection Officer should be appointed and be responsible for coordinating the response to any breach. This individual or team will be the primary point of contact for the Data Protection Board.

4. Document Every Step

Document every action taken during the breach response. This includes breach detection, internal reporting, risk assessments, and communications. Having comprehensive documentation will help demonstrate compliance if the breach is investigated later.

5. Educate and Train Your Team

Ensure your compliance and IT teams are trained to detect breaches quickly and report them in the shortest time possible. Conduct regular breach response exercises to ensure your team is prepared.

Read also: DPDP Act: Data Privacy as a Business Imperative

Key Takeaways

  • DPDP Act breach notifications must be made within 72 hours of discovering a breach.
  • Notifications must include a detailed description of the breach, affected data, and measures taken.
  • The Data Protection Board is the primary authority for breach reporting, similar to global regulators under the GDPR.
  • Failing to meet the 72-hour timeline can lead to severe penalties and reputational damage.
  • Organizations should have a breach response plan in place, with a designated Data Protection Officer (DPO) and continuous monitoring systems.

If you would like guidance on strengthening your DPDP compliance framework or understanding how governance, risk, and compliance tools can support your organization, feel free to contact us for assistance.

You can also visit our website to explore how modern GRC platforms help organizations manage data protection, risk management, and regulatory compliance in a more structured and scalable way.

FAQs

Under the DPDP Act, organizations must report data breaches to the Data Protection Board within 72 hours of discovering the incident. This notification should contain details of the breach, its impact, and the steps taken to mitigate it.

GRC Insights That Matter

Exclusive updates on governance, risk, compliance, privacy, and audits — straight from industry experts.

background-line