GDPR and Cookie Consent for UK Websites: What UK GDPR and PECR Expect From Your Site
GDPR and cookie consent for UK websites explained: how UK GDPR and PECR apply, what a compliant cookie banner looks like, and how to set it up properly.

Most UK websites have to follow two sets of rules: UK GDPR (with the Data Protection Act 2018) for personal data, and the Privacy and Electronic Communications Regulations (PECR) for cookies and similar tracking. In practice that means a clear privacy notice, forms that only collect what you need, and a cookie banner that stops non essential cookies loading until the visitor agrees. Rejecting should be as easy as accepting.
This is a practical guide from a web developer's point of view, covering what we check and build on client sites. It is not legal advice. The Information Commissioner's Office (ICO) is the regulator and its guidance is the reference point, so for anything specific to your business, read it or speak to a data protection professional.
Key takeaways
- UK GDPR covers personal data; PECR covers cookies and similar storage on a device.
- Non essential cookies, such as most advertising cookies, need consent before they are set.
- A banner that only says OK, or hides the reject option, does not give valid consent.
- The Data (Use and Access) Act 2025 changes some cookie rules, so check current ICO guidance.
- Your forms, plugins and third party scripts matter as much as the banner itself.
- Keep a written record of what your site collects and why.
Which rules apply to a typical UK business website
UK GDPR applies whenever you process personal data: names and emails from a contact form, customer accounts, order details, newsletter sign ups, and online identifiers such as IP addresses in some contexts. It sets out principles such as collecting only what you need, having a lawful basis, keeping data secure and telling people what you do with it.
PECR sits alongside it and covers storing or accessing information on a user's device. That includes cookies, but also local storage, tracking pixels and device fingerprinting. PECR also covers electronic marketing, which is why sending marketing emails to individuals generally needs consent (with a limited exception for existing customers).
Many businesses also need to pay the ICO data protection fee. The ICO has a short self assessment on its website to check if you need to pay.
What counts as a strictly necessary cookie
PECR allows cookies without consent where they are strictly necessary to provide a service the user has asked for. Typical examples on the sites we build:
- A WooCommerce session or basket cookie, so the basket remembers what was added.
- A login session cookie for a customer account or portal.
- Security cookies, such as those used for form protection or load balancing.
- The cookie that stores the visitor's consent choice itself.
Analytics, advertising, social media embeds, heatmaps and remarketing pixels have traditionally fallen outside that exemption, so they needed consent. That is the area where the law has recently changed, covered below.
The Data (Use and Access) Act 2025 and cookies
The Data (Use and Access) Act 2025 amends PECR and UK GDPR. Among other things, it introduces further exceptions to the cookie consent requirement for certain lower risk purposes, such as some forms of analytics used to improve a website, subject to conditions like giving clear information and an easy way to object. It also raises the maximum fines available under PECR to align them with UK GDPR.
We are being deliberately cautious here. The changes are being brought in in stages, the detail of the conditions matters, and the ICO is updating its guidance to reflect them. Do not remove your consent banner or start loading analytics without consent on the strength of a headline. Check the ICO website for its current cookie guidance, and treat advertising and cross site tracking as still needing consent unless that guidance clearly says otherwise.
What a compliant cookie banner looks like
The ICO's position on consent is that it must be freely given, specific, informed and an unambiguous positive action. On a website, that translates to a few concrete design rules:
- Non essential cookies do not load until the visitor clicks accept or switches a category on.
- There is a reject or reject all option at the same level as accept, not hidden behind a settings link.
- No pre ticked boxes for optional categories.
- Continuing to scroll or browse is not treated as consent.
- The banner explains in plain words what each category does and links to a cookie policy.
- Visitors can change their mind later, usually through a link in the footer.
A common mistake is a banner that looks right but does nothing. We regularly audit sites where the Google Analytics or Meta pixel fires on page load regardless of what the visitor chooses. The banner is decoration at that point. The test is simple: open the site in a private window, open developer tools, and check which cookies and network requests appear before you click anything.
Setting it up on a WordPress site
On WordPress, there are two parts to get right: the consent tool and the way scripts are loaded.
- Pick a consent management plugin or service that supports blocking scripts by category and records consent. Options vary in how much they auto detect; none of them are a substitute for knowing what your site loads.
- Inventory your scripts. List everything that sets cookies or calls third parties: analytics, Google Ads, Meta, embedded YouTube or Google Maps, chat widgets, review widgets, booking tools.
- Load tags through one route. If you use Google Tag Manager, set triggers based on consent state. If scripts are hard coded in the theme or added by plugins, wire each one to the consent tool.
- Configure Google Consent Mode if you use Google Analytics or Google Ads, so Google tags respect the visitor's choice. Google's documentation explains the settings.
- Replace embeds with click to load placeholders for YouTube and maps, so they only load third party content when someone wants it.
- Test in a private window with accept, reject and partial choices.
Plugins are also a data protection issue in their own right. Every plugin that stores form entries, logs IPs or phones home adds to your obligations. Our post on WordPress plugin security covers how to keep that list short and maintained.
Forms, privacy notices and the data you collect
Cookie banners get the attention, but UK GDPR problems on small business sites more often sit in forms and inboxes.
- Ask for less. A callback form rarely needs a date of birth or full address. Every extra field is data you then have to protect.
- Separate marketing consent. If you want to add enquirers to a newsletter, use an unticked checkbox with clear wording. Do not bundle it into submitting the form.
- Check where entries go. Form plugins often store every submission in the WordPress database forever, as well as emailing it. Set a retention period or turn storage off if email is enough.
- Write a real privacy notice. It should say who you are, what you collect, why, your lawful basis, who you share it with (hosting, email provider, CRM), how long you keep it and how people can exercise their rights.
Your contact page is a good place to start, because it is usually the main way personal data enters the business.
Third parties, hosting and transfers
Most websites send data to several other companies: the host, a transactional email service, a CRM, payment providers, analytics and marketing platforms. Under UK GDPR these are usually processors acting for you, and you need appropriate contracts with them (most large providers include data processing terms in their standard agreements).
If any of them store data outside the UK, international transfer rules apply. Many common services rely on recognised safeguards or UK adequacy arrangements, but you should know which ones you use and mention them in your privacy notice. Hosting in the UK keeps your own server side of the picture simple, which is one of the points we cover in our guide to UK web hosting.
Keeping it right after launch
Compliance drifts. Someone adds a chat widget, marketing installs a new pixel through Tag Manager, a plugin update starts loading Google Fonts from Google's servers. Six months later the cookie policy describes a different site.
A light routine works for most small businesses:
- Rescan the site for cookies and third party requests every quarter, and after any new marketing tool is added.
- Update the cookie policy and banner categories to match.
- Review form storage and delete old entries you no longer need.
- Check the ICO site for guidance updates, especially while the 2025 Act changes are being phased in.
This fits naturally into ongoing website maintenance, and it is cheaper to catch drift early than to rebuild trust after a complaint.
Frequently asked questions
Do I need a cookie banner if I only use Google Analytics?
Historically, yes, because analytics cookies were not strictly necessary. The Data (Use and Access) Act 2025 introduces exceptions for some analytics uses under conditions, so check the ICO's current guidance before changing anything. If you also run Google Ads or remarketing, consent is still expected.
Is UK GDPR the same as EU GDPR?
UK GDPR was based on the EU GDPR and is very similar, but it is a separate UK law and has been amended since, including by the Data (Use and Access) Act 2025. If you also target customers in the EU, the EU rules may apply to you as well.
Can my cookie banner have only an Accept button?
Not if it is used to set non essential cookies. The ICO expects visitors to be able to refuse as easily as they accept, so a reject option should sit alongside accept rather than being hidden in settings.
Does my small business website need a privacy policy?
If it collects any personal data, such as through a contact form, booking system or shop, you need to tell people how you use it, and a privacy notice on the site is the normal way to do that. It should reflect what your site and business really do, not a generic template.
What happens if my site is not compliant?
The ICO can investigate complaints and has a range of enforcement powers, including fines. For most small businesses the more immediate risk is a customer complaint or loss of trust, which is why fixing obvious issues such as scripts loading before consent is worth doing now.
Getting your site checked
We can audit what your website actually loads, set up a consent tool that works, tidy up forms and plugin storage, and make sure your pages match your practice. We are developers, not lawyers, so we will tell you where a question needs a specialist. Start with our website design service or contact us for a review of your current site.