How to Report a Data Breach to the ICO: Complete UK Guide for 2024
If personal data has been exposed, lost, or stolen, UK law can require you to tell the Information Commissioner's Office (ICO) within 72 hours. That window is short, the paperwork is specific, and the clock does not pause while you work out what happened. This guide walks you through exactly how to report a data breach to the ICO, what the ICO expects to see, and how Lunyb helps individuals and small organisations spot exposure early, document it clearly, and lock accounts down before more damage is done.
We write this as the Lunyb editorial team. We build privacy and scam-protection tools, and we see the aftermath of breaches every day — from leaked email addresses used in phishing, to stolen phone numbers hitting scam call lists. A fast, calm, organised response is always better than a late one, and the right tools make that possible.
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. In plain English: if personal information you hold about people has been seen, taken, lost, encrypted by ransomware, emailed to the wrong person, or made available to someone who should not have it, that is a breach.
The ICO groups breaches into three types:
- Confidentiality breach — personal data is disclosed to, or accessed by, someone unauthorised (for example, a phishing attack that exposes customer records).
- Integrity breach — personal data is altered without permission (for example, a bad actor changing payroll details).
- Availability breach — personal data is lost or made inaccessible (for example, a lost laptop with no backup, or a ransomware attack).
A breach is not only a hacker story. Sending a spreadsheet to the wrong email address, losing a USB stick, or leaving printouts on a train all count.
Do you have to report the breach to the ICO?
Not every breach needs to be reported. Under UK GDPR, a controller must notify the ICO unless the breach is unlikely to result in a risk to the rights and freedoms of individuals. If the risk is high, you must also tell the affected people themselves, without undue delay.
When reporting is required
- Personal data has been exposed that could lead to identity theft, financial loss, fraud, discrimination, reputational damage, or significant distress.
- Special category data (health, religion, ethnicity, sexual orientation, biometric data) is involved.
- Children's data is involved.
- Login credentials, financial details, or ID documents have been exposed.
- You cannot confidently rule out harm.
When you may not need to report
- The data was strongly encrypted and the key is safe.
- The data was already public.
- You can clearly demonstrate no meaningful risk to the people involved.
If you are unsure, the ICO's own guidance is to lean toward reporting. You must also record every breach internally, reportable or not, in a breach log. That log is one of the first things the ICO will ask to see if it ever audits you.
The 72-hour rule: when the clock starts
The 72-hour countdown starts when you become aware of the breach, not when the breach happened. "Aware" means you have a reasonable degree of certainty that a security incident has led to personal data being compromised.
You do not need every answer before you report. The ICO accepts phased reporting: send what you know now, then follow up with more detail. If you miss the 72-hour deadline, you can still report — you just need to explain the delay.
How to report a data breach to the ICO: step by step
Here is the practical process to follow the moment you suspect a reportable breach.
- Contain the incident. Disconnect affected systems, revoke compromised credentials, force password resets, lock lost devices, and stop any ongoing data flow (for example, recall a misdirected email where possible).
- Assess the scope. Work out what data was involved, how many people are affected, what categories of data (names, emails, financial, special category), and what the realistic harm looks like.
- Record everything. Start a timeline: when the incident happened, when it was discovered, who was told, what actions were taken, and when. This becomes your audit trail.
- Decide whether to notify the ICO. Apply the "risk to rights and freedoms" test. If in doubt, report.
- Submit the report. Use the ICO's online report a breach service, or call the ICO helpline on 0303 123 1113 for urgent issues outside normal processes.
- Notify affected individuals if the risk is high. Tell them in clear, plain language what happened, what data was involved, what you are doing, and what they should do (change passwords, watch for scams, check statements).
- Follow up. Send the ICO updated information as you investigate. Close the incident with a written post-mortem and lessons learned.
What information the ICO wants in your report
The ICO's report form is structured. Having this ready in advance cuts your reporting time from hours to minutes.
- Your organisation details — name, ICO registration number, contact person (usually the DPO if you have one).
- Nature of the breach — confidentiality, integrity, or availability; cause (phishing, lost device, misdirected email, cyber attack, insider, etc.).
- Categories and approximate number of individuals affected.
- Categories and approximate number of records affected.
- Likely consequences — financial loss, identity fraud, distress, discrimination.
- Measures taken — containment, remediation, and steps to prevent recurrence.
- Whether you have told affected individuals, and if not, why not.
Reporting as an individual: what to do if your data was breached
You do not report a breach to the ICO on your own behalf — the organisation that lost your data does that. But you have important rights and practical steps to take.
- Demand information from the organisation. Ask what data was exposed, when, and what they are doing.
- Change passwords for the affected service and any other account using the same password.
- Turn on two-factor authentication everywhere it is offered.
- Watch your bank and card statements for unfamiliar transactions.
- Be alert to phishing — breached email addresses and phone numbers are heavily used for follow-up scams.
- Complain to the ICO if the organisation is unresponsive or you believe it mishandled your data. Use the ICO's "make a complaint" route.
- Consider Action Fraud at actionfraud.police.uk if you have been defrauded or impersonated.
How Lunyb helps you detect, respond to and recover from a breach
A breach response is only as fast as your detection. Most people learn their data has leaked weeks or months after it happens — often from a strange login alert or a surge of scam calls. Lunyb is built to close that gap. Whether you are an individual protecting your household or a small business owner who holds customer data, our tools give you the early warning and the clean-up kit you need.
Data Breach Alerts for your email and phone
Lunyb's Data Breach Alerts continually check whether your email addresses and phone numbers have surfaced in known breaches. If a service you use is compromised, you find out quickly, with a clear note on what to change and where. This is exactly the early signal that lets you reset credentials before attackers get to them, and lets a business owner start the 72-hour clock with confidence instead of guesswork.
Scam Checker and Scam Shield for the fallout
After a breach, your details end up on target lists. The Lunyb Scam Checker lets you paste in a suspicious message or link and get a verdict before you click. Scam Shield helps filter and flag suspicious caller activity, so the inevitable wave of "your bank's fraud team" calls hits a wall instead of your family.
Encrypted Password and Photo Vault
Reusing passwords turns one breach into ten. Our encrypted vault gives you a safe place to store unique, strong credentials and sensitive photos (ID scans, insurance documents) so a single leaked site cannot cascade into your whole digital life.
Privacy Check and Security Score
Privacy Check reviews the permissions your apps have asked for and flags the ones that do not need that level of access. The Security Score gives you a single headline number that moves as you tighten things up, so you can see progress and know what to fix next.
On-device tracker and threat blocking
Lunyb includes a local, on-device DNS shield that blocks known trackers and malicious domains before your browser even connects. That reduces the surface area attackers can use to deliver follow-up phishing pages after a breach.
Photo Guard, browsing-history eraser and exposure help
If your face or documents are floating around, Photo Guard runs reverse-image checks to find where they have surfaced. The browsing-history eraser removes local traces that can be used to profile you, and our data-broker style exposure help walks you through reducing your footprint on the sites that aggregate personal data.
Lunyb plans start from about £19.99/month equivalent and renew until cancelled — you can cancel anytime online, no phone call required. Optional Leak Protection is billed separately and can be paused without cancelling your main plan. That transparency is deliberate: a privacy product should never trap you.
Doing it manually vs doing it with Lunyb
| Task after a breach | Manual approach | With Lunyb |
|---|---|---|
| Find out if your email or phone is in a breach | Check multiple sites yourself, repeatedly | Continuous Data Breach Alerts |
| Check if a follow-up message is a scam | Guess, or search snippets online | Paste into Scam Checker for a verdict |
| Block scam calls that follow a leak | Report each number one by one | Scam Shield caller protection |
| Stop password reuse | Try to remember, or use a spreadsheet | Encrypted Password Vault |
| See where your photos have been reused | Manual reverse-image searches | Photo Guard |
| Reduce data-broker exposure | Research and email each broker | Guided exposure help |
| Measure overall privacy health | No central view | Security Score dashboard |
Common mistakes organisations make when reporting to the ICO
- Waiting for "full facts" before reporting. The ICO expects phased reporting. Send what you have.
- Under-scoping the breach. Assuming only one record was affected when logs have not been reviewed properly.
- Not telling affected individuals. If the risk is high, individuals must be told in clear language — hiding behind legalese is a red flag to the ICO.
- No breach log. Failing to document even non-reportable breaches is itself a compliance failure.
- Weak follow-up. Reporting and then not fixing the root cause invites a second breach — and much harsher regulatory treatment.
Penalties for failing to report
Under UK GDPR, failing to notify the ICO when required can attract significant administrative fines — up to the higher of £8.7 million or 2% of global annual turnover. The ICO can also issue reprimands, enforcement notices, and audits. In practice the regulator tends to come down hardest on organisations that tried to hide a breach, misled affected people, or ignored obvious warning signs.
A sensible breach-ready checklist
- Appoint a named person responsible for breach response.
- Keep a simple breach log template ready.
- Know your ICO registration number and keep DPO contact details current.
- Document who can authorise notifying the ICO and affected individuals.
- Pre-write a plain-English notification template for customers.
- Enforce unique passwords and two-factor authentication across staff accounts.
- Use continuous breach-alert monitoring so you are not the last to know.
- Review and test the plan at least once a year.
Take the next step with Lunyb
Reporting a breach to the ICO is a legal duty, but the real work is making sure the people whose data was exposed — including you — come out the other side without lasting damage. That is where Lunyb fits naturally. Start with the free privacy quiz on lunyb.com to see where you stand in minutes, then download the Lunyb app from the App Store or Google Play to switch on Data Breach Alerts, Scam Shield, the encrypted vault, and the on-device threat blocker.
If you want to see how we think about trust and transparency in our other products, our team also covers related reviews such as Is Lunyb Legit? Honest Review of the Privacy-First URL Shortener (2026) and Rebrandly Review 2026: Is It Worth the Price (or Try Lunyb)?.
FAQ
How quickly do I have to report a data breach to the ICO?
Within 72 hours of becoming aware of it, where the breach is likely to risk people's rights and freedoms. If you miss the deadline, still report, and explain the delay.
Do I need to tell the people affected by the breach?
Yes, if the breach is likely to result in a high risk to their rights and freedoms. Communication must be in clear, plain language and explain what happened, what data was involved, and what they should do.
What if I am an individual whose data was breached by a company?
Contact the company first and ask what happened. Change passwords, enable two-factor authentication, watch for scams, and complain to the ICO if the company is unresponsive. Lunyb's Data Breach Alerts and Scam Checker help you spot exposure and the scams that follow it.
Does Lunyb replace the need to report a breach?
No. Reporting to the ICO is a legal duty for data controllers. Lunyb helps you detect breaches faster, respond cleanly, protect your accounts, and reduce the chance that leaked data is used against you.
How much does Lunyb cost and can I cancel?
Plans start from about £19.99/month equivalent and renew until cancelled. You can cancel anytime online. Optional Leak Protection is billed separately and can be paused without cancelling the main plan.
Protect your links with Lunyb
Create secure, trackable short links and QR codes in seconds.
Get Started FreeRelated Articles
How to Shorten a URL: The Complete 2026 Guide
Learn exactly how to shorten a URL in seconds with this complete 2026 guide. Covers free tools, custom slugs, branded domains, bulk shortening, QR codes, analytics, and safety best practices for creators, marketers, and everyday users.
How to Block Trackers on Your Phone: The Complete 2026 Guide
Phone trackers quietly collect your location, behavior, and identity across apps and websites. This step-by-step guide shows you how to block them on iOS and Android using built-in settings, encrypted DNS, and privacy-respecting browsers — no technical skills required.
How to Check if Your Password Was Leaked in a Data Breach (2026 Guide)
Billions of passwords are leaked in data breaches every year. This step-by-step guide shows you how to check if your password was exposed, which free tools are safe to use, and exactly what to do if you find a match.
How to Check if a Link Is Safe Before Clicking (2026 Guide)
Learn how to check if a link is safe before clicking with 10 proven methods, free scanner tools, and expert red-flag checks. A complete 2026 guide to spotting phishing, malware, and scam URLs in email, SMS, and social media.