
Cookie policy GDPR: missing and mislabelled cookies
At a glance
EU-24MediumePrivacy Art. 5(3) ('clear and comprehensive information'); GDPR Arts. 5(1)(a) and (e), 12 and 13(2)(a); CJEU C-673/17 Planet49 (2019); EDPB Cookie Banner Taskforce report (2023), paras. 26 to 30
Peeky accepts every cookie, then sets what your site really stores against your cookie list: each name, its purpose and its lifetime.
Last checked against the source:
The rule
Storing information on a visitor’s device, or reading it, is allowed only if the visitor “has given his or her consent, having been provided with clear and comprehensive information, in accordance with Directive 95/46/EC, inter alia, about the purposes of the processing.” The only exceptions are storage or access needed to carry a communication, or “strictly necessary in order for the provider of an information society service explicitly requested by the subscriber or user to provide the service.”
The Court of Justice said what that information covers in Planet49 (C-673/17, 1 October 2019). In the words of its press release, the information a site must give “includes the duration of the operation of cookies and whether or not third parties may have access to those cookies.”
Where cookies collect personal data, the GDPR’s transparency rules apply as well. Article 13(2)(a) asks for “the period for which the personal data will be stored, or if that is not possible, the criteria used to determine that period”. Article 12(1) asks for information “in a concise, transparent, intelligible and easily accessible form, using clear and plain language”. Article 5(1)(a) requires processing “in a transparent manner”, and Article 5(1)(e) storage limitation: data “kept in a form which permits identification of data subjects for no longer than is necessary”.
On lifetimes, the Article 29 Working Party’s Opinion 04/2012 says a cookie exempt from consent “should have a lifespan that is in direct relation to the purpose it is used for, and must be set to expire once it is not needed”. There’s no single EU maximum. For consent-free audience measurement the CNIL gives 13 months as its example of a fitting lifetime, not extended on each visit. The AEPD recommends cutting the lifetime of persistent cookies to “al mínimo necesario” (the minimum necessary), and the Garante wants the list of third parties “costantemente aggiornato” (kept constantly up to date).
“Some controllers classify as ‘essential’ or ‘strictly necessary’ cookies and processing operations which use personal data and serve purposes which would not be considered as ‘strictly necessary’” (para. 26). The taskforce discussed “the responsibility of website owners to maintain such lists, and to provide them to the competent authorities where requested and to demonstrate the « essentiality » of the cookies listed” (para. 28). It added that scanning tools “do not allow to check the nature of the cookies but only to list the cookies placed in order to ask the website owner to provide documentation on their purposes” (para. 29).
Cookies aren’t the only thing covered. The EDPB’s Guidelines 2/2023 say Article 5(3) applies to information kept in the browser, “such as cookies, local storage, WebSQL”, once that information or anything derived from it is accessed (para. 44).
Enforcement runs on two tracks. The information duty for cookies is enforced under each country’s ePrivacy law. The GDPR’s transparency and storage limitation rules sit in the upper fine tier of Article 83(5). In the decisions we found, an inaccurate cookie list has been fined as part of a wider cookie case, not on its own.
What PeekWell checks and how
EU-24 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 policy, and the details view of your consent tool. Layouts vary and some are in other languages, so the reading is AI-assisted. The comparison itself follows fixed rules.
The check fails on any of four things, numbered D1 to D4 in the report:
- D1: a cookie or storage name set by a non-essential or unrecognised service is missing from the declaration. A declared pattern such as
_ga_<id>or_ga_*covers the names it stands for. - D2: a known analytics, advertising, session-recording, social or marketing name is listed under strictly necessary or essential.
- D3: a cookie lives more than one and a half times its declared lifetime, and at least a day longer. A cookie declared as a session cookie that persists counts.
- D4: non-essential cookies or storage are set and there’s no declaration 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 names the disagreement. 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%.
A cookie table is a declaration, not a claim, so EU-05, the check on promises in your privacy policy, never decides it. EU-04 asks whether your policy names the companies your pages contact, and EU-01 whether anything loads before the visitor answers. The UK version is UK-21.
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 is filed 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
The clearest decision is the Belgian APD’s on Roularta Media Group, of 25 May 2022. Its inspectors found that only two cookies on knack.be and levif.be, the consent cookie and a PHP session cookie, were strictly necessary. The cookie policy used different category names from the consent tool, which the authority said “accroît l’ambiguïté” (adds to the ambiguity). It gave no concrete storage periods. And some cookies lived for years, one for 90,000 days. The authority added that correcting the policy afterwards can’t cancel out the earlier failing. The €50,000 fine covers several findings. A sister decision against the Rossel group, 103/2022, was annulled by the Market Court on 22 February 2023. We found no annulment notice on the Roularta decision as published, but couldn’t confirm whether it was appealed.
An earlier Belgian case shows how a list drifts. On a legal news site, inspectors found Google Analytics, Tag Manager and AdSense, while the cookie list the company sent didn’t match. The company said its consent tool had failed to return a correct list. Ireland’s DPC found the same pattern in its 2020 sweep of 38 websites: labelling cookies necessary when they plainly weren’t was “extremely common”, some controllers left Facebook pixels out of the cookie lists they sent, and one site had a “strictly necessary” cookie with a lifespan of “forever”. It called a template cookie policy “a futile and cosmetic exercise”.
The list matters beyond the page it sits on. A tracker filed under Necessary usually loads before anyone answers the banner, because that’s what the category means to the consent tool, and then it’s an EU-01 problem too. A cookie missing from the list can’t be refused, because the visitor never saw it. Regulators also read the list the way a scan does: the APD used a Cookiebot report and manual research to classify Roularta’s cookies, and the AEPD sorted Vodafone’s one by one.
Smaller companies and larger companies
The rule has no size threshold. What differs is how the list falls behind.
In a smaller company the declaration is usually produced by the consent tool’s own scan, monthly or less often, and published as is. A new plugin, chat widget or ad pixel arrives between scans and isn’t listed. A tool may also file unrecognised cookies as Unclassified or Necessary by default, and nobody looks again. The legal news site’s case turned up that kind of gap between the tool’s list and the real cookies.
In a larger company the problem is more often two lists that disagree. The consent tool’s categories come from the vendor or the ad industry’s framework, while the cookie policy is written by someone else in plainer words. That was one of the Roularta findings. With many teams adding tags, lifetimes are left at each vendor’s default, which is one way cookies end up lasting for 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.

