Skip to content
PeekWellThe Handbook
Join now

Cookie policy UK: every cookie, its purpose and lifetime

At a glance

UK-21MediumPECR reg. 6 and Sch. A1 paras. 2, 5 and 6 (DUAA 2025 s. 112 and Sch. 12); UK GDPR Arts. 5(1)(a) and (e), 12 and 13(2)(a); ICO guidance on storage and access technologies (29 April 2026)

Peeky accepts every cookie, then checks that your cookie list names each one your site stores, under its real purpose and with its real lifetime.

Last checked against the source:

I need to fix thisI need the rule

The rule

In the UK a cookie list has a legal job. Two of the exceptions added to PECR in 2026 apply only if the visitor has been told about the cookie.

Regulation 6 of PECR 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.” The consent route in Schedule A1, paragraph 2(1), needs a visitor who “is provided with clear and comprehensive information about the purpose of the storage or access” and “gives consent to the storage or access”. Both have applied since 5 February 2026, substituted and inserted by the Data (Use and Access) Act 2025. UK-01 sets out the consent rule in full.

The two exceptions read like this.

The statistics exception (para. 5) covers storage or access whose sole purpose is to collect statistics about how the service is used, with a view to improving it. The appearance exception (para. 6) covers adapting how a website looks or works to the visitor’s preferences. Both apply only if the visitor “is provided with clear and comprehensive information about the purpose of the storage or access” and “is given a simple means of objecting, free of charge, to the storage or access”, and does not object.

For a statistics or preference cookie, then, being described clearly is one of the conditions for skipping consent. The strictly necessary exception (para. 4) doesn’t carry that condition, but the ICO says that where the cookie involves personal data you must give the information anyway.

The ICO’s guidance on storage and access technologies, last updated 29 April 2026, says “PECR does not define what ‘clear and comprehensive’ information means. However, in practice this refers to the UK GDPR’s transparency requirements”. You must cover “the storage and access technologies you intend to use; the purposes you intend to use them for; any third parties who store or access information in the user’s device”, and “the duration for which any information will be stored for, or access to information granted for, such as the duration of cookies.” You “must not include ambiguous or unclear references to ‘partners’ or ‘third parties’”. PECR sets no fixed duration, but yours must be “proportionate in relation to your intended outcome; and limited to what is necessary to achieve your purpose.”

The same guidance describes an audit, and two of its steps are this check in plain words: “determine the lifespan of any persistent cookies, and justify their duration in relation to the purpose(s) you use them for”, and “review any automatic categorisation of storage and access technologies and whether this is correct”. It notes that objects kept in localStorage may have no expiry date at all.

The UK GDPR adds its own duties where cookies collect personal data: the storage period, in Article 13(2)(a), information that is “concise, transparent, intelligible and easily accessible” under Article 12(1), and storage limitation under Article 5(1)(e). The guidance quoted here was issued by the ICO. Since 30 September 2026 the regulator has been the Information Commission (ICO), which took over the Information Commissioner’s functions under the 2025 Act. Penalties for regulation 6 are the same as in UK-01.

What PeekWell checks and how

UK-21 asks one question: does your cookie list match what your site really stores? The scan answers it by setting the two side by side.

The scan is automated, with AI used for reading. It opens your public pages, accepts everything, and records every cookie with its real lifetime, plus every localStorage, sessionStorage and IndexedDB name and the script that wrote it. It then reads your declaration: the table in your cookie policy, the cookie section of your privacy notice, and the details view of your consent tool. Layouts vary, so the reading is AI-assisted. The comparison itself follows fixed rules.

Four things make it fail, numbered D1 to D4 in the report:

  • D1: a cookie or storage name from a non-essential or unrecognised service isn’t on the list. A listed pattern such as _ga_<id> or _ga_* covers the names it stands for.
  • D2: a known analytics, advertising, session-recording, social or marketing name sits under strictly necessary or essential.
  • D3: a cookie outlives its declared lifetime by more than half again, and by at least a day. A cookie listed as a session cookie that persists counts.
  • D4: non-essential cookies or storage are set and there’s no list at all.

Strictly necessary names missing from the list are named in the finding but decide nothing. Where the cookie policy and the consent tool disagree, a name fails D2 or D3 when either source is wrong, and the finding says so. The one-and-a-half-times measure is PeekWell’s own. It comes from Bollinger and colleagues at ETH Zurich (USENIX Security 2022), who compared declared and real cookies on 29,398 websites and found undeclared cookies on 82.5% of them and a lifetime discrepancy on 9.1%.

UK-06 asks whether your privacy notice names the companies your pages contact, and UK-07 whether it holds the other items UK GDPR Article 13 asks for. UK-01 records what loads before anyone answers the banner. The EU version of this check is EU-24.

