Key takeaways
- Since 5 February 2026, PECR regulation 6 bans storing or reading information on a visitor's device unless consent is given or a Schedule A1 exception applies[1][2].
- First-party analytics can now run without consent if it is used only to improve your site, the data is not shared for other purposes, and visitors get clear information and a free way to object[2].
- Advertising pixels, remarketing tags and most third-party embeds still need opt-in consent.
- PECR enforcement powers and fines are now aligned with the Data Protection Act 2018[3], so cookie failures carry more weight than before.
- Tracking on pages about divorce, crime or immigration can reveal sensitive information; keep those pages free of advertising tags.
Why your cookie banner matters more than it looks
For many prospective clients, your website is the first contact with the firm, and the banner is the first thing on it. Research before choosing a lawyer is common: when choosing a main adviser, 25% of people searched around, 15% looked for service details, 14% searched for reviews and 13% searched for prices[4]. A banner that hides the reject option, or a page that quietly loads advertising trackers before anyone has chosen, sends the wrong signal to someone deciding whether to trust you with a confidential problem.
The legal rules sit in the Privacy and Electronic Communications Regulations 2003, not UK GDPR, although UK GDPR applies to any personal data the cookies collect. The Data (Use and Access) Act 2025 rewrote the cookie rule and added new exceptions, and those changes have applied since 5 February 2026[1].
The rule after the 2026 reforms
Regulation 6 now says that, subject to Schedule A1, a person must not store information, or gain access to information stored, in the terminal equipment of a subscriber or user. Storing and accessing include instigating it, so tags you place for a third party count as yours[1]. Schedule A1 then sets out when that is allowed[2]:
| Ground | What it covers | Conditions |
|---|---|---|
| Consent | Anything not covered by another exception | Clear and comprehensive information first; consent can be signified through browser settings or another application |
| Transmission | Technical storage needed to carry the communication | Sole purpose is transmission |
| Strictly necessary | Security, fraud prevention, fault detection, authentication, load balancing, remembering form progress | Necessary for a service the visitor requested |
| Statistical purposes | First-party analytics to understand how the site is used and improve it | Sole purpose; data not shared except to help improve the service; clear information; simple free way to object |
| Appearance and functionality | Remembering preferences such as text size, language or region | Website only; clear information; simple free way to object |
| Emergency assistance | Location for emergency services | Sole purpose is emergency assistance |
The analytics exception is narrower than it sounds. If your analytics provider uses the data for its own purposes, such as advertising products or benchmarking, the sole-purpose and no-sharing conditions are unlikely to be met, and you are back to needing consent.
What still needs consent on a typical firm website
- Advertising and remarketing pixels from social networks and search engines, including conversion tags on thank-you pages.
- Embedded videos and maps that set third-party cookies when the page loads. Use privacy-enhanced embed modes or load them only after a click.
- Session replay and heatmap tools that record what visitors type or where they click, unless configured and contracted so that they genuinely fall within the analytics exception.
- Live chat or review widgets that drop tracking identifiers for the vendor's own purposes.
- Third-party analytics where the provider shares or reuses the data.
Things that can usually run without consent include the session cookie that keeps an enquiry form working, a load balancer cookie, a security token that blocks spam submissions, a cookie that remembers a visitor has dismissed the banner, and properly configured first-party analytics that meets the Schedule A1 conditions.
The special problem for law firm pages
Most businesses worry about cookies in the abstract. Law firms have a sharper issue: the page a visitor reads says something about them. A visitor who reads your pages on non-molestation orders, police station interviews or immigration appeals and is then tagged by an advertising pixel has, in effect, had sensitive information about their circumstances passed to an advertising platform. That can touch special category or criminal offence data, which needs far more than a cookie banner to justify.
The safest course is simple: no advertising or remarketing tags on practice-area pages that relate to health, crime, family breakdown, immigration status or sexuality, even with consent. Measure those campaigns with aggregate first-party analytics instead.
Audit and fix in one afternoon
Scan the site
Load the home page and three practice-area pages in a private browser window with developer tools open. List every cookie and every network request to a third-party domain before you click anything.
Classify each item
Map each cookie or tag to a Schedule A1 ground: strictly necessary, analytics, functionality or consent required. Anything you cannot explain gets switched off.
Block before consent
Configure your tag manager or consent tool so that nothing in the consent-required group fires until the visitor accepts.
Set up the analytics exception properly
Use first-party analytics with data sharing off, describe it in the cookie notice and add a one-click way to object.
Redesign the banner
Offer Accept and Reject with equal prominence on the first layer, with a link to settings. No pre-ticked boxes, and no wording that implies rejection will break the site.
Update the notice
Publish a cookie notice that lists each cookie or tool, its purpose, its duration and its ground, linked from the banner and the footer.
Repeat quarterly
Marketing agencies and website developers add tags. Re-scan every quarter and after every redesign or new campaign.
Consent that stands up
Where consent is the ground, it has to be the UK GDPR standard of consent: a clear, affirmative choice, freely given, specific and informed, and as easy to withdraw as to give. On a cookie banner that translates into a handful of concrete design rules.
- Nothing in the consent group fires on page load. Scrolling, continuing to browse or closing the banner is not consent.
- The first layer explains in a sentence what you want to do and why, for example to measure which adverts bring enquiries.
- Accept and Reject sit side by side, in the same size and style. A Manage settings link can sit beneath them.
- Categories are switched off by default in the settings panel.
- A persistent link, usually in the footer, lets visitors reopen the settings and withdraw consent at any time.
- Your consent tool keeps a record of what each visitor chose, when, and which version of the banner they saw.
Visitors who reject should get exactly the same site, including the enquiry form and telephone number. Hiding contact details behind an accepted banner turns a compliance question into a lost enquiry.
Working with your web agency
Most cookie problems at law firms are introduced by well-meaning suppliers: an agency adds a heatmap to test a new page, a pay-per-click consultant installs a conversion tag, a developer embeds a map. The firm remains responsible for all of it, so build controls into the relationship rather than relying on periodic clean-ups.
- Make it a contract term that no new script, tag, pixel or embed goes live without written approval from the firm's data protection lead.
- Ask the agency to maintain a tag register listing each tool, its purpose, the cookies it sets and its consent category.
- Require that the consent tool is tested after every release, with screenshots of the network requests before and after consent.
- Restrict access to the tag manager to named people, with multi-factor authentication switched on.
- Agree that the agency treats any data it can see through these tools as your client data, under a processor agreement.
A five-minute check at each monthly marketing meeting, has anything new been added to the site, catches most issues before a visitor, a regulator or an opponent does.
Enforcement and risk
The 2025 Act aligned PECR enforcement sanctions, including fines, with the Data Protection Act 2018[3], which raises the stakes for websites and marketing alike. It also made clear that a PECR direct marketing breach can occur even if a call or message never reached its intended recipient[5]. Cookie complaints often come from the same people who scrutinise firms most closely: competitors, privacy-minded clients and opponents in disputes.
Example: a fictional firm's audit finds that its home page loads a social media pixel, a video platform's tracking cookie and a third-party analytics tag before the banner appears. It moves the pixel behind consent and removes it entirely from family and crime pages, switches the video to a click-to-load embed, replaces the analytics with a first-party set-up that meets the statistical purposes conditions, and adds a Reject all button. The banner now appears on fewer page views because the analytics no longer needs consent.
Cookie information belongs in its own notice, linked from your main privacy notice. For the wider reforms, see the Data (Use and Access) Act 2025, and for email marketing to people who visit and enquire, our guide to PECR and the soft opt-in.
Frequently asked questions
Do we still need a cookie banner?
Yes, if you use anything that requires consent, such as advertising tags or third-party embeds. If your site only uses strictly necessary cookies and first-party analytics that meets the Schedule A1 conditions, you may only need clear information and a simple way to object to analytics.
Is Google Analytics covered by the new analytics exception?
It depends on configuration and contract. The exception requires the sole purpose to be improving your service and the data not to be shared for other purposes. If the provider can use the data for its own purposes, consent is still likely to be needed.
Can we use a cookie wall that blocks the site until visitors accept?
It is risky for a law firm. Consent must be freely given, and blocking access to basic information about legal services unless visitors accept tracking is hard to justify.
Who is responsible for cookies set by our web agency's tools?
The firm. Regulation 6 covers instigating storage or access, so tags placed on your site for any third party are your responsibility.
References
legislation.gov.uk (The National Archives) (2026). The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 6 (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). The Privacy and Electronic Communications (EC Directive) Regulations 2003, Schedule A1 (opens in a new tab) ↑
GOV.UK (DSIT) (2025). Data (Use and Access) Act factsheet: ICO (opens in a new tab) ↑
Legal Services Board (2024). Legal Needs Survey 2023: Summary report (opens in a new tab) ↑
GOV.UK (DSIT) (2025). Data (Use and Access) Act factsheet: PEC Regulations (opens in a new tab) ↑