facebook-pixel

How to Report a Data Breach to the ICO: A Complete UK Guide

L
Lunyb Security Team
··10 min read

If your organisation or personal data has been exposed, the clock starts ticking the moment you become aware. Under UK GDPR, most notifiable breaches must be reported to the Information Commissioner's Office (ICO) within 72 hours. This guide walks you through exactly how to report a data breach to the ICO, what counts as notifiable, and how to protect yourself (or your customers) from the fallout. We'll also show you how Lunyb makes the monitoring and response side of this process dramatically easier — before, during, and after a breach.

What counts as a data breach under UK GDPR?

A personal data breach is any security incident that leads to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to personal data. It is not only about hackers — a lost laptop, a misdirected email, or an employee opening a file they shouldn't can all qualify.

The ICO groups breaches into three broad categories:

  • Confidentiality breach — personal data is disclosed to or accessed by someone unauthorised.
  • Integrity breach — personal data is altered without authorisation.
  • Availability breach — personal data is lost, destroyed, or made inaccessible (for example, by ransomware).

Not every incident must be reported. You only need to tell the ICO if the breach is likely to result in a risk to the rights and freedoms of the people whose data was affected. If the risk is high, you also have to tell those individuals directly.

Quick examples

  • A spreadsheet of customer emails emailed to the wrong recipient — usually reportable.
  • An encrypted laptop stolen from a locked car with no sign of compromise — often not reportable, but document the decision.
  • A ransomware attack that encrypts HR files — reportable as an availability breach.
  • A mis-set privacy option that exposed a public database of names and addresses — reportable.

The 72-hour rule: what it really means

The 72-hour window starts when you become aware of the breach, not when the breach happened. Awareness means having a reasonable degree of certainty that a security incident has occurred that led to personal data being compromised.

You do not need every detail before you report. The ICO expects an initial notification followed by updates in phases if information is still coming in. Missing the 72-hour deadline without a reasoned justification can itself trigger enforcement action — so when in doubt, report and update later.

How to report a data breach to the ICO: step-by-step

Here is the practical process we recommend. Whether you're a data protection officer, a small business owner, or an individual reporting a breach that affected you, the structure is similar.

  1. Contain the breach. Stop the leak. Revoke access, isolate systems, reset passwords, recall emails if possible, and lock down the affected accounts.
  2. Record the time of awareness. Note the exact date and time someone in your organisation first knew. This is the start of your 72-hour clock.
  3. Assess the risk. Consider the type of data, volume, sensitivity, how easily individuals can be identified, and the potential consequences (financial loss, identity fraud, distress, reputational harm).
  4. Decide if it is notifiable. If there is a likely risk to individuals, you must tell the ICO. If the risk is high, you must also tell the individuals.
  5. Gather your facts. You'll need what happened, when, the categories and approximate number of individuals and records affected, likely consequences, and the measures taken or proposed.
  6. Submit the report. For a personal data breach, use the ICO's online Report a breach service at ico.org.uk, or call 0303 123 1113 for urgent advice.
  7. Notify affected individuals if required. Use clear, plain language. Explain what happened, what data was involved, what you're doing about it, and what they should do next.
  8. Document everything. Even breaches you decide not to report must be logged internally. The ICO can ask to see your breach log at any time.
  9. Review and learn. Update policies, training, and controls so the same breach can't happen twice.

What the ICO asks for in the online form

  • Organisation name and contact details (or your own details if reporting as an individual).
  • Nature of the breach (confidentiality, integrity, availability).
  • Categories of personal data affected (names, financial, health, special category, etc.).
  • Number of data subjects and number of records, even if approximate.
  • When the breach occurred and when you became aware.
  • Likely consequences for affected individuals.
  • Measures taken to address the breach and reduce harm.
  • Whether and how you have notified the people affected.

Reporting a breach as an individual (not an organisation)

If a company has mishandled your personal data, you don't file the official breach notification — that duty belongs to the organisation. But you can and should raise a complaint with the ICO if you believe an organisation has broken data protection law.

  1. Contact the organisation first in writing and give them a chance to respond (usually one month).
  2. If their response is inadequate or missing, submit a complaint via ico.org.uk using the Make a complaint service.
  3. Include copies of your correspondence, dates, and what outcome you want.
  4. Keep monitoring your accounts, email addresses, and phone numbers for signs your leaked data is being abused.

That last point is where most people drop the ball. A breach notification letter is not the end — it's the beginning of a window where criminals try to use the stolen data. This is exactly where Lunyb earns its place on your phone.

How Lunyb helps you handle a data breach — before and after

Reporting a breach is only half the job. The other half is making sure you (and your family, team, or customers) don't get burned when stolen data starts circulating. Lunyb is built for exactly this, and it covers the three moments that matter most: spotting exposure early, blocking the follow-up attacks, and locking down your accounts.

1. Data Breach Alerts for email and phone

Lunyb continuously checks whether your email addresses and phone numbers appear in known data breaches. Instead of waiting weeks for a company's apology letter, you get an alert as soon as your details surface — so you can change passwords, enable two-factor authentication, and warn your bank before anyone else does.

2. Scam Checker and Scam Shield