Larger companies
Roularta Media Group (knack.be and levif.be)
Inspectors found that only two cookies on the sites, OptanonConsent and PHPSESSID, were strictly necessary. The cookie policy used category names that differed from the consent tool's, gave no concrete storage periods and said only that retention depended on each cookie. Some cookies lived 720 to 1,698 days, and one, OB-USER-TOKEN, 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) publication about Roularta Media Group (knack.be and levif.be)Vodafone España, S.A.U.
AEPD inspectors loaded the home page without touching the banner and sorted every cookie they found by purpose, listing performance cookies, targeting cookies such as _gcl_au, IDE and demdex, and third-party cookies they couldn't classify. The agency fined the company under Article 22.2 of the Spanish e-commerce law (LSSI) for the deficiencies in its cookie policy while non-technical cookies were used without consent, and dismissed its request for reconsideration.
Read the AEPD (Spain) publication about Vodafone España, S.A.U.
Smaller companies
Legal news website (operator not named in the published decision)
Inspectors found Google Analytics, Google Tag Manager and Google AdSense on the site, but the cookie list the company submitted didn't match. The company said its consent tool had failed to return a correct list of the cookies placed. Early versions of the cookie statement gave no purpose or retention period per cookie. The fine also covers analytics cookies set without consent and other gaps in the privacy statement.
Read the APD (Belgium) publication about Legal news website (operator not named in the published decision)
How to fix it
If your list comes from a hosted consent tool, steps 2 and 5 do most of the work.
- Make the real list. Open the site in a fresh browser profile, accept everything, and browse a few main pages. In the developer tools, copy every cookie with its domain and expiry, and every localStorage and sessionStorage name.
- Rescan in the consent tool and compare. Run the tool’s scan again and set its list against yours. Add every missing cookie and storage name, with its provider.
- File each one under its real purpose. Keep Necessary for what the site can’t work without, such as the consent cookie, a session or a basket. Analytics, advertising, session recording and social cookies don’t belong there.
- Give each one its real lifetime. Copy the expiry from the browser, not the vendor’s brochure. If a lifetime is longer than the purpose needs, shorten it in the tag’s settings.
- Keep one list. Make the cookie policy show the consent tool’s list, or copy it across after every change, so the two can’t drift apart.
- Add a step to your release checklist. Before any new tag, plugin or script goes live, add its cookies to the list.
- 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 cookie is strictly necessary in a borderline case is a question for your legal adviser. Peeky reports what it saw stored and what your list said.
Questions
What must a cookie policy include under the GDPR?
Enough for a visitor to know what is stored on their device and why. The ePrivacy Directive asks for clear and comprehensive information about the purposes, and the Court of Justice said in Planet49 that this includes how long cookies last and whether third parties can access them.
The GDPR adds the storage period, in Article 13(2)(a). In practice that means each cookie, or each group of similar cookies, with its purpose, its provider and its lifetime.
Is a cookie declaration the same as a cookie policy?
Near enough. A cookie declaration is usually the table of cookies itself, often generated by a consent tool, while a cookie policy is the page around it that explains what cookies are and how to change your choice.
EU-24 reads both, along with the consent tool's own details view, and treats whatever lists your cookies as the declaration.
Do I need a separate cookie policy and privacy policy?
No, the law doesn't ask for two pages. Many sites put the cookie list in the privacy policy, and that works if visitors can find it.
What matters is that the list is complete and right. Peeky reads a cookie section in the privacy policy the same way as a separate cookie page.
How long can a cookie last?
No EU text sets one maximum. The Article 29 Working Party said a cookie exempt from consent should have a lifespan in direct relation to its purpose. For consent-free audience measurement, the CNIL gives 13 months as its example.
Whatever the lifetime, the declaration has to state it. Peeky compares the declared lifetime with the real one set in the browser.
Can analytics cookies be listed as necessary?
Not as a rule. The Cookie Banner Taskforce found sites filing cookies as essential or strictly necessary when they weren't, and said the website owner has to show that each listed cookie really is essential.
A few national rules exempt narrow first-party audience measurement, such as the CNIL's. A Google Analytics or advertising cookie under Necessary still fails this check.
How do I audit my cookie list?
Visit your site in a fresh browser profile, accept everything, and copy every cookie and storage name from the developer tools, with each cookie's expiry. Then set that list against your consent tool's list and your cookie policy, row by row.
Peeky does the same comparison on each scan and names what's missing. How a scan works has the full path.
Filed with
The rule
ePrivacy Directive 2002/58/EC, Art. 5(3), as amended by Directive 2009/136/EC, Art. 2(5)
Read the rule (ePrivacy Directive 2002/58/EC, Art. 5(3), as amended by Directive 2009/136/EC, Art. 2(5))A case
Roularta Media Group (knack.be and levif.be)
Read the decision (Roularta Media Group (knack.be and levif.be))Sources
The law
- Directive 2009/136/EC, Official Journal L 337, Art. 2(5) (replaces Art. 5(3) of Directive 2002/58/EC)
- Regulation (EU) 2016/679 (GDPR), Official Journal L 119
Guidance
- Article 29 Working Party, Opinion 04/2012 on Cookie Consent Exemption (WP194), adopted 7 June 2012
- EDPB, Report of the work undertaken by the Cookie Banner Taskforce, adopted 17 January 2023 (type I practice, paras. 26 to 30)
- EDPB, Guidelines 2/2023 on the technical scope of Art. 5(3) of the ePrivacy Directive, version 2.0, adopted 7 October 2024
- CNIL, Cookies: solutions pour les outils de mesure d'audience (4 July 2025)
- AEPD (Spain), Guía sobre el uso de las cookies, updated May 2024
- Garante per la protezione dei dati personali, Linee guida cookie e altri strumenti di tracciamento, 10 June 2021
Decisions and cases
- Autorité de protection des données (Belgium), Décision quant au fond 85/2022 of 25 May 2022 (Roularta Media Group, Knack and Le Vif)
- Autorité de protection des données (Belgium), Décision quant au fond 12/2019 of 17 December 2019 (fine on a website's transparency and consent obligations for cookies)
- Gegevensbeschermingsautoriteit (Belgium), Beslissing ten gronde 103/2022 of 16 June 2022 (Rossel group), annulled by the Market Court on 22 February 2023
- AEPD (Spain), decision on the request for reconsideration RR/00418/2023 in procedure PS/00567/2022 (Vodafone España, S.A.U.)
Further reading
- Data Protection Commission (Ireland), Report by the DPC on the use of cookies and other tracking technologies, 6 April 2020
- Court of Justice of the European Union, press release 125/19 on Case C-673/17 Planet49 (1 October 2019)
- 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.
