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.
- What Counts As A “Violation Of Privacy” Under UK Law?
Common Business Scenarios That Risk A Privacy Violation
- 1) Collecting Too Much Data, Or Without A Lawful Basis
- 2) Email Marketing Without Proper Consent (Or Soft Opt-In Misuse)
- 3) Cookie Banners That Don’t Offer Real Choice
- 4) Insecure Systems, Shared Logins, Or Unvetted Cloud Tools
- 5) CCTV And Audio Recording In Customer Or Staff Areas
- 6) Publishing Private Messages Or Photos Without Permission
- 7) Overbroad Workplace Monitoring
- Employment And Workplace Monitoring: Stay On The Right Side Of The Line
- Key Takeaways
Privacy mistakes aren’t just “big tech” problems. For small businesses, a violation of privacy can happen surprisingly easily - a poorly worded email, an overzealous CCTV setup, an unchecked marketing list, or a rushed new system that isn’t secured.
The good news? With some sensible processes and the right documents in place, you can reduce your risk dramatically and handle issues confidently if they arise.
In this guide, we’ll explain what a “violation of privacy” looks like under UK law, the common traps for small businesses, steps to prevent problems, and what to do if you receive a complaint or suffer a data breach.
What Counts As A “Violation Of Privacy” Under UK Law?
“Privacy” covers a few different legal concepts in the UK. As a business, the main areas to understand are:
- UK GDPR and the Data Protection Act 2018 (DPA 2018): These govern how you collect, use, store and share personal data. A violation might be processing data without a lawful basis, failing to keep it secure, or not respecting people’s rights (like access or deletion).
- PECR (Privacy and Electronic Communications Regulations): These sit alongside data protection law and cover marketing calls, emails and texts, use of cookies/trackers, and similar technologies.
- Misuse of private information and breach of confidence: Separate from data protection, this is a civil wrong (tort) where someone’s private information is used or disclosed without lawful justification, or confidential information is misused.
- Employment and monitoring rules: Employers must comply with data protection principles when monitoring staff. Covert or excessive monitoring can amount to a violation, and you’ll need a clear, communicated policy and a lawful basis.
- Surveillance and audio recording: CCTV and audio capture can be lawful, but there are strict rules around transparency, necessity, and proportionality.
The regulator is the Information Commissioner’s Office (ICO). They can investigate serious infringements and issue significant fines. Individuals can also bring claims for damages (including distress), so the risk isn’t just regulatory - it can be reputational and financial, too.
Common Business Scenarios That Risk A Privacy Violation
Most violations aren’t deliberate - they come from everyday activities that aren’t fully aligned with the rules. Watch out for these common scenarios:
1) Collecting Too Much Data, Or Without A Lawful Basis
If you collect personal data “just in case,” you may breach the minimisation principle. You must have a clear lawful basis (such as contract, consent, legitimate interests, or legal obligation) for each purpose. If you can’t explain why you need the data, you probably shouldn’t collect it.
2) Email Marketing Without Proper Consent (Or Soft Opt-In Misuse)
Sending promotional emails or texts without valid consent under PECR, or relying on the “soft opt-in” when it doesn’t apply, is a classic compliance slip. Ensure your lists are clean, your opt-ins are recorded, and you include clear unsubscribe links in every message. Review your approach to email marketing regularly, especially if you change CRMs or sign-up flows.
3) Cookie Banners That Don’t Offer Real Choice
Analytics, advertising, and social media pixels usually require consent before setting. If your banner nudges people to “accept all” but makes it difficult to reject non-essential cookies, that’s risky. You’ll also need a clear, accessible Cookie Policy that reflects what you actually do.
4) Insecure Systems, Shared Logins, Or Unvetted Cloud Tools
Data security is core to UK GDPR. Using shared passwords, failing to set access controls, or moving customer data into a new tool without due diligence can lead to breaches. If you use cloud storage, check the provider’s security, location of data, and sharing settings - for example, think carefully about how you use Google Drive across your team.
5) CCTV And Audio Recording In Customer Or Staff Areas
Surveillance can be lawful, but only where necessary, proportionate and properly signposted. Audio recording is particularly intrusive and requires heightened justification and transparency. Before you install or switch on any audio functionality, understand the rules for CCTV with audio and how they apply in your setting.
6) Publishing Private Messages Or Photos Without Permission
Using customer messages or staff chats as promotional content without consent can infringe privacy rights. Even if you “anonymise” screenshots, they can still be linked back to an individual. Always get permission for testimonials, photos and case studies - and keep a record of that consent.
7) Overbroad Workplace Monitoring
Tracking keystrokes, recording audio, or continuously monitoring screens is rarely justifiable. Even viewing browser histories raises issues: necessity, transparency, and least-intrusive methods are key. Make sure any monitoring is explained in policy, targeted to a legitimate aim, and supported by a DPIA (data protection impact assessment) where appropriate.
How To Prevent A Privacy Violation In Your Business
Prevention is far easier (and cheaper) than cure. Here’s a practical, small-business-friendly approach that gets you most of the way there.
1) Map Your Data And Purposes
List what personal data you collect, where it comes from, what you use it for, where it’s stored, who has access, and who you share it with (including any third-party tools). This simple “data map” helps you identify gaps and decide your lawful bases.
2) Choose (And Document) Lawful Bases
For each purpose, select the lawful basis that fits (for example, “contract” for order fulfilment, “legitimate interests” for some B2B operations, or “consent” for non-essential cookies and most direct marketing). Record your reasoning - this is key for accountability if you’re ever challenged.
3) Publish A Clear Privacy Notice
Tell people how you use their data in plain English. Include your purposes, lawful bases, retention periods, rights, and how to contact you. Make it accessible wherever you collect data (sign-up pages, checkout, contact forms). A well-drafted Privacy Policy is essential.
4) Get Cookies And Marketing Right
- Block non-essential cookies until the user consents (and let them say no as easily as yes).
- Make sure your cookie banner reflects your actual tracking set-up and your Cookie Policy matches reality.
- For marketing emails/texts, comply with PECR consent rules or the narrow soft opt-in. Keep opt-in records and respect opt-outs immediately.
5) Lock Down Security Basics
- Enforce strong passwords and multi-factor authentication (MFA) for staff accounts.
- Limit access to “need-to-know” and remove access promptly when roles change.
- Vet new tools (especially those storing customer data) and sign data processing terms before you upload anything.
- Train staff on phishing, safe sharing, and how to handle personal data.
6) Implement A Breach And Complaint Response Plan
Have a short, simple playbook that explains how staff should report issues, who leads the response, and the steps you’ll take (investigate, contain, assess risk, notify where required, learn lessons). Practising this once will save hours in a real incident.
7) Keep Documentation And Stay Proportionate
Document decisions, especially where you rely on legitimate interests or do monitoring. If an approach feels intrusive, ask: is there a less-intrusive way to achieve the same result? That question alone prevents many violations.
Handling A Privacy Complaint Or Breach The Right Way
Even with good controls, things happen. Acting quickly and transparently can turn a potential crisis into a manageable issue.
Step 1: Acknowledge And Log
If you receive a complaint, acknowledge it promptly. Log the details and set a response timeframe. If it’s a suspected breach, trigger your internal incident plan immediately.
Step 2: Understand The Issue
Identify the data involved, how it was processed or disclosed, how many people are affected, and the potential harm (financial, identity, distress). For incidents, contain the issue (e.g., revoke access, reset passwords, take down the data).
Step 3: Assess Legal Duties
- UK GDPR breach notification: If the breach is likely to pose a risk to individuals’ rights and freedoms, you must notify the ICO within 72 hours of becoming aware. If the risk is high, you’ll usually need to inform the individuals too.
- PECR implications: Some telecoms and cookie-related incidents can involve PECR as well as UK GDPR; factor this into your assessment.
- Contractual obligations: Check any data processing terms with clients - you may have to notify them quickly.
Step 4: Respond To Requests And Complaints Professionally
Individuals might ask for access to their data, or for you to stop certain processing. Make sure you can recognise and route a Subject Access Request (SAR) quickly. If you made a mistake, be open about what happened, what you’ve done to fix it, and how you’ll prevent a repeat.
Step 5: Learn And Improve
Privacy incidents are often caused by a process gap. Update your training, tighten access, patch your policy, or change tools if needed. Document what you changed - that record helps demonstrate accountability if the ICO ever asks.
Employment And Workplace Monitoring: Stay On The Right Side Of The Line
Employers handle large volumes of staff data, and monitoring is a hot-button area. To avoid a privacy violation:
- Be clear and transparent in your staff policies about what you monitor and why.
- Use the least-intrusive method that achieves your aim, and avoid continuous or blanket monitoring unless you have a compelling justification.
- Do a DPIA for higher-risk activities, such as audio capture, biometrics, or location tracking.
- Put up notices for CCTV and avoid microphones unless you can genuinely justify them (and even then, limit when and where they’re active).
- Restrict access to monitoring data and set strict retention periods.
If you’re considering more advanced tools (for example, face recognition or voice analytics), the bar for necessity and proportionality is much higher. In many cases, less-intrusive alternatives will be safer and just as effective.
Key Documents And Contracts To Put In Place
Good paperwork won’t magically solve privacy, but it sets expectations, creates accountability, and often prevents breaches in the first place. Prioritise the following:
- Privacy Notice/Policy: Explain your purposes, lawful bases, rights, and how people can contact you. Link it wherever you collect data. A tailored Privacy Policy helps you meet transparency duties.
- Data Processing Terms: If a supplier processes personal data for you (hosting, CRM, email tools, IT support), you must have appropriate written terms in place. Use a robust Data Processing Agreement and ensure it reflects the real processing and security measures.
- Cookies And Tracking: Keep your Cookie Policy up-to-date and ensure your consent banner aligns with what you actually set.
- Internal Policies: Staff-facing rules covering acceptable use, BYOD, data handling, access control, and incident response. These reduce human error (the biggest cause of breaches).
- Marketing Records: Maintain clear audit trails of consent and opt-outs, and document your soft opt-in assessments for each list.
- Third-Party Reviews: Keep due diligence notes on cloud providers and tools (locations, sub-processors, security features). Avoid uploading data into tools until contracts are signed and settings are configured.
Practical Tips For Rolling This Out
- Start with your highest-risk processes (payments, customer accounts, surveillance, staff monitoring).
- Assign one owner for data protection - even in a small team, someone needs to steer the ship.
- Train staff once a year (and on induction). Short, practical sessions beat one long lecture.
- Schedule a quick annual policy and vendor review - privacy compliance isn’t “set and forget.”
Key Takeaways
- “Violation of privacy” in the UK can mean a breach of UK GDPR/DPA 2018, PECR marketing and cookie rules, or misuse of private/confidential information - the consequences can be regulatory, legal and reputational.
- Most issues arise from everyday operations: excessive data collection, sloppy security, non-compliant cookie banners, marketing without valid consent, or overly intrusive monitoring.
- Prevention starts with a data map, clear lawful bases, and strong transparency. A well-drafted Privacy Policy, correct cookie consent, and good staff training go a long way.
- Get your vendor contracts in order with a proper Data Processing Agreement before uploading any personal data to third-party tools or platforms.
- Have a simple plan for complaints and incidents. Recognise a Subject Access Request, assess data breaches quickly, and notify the ICO/individuals when required.
- Marketing and cookies deserve special attention: follow PECR, maintain accurate consent records, and keep your Cookie Policy and banner aligned with your actual tracking setup.
- Think carefully before deploying surveillance or monitoring. If you can achieve your aim with a less-intrusive method, do that - especially with audio capture and biometrics. Review risks like CCTV with audio and how you use cloud tools such as Google Drive.
If you’d like tailored help setting up your privacy framework, policies and contracts - or support responding to a complaint or breach - we’re here to help. You can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.


