Look beyond the cookie list

PECR’s storage-and-access rules cover more than conventional cookies. Other browser storage and technologies that access information on devices can fall within their scope. Calling a service cookieless, server-side or privacy-friendly does not settle the question. The underlying operation matters more than the product label.

For a useful first review, list the systems loaded by the site: analytics, advertising, embedded video, maps, chat, booking tools, payment journeys and security services. Include scripts introduced through a tag manager. The main homepage may be simple while a campaign landing page or enquiry form loads several additional suppliers.

Separate what visitors need from what the business wants

The strictly necessary exception relates to providing a service the user requests. It is not a general exception for technology that is commercially valuable. For example, a business wanting more detailed advertising attribution does not make that tracking technically necessary for a visitor to read a page.

Other exceptions exist, including a conditional statistical-purpose exception. Each has its own limits. An exception covering one use does not automatically cover an additional advertising or profiling purpose attached to the same technology. Record the purpose and reasoning for each classification rather than adopting the supplier’s default category without checking it.

When consent is needed, collect it before the activity

For non-exempt storage or access, a visitor must make an informed, positive choice before it starts. Continuing to browse or failing to close a banner is not that choice. The ICO expects refusal to be as easy as acceptance, with appropriate control over the purposes involved.

This is why a handsome banner can still fail. If the advertising script runs as the page loads, asking the visitor afterwards does not undo the earlier access. Equally, a reject button achieves little if it changes the screen but leaves the relevant tags enabled. The interface and the technical controls have to work together.

Could a simpler website avoid the problem?

Yes, simplifying technology can be a sensible design decision. A business may replace an automatically loaded map with an ordinary link, remove an unused marketing pixel or choose a genuinely limited measurement approach. Assess the resulting site rather than assuming that removing one service eliminates every relevant operation.

We recommend starting with a business question for each tool. What decision will its data inform? Who uses the report? If nobody can answer, the integration may be adding maintenance and privacy work without adding value. Less technology can also make performance, accessibility and troubleshooting easier. These are design benefits, not a substitute for checking legal requirements.

Provide information even where no consent banner is necessary

Not needing consent for a particular operation does not mean that visitors need no information. Requirements depend on the exception and on whether personal data is processed. Where the statistical-purpose exception is used, clear information and a simple, free way to object are required conditions. UK GDPR duties can apply alongside PECR.

Keep the explanation intelligible. Describe what is measured or stored, why and who receives it. Avoid promising that a website collects no data while its hosting, enquiry form or newsletter service handles identifiable information. Different layers of a service can create different responsibilities.

A practical decision record

Create one row per technology with its purpose, trigger, information handled, supplier and proposed treatment: exempt with reasons, blocked pending consent, or removed. Save evidence from an actual browser test and note which journeys were examined. This gives a future developer something concrete to maintain.

Recheck after a redesign, a new marketing integration or a supplier configuration change. A decision that was sound for a simple brochure site may not fit a later advertising campaign. The goal is a proportionate visitor experience backed by an accurate technical assessment, not a banner added simply because competitors have one.

Keep unresolved questions visible in the action log, with a named owner and the evidence needed to close them.

Sources and further reading

Primary guidance behind this briefing. Requirements depend on the facts; check the current guidance before making a decision.

This is general guidance, not a legal opinion on your circumstances or a guarantee of compliance. An individual assessment may be needed, particularly where sensitive information, disputed rights or regulatory action is involved.