facebook-pixel

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

L
Lunyb Security Team
··10 min read

If you've just discovered a data breach, the clock is already ticking. Under UK GDPR, you have 72 hours to report a notifiable personal data breach to the Information Commissioner's Office (ICO) — and the penalties for getting it wrong are serious. This guide walks you through exactly how to report a data breach to the ICO, what counts as notifiable, what you need to prepare, and how Lunyb helps you catch exposure early so you're reporting from a position of control rather than panic.

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. That definition is wider than most people assume — it isn't only hackers.

Common examples the ICO treats as breaches

  • A ransomware attack that encrypts customer records.
  • A laptop, phone, or USB stick containing personal data being lost or stolen.
  • An email with personal data sent to the wrong recipient.
  • A misconfigured cloud bucket or database left publicly accessible.
  • Paper records left on a train or disposed of without shredding.
  • An employee accessing records they shouldn't.

Not every breach must be reported

You only need to notify the ICO if the breach is likely to result in a risk to people's rights and freedoms. If the risk is low — for example, a strongly encrypted device is lost and the key is secure — you may not need to report it. But you must still record the incident internally and be able to justify the decision.

The 72-Hour Rule: When the Clock Starts

The ICO requires notification "without undue delay and, where feasible, no later than 72 hours after becoming aware of it." The clock starts when you have a reasonable degree of certainty that a security incident has occurred that led to personal data being compromised — not when the attack began, and not when you've finished investigating.

What "aware" really means

  1. An initial alert (a staff report, an alarm, a tip-off) is not yet "awareness." A short investigation to confirm whether a breach actually happened is allowed.
  2. Once you reasonably conclude personal data has been compromised, you are aware — and the 72 hours start.
  3. If you can't provide all details within 72 hours, you can submit information in phases. The ICO expects this for complex incidents.

Weekends and bank holidays

The 72 hours run continuously. They do not pause for weekends, Christmas Day, or your team's holiday rota. Build your response plan around that reality.

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

Here is the practical sequence most UK organisations follow, from discovery to notification.

Step 1: Contain the incident

Before you touch the reporting form, stop the bleeding. Disconnect compromised systems, reset passwords, revoke access tokens, lock accounts, and preserve logs. Containment protects both the data subjects and your own regulatory position.

Step 2: Assess the scope and risk

  • What data was affected? Names, emails, passwords, financial details, health data, children's data?
  • How many people are affected? Even an approximate range is useful.
  • What is the likely impact? Identity theft, financial loss, reputational harm, physical safety, discrimination?
  • Is the data recoverable? Backups, encryption status, and whether the data has been exfiltrated or only accessed.

Step 3: Decide whether it's notifiable

If there is any likely risk to individuals, report it. If you're unsure, the ICO's view is that you should err on the side of reporting. Record your reasoning either way.

Step 4: Use the ICO's online breach reporting tool

  1. Go to the ICO website (ico.org.uk) and open the personal data breach reporting service.
  2. Choose whether you are the data controller or acting on behalf of one. Processors report to the controller, not directly to the ICO.
  3. Complete the form: nature of the breach, categories and approximate numbers of data subjects and records, likely consequences, measures taken, and your DPO or contact point.
  4. Submit. You'll get a case reference — keep it.

If you prefer, you can call the ICO helpline on 0303 123 1113 during office hours for guidance, especially for urgent or complex incidents.

Step 5: Notify affected individuals (when required)

If the breach is likely to result in a high risk to rights and freedoms, you must also tell the people affected without undue delay. The notice must be in plain English and include what happened, likely consequences, measures taken, and how they can contact you.

Step 6: Document everything

UK GDPR Article 33(5) requires you to keep a record of every personal data breach — including ones you decided not to report — with the facts, effects, and remedial actions. The ICO can ask to see this at any time.

What Information the ICO Will Ask For

You don't need to have perfect answers in 72 hours, but you should be ready to give the ICO what you reasonably know.

CategoryWhat to Provide
Nature of the breachConfidentiality, integrity, or availability breach; cause; timeline
Data categoriesNames, contact details, financial data, special category data, etc.
Data subjectsCustomers, employees, children, patients; approximate numbers
Likely consequencesFraud, identity theft, distress, physical harm, discrimination
Measures takenContainment steps, password resets, notifications, external support
ContactDPO or named incident lead with phone and email

Penalties for Getting It Wrong

The ICO can issue fines of up to £17.5 million or 4% of global annual turnover (whichever is higher) for serious infringements of UK GDPR. Failure to notify when required is itself an infringement, separate from the underlying breach. In practice, the ICO tends to focus on:

  • Whether you had reasonable security measures in place.
  • Whether you detected and responded quickly.
  • Whether you were transparent — with regulators and with affected people.
  • Whether you learned from the incident.

Organisations that report promptly, cooperate openly, and show mature processes almost always fare better than those who delay or downplay.

Where Lunyb Fits: Detecting Exposure Before It Becomes a Crisis

Most breaches aren't discovered by the organisation that was breached — they're discovered when stolen data surfaces online, when a customer notices fraud, or when a journalist calls. By then, the 72-hour clock has already been running, often for weeks.

