facebook-pixel

How to Report a Data Breach to the ICO: Complete UK Guide (2026)

L
Lunyb Security Team
··8 min read

If your organisation suffers a personal data breach, UK GDPR gives you just 72 hours to notify the Information Commissioner's Office (ICO). Miss that window without a valid reason and you risk significant fines, reputational damage, and regulatory scrutiny. This guide walks you through exactly how to report a data breach to the ICO, what information you'll need, and how to handle the aftermath properly.

What Is a Personal Data Breach Under UK GDPR?

A personal data breach is any security incident leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to personal data. It's broader than most people assume — it isn't limited to hackers stealing databases.

Common examples include:

  • An employee emailing a spreadsheet of customer data to the wrong recipient
  • A ransomware attack encrypting files containing personal information
  • A lost or stolen laptop containing unencrypted client records
  • Accidental publication of personal data on a public website
  • Unauthorised access to employee HR records by a colleague
  • Loss of paper files during an office move

The ICO defines three types of breach: confidentiality breaches (unauthorised disclosure or access), integrity breaches (unauthorised alteration), and availability breaches (loss of access or destruction). A single incident can fall into more than one category.

Do You Actually Need to Report It?

Not every breach must be reported to the ICO. Under Article 33 of UK GDPR, you must notify the ICO only when the breach is likely to result in a risk to the rights and freedoms of individuals. If the risk is unlikely, you still have to document the incident internally, but notification isn't required.

When notification is required

You should report if the breach could lead to:

  • Discrimination, identity theft or fraud
  • Financial loss
  • Damage to reputation
  • Loss of confidentiality of data protected by professional secrecy
  • Any other significant economic or social disadvantage

When notification may not be required

If the data was strongly encrypted and the decryption key wasn't compromised, or the exposed information was already public, risk may be low enough that notification isn't mandatory. Document your reasoning carefully — the ICO can ask to see it.

The risk-assessment table

ScenarioLikely Risk LevelReport to ICO?
Encrypted laptop lost, key not compromisedLowNo (document only)
Unencrypted customer list emailed externallyHighYes
Ransomware on system with personal dataHighYes
Internal misuse of HR recordsMedium–HighYes
Already-public marketing data exposedLowUsually no

The 72-Hour Rule Explained

The clock starts the moment you become aware of the breach — not when it happened. "Aware" means a reasonable degree of certainty that a security incident has occurred and personal data is affected. A short initial investigation to confirm whether a breach has actually taken place is acceptable, but delay beyond that will need justification.

If you cannot provide all the information within 72 hours, you can submit a phased notification: tell the ICO what you know now and provide further details as they emerge. This is often the realistic approach for complex incidents.

How to Report a Data Breach to the ICO: Step-by-Step

Step 1: Contain the breach

Before notifying anyone, stop the bleeding. Revoke compromised credentials, isolate affected systems, recall misdirected emails if possible, and secure physical assets. Containment both limits harm and demonstrates good-faith response.

Step 2: Assess the scope and risk

