← Back to Blog

UK Cookie Law Changed in 2026: What Your Website Needs Now

Illustration of a cookie with a bite taken out beside two switches, one on and one off

If your website has a cookie banner, this is worth five minutes of your time. If it doesn't have one, it's worth ten.

UK cookie rules changed in 2026. The parts of the Data (Use and Access) Act 2025 (DUAA) that amend the cookie rules came into force on 5 February, and the ICO has since published updated guidance on what a compliant cookie banner looks like. The maximum fine for breaking the rules has risen from £500,000 to £17.5 million.

Plenty of small business websites haven't caught up. That's rarely because owners don't care. Usually nobody told them anything had changed.

What changed

UK cookie law comes from the Privacy and Electronic Communications Regulations (PECR), which date from 2003 and were updated in 2011 to require consent for non-essential cookies. For years enforcement was gentle. The ICO sent warnings, websites added banners saying "by using this site you accept cookies", and not much happened.

Two things are now different.

Some cookies no longer need consent. The DUAA added a new Schedule A1 to PECR listing exceptions. They include cookies used to gather statistics so you can improve your own site, cookies that remember someone's display choices such as dark mode or text size, cookies needed for security, and cookies used in an emergency. For the analytics and preference exceptions, you still have to tell people clearly what the cookie does and give them a simple way to object. But you no longer need to ask first.

Everything else needs real consent. For any cookie outside those exceptions, consent has to be informed, freely given and as easy to refuse as to give. In practice that means "Accept all" and "Reject all" side by side on the first screen, with no pre-ticked boxes, no reject button hidden behind a settings menu, and no cookie wall that blocks the site until someone agrees.

The number that matters: PECR fines used to be capped at £500,000. The DUAA raised the ceiling to £17.5 million or 4% of global annual turnover, whichever is higher, matching UK GDPR.

Bar chart of the maximum fine for breaking UK cookie rules: £500,000 before the Data (Use and Access) Act, £17.5 million or 4% of global turnover after
The maximum penalty under PECR, before and after the Data (Use and Access) Act.

Reject must be as easy as accept

This is the change most businesses need to act on. If your banner has an "Accept all" button, refusing has to be just as easy: a button of similar size and prominence, in the same place, one click away.

Look at your own banner now. Is "Accept" a big coloured button while "Manage preferences" is small grey text underneath? That falls short. The reject option should sit next to accept and look just as clickable.

The ICO has already written to the operators of many of the UK's most-visited websites about exactly this, and regulators elsewhere in Europe, including France's CNIL, have been fining companies over unequal banners for several years.

Your suppliers' scripts are still your responsibility

Many tracking problems arrive in a snippet of code from an advertising network or analytics provider with the instruction "just paste this into your site". The script works, but it often starts setting cookies the moment the page loads, before anyone has agreed to anything.

You are responsible for what runs on your website, whoever wrote it. Before adding any third-party script, check what it sets and make sure it only loads once a visitor has agreed.

What a compliant banner looks like

First screen. A short, plain statement of what you use cookies for, with "Accept all" and "Reject all" given equal weight. Nothing pre-selected, no cookie wall, and the banner shouldn't vanish just because someone clicked elsewhere on the page.

Second screen, for anyone who wants to choose. A switch for each category, such as analytics, marketing and preferences, all off by default. Strictly necessary cookies can be listed without a switch, because the site can't work without them.

After the choice. If someone rejects non-essential cookies, the site should carry on working normally. They can still read, browse and use the basic features; you just don't load the tracking. If the site breaks when cookies are refused, the set-up is wrong.

Platform pitfalls

If your site runs on Wix, Squarespace or Shopify, it's easy to assume the built-in cookie tools handle all this. They help, but not always completely.

Wix and Squarespace provide a banner, but third-party code you add yourself, such as analytics tags or the Meta Pixel, may still load before consent unless it's set up carefully through the platform's own consent options. Because you can't change the underlying code, check the result rather than trusting the settings.

WordPress has good plugins, such as Complianz or Cookiebot, that can work with Google Tag Manager to load scripts only after consent. Installing one isn't enough, though. You need to list every script the site loads and put each in the right category.

Custom-built sites give you full control, so every non-essential script can be held back until the visitor agrees. That's how we build our AI-managed websites, with consent handled in the site itself from the start.

Does Google Analytics 4 still need consent?

Almost certainly, yes.

The new analytics exception is about collecting statistics to improve your own website. Google Analytics 4 sends data to Google, which can also use it for its own purposes, so it is very unlikely to fit. Turning on IP masking doesn't change that.

If you want analytics without the consent question, privacy-focused tools such as Plausible, Fathom or Umami are worth a look. Set up so the data is only used to understand and improve your site, they are much more likely to fall within the exception, as long as your privacy notice explains them and visitors can opt out. Ask us if you'd like help setting one up.

A six-point self-check

Go through these on your own site. If any answer is "no" or "not sure", it needs attention.

1. Is there a privacy policy link in the footer of every page? It should be easy to find and written in plain English, not copied from a template that talks about EU rules the UK no longer follows.

2. Is the policy dated and up to date? One last touched in 2023 won't reflect the DUAA. If it talks about "EU GDPR" without mentioning UK GDPR or PECR, it's out of date.

3. Does a banner appear on a first visit? Open the site in a private window. If no banner appears but the site uses non-essential cookies (analytics, adverts, social media widgets), that's a problem.

4. Can visitors reject everything in one click? If the only choices are "Accept" and "Manage settings", it doesn't meet the equal-prominence expectation.

5. Are tracking scripts held back until consent? Open your browser's developer tools (F12), go to the Network tab, load the site in a private window and don't click accept. Requests to google-analytics.com, facebook.net or advertising domains mean scripts are loading without consent.

6. Does the policy say who to contact about data? Visitors should know exactly how to get in touch about their personal data. A working email address is the minimum.

What it costs to ignore

The £17.5 million headline gets attention, but the realistic risk for a small business is different. The ICO tends to concentrate on sites that make no effort at all: no banner, no privacy policy and analytics running freely. A banner that needs adjusting is far less likely to attract action than nothing at all.

That could change as the new powers bed in, and the safest place to be is compliant before anyone looks. There's also trust to think about. A clear, honest banner tells visitors you take their privacy seriously, which is worth something in itself.

What to do next

If your site needs work, go in this order. First, find out which cookies and scripts it actually loads; there are often more than you'd expect. Second, decide which you really need, and remove the leftovers from tools you tried and forgot about. Third, put in a consent mechanism that holds back anything non-essential until the visitor agrees. Fourth, update your privacy policy for the DUAA changes and how you actually use data. Fifth, test the whole thing in a private window.

It can be a fair amount of work. It's also a good excuse to tidy the site up, remove scripts that slow it down and give visitors a better experience. Most businesses find they don't need half the tracking they have.

This article is general information about UK cookie rules, not legal advice. For advice on your own situation, speak to a qualified data protection adviser or see the ICO's guidance at ico.org.uk.

Not sure if your website is compliant?

We run a free compliance check that audits your cookie setup, privacy policy, and script loading against the current ICO guidance. You get a plain-English report on what needs fixing and what is already fine.

Get Your Free Website Health Check

Or request a compliance review.