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.
Running a small business usually means you’re juggling a lot: customers, sales, suppliers, staff, and growth plans.
But sooner or later, a privacy issue pops up - a customer asks what you do with their data, a staff member requests access to their records, or you realise your team is using personal devices for work.
The tricky part is that privacy problems aren’t always caused by “bad actors”. Most privacy issues come from everyday processes that haven’t been tightened up yet - especially when you’re moving fast.
Below, we’ll break down the most common privacy issues for UK businesses, what UK GDPR and the Data Protection Act 2018 expect from you, and the practical steps you can take to stay compliant (without grinding your operations to a halt).
What Counts As A Privacy Issue For A Small Business?
A privacy issue is any situation where personal data is handled in a way that is:
- Unlawful (for example, you don’t have a valid reason to collect or use it)
- Unfair or non-transparent (people aren’t properly told what’s happening with their data)
- Insecure (data is exposed, lost, accessed by the wrong person, or leaked)
- Excessive (you collect more than you need, keep it too long, or share it too widely)
For UK businesses, the main legal framework is the UK GDPR (as incorporated into UK law) and the Data Protection Act 2018.
Importantly, “personal data” isn’t just names and email addresses. It can include:
- Phone numbers, delivery addresses, and order history
- Online identifiers (like customer IDs, device IDs, IP addresses in some contexts)
- CCTV footage where individuals can be identified
- HR records, sickness information, disciplinary notes, and payroll data
- Customer service call recordings (even if the call is “just about an order”)
Once you spot that you’re dealing with personal data, it’s easier to see where privacy issues can arise - and how to prevent them.
The Most Common Privacy Issues We See In UK Businesses
Privacy compliance can feel abstract until you connect it to real business habits. Here are some of the most common privacy issues for small businesses (including online businesses, service providers, retail, and growing teams).
1) Collecting Data Without Being Clear About Why
If you collect personal data (even through a simple enquiry form), you need to explain what you’ll do with it. That’s where a properly written Privacy Policy becomes essential.
Common examples include:
- Collecting phone numbers “just in case”
- Adding people to a marketing list after they enquire (without a clear opt-in strategy under the UK GDPR and PECR rules)
- Using customer data for new purposes that weren’t explained at the point of collection
A good rule of thumb: if a customer would be surprised by how you use their data, you probably need to revisit your transparency and consent approach.
2) Poor Access Control (Too Many People Can See Too Much)
Many data leaks aren’t hackers - they’re internal access issues.
For example:
- A shared inbox where everyone can see sensitive customer disputes
- A spreadsheet shared with contractors containing customer details
- Former staff members still having access to systems after leaving
UK GDPR expects you to take appropriate technical and organisational measures to keep personal data secure. “Appropriate” depends on your business size and the sensitivity of the data - but access control is almost always a baseline expectation.
3) CCTV, Audio, And Monitoring Without Proper Rules
Workplace monitoring is a common area where a privacy issue can develop quickly, because it feels operational (“we’re just protecting the business”), but it’s also personal data processing.
Typical examples include:
- Using CCTV in a shop, warehouse, or office without clear signage and a clear purpose
- Monitoring staff activity or usage in ways that aren’t transparent
- Recording calls or meetings without thinking through privacy requirements
If you use cameras at work, you’ll want to be particularly careful about signage, data storage, retention periods, who can access footage, and when it can be reviewed - Are Cameras Legal In The Workplace is a good starting point for understanding the practical risks.
And if your business records calls (for training, quality, or dispute resolution), you should make sure you’ve thought through your lawful basis, notice to callers, and how recordings are stored - recording conversations can be lawful, but it’s not something to do casually.
4) Supplier And Outsourced Service Risks (Your Vendors Can Create Your Privacy Issue)
Lots of small businesses outsource parts of their operations - payroll, HR platforms, email marketing tools, customer support systems, website hosting, and analytics.
If a supplier processes personal data on your behalf, you may need a contract that properly governs that processing, including security obligations and how breaches are handled. This is where a Data Processing Agreement is often the right fit.
This is a common blind spot: you might do everything right internally, but still face a privacy issue because a vendor isn’t compliant or has weak security.
5) “Bring Your Own Device” (BYOD) Chaos
When your team uses personal phones and laptops for work, privacy issues can arise around:
- Work emails sitting on personal devices
- Customer files saved to personal cloud storage
- Unclear boundaries when an employee leaves (what data must be deleted or returned?)
- Security issues if a phone is lost or stolen
Even with a small team, it’s worth setting clear expectations early - work phones vs BYOD mobiles is a common “hidden” privacy risk for growing businesses.
How To Stay GDPR Compliant Without Overcomplicating Your Business
GDPR compliance doesn’t need to be a 200-page manual that no one reads. The goal is to build privacy into your daily operations in a way that’s realistic for a small business.
Here are practical steps that usually make the biggest difference.
1) Map What Personal Data You Actually Hold
Before you can fix a privacy issue, you need visibility.
Create a simple data map covering:
- What personal data you collect (customers, leads, staff, suppliers)
- Where you collect it (website forms, email, phone calls, bookings, in-store)
- Where it’s stored (CRM, spreadsheets, email inboxes, accounting software)
- Who has access (owners, admin staff, contractors, agencies)
- Who you share it with (delivery partners, payroll provider, marketing tools)
- How long you keep it and why
This gives you a clear action list - for example, you might discover you’re keeping old enquiry spreadsheets for years without a reason.
2) Make Sure You Have A Lawful Basis For What You Do
Under UK GDPR, you generally need a lawful basis to process personal data. For small businesses, common lawful bases include:
- Contract (you need the data to supply the product/service)
- Legal obligation (for example, certain records you must keep)
- Legitimate interests (where your business interest is balanced against the individual’s privacy rights)
- Consent (common in marketing and some cookies/online tracking, but must be freely given, specific, informed, and withdrawable)
If you’re relying on consent, make sure you can prove it, and make it easy for people to opt out.
3) Put The Right Documents And Notices In Place
Most privacy issues get worse when your paperwork (or website disclosures) don’t match reality.
At a minimum, many small businesses need:
- A clear Privacy Policy that matches how you really collect/use/store data
- Website cookie disclosures where relevant (especially if you use tracking/analytics) and, in many cases, a consent mechanism aligned with PECR
- Supplier/processor terms or a Data Processing Agreement where vendors process personal data for you
And if you have staff using company systems, a clear Acceptable Use Policy can help set boundaries around devices, logins, sharing, downloads, and security expectations.
These documents don’t just “tick a box”. They create a paper trail that you’ve taken privacy seriously, which matters if a dispute or complaint arises.
4) Build A Simple Security Checklist (And Actually Use It)
Security doesn’t have to be complicated, but it does need to be consistent.
A practical baseline checklist might include:
- Unique logins for staff (avoid shared passwords where possible)
- Multi-factor authentication on email and key systems
- Role-based access (staff only access what they need)
- Encryption on laptops and mobile devices
- A process for removing access when someone leaves
- Secure disposal of old devices and paper records
If you want a quick “stress test”, ask: if a laptop was stolen today, what personal data would be exposed? Your answer will usually tell you where the biggest risk is.
5) Set Sensible Retention Periods (And Don’t Keep Data “Just In Case”)
Holding personal data indefinitely is a very common privacy issue.
UK GDPR expects you to keep data only for as long as you need it for the purpose you collected it for. That usually means you need a retention approach for things like:
- Old customer enquiries that didn’t convert
- Past customers who haven’t bought in years
- Unsuccessful job applications
- Former employee records
- CCTV footage
Retention is also about reducing risk: the less you keep, the less can be exposed if something goes wrong.
Staff, Monitoring, And Workplace Privacy: Avoiding The “Accidental” Privacy Issue
As soon as you employ staff (even a small team), privacy compliance expands beyond customer data.
Employment-related privacy issues often arise because businesses rely on informal practices - for example, managers keeping personal notes, or accessing staff data without a defined process.
Monitoring Emails, Browsing, And Systems
It may be lawful in some circumstances to monitor workplace systems, but you need to do it carefully and transparently - and in higher-risk cases, you may need to carry out a Data Protection Impact Assessment (DPIA) to check necessity and proportionality.
From a risk perspective, problems often come from:
- Monitoring without notifying staff (or without a clear policy)
- Monitoring more than is necessary for your stated purpose
- Looking at content that is sensitive or irrelevant to the issue at hand
If your business is considering monitoring staff browsing history, this is exactly the kind of area where a privacy issue can arise if you don’t set clear rules and communicate them - monitor your internet search history at work is a common question, and the answer is usually “it depends” on your purpose, necessity, proportionality, and transparency.
Train Your Team On The “Everyday” Privacy Triggers
You don’t need your staff to become privacy experts. You do need them to recognise common risk moments, such as:
- Forwarding customer emails to personal accounts
- Discussing customer information in public places or shared channels
- Sharing screenshots that contain names, addresses, or payment details
- Downloading customer lists onto personal devices
- Leaving printed documents visible at the front desk
A short privacy training session (and a refresher every so often) can prevent a large percentage of day-to-day privacy issues.
What To Do If A Privacy Issue Happens (Your Practical Response Plan)
Even with good systems, privacy issues can still happen. The key is to respond quickly, document what happened, and reduce the risk of harm.
Step 1: Contain The Issue
- Stop the unauthorised access/sharing
- Recover data if possible (for example, recall an email, disable a link)
- Secure affected accounts (password resets, revoke access, enable MFA)
Step 2: Assess What Happened And The Risk
Get clear on the facts:
- What personal data was involved?
- How many people are affected?
- Is it sensitive data (health, ID documents, financial details)?
- Was it actually accessed, or just exposed?
- What harm could realistically occur (fraud, identity theft, distress)?
Step 3: Decide Whether You Need To Report It
Not every incident is reportable, but some are.
Depending on the circumstances, you may need to consider reporting to the Information Commissioner’s Office (ICO) and/or notifying affected individuals, especially where there’s a risk to people’s rights and freedoms. Where an incident is notifiable to the ICO, the general rule is you must report it without undue delay and, where feasible, within 72 hours of becoming aware.
This is one of those moments where tailored legal advice is genuinely helpful - because reporting decisions are very fact-specific, and timing can matter.
Step 4: Fix The Root Cause
Once things are under control, focus on prevention. That could mean:
- Updating policies and training
- Changing how you share documents
- Restricting access levels
- Replacing spreadsheets with a proper system
- Reviewing supplier security and contracts
A privacy issue that is handled well can actually strengthen your business. It’s a chance to tighten your processes and show customers you take trust seriously.
Key Takeaways
- A privacy issue isn’t just a data breach - it can be any unfair, insecure, excessive, or non-transparent use of personal data in your business.
- Common privacy issues for small businesses include unclear data collection practices, weak access controls, risky supplier arrangements, and informal staff handling of personal data.
- Staying GDPR compliant usually starts with mapping your data, confirming your lawful basis, and putting clear documents in place like a Privacy Policy and (where needed) a Data Processing Agreement.
- Marketing and cookies can have extra rules (including under PECR), so make sure your opt-ins, consent tools, and notices match what you actually do.
- Workplace monitoring, CCTV, and call recordings can create privacy issues quickly if you’re not transparent, necessary, and proportionate, so set rules early and document your approach (and consider a DPIA where appropriate).
- Have a practical response plan so if a privacy issue happens, you can contain it, assess risk, decide on any reporting steps (including the 72-hour ICO deadline where applicable), and prevent repeats.
If you’d like help tightening up your privacy compliance, reducing the risk of a privacy issue, or putting the right policies and contracts in place, you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.
Business legal next step
When should you formalise this?
If you collect customer data, sell online or run marketing campaigns, your public terms and privacy documents should match the real customer journey.