Identify:

  1. What categories of personal data are involved (names, addresses, financial details, special category data, children's data)
  2. Approximate number of data subjects affected
  3. Approximate number of records affected
  4. The potential consequences for individuals
  5. Mitigations already in place or planned

Step 3: Decide whether notification is required

Use the ICO's self-assessment tool at ico.org.uk to confirm. If you decide not to notify, record the decision and reasoning in your breach register.

Step 4: Submit the report

There are three ways to report:

  • Online reporting form — the preferred method, available on the ICO website
  • Telephone — call the ICO helpline on 0303 123 1113 (open Monday–Friday, 9am–5pm) for urgent breaches, especially outside normal information you can submit online
  • Non-urgent cases can also be reported via the online portal during business hours

You'll need to provide:

  • Your organisation's details and DPO contact (if applicable)
  • Nature of the breach (confidentiality, integrity, availability)
  • When it occurred and when you became aware
  • Categories and approximate numbers of data subjects and records
  • Likely consequences
  • Measures taken or proposed to address the breach

Step 5: Notify affected individuals (if required)

Under Article 34, if the breach is likely to result in a high risk to rights and freedoms, you must also inform affected individuals "without undue delay." The communication must be in clear, plain language and include the DPO contact, likely consequences, and mitigation measures.

You don't need to notify individuals if you've since applied measures (such as encryption applied retrospectively, which is rare) that make the data unintelligible, or if individual notification would involve disproportionate effort — in which case a public communication is acceptable.

Step 6: Document everything

Even for breaches you don't report, UK GDPR requires you to maintain an internal breach register. Include facts, effects, remedial action, and the rationale for any decisions about notification. The ICO can inspect this register at any time.

What Happens After You Report

The ICO will acknowledge your report and may ask follow-up questions. In most cases, if your response was appropriate and controls were reasonable, no enforcement action follows. The ICO prefers education and improvement over fines, particularly for first-time incidents handled responsibly.

However, serious breaches — especially those involving poor security hygiene, repeated incidents, or sensitive data — can lead to:

  • Formal reprimands
  • Enforcement notices requiring specific actions
  • Monetary penalties up to £17.5 million or 4% of global annual turnover (whichever is higher)

Common Mistakes to Avoid

Reporting too late

The single most common error. If you're unsure, report anyway — late reports draw more scrutiny than cautious early ones.

Over-reporting trivial incidents

The flip side: reporting every minor email misdirection clogs your record and the ICO's inbox. Apply the risk test honestly.

Not documenting non-reported breaches

A breach register is mandatory. "We didn't think it was serious" isn't a defence if nothing is written down.

Forgetting third-party processors

If a processor (such as a cloud provider or payroll bureau) suffers the breach, they must notify you "without undue delay," and you remain responsible for notifying the ICO. Review your data processing agreements.

Poor internal communication

Staff who discover incidents often don't know who to tell. Publish a simple internal reporting route — ideally a single email address or hotline monitored by your DPO or security lead.

Reducing Breach Risk in the First Place

Prevention is cheaper than notification. Focus on the controls that address the most common causes of UK breaches: misdirected emails, lost devices, phishing, and weak access controls.

  • Encrypt everything portable — laptops, USB sticks, mobile devices
  • Enforce multi-factor authentication on all accounts handling personal data
  • Train staff quarterly on phishing recognition and safe data handling
  • Use encrypted DNS and reputable email gateways to catch malicious links before users click
  • Audit sharing links regularly — expired or publicly accessible cloud links are a leading breach source. When sharing links externally, use a privacy-respecting shortener like Lunyb that lets you set expiry dates and password-protect destinations
  • Review processor contracts to confirm they include breach-notification clauses meeting UK GDPR standards

For teams that routinely share links to sensitive documents or client portals, controlling link lifecycle matters as much as the document itself. If you're evaluating link-management tools, our honest review of Lunyb and our Rebrandly comparison cover the privacy and security features worth looking for.

Your Breach Response Checklist

TimingAction
Hour 0–1Contain breach, preserve evidence, alert DPO/incident lead
Hour 1–12Assess scope, identify data types and subjects affected
Hour 12–48Decide on notification; draft ICO submission
Hour 48–72Submit to ICO (phased if necessary)
Within 72 hours+Notify high-risk individuals if required
Within 7 daysComplete internal breach register entry
Within 30 daysPost-incident review; update controls and training

Frequently Asked Questions

What happens if I miss the 72-hour deadline?

You should still report as soon as possible and include a clear explanation for the delay. Late notification isn't automatically penalised, but unexplained delays can be treated as an aggravating factor. The ICO looks more favourably on honest, late-but-thorough reports than on no report at all.

Does a data breach always result in a fine?

No. Most reported breaches result in no financial penalty. The ICO typically issues fines only when there's evidence of systemic failure, negligence, or repeated non-compliance. A well-handled breach with appropriate prior controls and prompt notification usually results in guidance rather than enforcement.

Do I need to report a breach that only affects one person?

Possibly, yes. The threshold is risk to rights and freedoms, not number of people. A single incident involving sensitive data (health records, financial details, children's data) can easily meet the notification threshold even if it affects one individual.

What if the breach happened at a third-party supplier?

As the data controller, you remain responsible for notifying the ICO. Your processor must inform you without undue delay, and you then assess and report within your own 72-hour window from when you became aware. This is why processor contracts must include strict breach-notification obligations.

Can I report anonymously or on behalf of another organisation?

Formal Article 33 notifications must come from the data controller or their authorised representative (such as the DPO). If you're a member of the public concerned about someone else's data handling, use the ICO's separate "make a complaint" route rather than the breach-reporting form.

Final Thoughts

Reporting a data breach to the ICO isn't just a legal box-tick — it's a signal of organisational maturity. The regulator rewards transparency, good documentation, and demonstrable improvement far more than it punishes honest mistakes. Build a simple internal process now, train the people who might spot incidents first, and treat prevention as the real win. The notification form should be the last step of a well-rehearsed plan, not an emergency scramble.

Protect your links with Lunyb

Create secure, trackable short links and QR codes in seconds.

Get Started Free

Related Articles