Privacy

What is the GDPR 72-hour breach notification rule?

Direct answer

Under GDPR Article 33, a controller must notify the competent supervisory authority of a personal data breach without undue delay and, where feasible, within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to individuals.

Where the breach is likely to result in a high risk, the controller must also notify affected data subjects under Article 34. The clock starts at awareness, not at the conclusion of the investigation; Article 33(4) permits phased notification as facts emerge. Every breach must be documented under Article 33(5) whether or not it meets the notification threshold.

What counts as a personal data breach?

Article 4(12) of the GDPR defines a personal data breach as a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data transmitted, stored or otherwise processed. The EDPB notes that all personal data breaches are security incidents, but not all security incidents are personal data breaches.

The EDPB’s Guidelines 9/2022 group breaches into three types, and one breach can be more than one of them:

  • Confidentiality breach: unauthorised or accidental disclosure of, or access to, personal data.
  • Integrity breach: unauthorised or accidental alteration of personal data.
  • Availability breach: accidental or unauthorised loss of access to, or destruction of, personal data.

The availability type is the one teams most often miss. In the EDPB’s example of a lost USB key holding unencrypted personal data, the controller may never know whether anyone read the data, but the loss itself is an availability breach and has to be notified.

When exactly does the 72-hour clock start?

The EDPB treats a controller as aware when it has a reasonable degree of certainty that a security incident has occurred that has led to personal data being compromised. After a first alert, a short period of investigation to establish whether a breach has happened does not count as awareness, but that investigation should begin as soon as possible. A more detailed investigation can follow after notification.

When a processor holds the data, Article 33(2) requires it to notify the controller without undue delay after becoming aware of the breach. The EDPB considers the controller, in principle, aware once the processor has informed it, and recommends that processors alert controllers promptly and send further details in phases. The processor does not first assess the risk: that assessment belongs to the controller.

If the notification reaches the authority after 72 hours, Article 33(1) requires it to be accompanied by the reasons for the delay.

What must the notification say, and who receives it?

Under Article 33(3), the notification must at least:

  • describe the nature of the breach, including where possible the categories and approximate number of data subjects and of personal data records concerned;
  • give the name and contact details of the data protection officer or another contact point;
  • describe the likely consequences of the breach;
  • describe the measures taken or proposed to address it and mitigate its possible adverse effects.

The recipient is the supervisory authority competent under Article 55. For cross-border processing, the EDPB says notification goes to the lead supervisory authority, which is not necessarily where the affected people are or where the breach happened. A controller not established in the EU but subject to the GDPR under Article 3(2) or 3(3) cannot rely on the one-stop-shop through its representative, so it must notify every supervisory authority in whose member state affected data subjects reside. The EDPB added this point in version 2.0 of the guidelines, adopted on 28 March 2023.

When do you also have to tell the people affected?

Article 34 applies when the breach is likely to result in a high risk to the rights and freedoms of individuals. The communication must use clear and plain language, describe the nature of the breach and contain at least the contact point, the likely consequences and the measures taken. It is not required where:

  • the affected data was protected by measures that make it unintelligible to anyone not authorised to access it, such as encryption;
  • later measures ensure the high risk is no longer likely to materialise;
  • it would involve disproportionate effort, in which case a public communication or a similar, equally effective measure replaces it.

The supervisory authority can require the controller to inform the people affected if it has not done so.

Other regimes run their own clocks. A breach in Switzerland follows the FADP, which asks for a report to the FDPIC as soon as possible when a breach is likely to lead to a high risk (see the FADP compliance checklist), and a financial entity may also have to report a major ICT-related incident under DORA.

How Acuna GRC handles it

Sources

  1. Regulation (EU) 2016/679 (GDPR), Articles 4(12), 33, 34 and 83(4)
  2. EDPB Guidelines 9/2022 on personal data breach notification under GDPR, version 2.0

This page explains the rules in general terms and is not legal advice.

Frequently asked

Do weekends count in the 72 hours?

Article 33 sets the limit as 72 hours after awareness, with no exception for weekends or public holidays. The EDPB refers to Regulation No 1182/71, the EU rules on periods, dates and time limits, for how such periods are counted. Plan your response rota on that basis.

Can a processor decide a breach is not notifiable?

No. A processor must tell the controller about any breach without undue delay under Article 33(2). The EDPB states that the processor does not need to assess the risk first: the controller decides whether to notify the authority and the people affected.

What fine applies to a failure to notify?

Breaches of Articles 33 and 34 fall under Article 83(4)(a): administrative fines of up to EUR 10 000 000 or, for an undertaking, up to 2 % of total worldwide annual turnover of the preceding financial year, whichever is higher.

See how Acuna GRC runs this.

Tell us your frameworks and your team. We show you how Acuna GRC runs the program.

Hosted in Switzerland, the EU or the US