Black Friday10% off any legal service

NHS Data Leak: What To Do Now

If news about an NHS data leak has you wondering “could that happen to us?”, you’re asking exactly the right question. High‑profile incidents are a stark reminder that even well‑resourced organisations can be caught out by complex systems, supply chains and human error.

For UK small businesses, the takeaway isn’t panic - it’s preparation. Solid data protection practices don’t have to be complicated or costly, and getting your legal and operational foundations right now will dramatically reduce risk later.

In this guide, we’ll break down what the NHS incident means for SMEs, your core legal duties under UK law, and practical steps you can take today to protect your business, your customers and your team.

What Counts As An NHS Data Leak Or Data Breach?

A personal data breach isn't just a hacker stealing a database. Under UK GDPR, it can be any security incident that leads to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data.

In everyday business terms, that can include:

  • An email containing customer, patient or employee details being sent to the wrong recipient.
  • A spreadsheet being uploaded to a public folder or shared with the wrong permissions.
  • A stolen laptop, phone or USB drive containing personal data.
  • A compromised email account, CRM, payroll platform or booking system.
  • A supplier exposing data through an insecure portal, misconfigured cloud storage or weak admin controls.
  • Records being deleted, corrupted or destroyed before the end of a required retention period.

NHS data leaks usually involve very sensitive information. Health data is special category data, which usually increases the potential harm if it's exposed. Your business may not handle NHS records, but you may still hold personal data that could cause harm if leaked, such as ID documents, financial details, HR files, customer complaints, location data, children's data or confidential notes about service users.

What Recent NHS Data Breach News Means For Your Business

NHS data privacy news tends to involve large organisations, complex systems and long supply chains. That can make the issue feel remote from a small business. In practice, the same weak points appear again and again in SMEs: too much data collected, too many people with access, unclear supplier responsibilities, old files kept forever and no tested breach response process.

  • Suppliers matter. If your CRM, payroll provider, outsourced IT support, marketing platform or booking tool mishandles data, your customers may still look to you for answers.
  • Sensitive data needs extra care. Health, HR and financial information are more likely to create a risk, or high risk, if exposed.

For example, suppose a private physiotherapy clinic uses a third-party booking platform. On Monday morning, the platform discovers that 480 appointment records were accessible through a misconfigured link. The records include names, contact details, dates of birth and appointment notes that reveal health information. The platform tells the clinic that afternoon.

The platform is likely acting as a processor, and the clinic is likely the controller for its patient data. The platform must notify the clinic without undue delay after becoming aware of the personal data breach. The clinic then needs to assess whether the incident is likely to risk people's rights and freedoms. Because health-related appointment notes are involved, the clinic may decide the ICO should be notified within 72 hours of becoming aware. If the clinic also concludes the breach is likely to create a high risk for those patients, it should tell affected people without undue delay, in clear language, with practical steps they can take.

What Are Your UK GDPR Duties And What Has Changed?

As a UK business handling personal data, you're generally subject to the UK GDPR and the Data Protection Act 2018. The Data (Use and Access) Act 2025 doesn't replace those laws or PECR, but it makes targeted changes that businesses should factor into their compliance processes, including complaint-handling duties and changes affecting subject access request time limits.

Know Whether You Are A Controller Or Processor

You're usually a controller when you decide why and how personal data is used, such as your customer database, employee records or marketing list. You may be a processor when you handle personal data only on another organisation's instructions, such as providing outsourced services to a client.

Controllers carry the main responsibility for deciding whether a breach is reportable and making any ICO notification. Processors have direct duties too, including notifying the controller without undue delay after becoming aware of a personal data breach. If you use processors, you need a compliant Data Processing Agreement with the mandatory UK GDPR clauses.

Use A Lawful Basis And Be Transparent

  • Identify a lawful basis for each use of personal data, such as contract, legal obligation, legitimate interests or consent.
  • Explain what you collect, why, how long you keep it, who you share it with and what rights people have in an up-to-date Privacy Policy.
  • Don't reuse personal data in ways that are incompatible with the original purpose unless the law allows it.

Secure Data And Prove Accountability

  • Use appropriate technical and organisational measures, such as MFA, encryption, access controls, staff training and supplier checks.
  • Keep evidence of compliance, including data maps, DPIAs where needed, training records, incident logs and supplier due diligence.
  • Pay the ICO data protection fee unless an exemption applies. The current tiers are £52, £78 and £3,763, and fixed non-payment penalties are £400, £600 or £4,000, with a possible maximum of £4,350 in some cases.

Keep Retention, Deletion And Data Destruction Under Control

Keep personal data only for as long as you need it for a clear purpose. After that, delete it securely, anonymise it properly, or archive it with restricted access if you genuinely still need it. Old data can turn a small incident into a much larger breach.

If you're unsure where to start, our overview of Data Retention can help you set sensible retention periods.

When You Must Report A Data Breach To The ICO

You don't have to report every personal data breach to the ICO. A controller 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. The official Article 33 rule is available here: https://www.legislation.gov.uk/eur/2016/679/article/33.

Risks can include identity theft, fraud, financial loss, distress, reputational damage, discrimination, loss of confidentiality, loss of control over personal data or harm caused by sensitive information being exposed.

If the breach is likely to result in a high risk to people's rights and freedoms, you must also communicate it to affected individuals without undue delay, unless an exception applies. For example, you may not need to contact every person directly if the data was already protected in a way that made it unintelligible to unauthorised people, if later steps removed the high risk, or if direct communication would involve disproportionate effort and an equally effective public communication is used instead. The Article 34 rule is available here: https://www.legislation.gov.uk/eur/2016/679/article/34.

