GDPR data breach notification: the 72-hour rule step by step

A laptop is stolen, an invoice goes to the wrong customer, ransomware encrypts a file server. Under the GDPR, each of these can start a 72-hour countdown to notify the supervisory authority. Most companies do not fail because they ignore the rule, but because nobody knows who decides, when the clock started and what has to be written down. This guide walks through the process hour by hour.

GDPR Data breach Incident response Published: 8 min read

What counts as a personal data breach

Article 4(12) of Regulation (EU) 2016/679 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. The definition is broader than most people expect. It covers not only hacking, but also human error and availability incidents.

Regulators and the European Data Protection Board usually describe three categories. A confidentiality breach is unauthorised disclosure or access. An integrity breach is unauthorised alteration. An availability breach is loss of access or destruction, for example when ransomware encrypts data and there is no working backup. A temporary outage can also be a breach if it affects individuals in a meaningful way.

  • An email with a customer list sent to the wrong recipient
  • A lost unencrypted USB stick or laptop
  • Ransomware encrypting HR or customer records
  • A misconfigured cloud storage bucket that is publicly readable
  • An employee viewing records out of curiosity without a business reason

When the 72-hour clock actually starts

Article 33(1) requires the controller to notify the competent supervisory authority without undue delay and, where feasible, not later than 72 hours after having become aware of the breach. The key phrase is becoming aware. According to EDPB guidance, a controller is aware when it has a reasonable degree of certainty that a security incident has occurred that has led to personal data being compromised.

That does not mean you can wait for a full forensic report. A short initial investigation to establish whether a breach has happened is acceptable, but it should start immediately and be documented. If your service provider tells you on Friday evening that a database was exposed, your clock has probably started on Friday evening, not on Monday morning when the DPO reads the email.

The 72 hours are calendar hours, including weekends and public holidays. If you notify later, Article 33(1) requires you to give the reasons for the delay.

Step by step: the first 72 hours

A workable process splits the first three days into clear phases. The exact timing will vary, but writing down the phases in advance means people do not have to invent the process during a crisis.

Each step should leave a trace: a ticket, a timeline, a decision log. That record becomes part of the documentation required by Article 33(5) and is the first thing an authority will ask for if it opens an inquiry.

  • Hour 0: incident detected or reported. Log the time, the reporter and the first facts.
  • Hours 0 to 4: contain the incident. Revoke access, recall emails, isolate systems, change credentials.
  • Hours 0 to 24: assess. Which data, how many people, which categories, is it encrypted, who could access it?
  • Hours 12 to 48: decide on risk to individuals and whether notification is required. Record the decision and reasoning.
  • Before hour 72: notify the supervisory authority if required, even if some facts are still missing.
  • Afterwards: inform individuals if the risk is high, complete the investigation, send follow-up information, update the breach register.

Check your readiness for free

10–15 minutes, no account needed: readiness score, gap report and AI recommendations.

Do you need to notify? The risk test

Not every breach must be reported. Notification to the authority is required unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons. Communication to the affected individuals under Article 34 is required when the breach is likely to result in a high risk.

When assessing risk, consider the type of breach, the nature and sensitivity of the data, how easy it is to identify individuals, the severity of consequences, special characteristics of the people affected such as children, and the number of people involved. Health data, financial data, identity documents and login credentials usually point towards notification.

Article 34(3) lists cases where individual communication is not needed, for example when the data was protected by state of the art encryption and the key was not compromised, or when the controller has taken steps that ensure the high risk is no longer likely to materialise. Even when you decide not to notify, you must document the breach and the reasoning.

What the notification must contain

Article 33(3) sets the minimum content. Most authorities provide an online form that follows this structure, so prepare the information in the same order.

Article 33(4) allows information to be provided in phases. If you do not yet know the exact number of records, give your best estimate, say that the investigation is ongoing and send an update later. An incomplete notification on time is better than a complete one that is late.

  • The nature of the breach, including categories and approximate number of data subjects and records
  • Name and contact details of the DPO or another contact point
  • Likely consequences of the breach
  • Measures taken or proposed to address the breach and mitigate its possible adverse effects

Controllers, processors and cross-border cases

Only the controller notifies the authority. A processor, such as a hosting provider or payroll service, must notify the controller without undue delay after becoming aware of a breach (Article 33(2)). Your data processing agreements should specify a short deadline and the information the processor must provide, because the processor's delay directly eats into your 72 hours.

If you process data across several EU countries and have a main establishment in the EU, you usually notify the lead supervisory authority under the one-stop-shop mechanism. A controller without an establishment in the EU may have to notify each authority where affected individuals live. Check the guidance of the authority you deal with, as procedures and forms differ between countries.

Documentation and the breach register

Article 33(5) requires the controller to document any personal data breach, including the facts, its effects and the remedial action taken. This applies to every breach, not only those that were notified. Authorities can request the register during an inspection and compare it with incidents they learned about from other sources.

A useful register has one row per incident with the date and time of detection, the date of awareness, a description, data categories, number of people, the risk assessment, the decision on notification with justification, dates of notifications, and corrective actions. If a pattern appears, for example repeated misdirected emails, the corrective action should address the root cause, not only the individual case.

Common mistakes and how to prepare

Companies most often struggle with ownership and timing rather than with the form itself. Preparation is cheap compared with improvising under pressure. A free self-assessment on baltum.ai shows how well your breach response and wider GDPR processes are documented and where the gaps are.

  • No named decision maker, so the decision waits until the CEO returns from holiday
  • Processor contracts with vague breach notification clauses
  • Treating ransomware with restored backups as a non-event without assessing data access or exfiltration
  • Waiting for complete facts instead of notifying in phases
  • No record of breaches that were assessed as not notifiable
  • Telling customers about a breach in vague terms that do not explain what they should do

Frequently asked questions

Does the 72-hour deadline include weekends?

Yes. The GDPR counts 72 hours from awareness, regardless of weekends or public holidays. Your incident process therefore needs someone who can assess and notify outside normal office hours.

What happens if we notify after 72 hours?

A late notification is still required and must include the reasons for the delay. Missing the deadline without a good reason can itself be treated as an infringement of Article 33. Fines for such infringements are possible under Article 83, so document why the delay happened.

Do we need to notify if the lost laptop was encrypted?

If the device used strong, properly implemented encryption and the key was not compromised, the breach is often unlikely to result in a risk, and notification may not be needed. You still have to record the incident and your assessment in the breach register.

Who should contact affected individuals?

The controller is responsible for communicating with data subjects when the risk is high. The message must be in clear and plain language and describe the nature of the breach, the likely consequences, the measures taken and practical advice, such as changing passwords or watching for phishing.

Is a breach at our cloud provider our responsibility?

If you are the controller of the affected data, yes. The provider must inform you without undue delay, but you assess the risk and notify the authority. Your contract and data processing agreement should define how fast and in what format the provider reports incidents.

Check your readiness for free

10–15 minutes, no account needed: readiness score, gap report and AI recommendations.

This article is for general information and is not legal advice. baltum.ai is independent software, not a certification body.