MOSH

All notes / 4 min read

Do UK websites need a cookie banner?

Not every website needs a cookie banner. Whether yours does depends on what it stores in visitors’ browsers, and why.

Published · By MOSH

The short answer

A UK website needs to ask for consent before it stores or reads information on a visitor’s device, unless that storage is strictly necessary for something the visitor has asked for. Cookies are the best-known example, but the same principle covers similar technologies such as local storage, tracking pixels and device fingerprinting.

So the real question isn’t “do we need a banner?” but “what does our site actually do in people’s browsers?” If the honest answer is “only what’s needed to make the site work”, you may not need a consent banner at all. You will still need to explain what you use in a privacy or cookie notice.

This note explains the principles in plain English. It isn’t legal advice, and the rules do change, so always check the current guidance from the Information Commissioner’s Office (ICO), the UK regulator for this area.

What counts as strictly necessary

“Strictly necessary” is a narrow idea. It means storage that is essential to provide a service the visitor has explicitly requested. Typical examples include:

  • Shopping baskets. Remembering what someone has added while they browse.
  • Logging in. Keeping a signed-in visitor signed in as they move between pages.
  • Security. Protecting forms and accounts from abuse, such as a token that guards against forged requests.
  • Load balancing. Making sure a visitor’s requests reach the right server.
  • Remembering a choice the visitor made. Including, helpfully, their cookie preferences.

What usually doesn’t count: advertising and retargeting, social media tracking, most third-party embeds that set their own cookies, and, under the traditional reading of the rules, analytics. Something being useful to you as the site owner doesn’t make it strictly necessary for the visitor.

Where the banners come from

Most banners exist because of a few common additions to a site:

  • Analytics tools that set cookies to recognise returning visitors.
  • Advertising pixels from social networks and ad platforms.
  • Embedded content such as videos, maps and social feeds, which can set third-party cookies the moment the page loads.
  • Chat widgets and marketing tools that track visitors across sessions.

Each of these is a choice. It’s worth asking, for every one, whether it earns its place. A small business site that adds three tracking scripts “just in case” ends up with a banner, slower pages and data it never looks at.

Avoiding a banner by not tracking

The simplest way to avoid a consent banner is to avoid the things that need consent. For many small business websites that’s very achievable:

  • Remove tracking you don’t use. If nobody has looked at an ad platform’s data in months, take its pixel out.
  • Embed carefully. Many video and map providers offer privacy-enhanced modes, or you can show a placeholder that only loads the embed when someone clicks it.
  • Host your own fonts and scripts rather than loading them from third parties where you can.
  • Choose privacy-friendly analytics (more on that below).

A site without a banner is also a nicer site to use. Visitors see your content first, not a pop-up, and pages tend to load faster.

Privacy-friendly analytics

You can usually still understand how your site is used without invasive tracking. In general terms, the options are:

  • Cookieless analytics tools that count page views and referrers without setting cookies or building profiles of individuals.
  • Server-side or edge statistics provided by your host or network, based on requests the server already sees.
  • Configuring a mainstream tool conservatively, though this rarely removes the need for consent on its own.

A cookieless tool is not automatically exempt from the rules: what matters is whether anything is stored on or read from the device, and how personal data is handled. UK law has been changing in this area, including around low-risk analytics, so check the ICO’s current position before deciding a banner isn’t needed.

If you do need consent

If your site genuinely needs non-essential cookies, do consent properly. The broad principles are:

  • Don’t set non-essential cookies until the visitor has agreed.
  • Make rejecting as easy as accepting, with no pre-ticked boxes.
  • Explain clearly what each category does, in plain English.
  • Let people change their mind later, with a link that’s easy to find.
  • Test it: open the site in a private window, reject everything, and check in the browser’s developer tools that nothing non-essential appears.

That last step catches more problems than any other. Banners that look compliant but still load trackers in the background are common.

Where to start

Make a list of everything your site stores in visitors’ browsers and every third-party script it loads. For each, write down why it’s there. You’ll often find you can remove more than you expected, and the banner question answers itself.

If you’d like help auditing a site, or building one that’s fast and private from the start, that’s part of our website work.

More notes

Keep reading.

Want a hand with this?

Tell us what you’re working on. You’ll get a proper reply, usually with a few questions.