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.
If your business touches customer data (and most do), UK privacy law applies to you. The good news? You don’t need to be a tech giant to get it right. With a clear plan and the right templates, you can build trust, avoid fines and keep things running smoothly.
Below, we break down the core privacy laws in the UK, what they mean for small businesses, and the practical steps you can take to stay compliant from day one.
- What Are Privacy Laws In The UK?
- Does UK Data Protection Law Apply To Your Small Business?
- What's Changed In UK Privacy Law?
- What Should Your Privacy Notice And Lawful Basis Cover?
- What Are The UK Rules For Email Marketing, SMS And Cookies?
- How Do You Handle DSARs, Breaches, Vendors And ICO Fees?
- Worked Example: Online Retailer Marketing And DSAR
- Key Takeaways
What Are Privacy Laws In The UK?
The main UK privacy regimes for businesses are:
- UK GDPR: the main framework for collecting, using, storing and sharing personal data. It covers lawful bases, transparency, security, data rights, records, processors and international transfers.
- Data Protection Act 2018: the UK legislation that sits alongside UK GDPR and deals with UK specific rules, enforcement powers, special categories of data and criminal offence data.
- Privacy and Electronic Communications Regulations: usually called PECR. These rules cover electronic marketing, cookies, similar tracking technologies and some communications services.
- Data (Use and Access) Act 2025: this Act received Royal Assent on 19 June 2025. It amends the UK GDPR, Data Protection Act 2018 and PECR rather than replacing them.
Personal data means information relating to an identified or identifiable person. For businesses, that can include names, addresses, dates of birth, National Insurance numbers, driving licence numbers, bank details, health information, CVs, IP addresses, account details, purchase history, messages, photographs, call recordings and CCTV footage.
Some data needs extra care. Special category data includes information about race, ethnic background, political opinions, religious beliefs, trade union membership, genetics, biometrics used for identification, health, sex life and sexual orientation. Criminal conviction and offence data has separate safeguards too.
The practical principles are simple to state, but important to embed: use personal data fairly, lawfully and transparently; use it for clear and legitimate purposes; collect only what you need; keep it accurate; delete it when it's no longer needed; and protect it with appropriate security.
Does UK Data Protection Law Apply To Your Small Business?
In most cases, yes. UK data protection law applies if your business handles personal data about customers, business contacts, staff, job applicants, website users, suppliers or prospects. It can apply to sole traders, startups, micro businesses, ecommerce brands, agencies, consultants, clinics, SaaS companies, hospitality businesses and employers.
A useful first question is whether you're acting as a controller, processor or joint controller:
- Controller: you decide why and how personal data is used. Most businesses are controllers for customer, staff and marketing data.
- Processor: you process personal data on another organisation's instructions. For example, you might provide outsourced payroll, fulfilment, cloud software or marketing services.
- Joint controller: you and another organisation jointly decide key purposes and means of processing. This needs clear written allocation of responsibilities.
Your role affects what contracts, notices and records you need. If you use suppliers such as hosting providers, CRMs, payment processors, email platforms or outsourced HR tools, you should check whether they process personal data for you. If they do, you'll usually need a compliant Data Processing Agreement.
What's Changed In UK Privacy Law?
The biggest recent UK privacy law development is the Data (Use and Access) Act 2025. It doesn't scrap UK GDPR. Instead, it adjusts parts of the UK data protection framework and PECR. For most small businesses, the core compliance job remains the same, but there are some practical changes worth building into your processes as they apply.
- Subject access searches: the Act clarifies that searches for personal data should be reasonable and proportionate. You still need a genuine, organised search, but you aren't expected to take limitless steps.
- Stop the clock for DSARs: where you reasonably need more information to respond to a data subject access request, the time limit can pause while you wait for that information.
- Complaints handling: organisations need a way to handle data protection complaints, including facilitating electronic complaints and telling individuals the outcome.
- PECR updates: PECR remains important for electronic marketing and cookies, and the Act makes targeted amendments rather than removing the consent based framework.
The regulator is the Information Commission, with the organisation commonly known as the Information Commission's Office or ICO. The ICO can investigate, require changes and issue monetary penalties. For serious UK GDPR breaches, the maximum penalty can be the higher of GBP 17.5 million or 4% of annual worldwide turnover, although most small business enforcement is much more focused on fixing poor practices before they cause serious harm.
What Should Your Privacy Notice And Lawful Basis Cover?
You need a lawful basis for each reason you use personal data. The common bases for businesses are contract, legal obligation, legitimate interests and consent. Consent isn't always the best choice under UK GDPR, because it must be freely given, specific, informed and easy to withdraw. For ordinary customer service or order fulfilment, contract is often more appropriate. For some business administration and lower risk B2B activity, legitimate interests may fit if you have balanced your interests against the person's rights.
PECR is different. Even if you have a UK GDPR lawful basis, marketing emails, SMS and cookies may still need consent or another PECR compliant route.
Your Privacy Policy or privacy notice should be written in plain English and kept up to date. It should usually include:
- Who You Are: your business name, contact details and any relevant data protection contact.
- What You Collect: the categories of personal data you collect from customers, staff, suppliers, users or leads.
- How You Collect It: for example, forms, checkout pages, emails, calls, website tracking, integrations or third parties.
- Why You Use It: the business purposes, such as orders, accounts, support, recruitment, marketing, safety or analytics.
- Your Lawful Basis: the UK GDPR basis for each purpose and any extra condition for special category data.
- Who You Share It With: suppliers, platforms, professional advisers, payment providers, group companies or regulators where relevant.
- International Transfers: whether data leaves the UK and what transfer mechanism you use.
- How Long You Keep It: your retention periods or the criteria you use to decide them.
- People's Rights: access, rectification, erasure, restriction, objection, portability and complaints.
- How To Contact You: a clear route for privacy requests and complaints.
What Are The UK Rules For Email Marketing, SMS And Cookies?
Marketing is where UK privacy laws catch many small businesses. You need to think about both UK GDPR and PECR.
For business to consumer email and SMS marketing, PECR generally requires prior consent unless the soft opt in applies. The soft opt in can apply where you obtained someone's details during a sale or negotiation for a sale, you're marketing your own similar products or services, and you gave a clear opt out when you collected the details and in every later message. If you're relying on it, your forms, CRM fields and unsubscribe process should prove each requirement is met. You can read more on soft opt-in if you're checking your mailing lists.
For B2B marketing, the rules can be more flexible, especially for corporate subscribers, but you still need a UK GDPR lawful basis, you should be transparent, and every message should include a simple unsubscribe. Sole traders and some partnerships are treated more like individual subscribers, so don't assume every business email address is fair game.
Service messages are different from marketing. A password reset, delivery update or change to essential service terms is usually not marketing. A discount code, cross sell or product launch is marketing, even if it's added to an otherwise operational email.
Cookies and similar technologies also fall under PECR. Strictly necessary cookies can usually be set without consent. Non essential cookies, such as advertising, remarketing and many personalisation tools, generally need prior consent, while some analytics may be used without consent if a PECR exception applies. Consent should be informed, freely given and specific, with no pre ticked boxes or implied acceptance. Users should be able to reject non essential cookies as easily as they accept them and change preferences later.
In practice, you should categorise your cookies, configure scripts so they don't fire before consent where consent is needed, use a balanced banner, and keep your Cookie Policy consistent with your actual site. If you're reviewing the design of your banner, these practical notes on compliant cookie banners can help.
How Do You Handle DSARs, Breaches, Vendors And ICO Fees?
A data subject access request, often called a DSAR, is a request from an individual for a copy of their personal data and related information about how it's used. You generally have one month to respond and usually can't charge a fee. Under the 2025 changes, if you reasonably need more information to identify the request or locate the data, the clock can pause while you wait for that information.
A workable DSAR process should include one inbox, one owner, an identity check, a search plan, redaction steps, approval before release and a clear response record. Your team should also know that a DSAR doesn't need to use formal legal wording. A message saying "I want all the information you hold about me" can be enough.
You also need a breach process. A personal data breach can mean accidental deletion, unauthorised access, ransomware, a lost laptop, an email sent to the wrong person, or a misconfigured database. If a breach is likely to risk people's rights and freedoms, you may need to notify the ICO within 72 hours of becoming aware of it. If the risk is high, affected individuals may also need to be told. A written Data Breach Response Plan helps your team contain the incident, preserve evidence, assess risk and meet deadlines.
Check each supplier contract for processor terms, security obligations, sub processor controls, breach support, audit rights, deletion or return of data, and where the data is stored. If data leaves the UK, you need an appropriate transfer mechanism and a transfer risk assessment where required.
Most UK businesses must register with the ICO and pay an annual data protection fee unless exempt. You may be exempt if you only use personal data for staff administration, advertising, marketing, public relations, accounts or record keeping. You're more likely to need to register if you use CCTV for crime prevention or use personal data in areas such as health, childcare, legal or financial services. Use the ICO fee checker and keep a record of your conclusion.
Worked Example: Online Retailer Marketing And DSAR
Imagine a hypothetical online retailer selling homeware across the UK. It has customer accounts, newsletter subscribers, staff records, analytics, a payment processor, an email marketing platform and a warehouse fulfilment partner.
First, it maps its data. Customer names, delivery addresses, email addresses and purchase histories are used to fulfil orders, so the main lawful basis is contract. Accounting records are kept for legal obligations. Newsletter emails rely on consent for website sign ups, and soft opt in for customers who bought similar products and were given an opt out at checkout. Analytics cookies are held back until the user clicks accept, because the retailer is not relying on a PECR analytics exception.
Next, it cleans up its forms. The checkout has one unticked marketing box for new consent and a separate line explaining service emails. Every campaign includes an unsubscribe link. The cookie banner has accept all and reject all buttons with equal prominence. The Cookie Policy names the categories actually used on the site.
Then a former customer sends an email saying "Please send me all personal data you hold about me." The retailer verifies the customer's identity, logs the one month deadline, searches the ecommerce platform, email tool, support inbox and fulfilment records, redacts third party personal data where needed, and responds with the data, purposes, recipients, retention information and rights details.
A month later, the retailer discovers that order confirmation emails were accidentally sent with the wrong first name in the greeting, but no address, payment data or account access details. The team follows its breach plan, records what happened, assesses the risk, fixes the mail merge field and decides whether ICO notification is required. That gives the retailer control.
Key Takeaways
- UK business privacy laws are mainly the UK GDPR, the Data Protection Act 2018 and PECR, with targeted changes from the Data (Use and Access) Act 2025.
- Most businesses that handle customer, staff, supplier, website or marketing data need a lawful basis, clear privacy information, security controls and a rights request process.
- Email, SMS and cookies need special attention because PECR can require consent even where UK GDPR has a separate lawful basis.
- DSARs usually need a response within one month, and your searches should be reasonable and proportionate with a stop the clock process where clarification is needed.
- Supplier contracts, international transfers, retention periods, ICO fee checks and breach response plans are practical compliance essentials, not admin extras.
- A tailored Privacy Policy, Data Processing Agreement and Data Breach Response Plan can make the rules much easier to operate day to day.
If you'd like help with privacy policies, data processing agreements, marketing consent or cookie compliance, 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.