The scan has limits, and the report says so. It sees the public pages it visited, and the members area when you give it a sign-in. It doesn’t port-scan, try to get in where it isn’t allowed, run any security test or open addresses nobody linked to. Cookies set only in an app, only after signing in, or only in a country the scan didn’t visit from aren’t seen. It doesn’t test whether a declared purpose is true, only whether a known tracker sits under the wrong heading. A Passed means the expected behaviour was observed on the pages scanned. It doesn’t say the site complies.

Why it matters for a company

We found no published action by the ICO, before or since it became the Information Commission, on an inaccurate cookie list alone as of 4 November 2026. The 2026 rules raise the stakes another way. If an analytics cookie is missing from your list, or described too vaguely to count, it can’t use the statistics exception, so it needed consent all along. A site that relied on the exception to run analytics before the banner is then in the position UK-01 describes. How the regulator will treat that in practice is still open, and we found no decision on it.

A tracker filed under Necessary has the same effect. Consent tools usually switch the Necessary group on before anyone answers, so a mislabelled advertising or analytics cookie loads without a choice. And a cookie that isn’t on the list can’t be refused, because the visitor never saw it.

For comparison, EU regulators have fined inaccurate lists as part of wider cookie cases. The Belgian APD’s 2022 decision on Roularta Media Group found policy categories that didn’t match the consent tool, no concrete storage periods, and one cookie set to last about 246 years, among other findings, with a €50,000 fine. In an earlier Belgian case, a legal news site’s cookie list didn’t match what inspectors found, and the company blamed its consent tool’s scan. The study behind the check suggests these aren’t rare: on more than four in five of the sites it examined, the declaration left cookies out.

Smaller companies and larger companies

The rule has no size threshold, and the ICO’s audit steps are written for any site.

In a smaller company the list usually comes from the consent tool’s automatic scan and is published as is. New plugins and widgets arrive between scans, and the tool files what it doesn’t recognise under a default heading. The 2026 exceptions make this easier to get wrong, because a small site may run a simple analytics tool on the statistics exception without a banner, and then the list is doing the legal work.

In a larger company the list often splits in two. The consent tool has one set of categories and the cookie policy another, written by different teams, and they drift apart. With many tags, lifetimes stay at each vendor’s default, which can run to years.

Enforcement cases

Published decisions about other companies, listed for context. Each links to the authority's own page. They say nothing about any particular website.

The Officer, squinting at a file.

Larger companies

  • Roularta Media Group (knack.be and levif.be)

    APD (Belgium, EU data protection authority), 2022€50,000 (several findings)

    Shown for comparison: this is an EU decision, not a UK one. Inspectors found only two strictly necessary cookies on the sites, while the cookie policy used category names that differed from the consent tool's and gave no concrete storage periods. Some cookies lived 720 to 1,698 days, and one 90,000 days, about 246 years, which the authority called manifestly disproportionate. The fine also covers cookies set without consent and withdrawal that didn't work.

    Read the APD (Belgium, EU data protection authority) publication about Roularta Media Group (knack.be and levif.be)

Smaller companies

  • Legal news website (operator not named in the published decision)

    APD (Belgium, EU data protection authority), 2019€15,000 (several findings)

    Shown for comparison: this is an EU decision, not a UK one. Inspectors found Google Analytics, Google Tag Manager and Google AdSense on the site, but the cookie list the company submitted didn't match, which the company put down to its consent tool failing to return a correct list. Early versions of the cookie statement gave no purpose or retention period per cookie. The fine also covers analytics cookies set without consent.

    Read the APD (Belgium, EU data protection authority) publication about Legal news website (operator not named in the published decision)

How to fix it

The ICO’s audit steps, applied to the list, look like this.

  1. Make the real list. Open the site in a fresh browser profile on a device outside your network, accept everything, and browse the main pages. In the developer tools, copy every cookie with its domain and expiry, and every localStorage and sessionStorage name.
  2. Confirm the purpose of each one. Use the vendor’s own documentation. Note which ones rely on an exception, and which exception.
  3. Check the categories by hand. Don’t take the consent tool’s automatic sorting on trust. Necessary is for what the site can’t work without. Statistics cookies on the exception go under their own heading, with a way to object.
  4. State each lifetime and justify it. Copy the real expiry from the browser. If it’s longer than the purpose needs, shorten it in the tag’s settings. For localStorage, say how long you keep it, since it may never expire on its own.
  5. Name the companies. Say which provider sets or reads each cookie, without falling back on partners or third parties.
  6. Keep one list. Make the cookie policy show the consent tool’s list, or update both together, and add a step to your release checklist for every new tag.
  7. Re-scan. Clear cookies and storage, and run a scan again. The finding should clear once every name is listed, in the right category, with a lifetime the real one doesn’t exceed.

