The Data (Use and Access) Act's cookie changes mean that, since 5 February 2026, UK websites no longer need consent for cookies and similar technologies used only to collect statistics to improve the site, or only to remember how a visitor wants the site to look or work. You must still tell people about them and give them a simple, free way to object. Everything else that isn't strictly necessary, including advertising, retargeting and affiliate tracking, still needs opt-in consent, and PECR fines are now as high as UK GDPR fines.
This guide explains exactly what the new exemptions say, how the ICO interprets them in its April 2026 guidance, how to build a compliant opt-out and what has not changed.
General information only, not legal advice.
PECR changes in 2026: what the Act did
The Privacy and Electronic Communications Regulations 2003 (PECR) are the UK's version of the EU ePrivacy rules. Regulation 6 has always banned storing or accessing information on a user's device without consent, unless it is strictly necessary. Section 112 and Schedule 12 of the Data (Use and Access) Act 2025 replaced that rule with a new regulation 6 and a new Schedule A1 listing the exceptions. They came into force on 5 February 2026.
Schedule A1 now contains five routes:
- Consent with clear and comprehensive information (the general rule).
- Transmission of a communication over a network.
- Strictly necessary for a service the user has requested, now with examples written into the law: security, fraud prevention, fault detection, authentication and remembering what a user entered or selected (such as a basket).
- Statistical purposes, with conditions (new).
- Appearance and functionality of a website, with conditions (new).
There is also a narrow emergency-assistance exception for locating someone who has asked for help. The Secretary of State can add or change exceptions by regulations after consulting the ICO, so this list may grow.
The statistical cookies exemption in the UK
This is the change most publishers care about. You can set or read analytics cookies without consent if all of these are true:
- You provide the service (your website or online service).
- The sole purpose is to collect information for statistical purposes about how the service is used, with a view to improving it.
- The information is not shared with anyone else except to help you make those improvements.
- You give the user clear and comprehensive information about the purpose.
- You give the user a simple means of objecting, free of charge, and they do not object.
The ICO's guidance on storage and access technologies describes this as covering analytics about how a service is used (visits, page interactions, how users arrived), not analytics about who the users are. It reads the sharing condition as allowing a third-party analytics provider only where it acts as your processor and uses the data only to help improve your service.
What this means for common tools
| Tool or setup | Likely position |
|---|---|
| Self-hosted analytics (e.g. Matomo on your own server) used only for site statistics | Good fit for the exemption, with an opt-out |
| Privacy-focused hosted analytics acting as your processor | Often a good fit; check the contract and that data isn't reused |
| GA4 with Google signals, ads linking or optional data sharing on | Outside the exemption; needs consent |
| GA4 stripped to statistics only | Possible but contested; take advice and document your configuration |
| Heatmaps and session recordings | Depends on what is captured; recordings of individual sessions go beyond simple statistics, so be cautious |
For a deeper look at the tool question, see analytics without cookie consent.
Single purpose matters. The ICO stresses that each exception applies only where the storage or access is for that purpose. A cookie that measures page views and also builds ad audiences doesn't qualify. If you can, use separate technologies for separate purposes.
The appearance and functionality exemption
The second new exemption covers storage or access whose sole purpose is to adapt how your website looks or works to the user's preferences, or otherwise enhance its appearance or functionality. The ICO's examples include detecting screen size to reconfigure a page and remembering a chosen language. Think dark mode, text size, region or currency selection and layout choices.
The same conditions apply: clear information and a simple, free way to object. The ICO notes that this does not extend to personalising content based on users' known or inferred interests. "Recommended for you" carousels driven by browsing history are personalisation, not appearance, and need consent.
How to run UK analytics cookies without consent, properly
Relying on the exemptions is not the same as having no banner. You still need to inform and offer an objection. The ICO suggests the objection can run through your existing consent tool, for example with statistics and appearance toggles that default to on and can be switched off at any time. A workable setup:
- Classify every tag. Strictly necessary, statistical, appearance, or consent required. Be strict: a tag with any advertising function goes in the last group.
- Geo-target. Apply the exemptions only to UK visitors. EU visitors still need opt-in consent for analytics (with narrow national exceptions).
- Update the banner. For UK visitors, explain that analytics and preference cookies are on, with a clear, one-click way to turn them off, alongside the normal accept/reject choice for everything else.
- Make objection stick. When someone objects, stop the storage and access. Ideally delete existing analytics cookies, and remember the objection.
- Configure the tool. Turn off advertising features, cross-site identifiers and optional data sharing. Check data retention settings.
- Update your cookie and privacy notices to describe the exemptions you rely on.
- Document it. Keep a short note of why each tag meets the conditions. If the ICO asks, you'll need it.
The ICO also suggests asking again roughly every six months, particularly where someone has declined. That's guidance rather than a fixed legal time limit, but it's a sensible default.
A hypothetical example
A UK-based affiliate site gets 70% UK traffic. Before February 2026, roughly half of visitors rejected cookies, so analytics saw only about half of sessions. After moving to self-hosted analytics configured for statistics only, with an opt-out, it can measure most UK sessions again. EU visitors still see an opt-in banner, and affiliate pixels stay behind consent for everyone. The figures are illustrative: your reject and objection rates will differ.
What still needs consent in the UK
The list is longer than the exemptions:
- Advertising cookies, retargeting pixels and frequency capping.
- Ad measurement and conversion tracking for ad platforms. The ICO's consultation response confirms that online advertising still needs consent under PECR.
- Affiliate tracking pixels and scripts on your pages. The ICO's guidance uses affiliate pixels as an example requiring consent.
- Social media pixels and most embedded third-party content that sets cookies.
- Fingerprinting and other techniques that read device information for tracking.
- Any analytics shared with a provider for its own purposes.
The ICO has said it is reviewing whether some low-risk advertising could be exempted and has sent advice to government. Until the law changes, treat advertising as consent-only. For affiliate specifics, read do affiliate cookies need consent?
PECR fines of £17.5 million: the enforcement picture
Before the Act, PECR fines were capped at £500,000. Schedule 13 of the DUAA aligned them with UK GDPR, so the ICO can now fine up to £17.5 million or 4% of worldwide annual turnover, whichever is higher, for cookie and electronic marketing breaches.
The ICO has made online tracking a priority, including a review of cookie practices on the UK's top 1,000 websites announced in 2025. Larger fines don't mean every small site will be fined, but they change the cost-benefit calculation for anyone ignoring the rules, and complaints can trigger investigations at any size.
What about EU visitors?
None of this applies in the EU. The ePrivacy Directive still requires consent for analytics cookies, apart from narrow national exemptions such as France's for strictly configured audience measurement. The EU's proposed Digital Omnibus includes cookie reforms, but it is only a proposal. If your site serves both markets, your consent tool needs region-specific behaviour or a single EU-standard setup. Our guide to EU cookie banner requirements covers that side, and UK GDPR vs EU GDPR sets out the wider divergence.
Frequently asked questions
Can I remove my cookie banner in the UK now?
Only if every cookie and tracker on your site is strictly necessary or falls within the new exemptions, and you still tell people about the exempt ones and let them object. Most commercial sites use at least one advertising or affiliate tag, so they still need a consent banner.
Does Google Analytics count as a statistical cookie?
Not automatically. GA4 can feed advertising and Google's own purposes depending on your settings, which takes it outside the exemption. A heavily restricted configuration may fit, but it's a judgement call, so document it and take advice. See our guide on tracking affiliate clicks in GA4 for set-up details.
What counts as a "simple means of objecting"?
Something free and easy, such as a clearly labelled toggle in your banner or a one-click link in your cookie notice that turns the cookies off. Making people email you or dig through settings menus is unlikely to qualify.
Next steps
Audit your tags, decide which genuinely meet the statistical or appearance conditions, and update your consent tool for UK visitors. If you need help choosing analytics tools, our GDPR and cookies guides cover the options in detail.