Opens in a new tab.

Our approach: Assess, find the gaps; Fix, put it right; Manage, keep it working; Assure, prove it stays that way.

← All insights DIGIPEST / INSIGHT

A practical guide to UK website cookie compliance

What UK organisations should check before using cookies, local storage, embedded media and other browser technologies.

3 min readBy DigiPest

Cookie compliance is not solved by adding a banner copied from another website. An organisation first needs to know which technologies its site uses, what they do and whether they store information on—or access information from—a visitor’s device.

This includes more than traditional cookies. Local storage, tracking pixels, embedded services, device fingerprinting, scripts and tags may fall within the same UK rules.

This article is general operational guidance, not legal advice. The site’s actual use and purpose must be assessed against current ICO guidance.

Inventory the technologies before writing the notice

Review the site in a clean browser before and after each consent choice. Record:

  • the cookie, storage key, script or other technology;
  • the organisation that provides it;
  • its purpose;
  • what information it stores or accesses;
  • whether personal data is processed;
  • how long it remains; and
  • when it is activated.

Check every template and feature, including forms, analytics, videos, maps, chat, advertising, social media embeds and payment services. Repeat the audit after material site or supplier changes.

The ICO’s current guidance expressly covers technologies including local storage, tracking pixels, scripts, tags and device fingerprinting—not only files named as cookies. See its guidance on storage and access technologies .

Separate necessary use from optional use

Some storage or access may fall within an exception, including where it is strictly necessary to provide a service the user requested. Necessary does not mean merely useful to the website owner.

Analytics, advertising and many embedded third-party features should not be described as necessary simply because the organisation values them. Document why each exception applies.

Where consent is required, do not activate the technology before the visitor makes a choice. Consent needs a clear positive action and must be informed and specific.

Rejecting optional use should be as straightforward as accepting it. Do not rely on continued browsing, preselected options or a design that makes rejection materially harder to find.

Visitors should be able to change their choice later without clearing all browser data.

Provide useful information

Explain in plain language:

  • which technologies are used;
  • their purposes;
  • whether third parties are involved;
  • how long storage or access lasts; and
  • how the visitor can control the choice.

A table can make the detailed inventory easier to use, while the consent interface can provide a shorter explanation at the point of choice. Keep the two consistent.

The ICO states that organisations must provide clear and comprehensive information, including the purpose, relevant third parties and duration. Its current summary is available in What are the PECR rules? .

Choose a proportionate duration

PECR does not prescribe one duration for every technology. The period should be necessary and proportionate to the purpose. If personal data is involved, data-protection storage-limitation requirements also apply.

Record both the technology’s lifetime and how long a consent choice is remembered. Revisit consent when purposes or providers change, and periodically where a long-lived preference would no longer represent a meaningful current choice.

Treat embeds and third-party scripts as part of your site

An embedded video or social component can contact its provider and access browser information before the visitor interacts with it. Use privacy-enhanced modes where appropriate, but verify their behaviour rather than relying on the label.

A consent-controlled placeholder can prevent optional content from loading until the visitor chooses to activate it. Explain the consequence: for example, enabling a video may connect to the external provider.

Keep evidence and repeat the audit

Retain the inventory, reasons for classification, test results, policy version and consent implementation decisions. Assign ownership so a new marketing tool or website plugin cannot bypass the review.

Compliance is an ongoing configuration task. A clear notice is important, but it must describe what the site actually does—and the site’s code must respect the choices the notice offers.