Cookies in 2026: what changed, and what old websites still get wrong
· 6 min read
In part one we looked at the ways an old website quietly drifts out of date. This post is about the one most business owners have heard of but few have looked at closely: cookies.
The rules changed in 2026, and for once some of the change is good news for small businesses. But the old mistakes are still out there, and they now carry much bigger potential fines.
A quick reminder of what the rules are
Cookies are small files a website saves in your visitor’s browser. Similar technologies, like tracking pixels, work in much the same way, so the rules cover them too.
In the UK, these are covered by the Privacy and Electronic Communications Regulations, usually shortened to PECR. Since 2011, the basic rule has been simple: you need the visitor’s consent before you put anything on their device, unless it’s strictly necessary for something they’ve asked for.
That’s why cookie banners exist.
What changed in 2026
The Data (Use and Access) Act 2025 changed the rules in two ways that matter to a small business website.
1. Some cookies no longer need consent. Since 5 February 2026, you don’t need consent for cookies used only to:
- Count visits and see how your site is used, so you can improve it. Things like page views, which pages people leave from, what devices they use and how fast pages load.
- Make the site look or work the way the visitor wants, like remembering their language or a dark mode setting, or loading the fonts your site uses.
There are conditions, and they matter. You have to tell people clearly what you’re doing, and give them a simple, free way to say no. For analytics, the information has to be turned into overall statistics, not used to follow or profile individual people. If you use an outside analytics service, it can only use the data to help you improve your site. It can’t use it for its own purposes or combine it with other data it holds. The ICO’s guidance sets all of this out in detail.
2. The fines went up. The maximum fine for breaking the cookie rules used to be £500,000. It’s now the same as UK GDPR: up to £17.5 million or 4% of worldwide turnover, whichever is higher.
What still needs consent
This is the part that catches people out. The new exceptions are narrow. You still need consent first for:
- Advertising and marketing tracking, including the pixels that social networks and ad platforms give you to measure campaigns.
- Social media tracking, such as share buttons or feeds that track visitors, whether or not they have an account.
- Embedded content that tracks, which often includes embedded videos and maps.
- Anything that builds a profile of a visitor, or follows them across other websites.
- Analytics that goes beyond counting, such as recording individual visitors’ sessions, or sharing data with advertising partners.
The ICO has been clear that online advertising has never been exempt, and still isn’t.
What old websites get wrong
When we look at older small business sites, the same problems come up again and again.
The banner that doesn’t do anything
The most common one. There’s a banner, it looks the part, but the tracking loads the moment the page opens, before anyone clicks anything. Clicking “Reject” changes nothing. Legally, that’s the same as having no banner at all.
“By using this site you agree to cookies”
This used to be everywhere. It has never been valid consent, and it isn’t now. Consent has to be a clear, positive choice, and saying no has to be as easy as saying yes.
Tracking code nobody remembers adding
A marketing agency adds an advertising pixel for a campaign in 2021. The campaign ends, the agency moves on, and the pixel stays on every page for years, quietly sending visitor data to an ad platform. We find this a lot. Often the business has no idea it’s there.
Embeds that load before anyone agrees
Embedded videos, maps and social media feeds often set their own cookies or send visitor data to the provider as soon as the page loads. On older sites, they’re rarely held back until the visitor agrees.
A cookie policy that describes a different website
The cookie policy was copied from a template at launch and never updated. It lists cookies the site doesn’t use, and misses the ones it does.
What a good setup looks like now
For a typical small business brochure site, the goal is simpler than people expect.
- Use as few cookies as you can. Many brochure sites need almost none.
- Use privacy-friendly analytics that counts visits without tracking people. With the new exception, that may mean you don’t need a banner for analytics at all, as long as you explain it and offer an easy opt-out.
- Host your own fonts rather than loading them from an outside service each time. It’s faster, and it takes one question off the table.
- If you do use advertising pixels or tracking embeds, use a proper consent tool that genuinely blocks them until the visitor says yes, with “Reject” as easy as “Accept”.
- Keep your cookie information accurate. If you change what the site loads, update the policy.
Our own site works this way. Analytics is cookie-less, nothing tracks visitors, and the only thing our banner asks about is remembering your light or dark mode choice.
Check your own site in ten minutes
- Open your site in a private browser window and don’t click the banner. If you know how, open the browser’s developer tools and look at the cookies and network requests. Anything from an ad platform or social network loading at this point is a problem.
- Click “Reject” if there is one, reload, and check again. Nothing non-essential should appear.
- Ask whoever manages your site for a list of every outside service the site loads, and why. Anything nobody can explain should probably go.
- Check your cookie policy matches what you find.
If you’d like a second pair of eyes, get in touch and we’ll check it for you as part of a website security check.
Technical notes
If someone else manages your site, send them this bit.
- Regulation 6 PECR was amended by s.112 of the Data (Use and Access) Act 2025, in force 5 February 2026. New exceptions cover storage or access solely for statistical purposes to improve the service, and solely to adapt or enhance appearance or functionality. Both require clear and comprehensive information and a simple, free means of objecting.
- For analytics under the exception, data must be aggregated, individual-level data not retained after aggregation, and no inferences or decisions made about individuals. A third-party provider must act as a processor only and must not combine the data with other data. Session recording, cross-site identifiers and conversion sharing with ad partners are outside it. See the ICO’s final guidance (May 2026).
- Advertising, social tracking, fingerprinting and cross-device tracking still require prior consent. Check that consent tooling blocks tags before consent, not just hides them, and that rejection is respected on reload.
- Third-party embeds (video, maps, social) should be click-to-load or held behind consent unless you’ve confirmed they set nothing outside the exceptions.
- Self-hosting web fonts avoids relying on the appearance exception for a third-party font service.
This is general information for UK businesses, not legal advice. If you’re unsure how the rules apply to your site, speak to a solicitor or see the ICO’s guidance.