How to Report a Data Breach to the ICO Within 72 Hours (UK Guide)
If your organisation has suffered a personal data breach, the clock is already ticking. Under the UK GDPR, you generally have 72 hours from becoming aware of a notifiable breach to report it to the Information Commissioner's Office (ICO). Miss that window, or get the detail wrong, and you risk enforcement action, reputational damage and a wave of customer complaints you could have avoided.
This guide walks you through exactly how to report a personal data breach to the ICO within the official 72-hour deadline. It also shows how Lunyb helps UK businesses and the individuals they employ catch leaked credentials and exposed data early — often before a breach escalates into a reportable incident.
What counts as a personal 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 just hacking. It includes lost laptops, misdirected emails, ransomware, stolen paperwork and insider misuse.
You must report a breach to the ICO when it is likely to result in a risk to the rights and freedoms of individuals. If the risk is high, you must also notify the affected individuals directly, without undue delay.
Examples of notifiable breaches
- A ransomware attack that encrypts customer records.
- An email containing a client spreadsheet sent to the wrong recipient.
- A lost unencrypted USB stick holding HR files.
- A phishing compromise of a staff mailbox containing personal data.
- A misconfigured cloud bucket exposing user details to the public internet.
Examples that may not need reporting
- An encrypted laptop lost where the key is secure and no data is accessible.
- A minor internal error with no realistic risk to individuals (document this anyway).
Even if you decide not to report, you must keep an internal record of every breach, the reasoning behind your decision and the remedial steps taken.
The 72-hour rule explained
Article 33 of the UK GDPR sets the 72-hour clock. The countdown starts when your organisation becomes aware of the breach — not when it technically occurred and not when you finish investigating. Awareness means you have a reasonable degree of certainty that a security incident has occurred that led to personal data being compromised.
If you cannot provide every detail within 72 hours, you can still report on time and supply the remaining information in phases. The ICO explicitly allows a phased approach — late and silent is worse than early and incomplete.
What the ICO expects within 72 hours
- The nature of the breach, including categories and approximate numbers of data subjects and records affected.
- The name and contact details of your Data Protection Officer or a nominated contact.
- The likely consequences for the individuals involved.
- The measures you have taken or propose to take to address the breach and mitigate harm.
Step-by-step: how to report a data breach to the ICO
Here is the exact process UK organisations should follow when the 72-hour clock is running.
Step 1: Contain the breach immediately
- Isolate affected systems, accounts or endpoints from the network.
- Revoke compromised credentials, API keys and session tokens.
- Recall or delete misdirected emails where possible and ask recipients to confirm deletion.
- Preserve logs and forensic evidence — do not wipe or reinstall before investigation.
Step 2: Assess the risk to individuals
Decide whether the breach is likely to result in a risk to people's rights and freedoms. Consider:
- Type of data (special category data, financial data and ID documents raise the risk).
- Volume of records and number of people affected.
- Ease of identification of individuals.
- Severity of potential consequences: identity theft, fraud, discrimination, distress or physical harm.
Step 3: Decide if it is notifiable
If there is any realistic risk to individuals, treat it as notifiable. When unsure, the ICO's position is to err on the side of reporting. Document your decision either way in your breach log.
Step 4: Submit the report to the ICO
You have three official routes:
- Online form: use the ICO's personal data breach reporting service at ico.org.uk. This is the quickest option and generates a case reference.
- Telephone: call the ICO helpline on 0303 123 1113 (open Monday to Friday). Useful out of hours for live incidents escalating fast — follow up with the online form.
- Public sector electronic communications breach: telecoms and ISPs follow PECR-specific routes.
Step 5: Notify affected individuals if risk is high
If the breach is likely to result in a high risk to individuals, you must also tell them directly, in clear plain English. The notice should include:
- A description of what happened.
- The contact point for more information.
- Likely consequences.
- Steps you have taken and advice they should follow (change passwords, watch for phishing, monitor financial accounts).
Step 6: Record everything
Maintain an internal breach register with timestamps, decisions, evidence and remedial actions. The ICO can request this at any time.
What happens after you report
Once you submit a report, the ICO issues a case reference and may contact you for more information. Possible outcomes include:
- No further action if the response was appropriate and the risk is low.
- Guidance or recommendations to improve controls.
- Formal investigation, enforcement notice or monetary penalty for serious failings.
The quality of your response — containment, honesty, communication with data subjects — materially affects the outcome. Organisations that detect fast, contain fast and report transparently fare far better than those that delay.
Why early detection is the real win — and where Lunyb fits in
The 72-hour clock only starts when you become aware of a breach. The uncomfortable truth is that most organisations find out weeks or months late, often from a customer, a journalist, or a credential dump surfacing on the dark web. By then, damage is done and the ICO report is a firefighting exercise.
This is exactly where Lunyb earns its place in your stack. Lunyb is a privacy and scam-protection platform built for the way real people — including your staff, founders and customers — actually get breached: through reused passwords, exposed emails, leaked phone numbers and phishing links that slip past filters.
How Lunyb helps UK businesses and their people
- Data Breach Alerts for email and phone: Lunyb continuously monitors whether staff emails and phone numbers appear in known breaches, so you can rotate credentials and act before attackers exploit them.
- Scam Checker: paste a suspicious message, link or sender into Lunyb to get a fast risk read before anyone clicks. Great for finance teams targeted by invoice fraud and CEO-impersonation attacks.
- Scam Shield and caller protection: cuts down on the social-engineering calls that often precede a breach.
- Privacy Check: reviews app permissions on personal and work devices to flag over-sharing apps that leak contacts, location and identifiers.
- Encrypted Password and Photo Vault: stops staff storing credentials in Notes, email drafts and screenshots — a leading cause of accidental exposure.
- On-device tracker and threat blocking: a local DNS shield that blocks known malicious domains and trackers at the device level, reducing the attack surface without routing traffic through a third-party tunnel.
- Photo Guard reverse-image check: helps spot impersonation accounts using your brand's or executives' photos.
- Security score: a single number that tells each user how exposed they are and what to fix next.
None of this replaces your enterprise SIEM or incident-response plan. What Lunyb does is close the human-layer gap: the moment a staff password surfaces in a breach dump, the moment someone almost clicks a phishing link, the moment a personal device starts leaking contact data. Catching those earlier means fewer notifiable incidents, and when one does happen, you spot it faster — which is the difference between a clean 72-hour report and a messy, delayed one.
Lunyb vs. doing it all manually
| Task | Manual approach | With Lunyb |
|---|---|---|
| Check if staff emails are in breaches | Search multiple sites, repeat monthly | Continuous automated alerts |
| Vet a suspicious link or SMS | Guesswork or ask IT | Paste into Scam Checker for instant risk read |
| Block malicious domains on personal devices | Not possible without MDM | On-device DNS-level shield |
| Review risky app permissions | Manual device-by-device audit | Guided Privacy Check |
| Store credentials securely | Varies wildly by employee | Encrypted vault built in |
| Measure personal exposure | No clear metric | Security score per user |
Common mistakes UK organisations make with ICO breach reporting
Waiting until the investigation is complete
You do not need the full picture to report. Submit what you know within 72 hours and update in phases.
Underestimating the breach
A single misdirected email containing special category data can be notifiable. Do not downplay — assess honestly.
Forgetting to notify individuals
Reporting to the ICO is not the same as notifying data subjects. If the risk is high, people deserve to know, promptly and clearly.
No breach register
Even non-reportable incidents must be logged. The ICO can and does ask to see the register.
Treating prevention as a one-off
Breach prevention is a running process. Credential leaks happen weekly across the web. Tools like Lunyb give you ongoing visibility rather than annual snapshots.
Your next step: tighten exposure before the clock ever starts
The best ICO breach report is the one you never have to file. Start by reducing the exposure of the people inside and around your organisation.
- Go to lunyb.com and take the free privacy quiz to see where your immediate risks are.
- Install the Lunyb app on staff devices to enable Data Breach Alerts, Scam Shield and the on-device threat shield.
- Roll out the encrypted vault so credentials stop living in notes, chats and spreadsheets.
- Review your 72-hour breach response playbook so every manager knows the ICO process by heart.
Plans start from about £19.99 / $19.99 per month, renew until cancelled, and you can cancel anytime online. Optional Leak Protection is billed separately and can be paused without cancelling the main plan — transparent pricing, no lock-in, no surprises.
If you also want to see how Lunyb performs as a broader privacy product, read our honest review of Lunyb or our 2026 deep-dive. Teams using Lunyb for secure link sharing can also compare it with alternatives in our Rebrandly 2026 review.
FAQ
When does the 72-hour ICO reporting clock start?
It starts when your organisation becomes aware that a personal data breach has occurred — meaning you have a reasonable degree of certainty that a security incident has compromised personal data. Not when it happened, and not when the investigation ends.
What if I miss the 72-hour deadline?
Report as soon as you can and include an explanation for the delay. Late reporting can lead to enforcement action, but failing to report at all is worse. Document your timeline and reasoning in your breach register.
Do I have to tell affected customers?
Only if the breach is likely to result in a high risk to their rights and freedoms. If so, notify them directly and in plain English, including what happened, likely consequences and the steps they should take.
Can Lunyb report breaches to the ICO for me?
No — the legal obligation to report sits with your organisation as the data controller. What Lunyb does is help you detect exposure earlier (through Data Breach Alerts, Scam Checker and on-device protection) so breaches are caught sooner, contained faster and often prevented from escalating into notifiable incidents.
Is Lunyb suitable for small UK businesses?
Yes. Lunyb is designed for individuals and small teams who need enterprise-grade privacy hygiene without an enterprise security team. Start with the free quiz on lunyb.com, roll out the app to staff, and build from there.
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.