Whether a given cookie fits the statistics or appearance exception is a question for your legal adviser. Peeky reports what it saw stored and what your list said.

Questions

What should a cookie policy include in the UK?

The ICO's guidance lists four things: which storage and access technologies you use, what for, which third parties store or read information through them, and how long each lasts, such as the duration of each cookie.

It also says not to hide companies behind vague words like partners or third parties. A table with name, provider, purpose and expiry covers it.

Do I need a cookie policy if I only use analytics?

You need the information one holds. Since 5 February 2026, PECR lets some statistics cookies run without consent, but only if visitors get clear and comprehensive information about the purpose and a simple, free way to object.

So an analytics cookie your list leaves out can't use that exception. It needs consent like any other non-essential cookie.

Does the ICO set a maximum cookie lifetime?

No. The ICO says PECR doesn't fix a duration, and that yours must be proportionate to what you want to achieve and limited to what's necessary. It gives 90 days for a preference cookie as an example, where that suits the service.

Whatever you choose, the list should state it, and the real cookie shouldn't outlive it.

Can I trust my consent tool's cookie categories?

Check them. The ICO's audit steps include reviewing any automatic categorisation and whether it's correct, and confirming the purpose of each technology yourself.

Consent tools often file cookies they don't recognise under a default heading. Peeky flags a known analytics or advertising cookie that ends up under Necessary.

What does the ICO say about cookie policies?

That the information must be clear and comprehensive, written for your audience, and easy to find. The ICO reads clear and comprehensive as the same kind of information the UK GDPR asks for when you process personal data.

Peeky checks the list part of that. It accepts every cookie on your public pages, then compares what was stored with what your list says. How a scan works has the full path.

Filed with

The rule

Privacy and Electronic Communications (EC Directive) Regulations 2003 (PECR), reg. 6 and Schedule A1, paras. 2, 5 and 6, as substituted and inserted by the Data (Use and Access) Act 2025, s. 112 and Sch. 12

Read the rule (Privacy and Electronic Communications (EC Directive) Regulations 2003 (PECR), reg. 6 and Schedule A1, paras. 2, 5 and 6, as substituted and inserted by the Data (Use and Access) Act 2025, s. 112 and Sch. 12)

A case

Roularta Media Group (knack.be and levif.be)

APD (Belgium, EU data protection authority), 2022

Read the decision (Roularta Media Group (knack.be and levif.be))

Your site

Is your website affected? Join now to find out.

Join now

Sources

The law

  1. PECR 2003, regulation 6 (as substituted 5 February 2026), legislation.gov.uk
  2. PECR 2003, Schedule A1 (storage and access exceptions), legislation.gov.uk
  3. Data (Use and Access) Act 2025, section 112 (substitutes PECR regulation 6), in force 5 February 2026
  4. Data (Use and Access) Act 2025, Schedule 12 (inserts PECR Schedule A1), in force 5 February 2026
  5. UK GDPR, Article 5 (principles, including storage limitation)
  6. UK GDPR, Article 12 (transparent information)
  7. UK GDPR, Article 13 (information to be provided, including the storage period in Art. 13(2)(a))
  8. The Data (Use and Access) Act 2025 (Commencement No. 9 and Transitional and Saving Provisions) Regulations 2026 (SI 2026/1015), provisions in force 30 September 2026

Guidance

  1. ICO, Guidance on the use of storage and access technologies (last updated 29 April 2026)
  2. ICO, Guidance on the use of storage and access technologies: What are the PECR rules? (clear and comprehensive information)
  3. ICO, Guidance on the use of storage and access technologies: What are the exceptions?
  4. ICO, Guidance on the use of storage and access technologies: How do we comply with the PECR rules? (information, duration and audits)
  5. EDPB (EU), Report of the work undertaken by the Cookie Banner Taskforce, adopted 17 January 2023 (type I practice, paras. 26 to 30)

Decisions and cases

  1. Autorité de protection des données (Belgium, EU), Décision quant au fond 85/2022 of 25 May 2022 (Roularta Media Group)
  2. Autorité de protection des données (Belgium, EU), Décision quant au fond 12/2019 of 17 December 2019 (a website's cookie transparency and consent)

Further reading

  1. GOV.UK, Information Commission succeeds the ICO as UK's data protection regulator (30 September 2026)
  2. Bollinger, Kubicek, Cotrini and Basin, Automating Cookie Consent and GDPR Violation Detection, 31st USENIX Security Symposium, 2022

Last checked against the source:

For information only. Not legal advice.