The scariest part of a breach isn't the leak — it's the wave of phishing texts, fake ICO emails, "your parcel is held" messages, and bank impersonation calls that follow. Lunyb's Scam Checker lets you paste any suspicious message or link to see if it's safe, and Scam Shield helps catch dodgy callers before you answer. More risks caught, faster recovery.

3. Privacy Check and Security Score

After a breach, you want to know which apps on your phone can see what. Lunyb's Privacy Check reviews app permissions in plain English, and your Security Score gives a single number that tells you where you stand and what to fix next.

4. Encrypted Password and Photo Vault

If passwords were in the breach, you need new ones — and somewhere safe to store them. Lunyb includes an encrypted Password Vault and Photo Vault so sensitive credentials and images aren't sitting in your camera roll or a notes app.

5. On-device tracker and threat blocking

Lunyb's local DNS shield blocks known malicious domains and trackers at the network level on your device, which helps reduce exposure to the kind of shady infrastructure often used in post-breach phishing campaigns.

6. Optional Leak Protection

For people whose data is already circulating widely, Lunyb offers optional Leak Protection, billed separately. You can pause it without cancelling your main plan — useful if you want extra help during an active incident and then dial it back.

Lunyb vs. the DIY breach response

You can do all of this manually. Most people don't, because it's tedious and easy to miss something. Here's how the two approaches compare on the jobs that actually matter after a breach.

Task after a breachDIY approachWith Lunyb
Know when your email or phone is leakedCheck multiple free sites manually, hope you rememberAutomatic Breach Alerts on monitored accounts
Check if a suspicious message is a scamGoogle the sender, guess, or click and hopePaste into Scam Checker for an instant verdict
Block scam callersBlock one-by-one in phone settingsScam Shield helps filter risky calls
Review app permissionsDig through settings on every appPrivacy Check gives a single prioritised view
Store new strong passwordsNotes app, spreadsheet, or memoryEncrypted Password Vault
Block tracker and phishing domainsEdit hosts files or install multiple toolsOn-device DNS shield enabled with a tap
Track overall progressNo single viewSecurity Score shows what to fix next

What to tell affected individuals (template approach)

If you're the organisation reporting the breach and need to tell the people affected, the ICO expects plain language and practical guidance. Cover these points:

  1. What happened, in one or two sentences, without jargon.
  2. When it happened and when you discovered it.
  3. Exactly what categories of their data were involved.
  4. What the likely consequences could be.
  5. What you have done to contain the breach and prevent repetition.
  6. What they should do now — change passwords, watch for phishing, monitor bank statements, and consider a breach-monitoring tool like Lunyb.
  7. Who to contact for questions (name, email, phone).

Common mistakes to avoid

  • Waiting for "complete" information. Report what you know within 72 hours and update later.
  • Under-reporting the number of records. Approximate numbers are acceptable; false precision is not.
  • Not logging near-misses. Even non-notifiable incidents should be in your internal breach log.
  • Telling individuals too late. If risk is high, tell them without undue delay — before they hear it from the press.
  • Forgetting the aftermath. The real damage usually arrives in the weeks after a breach, through phishing and account takeover. This is why ongoing monitoring matters.

Build a breach-ready stack with Lunyb

The best time to prepare for a breach is before one happens. If you're an individual, install Lunyb and connect the email addresses and phone numbers you actually use. If you run a small team, encourage your staff to do the same — a single leaked personal account is a common route into company systems.

Lunyb plans start from about £19.99 / $19.99 per month and renew until cancelled. You can cancel anytime online, and the optional Leak Protection add-on can be paused without touching your main plan. No lock-in tricks, no surprises — just clear, continuous protection.

For more on how Lunyb works and why we built it this way, see our honest review of Lunyb.

FAQ

How quickly must I report a data breach to the ICO?

You must report a notifiable personal data breach to the ICO without undue delay and, where feasible, within 72 hours of becoming aware of it. If you miss the deadline, you must explain the reasons for the delay in your notification.

What happens if I report a breach that turns out not to be notifiable?

The ICO would rather you report and be wrong than stay silent and be right about the risk. You can update or withdraw your report as more information becomes available, and you won't be penalised for a good-faith notification.

Do I have to tell the people whose data was affected?

Only if the breach is likely to result in a high risk to their rights and freedoms. When you do, use clear language and tell them what to do next — including steps like changing passwords, watching for phishing, and using monitoring tools such as Lunyb's Data Breach Alerts.

Can Lunyb tell me if my data has already been leaked?

Yes. Lunyb's Data Breach Alerts monitor your registered email addresses and phone numbers against known breaches and alert you when your details appear, so you can take action before criminals do.

How do I start with Lunyb?

Visit lunyb.com and take the free privacy quiz, or download the Lunyb app from the App Store or Google Play. Set up Breach Alerts, run a Privacy Check, and switch on Scam Shield — all in a few minutes.

Your next step

Reporting a breach to the ICO is a legal duty. Protecting yourself and the people who trust you with their data is a daily one. Lunyb handles the day-to-day monitoring, scam checking, and account hygiene so that when something does go wrong, you're ready — not reacting.

Head to lunyb.com, take the free privacy quiz, and install the app today. It's the easiest way to turn a 72-hour emergency into a controlled, documented response.

Protect your links with Lunyb

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

Get Started Free

Related Articles