Harper James advises UK businesses on cookie compliance under the laws of England and Wales, helping teams turn consent requirements into workable website processes. The starting point is the Privacy and Electronic Communications Regulations (PECR), read alongside the UK GDPR where cookies process personal data.
Non-essential cookies, including many analytics, advertising and personalisation cookies, require consent before they are placed or read. Consent must be informed, specific, freely given and based on a clear affirmative action. Pre-ticked boxes, implied consent from continued browsing and bundled acceptance are not reliable methods. A user must also be able to reject non-essential cookies as easily as accepting them, and withdrawal must remain straightforward. The Data (Use and Access) Act 2025 widened some exemptions for lower-risk purposes, but those exemptions have conditions and do not create a general exception for analytics or marketing technology. Businesses should review the latest ICO guidance when classifying each cookie.
For a practical overview of the rules and implementation issues, see this cookie compliance resource. It is useful to treat the exercise as a technology and governance project rather than simply a banner design task. A cookie audit should identify every tag, its provider, purpose, expiry, data destination and trigger. Server-side tracking, pixels and software development kits also require assessment. Moving processing away from the browser does not automatically remove PECR or UK GDPR obligations.
Keep evidence of the consent framework in operation, including the banner wording, consent categories, consent management platform settings, vendor list, policy version, timestamps, consent choices and withdrawal records. Record how tags are blocked before consent and test the result after website releases, tag manager changes and new marketing integrations. The privacy and cookie notices should match the live configuration, explain purposes in plain English and identify relevant third parties.
A sensible implementation sequence is to appoint an owner, scan the site and applications, classify each technology, remove unnecessary tags, configure a reject option, test blocking and document the decision for each category. Review the register at least when a new vendor or campaign is introduced. Marketing, product, IT and legal teams should use the same approval route, so a new tracking tool does not go live without a consent assessment. Where the processing is extensive or intrusive, add a data protection impact assessment to the project file.