When you tell affected people, use plain English and include:

  • What happened, in clear and factual terms.
  • What personal data was affected.
  • The likely consequences.
  • What you have done or will do to reduce the impact.
  • Practical protective steps, such as password resets, fraud monitoring or phishing warnings.
  • A contact point for questions.

If you decide not to notify the ICO, don't just move on. Controllers must record all personal data breaches, including those that aren't reportable. Your incident record should show what happened, what data was involved, your risk assessment, who made the decision, why notification was or wasn't required, and what remedial steps were taken. Failing to notify the ICO when required can result in a fine of up to £8.7 million or 2% of total worldwide annual turnover, whichever is higher.

  • Identify And Contain. Record who found the issue, when your business became aware, which systems are affected, whether access has been revoked and what evidence must be preserved.
  • Classify The Data. Check whether the incident involves personal data, special category data, financial data, children's data, staff data, customer data or supplier data.
  • Decide Notifications. Decide whether the ICO reporting threshold is met, whether individuals must be told, and whether Action Fraud or the National Cyber Security Centre should be contacted where cybercrime is suspected.

How To Reduce Breach Risk Before It Happens

You don't need enterprise-level infrastructure to reduce your risk. Focus on high-impact actions that work in a small business environment.

Map Your Data And Minimise Collection

  • List what personal data you hold, where it lives, who has access and why you need it.
  • Stop collecting data that isn't genuinely useful or required.
  • Keep your Privacy Policy aligned with your real data flows.

Tighten Access And Authentication

  • Use multi-factor authentication on email, cloud storage, admin accounts, finance systems and customer databases.
  • Apply least privilege access so staff only see what they need for their role.
  • Remove ex-employee, contractor and unused accounts immediately.
  • Review shared drives, shared inboxes and public links regularly.

Secure Devices And Cloud Tools

  • Enable device encryption, screen locks and remote wipe where possible.
  • Avoid local downloads of sensitive data unless there's a clear need.
  • If staff use personal phones or laptops, set clear rules for BYOD mobiles.
  • Check whether tools like Google Workspace or Drive are configured appropriately. Our explainer on when Google Drive is GDPR-compliant covers key cloud storage points.

Train Your Team In Short Bursts

  • Run practical training on phishing, mis-sent emails, secure sharing, passwords and breach reporting.
  • Make it easy for staff to report mistakes quickly without fear of blame.
  • Use realistic scenarios, such as a spreadsheet sent to the wrong customer or a suspicious payroll email.

If you want a broader view of your legal and compliance gaps, a Legal Health Check can help you spot areas to review.

Managing Suppliers, Cloud Tools And NHS-Style Supply Chain Risk

Many data leaks start outside the business that customers recognise. If a third party processes personal data for you, you need both due diligence and a contract that makes breach response workable in real time.

What To Check Before Using A Supplier

  • What personal data the supplier will access, store or transmit.
  • Whether the supplier uses MFA, encryption, secure development and vulnerability management.
  • Where data is stored and whether any sub-processors are involved.
  • Whether the supplier has credible security certifications or audit reports, such as ISO 27001.
  • How quickly the supplier will tell you about suspected or confirmed breaches.

Contract Terms That Matter In A Breach

  • A compliant Data Processing Agreement for processor relationships.
  • A clear breach notification timeframe, such as immediate notice or notice within a short stated number of hours after awareness.
  • Obligations to help you investigate, notify the ICO, communicate with individuals and respond to rights requests.
  • Limits on sub-processors and clear rules for international transfers.
  • Deletion or return of personal data when the contract ends.

Where you share data with another controller, a Data Sharing Agreement can clarify each party's role, responsibilities and communications. If tools, contractors or support teams are outside the UK, you may also need an appropriate transfer safeguard, such as the UK IDTA or EU SCCs with the UK addendum, plus a transfer risk assessment. This often comes up when engaging overseas contractors or using global SaaS platforms.

Your website tools can also create risk. Analytics, advertising pixels, chat widgets and webforms may collect personal data, so your Cookie Policy and consent banner should match what is actually in use. If a breach triggers more customer queries, make sure your team knows how to recognise and escalate a Subject Access Request.

Key Takeaways

  • An NHS data leak is a useful reminder that any SME holding customer, staff or supplier data needs a practical breach response process.
  • Not every incident is reportable, but if a breach is likely to risk people's rights and freedoms, the ICO must be notified without undue delay and, where feasible, within 72 hours.
  • If the risk to affected people is high, you usually need to tell them without undue delay in clear, practical language.
  • Controllers must record all personal data breaches, including those that aren't reported to the ICO.
  • Strong access controls, MFA, data minimisation, retention rules, staff training and supplier contracts reduce both the chance and impact of a data leak.
  • The Data (Use and Access) Act 2025 doesn't replace UK GDPR, but it does mean businesses should keep complaint-handling and subject access request processes up to date.

If you'd like help with reviewing data protection compliance, preparing a breach response plan, tightening supplier contracts or updating privacy documents, you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.

Get your customer-facing terms right

What should your privacy and online terms cover?

If you collect customer data, sell online or run marketing campaigns, your public terms and privacy documents should match the real customer journey.

Alex Solo

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.

Get your customer-facing terms right

Get in touch with our team

Tell us what you need and we'll come back with a fixed-fee quote - no obligation, no surprises.

Need support?

Need help with your business legals?

Speak with Sprintlaw to get practical legal support and fixed-fee options tailored to your business.