Alex is Sprintlaw's co-founder and principal lawyer. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.
Imagine you wake up to an email from your IT manager - your business has just suffered a data breach. Customer information, employee records or even payment details might be at risk. It’s a nightmare scenario for any UK business, but it’s also, unfortunately, more common than many realise.
With cyberattacks on the rise and more business taking place online, understanding your legal responsibilities around data breaches is now essential - whether you run a bustling e-commerce shop, a growing startup, or a local consultancy. Don’t stress - with the right knowledge and a solid compliance plan, you can minimise the risks, protect your reputation, and avoid costly fines.
In this guide, we’ll break down exactly what a data breach is, your key legal duties under UK data protection laws, and the practical steps you should have in place so your business is protected from day one. Let’s get started!
- What Is A Data Breach Under UK Law?
- Is Every Security Incident A Reportable Data Breach?
- What Must A UK Business Do In The First 72 Hours?
- When Do You Need To Notify The ICO Or Affected People?
- What Are The Legal Implications Of A Data Breach?
- Data Breach Example: How The Rules Work In Practice
- How Can You Prevent Data Protection Breaches?
- What Documents Should You Have Ready Before A Breach?
- Key Takeaways
What Is A Data Breach Under UK Law?
A personal data breach is a breach of security that leads to personal data being accidentally or unlawfully destroyed, lost, altered, disclosed or accessed without authorisation. In plain English, it's any situation where personal data your business is responsible for is no longer properly protected.
A data breach isn't only a cyberattack. It can happen because of a technical fault, a supplier error, a lost device, an email mistake or an employee doing the wrong thing. Common examples include:
- Cyberattacks such as ransomware, phishing, malware or a hacker accessing your CRM, ecommerce platform or HR system.
- Lost Or Stolen Devices such as a laptop, phone or USB drive containing unencrypted customer or employee information.
- Email Or Posting Errors such as sending invoices, payroll information or customer lists to the wrong person.
- Paperwork Going Astray such as personnel files, order forms or medical information being left in a public area or placed in ordinary rubbish.
- Incorrect System Permissions such as customers being able to see another customer's account details after a software update.
- Insider Misuse such as a staff member downloading client records for personal use or after leaving the business.
Personal data means information relating to an identified or identifiable person. It includes names, email addresses, phone numbers, postal addresses, account IDs, IP addresses, CCTV footage, order history, employee records, payroll details, health information, location data and online tracking data that can identify someone.
Some data is more sensitive. Special category data, such as health information, race or ethnic origin, political opinions, religious beliefs, trade union membership, genetic or biometric data and sex life or sexual orientation information, usually increases the seriousness of a breach. Financial details, login credentials and national insurance numbers can also create obvious risks.
Is Every Security Incident A Reportable Data Breach?
No. A security incident, a personal data breach and a reportable breach are related, but they aren't the same thing.
- A Security Incident is any event affecting your systems or information security. For example, a blocked phishing email or attempted login that doesn't expose personal data.
- A Personal Data Breach happens when personal data is actually lost, accessed, disclosed, altered or destroyed without proper authority. For example, an employee sends a spreadsheet of customers to the wrong external address.
- A Reportable Data Breach is a personal data breach that's likely to result in a risk to people's rights and freedoms. That's when the ICO notification duty usually applies.
The risk test focuses on the possible harm to people, not just embarrassment for the business. You should consider risks such as fraud, identity theft, financial loss, discrimination, loss of confidentiality, damage to reputation, distress, physical harm or loss of control over personal data.
For example, if an encrypted work laptop is lost but the password and encryption are strong and there's no evidence of access, you may decide the risk to people is low and the breach isn't reportable. You still need to record the incident and your reasons. If the same laptop is unencrypted and contains employee bank details, the position is very different.
What Must A UK Business Do In The First 72 Hours?
The 72-hour ICO clock starts when your business becomes aware of a personal data breach, meaning you have a reasonable degree of certainty that a security incident has compromised personal data. You don't need to know every detail before the clock starts.
If you're a processor handling data for another business, you must tell the controller without undue delay after becoming aware of a breach. The controller usually decides whether to notify the ICO and affected individuals, so delays from processors can create serious problems.
Use this first 72 hours checklist as your working incident log:
- Record The Time And Date Discovered so you can track the 72-hour reporting window and show when the business became aware.
- Appoint An Incident Lead who can coordinate IT, legal, customer support, HR, senior management and suppliers.
- Identify Systems, Accounts And Suppliers Involved including CRMs, payment platforms, cloud storage, email accounts, payroll providers and marketing tools.
- Take Immediate Containment Steps such as disabling accounts, resetting passwords, revoking API keys, isolating devices or stopping an email recall where possible.
- List The Personal Data Categories including names, emails, passwords, payment details, health data, payroll data or ID documents.
- Estimate People Affected including customers, employees, contractors, suppliers or website users, even if the first number is approximate.
- Assess Risk To Individuals by looking at sensitivity, volume, likelihood of misuse, vulnerability of people affected and whether data is encrypted or otherwise protected.
- Decide Whether To Notify The ICO and record the reasons for reporting or not reporting.
- Decide Whether To Notify Individuals and record whether the breach is likely to create a high risk.
- Nominate A Message Owner to prepare clear communications for customers, staff, partners and affected people.
- Check Insurer, IT Provider And Key Customer Notices because cyber insurance policies and commercial contracts often require prompt notification.
- Preserve Evidence including logs, emails, screenshots, access records, device details and supplier correspondence.
- Set Follow-Up Actions such as patching systems, updating policies, retraining staff and reviewing supplier contracts.
A good plan in place turns this from a panic into a process. It also helps show the ICO, customers and commercial partners that your business took the incident seriously.
When Do You Need To Notify The ICO Or Affected People?
You must notify the ICO if the breach is likely to result in a risk to people's rights and freedoms. The notification must be made without undue delay and, where feasible, within 72 hours of becoming aware of the breach. If you notify late, you should explain the reasons for the delay.
Your ICO notification should include, as far as possible:
- what happened, including the nature of the breach;
- the categories and approximate number of people affected;
- the categories and approximate number of personal data records affected;
- the likely consequences for affected people;
- the steps taken or proposed to deal with the breach;
- measures taken to reduce possible harm; and
- contact details for your data protection officer or other contact point, if you have one.
You can provide information in phases if you don't have everything within 72 hours. Don't delay an initial notification just because your investigation is ongoing. Our detailed article on GDPR data breach reporting walks through the notification process in more detail.
You must tell affected individuals without undue delay if the breach is likely to result in a high risk to their rights and freedoms. High risk is more likely where the breach involves bank details, passwords, identity documents, special category data, children's data, vulnerable people, large volumes of data or information that could cause serious distress or financial harm.
Affected-person notices should be clear, practical and not misleading. A lawyer should tailor the wording, but a sensible outline is:
- What Happened with a short, honest description of the incident and when it was discovered.
- What Data Was Involved using categories people can understand, without exposing more information.
- What You Have Done including containment, investigation and security steps already taken.
- What The Person Should Do such as changing passwords, watching bank accounts or being alert to phishing.
- Who To Contact for questions, support and data protection requests.
- Where To Complain including the right to raise concerns with the ICO where appropriate.
If you're also handling deletion requests or wider privacy rights after a breach, our article on GDPR right to erasure and data breach notification may help your team avoid inconsistent responses.
What Are The Legal Implications Of A Data Breach?
The legal implications of a data breach can go well beyond the immediate IT problem. Under UK GDPR and the Data Protection Act 2018, the ICO can investigate, issue warnings or reprimands, require changes to your practices, restrict processing and impose fines.
For the most serious infringements, ICO fines can currently reach up to £17.5 million or 4% of annual worldwide turnover, whichever is higher. In practice, the ICO looks at factors such as the nature and seriousness of the breach, whether security was appropriate, how quickly you acted, whether you notified on time, cooperation with the ICO, previous issues and steps taken to reduce harm.
Individuals can also bring compensation claims. Under section 168 of the Data Protection Act 2018, compensation can cover material damage, such as financial loss, and non-material damage, including distress. Data breach compensation isn't automatic. A person usually needs to show that the breach caused loss or distress, but even small claims can take time and money to manage.
There can also be commercial consequences. Key customers may require incident reports, suppliers may suspend integrations, payment providers may ask for evidence of security improvements, and future enterprise customers may scrutinise your data protection documents before signing. If you process data for another business, your contract may require urgent notice, cooperation, audit support or indemnities.
Data Breach Example: How The Rules Work In Practice
Imagine BrightBox Gifts, a 12-person online gift retailer, discovers at 9:00am on Monday that a staff member clicked a phishing link on Friday. The attacker accessed the staff member's email account and downloaded an attachment containing a Christmas fulfilment spreadsheet.
The spreadsheet includes 1,850 customer names, email addresses, delivery addresses and order notes. It also includes 120 gift messages, some of which reveal personal relationships and special occasions. It doesn't include card numbers because payments are handled by a separate payment provider. The attacker also sent 300 phishing emails from the staff account before access was disabled.
BrightBox's first steps are to reset passwords, revoke active sessions, turn on multi-factor authentication for the affected account, check email forwarding rules, preserve logs and ask its IT provider to confirm whether any other accounts were accessed. It appoints one director as incident lead and records the time the business became aware.
By Monday afternoon, BrightBox decides the breach is likely to create a risk to people's rights and freedoms because customer contact details and order information could be used for targeted phishing or scams. It notifies the ICO within 72 hours, explaining that some numbers are still approximate and that a fuller update will follow.
BrightBox also considers whether the risk is high enough to require direct customer notification. Because the data doesn't include payment card numbers, passwords or identity documents, it may not be high risk for every customer. However, the business decides to send a clear warning to the 1,850 affected customers anyway, telling them what happened, what data was involved, that payment details weren't affected, and how to spot scam emails pretending to be from BrightBox.
BrightBox's records show containment, risk assessment, timely ICO notification, customer communications and follow-up improvements.
How Can You Prevent Data Protection Breaches?
No business can guarantee a breach will never happen, but UK data protection law expects security to be appropriate to the risk. That means your controls should match the type and amount of data you hold, the harm that could occur, your systems and your business size.
Practical prevention steps include:
- Data Mapping so you know what personal data you collect, where it sits, who can access it and which suppliers process it.
- Access Controls so staff only access what they need and leavers are removed promptly.
- Multi-Factor Authentication for email, admin dashboards, cloud storage, payroll, CRM and ecommerce systems.
- Encryption And Secure Storage for laptops, portable devices, backups and sensitive files.
- Regular Updates And Backups to reduce ransomware risk and help restore operations.
- Staff Training on phishing, passwords, safe sharing, reporting mistakes quickly and handling personal data securely.
- Supplier Checks before giving vendors access to customer, employee or user data.
- Privacy Notices And Cookie Documents so people understand your processing and your team handles data consistently. Your website policies should explain data use clearly, and policies explain how tracking technologies are used.
If you want a broader sense of where your business might be exposed, the Legal Health Check can help you spot common legal and compliance gaps.
What Documents Should You Have Ready Before A Breach?
Data breach response is much easier when your legal documents and internal processes are already in place. The most useful documents for many UK businesses are:
- Privacy Policy explaining how your business collects, uses, stores, shares and protects personal data. You can Get your Privacy Policy reviewed for GDPR compliance.
- Data Breach Response Plan setting out who does what, how incidents are escalated, who decides on ICO notification and how communications are approved. See our bespoke plans.
- Data Processing Agreements with suppliers who process personal data for you, such as payroll providers, email marketing platforms, IT support, hosting providers and fulfilment partners. Read more about Data Processing Agreements and why they matter.
- Information Security Policy covering passwords, devices, remote work, software updates, access permissions, backups and incident reporting.
- Staff Training Materials so employees understand what counts as personal data, how to report mistakes and what not to send by email.
- Breach Register recording every personal data breach, including minor incidents you decide not to report to the ICO. You can learn more about effective breach recordkeeping here.
For a broader compliance overview, see our guide on data protection and security compliance under UK GDPR. It's also sensible to speak to a data privacy lawyer about documents tailored to your business model and sector.
Key Takeaways
- A data breach isn't just a hack. It can include lost devices, email mistakes, unauthorised access, accidental disclosure or destruction of personal data.
- Under UK GDPR and the Data Protection Act 2018, you must contain, assess and record every personal data breach.
- You must notify the ICO without undue delay and where feasible within 72 hours if the breach is likely to risk people's rights and freedoms.
- You must tell affected individuals without undue delay if the breach is likely to create a high risk for them.
- Data breach consequences can include ICO action, fines, compensation claims, contract issues and reputational damage.
- Strong policies, supplier contracts, staff training and a practical response plan can make a major difference when the first 72 hours matter.
If you'd like help with assessing a data breach, preparing ICO or customer notifications, drafting a data breach response plan or reviewing your privacy documents, you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.
Build privacy controls around the real data flow
What should the business document next?
Map the purpose, roles, lawful basis, notices, processor terms, retention, rights requests and incident response before relying on a policy alone.








