The clock starts the moment you become aware of a personal data breach. If the breach is likely to put people at risk, UK GDPR gives you 72 hours to tell the Information Commissioner’s Office. Miss that breach notification deadline without good reason and you invite closer scrutiny of everything else you did.

This post walks through what counts as a breach, when the clock starts, how to report and what happens next. It ends with how to prepare before anything goes wrong.

Contents

  1. What Is a Personal Data Breach?
  2. When Does the 72-Hour Clock Start?
  3. Not Every Breach Needs to Be Reported
  4. How to Notify the ICO
  5. Notifying Affected Individuals
  6. What Happens After You Report
  7. Building a Breach Response Plan Before You Need It

What Is a Personal Data Breach?

Article 4(12) of UK 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. Breaches cover far more than hacking. They include accidents, loss of access to data, and loss of the data itself.

Common examples include:

  • A lost or stolen laptop holding unencrypted customer or staff records
  • Ransomware that encrypts your systems or copies data out of them
  • An email sent to the wrong person, or a spreadsheet attached by mistake
  • Unauthorised access, such as an employee browsing records they have no reason to see

Some incidents aren’t breaches at all. A single spam email, or a phishing attempt that nobody clicked and that exposed no data, is a security event worth logging. It isn’t a breach under UK GDPR, because no personal data was compromised.

When Does the 72-Hour Clock Start?

The 72 hours run from when you become aware of the breach, not from when it happened. Breach guidance from European regulators, which the ICO points organisations to, says you become aware once you have a reasonable degree of certainty that a security incident has compromised personal data.

That doesn’t give you room to wait for perfect information. If a staff member reports a suspicious login on a Friday evening, you should start investigating straight away. A short investigation to confirm what happened is expected, but leaving a credible warning untouched over a weekend won’t stop the clock.

If a supplier processes the data for you, it must tell you without undue delay once it becomes aware of a breach. Set a tight reporting deadline in your contract, because your own 72 hours can start as soon as their alert reaches you.

Record the Moment You Became Aware

Write down when you first heard about the incident, who told you, and what you knew at that point. Then record when you confirmed that personal data was involved. Good data incident reporting starts inside your business, so staff need to know who to tell, and how, the moment they spot something wrong.

Not Every Breach Needs to Be Reported

You only need to report a breach to the ICO if it’s likely to result in a risk to people’s rights and freedoms. Think about the harm it could cause: identity theft, fraud, financial loss, discrimination, damage to reputation or loss of confidentiality.

Plenty of breaches fall below that line. A securely encrypted laptop lost on a train, with the key kept safe, is unlikely to put anyone at risk. Neither is an internal email sent to the wrong colleague, who confirms they’ve deleted it unread.

Document Every Breach, Reported or Not

Under Article 33, you must record every breach, including the ones you decide not to report. Your breach log should set out the facts, the effects and the action you took. Record your reasoning too, because the ICO can ask to see why you judged a breach unreportable. If you’re unsure, the ICO’s self-assessment tool will help you decide.

How to Notify the ICO

Here’s how to report a data breach to the ICO. ICO breach reporting runs through an online form, which the ICO says takes about 30 minutes. You can’t save it and come back later, so gather the details before you start.

Your UK GDPR breach report should include:

  • The nature of the breach, including the categories of data and people involved
  • Approximate numbers of people and records affected
  • The likely consequences for those people
  • The measures you’ve taken, or plan to take, to deal with the breach and limit harm
  • A contact point, such as your DPO, who can answer the ICO’s questions

You don’t need every answer before you report. Article 33 lets you provide information in phases, so send what you know within 72 hours and follow up without undue delay. If your report arrives after 72 hours, explain the reasons for the delay.

Notifying Affected Individuals

Telling the ICO and telling the people affected are separate duties with separate thresholds. You must tell individuals when a breach is likely to result in a high risk to them. That’s a higher bar than the risk test for reporting to the ICO.

When the duty applies, Article 34 says you must tell people without undue delay. Use clear, plain wording to explain what happened, who they can contact, the likely consequences and what you’ve done about it. Add specific advice too, such as changing passwords or watching for suspicious payment requests.

When You Don’t Have to Tell Individuals

There are three exceptions. You don’t have to notify individuals if the data was unintelligible to anyone who accessed it, for example because it was properly encrypted. The same applies if your follow-up action means the high risk is no longer likely. Where contacting each person would take disproportionate effort, a public announcement can replace individual notices.

What Happens After You Report

After you report a data breach, ICO caseworkers assess what happened and how you responded. Some cases close with no further action or with advice. Others lead to more questions, an investigation and, in serious cases, a reprimand, an enforcement notice or a fine.

Several factors shape that outcome. The ICO looks at how serious the breach was, how many people it affected and what security you had in place beforehand. It also looks at how quickly you acted to limit harm.

Cooperation Counts

Article 83 lists cooperation with the regulator, and the way it learned of the breach, among the factors it weighs when deciding on a fine. Reporting on time and answering questions openly work in your favour. Failing to notify a reportable breach can, on its own, lead to a fine of up to £8.7 million or 2% of global turnover.

Building a Breach Response Plan Before You Need It

Data breach notification goes far more smoothly when the decisions are made in advance. Seventy-two hours disappears fast when nobody knows who’s in charge, who assesses the risk or who signs off the report.

Your plan should name an incident lead and set out how a breach moves from the person who spots it to the people who decide. It should include templates for the ICO report and for messages to individuals, plus a breach log ready to fill in. It also needs testing, because a tabletop exercise exposes gaps that a document on a shared drive never will.

For GDPR breach notification, UK businesses that rehearse their response decide faster and make fewer mistakes under pressure. Our team builds breach response plans around your systems, your people and the data you hold, so the first hour of a real incident doesn’t start with a blank page.

Who Else You May Need to Tell

Your cyber insurer will want to hear early, and some policies set their own notice periods. You can report cybercrime to Report Fraud, or to Police Scotland, and serious cyber incidents to the National Cyber Security Centre. Regulated firms may also owe notice to their sector regulator.

Don’t Wait for a Breach. Build Your Response Plan Now.

You can’t control when a breach happens, but you can control how ready you are. Our team will map your escalation routes, prepare your reporting templates, and test the plan with the people who’ll use it.

Don’t wait for a breach. Build your response plan now.

Leave A Comment

Receive the latest news in your email
Table of content
Related articles