Lunyb is a phone privacy and scam-protection platform built around one simple idea: you should know the moment your data is exposed, not months later. For UK consumers, business owners, and teams who handle personal data, Lunyb gives you an always-on early warning system — and the tools to act on it.

Data Breach Alerts for email and phone

Lunyb monitors known breach sources for your email addresses and phone numbers and alerts you when they appear in a new leak. If you're a sole trader, a DPO monitoring your own exposure, or a team lead protecting staff accounts, this is the difference between finding out in minutes and finding out from an angry customer.

Scam Checker and Scam Shield

Breaches almost always lead to targeted phishing — fraudsters use leaked data to send convincing texts and emails. Lunyb's Scam Checker lets you paste in suspicious messages or links and get a quick read on whether they're dangerous. Scam Shield adds caller protection against the wave of calls that typically follows a leak.

Privacy Check and Security Score

Lunyb's Privacy Check reviews the permissions your apps are quietly holding onto — location, contacts, microphone, photos — and helps you shut down anything you don't need. Your Security Score gives you a single, honest number for where you stand, so you can demonstrate improvement over time.

Encrypted Password & Photo Vault

Most breaches start with a reused password. Lunyb's encrypted vault stores credentials and sensitive photos on-device, so even if one service is compromised, the damage stops there. It's a practical step that genuinely reduces the risk of a notifiable incident happening to you in the first place.

On-device tracker and threat blocking

Lunyb's local DNS shield blocks known trackers and malicious domains at the network level on your phone — no complicated setup, no browser extensions. Combined with the browsing-history eraser and Photo Guard reverse-image check, it's a complete personal privacy layer.

Transparent pricing you can cancel anytime

Plans start from about £19.99/month (billed in your local currency), renew until you cancel, and you can cancel online whenever you like. Optional Leak Protection is billed separately and can be paused without cancelling the main plan. No long contracts, no surprises — the same clarity the ICO expects from you, we expect from ourselves.

A Simple Pre-Breach Checklist

You can't guarantee a breach won't happen, but you can guarantee you'll respond well. Work through this list now, not at 11pm on a Friday.

  1. Know your data. Keep an up-to-date record of what personal data you hold and where.
  2. Have an incident response plan. One page is better than none. Name the decision-maker.
  3. Set up breach monitoring. Use Lunyb's Data Breach Alerts for your key accounts and staff emails.
  4. Harden passwords. Use the Lunyb vault or an equivalent; kill reused passwords.
  5. Review app permissions. Run Privacy Check monthly on company phones.
  6. Train your team. Most breaches start with a click. Make reporting easy and blame-free.
  7. Know the ICO reporting route. Bookmark ico.org.uk and save the helpline number.

After the Report: What Happens Next

Once you submit, the ICO will acknowledge your report and may ask for more information. For most incidents, no further action follows beyond that record. For serious cases, you may be assigned a case officer and asked to explain your security posture and remediation steps. Keep your documentation tidy, respond promptly, and treat the ICO as a regulator you want on your side — because, in practice, cooperative organisations are treated very differently from evasive ones.

Protect Yourself and Your Customers With Lunyb

Reporting a breach is the legal minimum. Preventing one — or catching it in hours instead of months — is what actually protects the people whose data you hold. Lunyb gives you breach alerts, scam protection, encrypted storage, and on-device privacy tools in one app, with clear pricing and a cancel-anytime promise.

Start with the free privacy quiz at lunyb.com to see where your exposure stands today, or download the Lunyb app from the App Store or Google Play and turn on Data Breach Alerts in under five minutes. If you're curious about how we built the platform, our team has written more about our approach in this honest review of Lunyb.

Frequently Asked Questions

Do I have to report every data breach to the ICO?

No. You only need to report personal data breaches that are likely to result in a risk to people's rights and freedoms. But you must record every breach internally, including the reasoning for not reporting, and be able to show that record on request.

What if I miss the 72-hour deadline?

Report it anyway, as soon as you can, and explain the reason for the delay in the notification. Late reporting is itself an infringement, but trying to hide a breach or not reporting at all is treated far more seriously by the ICO.

Can Lunyb report a breach to the ICO for me?

No — only the data controller can submit the official notification. Lunyb helps you detect exposure early through Data Breach Alerts, reduce the likelihood of a breach with privacy and password tools, and respond faster to scams that follow leaks. The ICO submission itself stays with you or your DPO.

What's the difference between a data controller and a data processor when reporting?

The controller decides why and how personal data is processed and is responsible for reporting to the ICO. A processor acts on the controller's instructions and must notify the controller of any breach without undue delay, so the controller can meet the 72-hour deadline.

How much does Lunyb cost and can I cancel?

Lunyb plans start from about £19.99/month and renew until you cancel. You can cancel anytime online. Optional Leak Protection is billed separately and can be paused without cancelling your main plan. Start with the free privacy quiz at lunyb.com to see what you need before you pay for anything.

Protect your links with Lunyb

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

Get Started Free

Related Articles