How to Report a Data Breach to the ICO: A Complete UK Guide
If your personal data has been exposed — or if you run an organisation that has suffered a breach — the Information Commissioner's Office (ICO) is the UK regulator you need to deal with. Reporting a data breach to the ICO sounds intimidating, but the process is well defined, and acting quickly protects both you and the people whose data has been exposed.
At Lunyb, we help people in the UK monitor their exposed emails and phone numbers, spot scam follow-ups, and lock down what attackers could do next. This guide walks you through the full ICO reporting process, and then shows you how to use Lunyb to handle the part the ICO can't do for you: protecting yourself from the fallout.
What counts as a data breach under UK GDPR
A personal data breach is a security incident that leads to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to personal data. In plain English: data about a living person has been seen, changed, stolen, or lost by someone who shouldn't have touched it.
Under UK GDPR and the Data Protection Act 2018, breaches fall into three broad categories:
- Confidentiality breach — unauthorised or accidental disclosure of personal data (e.g. an email sent to the wrong recipient, a database leaked online).
- Integrity breach — unauthorised or accidental alteration of personal data (e.g. a hacker changing customer records).
- Availability breach — accidental or unauthorised loss of access to, or destruction of, personal data (e.g. ransomware locking files, a lost unencrypted laptop).
Not every incident has to be reported. A breach only needs to go to the ICO if it is likely to result in a risk to the rights and freedoms of individuals.
Who is responsible for reporting to the ICO
The duty to report a personal data breach sits with the data controller — the organisation that decides how and why personal data is processed. If you are a data processor (you handle data on someone else's behalf, like a cloud provider or payroll bureau), your job is to notify the controller without undue delay. The controller then decides whether to notify the ICO.
If you are an individual whose data has been exposed — for example, a customer of a breached retailer — you don't report the breach to the ICO as a notification. Instead, you can make a complaint to the ICO if you believe an organisation has mishandled your data. We cover both paths below.
The 72-hour rule: when organisations must report
UK GDPR Article 33 is strict: organisations must notify the ICO of a notifiable breach within 72 hours of becoming aware of it. The clock starts when you have a reasonable degree of certainty that a breach has occurred, not when you have every detail nailed down.
If you can't provide all the information within 72 hours, you can submit what you have and send the rest in phases. Reporting late is possible, but you must explain why. The ICO takes delay seriously and can increase enforcement action against organisations that sit on breaches.
When you do NOT need to report
You don't have to notify the ICO if the breach is unlikely to result in a risk to people's rights and freedoms. For example, a stolen laptop that was fully encrypted, with the attacker having no access to the key, may not be notifiable. You still need to document the decision internally, including your reasoning. The ICO can ask to see that record.
When you must also notify affected individuals
If the breach is likely to result in a high risk to individuals — think identity theft, financial loss, significant distress, or exposure of sensitive data — you must tell the affected people directly, without undue delay, in clear and plain language.
How to report a data breach to the ICO: step by step
Here is the full process an organisation should follow when reporting a personal data breach to the ICO.
- Contain the breach. Lock out the unauthorised user, isolate affected systems, reset credentials, and stop further data loss before anything else.
- Assess the risk. Identify what data was involved, how many people are affected, the type of data (financial, health, children's data, etc.), and the potential consequences.
- Decide if it is notifiable. If there is a risk to individuals' rights and freedoms, it is reportable. If in doubt, report.
- Gather the required information. See the next section for the exact fields the ICO expects.
- Report via the ICO website. Go to ico.org.uk and use the personal data breach reporting tool, or call the ICO breach helpline on 0303 123 1113 (option 3 for security breaches).
- Notify affected individuals if required. Use clear language, tell them what happened, what data is involved, what you're doing, and what they can do to protect themselves.
- Document everything. Keep an internal breach log with facts, effects, and remedial action — even for breaches you decide not to report.
- Review and improve. Run a post-incident review and update your policies, training, and controls.
What information the ICO needs in your breach report
When you submit your report through the ICO's online form, you'll be asked for the information set out in Article 33(3) of UK GDPR. Have this ready before you start:
- A description of the nature of the breach, including the categories and approximate number of individuals and records affected.
- The name and contact details of your Data Protection Officer (DPO) or another point of contact.
- A description of the likely consequences of the breach.
- A description of the measures taken or proposed to address the breach and mitigate its effects.
- The date and time the breach was discovered and the date and time it occurred (as best as you can tell).
- How the breach was discovered (internal audit, external report, customer complaint, etc.).
If some fields are unknown, say so. A phased report is better than no report.
How to report a breach as an individual whose data was leaked
If you've received a breach notification email, seen your details in the news, or found your email in a public leak, you have options as a data subject.
- Contact the organisation first. Ask what data was exposed, what they're doing, and what they recommend you do. UK GDPR gives you the right to a clear answer.
- Make a complaint to the ICO. If the organisation won't respond, dismisses your concern, or you believe they handled the breach badly, submit a complaint at ico.org.uk/make-a-complaint. You'll need to show you raised it with the organisation first.
- Report fraud if you've lost money. Contact Action Fraud on 0300 123 2040 or actionfraud.police.uk. In Scotland, call Police Scotland on 101.
- Protect yourself going forward. Change passwords, enable two-factor authentication, watch your bank statements, and monitor your email and phone for scam follow-ups. This is the stage where Lunyb matters most.
How Lunyb helps you handle a data breach — before, during, and after
The ICO process is about accountability. It doesn't tell you which of your accounts to change, which scam texts are phishing follow-ups, or whether your email is sitting in another leak you haven't heard about yet. That's the gap Lunyb fills.
Lunyb is a UK-friendly privacy and scam-protection app that gives you a practical toolkit to deal with the aftermath of a breach — and to spot the next one early.
Data Breach Alerts for your email and phone
Our Data Breach Alerts continuously monitor your email addresses and phone numbers against known breach datasets. When your details show up in a new leak, we tell you which breach it was, what categories of data were exposed, and what to do next. That means you don't have to wait for the breached company to email you — you find out as soon as the data surfaces.
Scam Checker and Scam Shield
Breaches are followed by a wave of phishing. Attackers use leaked phone numbers and emails to send convincing scams that reference your real details. Lunyb's Scam Checker lets you paste a suspicious message or link and get a verdict in seconds. Scam Shield helps screen suspicious calls so you don't have to pick up every unknown number after a leak.
Privacy Check and Security Score
After a breach is a good moment to tighten everything else. Privacy Check reviews the permissions your apps have taken (location, microphone, contacts, photos) so you can revoke what you don't need. Your Security Score gives you a running number to improve, with specific actions — not a vague "you should do better".
Encrypted Password and Photo Vault
If your credentials were in the breach, you need unique strong passwords across every account. Lunyb's encrypted Password Vault stores them securely, and the Photo Vault keeps sensitive images (passport scans, documents) out of your main gallery where apps can scrape them.
On-device tracker and threat blocking
Lunyb includes a local DNS shield that blocks known trackers and malicious domains on your device, without routing your traffic through a third party. Combined with the browsing-history eraser, it reduces how much ambient data about you is sitting around to be leaked in the next breach.
Data-broker exposure help and Photo Guard
Breached data often ends up aggregated by data brokers. Lunyb helps you see where your details are exposed so you can request removals. Photo Guard runs a reverse-image check so you can see where your pictures have ended up online — useful if a breach included profile photos.
Plans start from around £19.99 / $19.99 a month and renew until you cancel. You can cancel anytime online, and optional Leak Protection is billed separately and can be paused without cancelling the main plan. No lock-in, no games.
Comparison: DIY breach response vs Lunyb
| Task | Doing it manually | With Lunyb |
|---|---|---|
| Find out you're in a new breach | Wait for the breached company to email you | Automatic alerts on your email and phone |
| Check if a text or link is a scam | Google it and hope | Paste into Scam Checker for an instant verdict |
| Screen unknown callers | Answer and find out | Scam Shield flags suspicious calls |
| Review app permissions | Dig through each phone setting | Privacy Check surfaces risky permissions in one place |
| Store new unique passwords | Browser autofill or a notebook | Encrypted Password Vault |
| Block trackers on your phone | Install and configure filter lists | On-device DNS shield built in |
| Track your overall exposure | No clear number | Security Score with concrete next steps |
Penalties and consequences for organisations that don't report
The ICO has real enforcement powers under UK GDPR. Failing to notify a notifiable breach — or notifying late without good reason — can result in administrative fines of up to £8.7 million or 2% of global annual turnover, whichever is higher. More serious infringements (like unlawful processing) can go up to £17.5 million or 4% of global turnover.
Beyond fines, the ICO can issue reprimands, enforcement notices, and audits. And the reputational cost of a mishandled breach — covered in the press, discussed by customers, and remembered for years — is often worse than the regulatory penalty.
Common mistakes to avoid when reporting
- Waiting until you have perfect information. Submit a phased report instead. The 72-hour clock does not pause.
- Underestimating the risk. If sensitive categories (health, children, financial) are involved, treat it as high risk by default.
- Forgetting to tell affected individuals. Notifying the ICO is not the same as notifying data subjects. If the risk is high, you must do both.
- Not documenting non-notifiable breaches. Even if you decide not to report, you must log the incident and your reasoning.
- Vague communications to customers. UK GDPR requires clear, plain language. No PR fluff.
Take the next step with Lunyb
Reporting a breach to the ICO is the legal part. Protecting yourself and the people around you is the practical part — and that's where Lunyb comes in. Whether a breach has already hit you or you want to be ready for the next one, our app gives you alerts, scam defence, a password vault, privacy controls, and a clear security score in one place.
Head to lunyb.com to take the free privacy quiz, see where you're exposed, and download the Lunyb app on the App Store or Google Play. If you also handle links professionally, our secure link shortener and QR platform is worth a look — see our breakdowns in Is Lunyb Legit? Honest Review of the Privacy-First URL Shortener (2026) and Rebrandly Review 2026: Is It Worth the Price (or Try Lunyb)?.
Frequently asked questions
How quickly must I report a data breach to the ICO?
Organisations must report notifiable personal data breaches to the ICO within 72 hours of becoming aware of them. If you can't gather all the information in time, submit a phased report with what you have and follow up with the rest.
Do I report every data breach to the ICO?
No. You only need to report breaches that are likely to result in a risk to the rights and freedoms of individuals. For breaches you decide not to report, you still have to document the incident and your reasoning in an internal log that the ICO can request.
Can I report a breach as an individual whose data was leaked?
You don't file a formal Article 33 notification as an individual — that duty is on the data controller. But you can make a complaint to the ICO at ico.org.uk/make-a-complaint if an organisation has mishandled your data, after first raising it with the organisation itself.
What happens if an organisation doesn't report a breach?
Failure to notify a notifiable breach can lead to ICO enforcement action including reprimands, enforcement notices, and fines of up to £8.7 million or 2% of global annual turnover, whichever is higher. Reputational damage is often just as serious.
How does Lunyb help after a data breach?
Lunyb monitors your email and phone for new breach appearances, checks suspicious messages and links, screens unknown callers, reviews risky app permissions, stores unique passwords in an encrypted vault, and blocks trackers on your device. It turns the "what do I do now" after a breach into a clear, guided checklist. Start at lunyb.com.
Protect your links with Lunyb
Create secure, trackable short links and QR codes in seconds.
Get Started FreeRelated Articles
How to Remove Your Personal Information from Data Brokers (2026 Guide)
Data brokers collect and sell your personal information to anyone willing to pay. This step-by-step guide shows you exactly how to opt out of the biggest people-search sites and aggregators, use your legal rights under GDPR and CCPA, and keep your data from coming back.
How to Encrypt Your Internet Traffic: A Complete 2026 Guide
Encrypting your internet traffic protects you from ISP tracking, public Wi-Fi attackers, and data brokers. This complete 2026 guide covers HTTPS, encrypted DNS, Tor, secure messaging, and router hardening with step-by-step instructions.
How to Create a Link in Bio Page in 2026: Step-by-Step Guide
A link in bio page centralizes your most important links behind a single shareable URL, helping creators and brands convert social followers into customers. This step-by-step guide shows you how to plan, design, build, and optimize one in 2026 without wasting time on bloated tools.
How to Set Up Link Retargeting: A Complete Step-by-Step Guide
Link retargeting lets you build ad audiences from people who click your shortened links — even when the destination isn't your own site. This step-by-step guide walks you through platform selection, pixel setup, audience building, and campaign launch.