
Legitimate interest cookies: tracking on after Reject all
At a glance
EU-22MediumePrivacy Art. 5(3); GDPR Arts. 6(1)(a) and (f) and 21; EDPB Cookie Banner Taskforce report (2023), paras. 20 to 25; EDPB Guidelines 1/2024 on legitimate interest, para. 115
Peeky clicks Reject all, then checks whether any purpose, vendor or switch stays on under legitimate interest, so a visitor would have to say no a second time.
Last checked against the source:
The rule
EU law has no legitimate-interest route for cookies. The rule about the device and the GDPR’s list of lawful bases sit in two different texts, and a banner that blends them is where this check starts.
Article 5(3) of the ePrivacy Directive says that storing information on a user’s device, or reading information already there, “is only allowed on condition that the subscriber or user concerned has given his or her consent, having been provided with clear and comprehensive information”. It names two exceptions: storage or access “for the sole purpose of carrying out the transmission of a communication”, and what is “strictly necessary in order for the provider of an information society service explicitly requested by the subscriber or user to provide the service”. Legitimate interest isn’t one of them.
Legitimate interest comes from the GDPR. Article 6(1)(f) allows processing that “is necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject”. It covers what a company does with personal data. Whether anything may go on the device in the first place is Article 5(3)’s question. Article 21 gives people the right to object to that processing. For direct marketing, which “includes profiling to the extent that it is related to such direct marketing”, an objection ends it: the data “shall no longer be processed for such purposes” (Art. 21(2) and (3)). The right must be “explicitly brought to the attention of the data subject” and shown “clearly and separately from any other information” (Art. 21(4)).
The European authorities described this banner design in the Cookie Banner Taskforce report, adopted by the EDPB on 17 January 2023, as type H: legitimate interest claimed for a list of purposes. By its own disclaimer the report sets a minimum threshold, and national guidance stays fully applicable.
On the second layer of these banners, “a distinction is made between the refusal given to read/write operations and the potential objection to further processing presented as falling within the legitimate interest of the data controller” (para. 21). Controllers claimed legitimate interest for purposes such as “Create a personalised content profile” or “Select personalised ads”, “whereas it could be considered that no overriding legitimate interest would exist”, and putting it “in the deeper layers of the banner” could confuse “users who might think they have to refuse twice in order not to have their personal data processed” (para. 22). The members confirmed that “the legal basis for the placement/reading of cookies pursuant to Article 5 (3) cannot be the legitimate interests of the controller”, and that where Article 5(3) isn’t met, “the subsequent processing cannot be compliant with the GDPR” (para. 24).
The EDPB’s Guidelines 1/2024 on legitimate interest, adopted on 8 October 2024 and still published as the version for public consultation, land in the same place. Where Article 5(3) requires consent for tracking, consent “will likely constitute the appropriate legal basis both for storing and gaining access to information already stored on the user’s device and for the subsequent processing of personal data, thus normally precluding reliance on Article 6(1)(f) in this context” (para. 115). The Court of Justice said something close in Meta Platforms (C-252/21, 4 July 2023): a social network’s user “cannot reasonably expect” their data to be processed “without his or her consent, for the purposes of personalised advertising” (para. 117, as the EDPB quotes it).
National authorities put it more bluntly. The CNIL’s cookie FAQ (question 33) separates the two steps and concludes that “aucun traceur non essentiel ne peut être déposé sans consentement préalable de la personne concernée”: no non-essential tracker may be placed without the person’s prior consent, even when the interface names legitimate interest. The Garante’s guidelines of 10 June 2021 (section 5) say that “in nessun caso”, in no case, can a controller invoke legitimate interest to justify cookies or other tracking tools, and add that its checks had found sites doing just that. Germany’s data protection conference, in its guidance for digital services (version 1.2, November 2024, paras. 68 and 69), says the German cookie rule allows only consent or one of its two exceptions, and that a balancing test under Article 6(1)(f) never meets the strictly necessary exception automatically. Swapping the legal basis named in a privacy notice is “nicht ausreichend”, not enough.
Many banners that mention legitimate interest run IAB Europe’s Transparency and Consent Framework (TCF), an industry standard that passes the visitor’s choices to advertising vendors in a coded “TC string”. Version 2.2, which consent tools and vendors had to put in place before 20 November 2023, made purposes 3 to 6 consent only: building profiles and using them for personalised ads and content. It kept legitimate interest as an option for purposes 2 and 7 to 11, such as choosing ads from limited data and measuring ad performance, and it leaves a publisher’s own legitimate interests outside its policies. IAB Europe’s own audit check for a Reject all button asks only whether every consent signal is off, so legitimate-interest signals left on still pass it. In IAB Europe (C-604/22, 7 March 2024) the Court of Justice confirmed that the TC string “contains information concerning an identifiable user and therefore constitutes personal data”.
Cookie rules are enforced under each Member State’s own law implementing Article 5(3). On the GDPR side, Article 83(5) puts Article 6 (point (a)) and the rights in Articles 12 to 22, the right to object among them (point (b)), in the upper fine tier: up to EUR 20 million or 4% of worldwide annual turnover, whichever is higher.
What PeekWell checks and how
EU-22 asks one question: after a visitor clicks Reject all, is anything still switched on under legitimate interest, so that saying no takes a second step? The scan answers it from the choices your banner records and from what the banner says.
The scan is automated. It opens your public pages the way a first-time visitor’s browser would and clicks Reject all. On another run it accepts, then reopens the cookie settings and takes the consent back. After each refusal it reads three things:
- The framework’s record. On pages that run the IAB framework, it listens for the consent tool’s update through the framework’s public interface, the
addEventListenercall that TCF 2.2 requires every consent tool to answer, and decodes the TC string as a cross-check. It’s a finding if any purpose from 2 or 7 to 11, any vendor or the publisher is still marked on by legitimate interest, or if there’s any legitimate interest at all for purposes 1 or 3 to 6, which the framework itself no longer allows. - The settings and vendor lists. It opens the settings layer and every vendor list and reads each switch. A legitimate-interest or “object” switch still on after the refusal is a finding.
- The banner’s words. If the banner or its settings give legitimate interest as the basis for storing or reading information on the device, or for advertising, profiling, personalisation or audience measurement, with an objection step apart from the refusal, that’s a finding too. When the wording is the only evidence, the report marks the finding as AI-assisted, because reading text takes judgement.
The framework’s special purposes, such as security and fraud prevention, carry no signal a visitor can switch off, and the scan doesn’t count them. The check passes when nothing is on by legitimate interest after the refusal and the banner doesn’t offer legitimate interest as a basis for storage or tracking. Legitimate interest named only in your privacy policy, for processing that stores nothing on the device and reads nothing from it, such as fraud checks on your own server or network security, isn’t what this check looks for.
Two other checks sit next to this one. Consent switches that start on before anyone chooses are EU-21. Trackers that keep loading after Reject all are EU-02, and EU-22 leaves them to it. The UK version, which allows for the UK’s statistics and appearance exceptions, is UK-20.
A site with no banner, or no way to refuse, still gets an answer. If any run records non-essential storage, EU-22 is a finding, because there’s no refusal a visitor could make. If nothing non-essential shows up at all, the check passes and says which runs showed that.
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. A legitimate-interest signal shows what your consent tool tells vendors they may do. Whether a vendor then processes data on its own servers can’t be seen from a browser. 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
Sweden’s IMY ruled on this design on 28 April 2025. The decision, on Aller Media AB, looked at the banner on recept.se as it stood on 21 May 2021. The first layer had a consent button and a link to the purposes, and said visitors could object where legitimate interest was used, but there was no way to object on that layer. In the words of the English translation the EDPB published, “a data subject first had to refuse consent and then go ahead and find the option to object to processing for certain purposes.” Aller said its consent platform provider had recommended both legal bases. IMY replied that a controller can’t hand its responsibility for a legal basis to a supplier’s recommendation, found no legitimate interest had been shown, and issued a reprimand. By then the company had changed its banner and named consent as its basis.
Spain’s AEPD dealt with the same pattern on a smaller site, run by Chatwith.io Worldwide, S.L., where lawyers advertise. In the vendor list, more than half of about 130 vendors had the legitimate-interest box ticked by default, and objecting meant unticking them “una a una”, one by one, down the whole list. There was an Accept all button but none to reject or object to everything. The AEPD called this a deceptive design that overloads the visitor and fined €5,000 under Article 5(1)(a), alongside separate fines for the privacy notice and under Spain’s cookie law. It said it wasn’t deciding whether the legitimate interests could be justified, so the fine rests on the design alone.
The TC string is personal data, and it’s shared with the data brokers and ad platforms down the chain, so a legitimate-interest yes the visitor never gave travels with it. In the taskforce’s view, storage without valid consent also leaves whatever processing follows without a footing (para. 24). Anyone can see the problem from outside, too. It takes one click on Reject all and a look at the vendor list.
Smaller companies and larger companies
The rule has no size threshold. What differs is how the second step ends up on the banner.
In a smaller company the banner usually comes from a consent tool set up once and left on its defaults, and switching on the IAB setup brings a vendor list with hundreds of entries. The Chatwith.io decision shows how that looks: Accept all at the top, and a long list where legitimate interest is ticked unless you untick each line. The Aller decision covers the other half. The company did what its consent tool provider recommended, and the authority still held the company responsible.
In a larger company, legitimate interest tends to be a revenue decision. A publisher selling advertising through the framework can claim legitimate interest for its own purposes in the publisher segment, which the TCF’s policies don’t cover, and partners can claim it for measurement. The Belgian authority looked at the framework itself and found in February 2022 that the legal grounds it offered for adtech vendors’ later processing were inadequate. Its summary of the May 2025 appeal ruling, which kept the fine, doesn’t say what became of the ban on legitimate interest. A German court looked at the publisher’s side. In a case the consumer centres’ federal body brought against the operator of focus.de, the Munich Regional Court held on 29 November 2022 that tracking cookies for cross-domain analysis and marketing weren’t strictly necessary for a news site. Funding the site through advertising, or what TCF 2.0 prescribes, didn’t change that; the court called these “lediglich […] subjektive Interessen”, only the publisher’s own interests.
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
Aller Media AB (recept.se)
After a complaint, IMY examined the cookie banner on recept.se as it was on 21 May 2021. The first layer said visitors could object where legitimate interest was used, but offered no way to do it there; to refuse all processing, a visitor had to refuse consent and then find the option to object. The banner claimed legitimate interest for profiling and precise geodata. The company said its consent platform provider had recommended using both bases. IMY found it had not shown a legitimate interest, held that a supplier's advice does not shift that responsibility, and issued a reprimand.
Read the IMY (Sweden) publication about Aller Media AB (recept.se)IAB Europe (Transparency and Consent Framework)
The Belgian authority found that the framework processes personal data through the TC string, that IAB Europe is a controller for it, and that the legal grounds the framework offered for adtech vendors' later processing were inadequate. Its orders included a ban on legitimate interest as a basis for processing by the organisations taking part. On 14 May 2025 the Market Court annulled the decision on procedural grounds, endorsed the authority's reasoning and confirmed the fine, while rejecting the finding that IAB Europe is a joint controller for processing that takes place entirely within the OpenRTB protocol.
Read the APD (Belgium) publication about IAB Europe (Transparency and Consent Framework)Operator of focus.de (name withheld in the published judgment)
In a case brought by the federal umbrella body of Germany's consumer centres, the court ordered the operator of the news site focus.de, whose consent tool followed the IAB framework (TCF 2.0), to stop storing or reading information on visitors' devices for cross-domain tracking for analysis and marketing without informed, freely given consent. It held those cookies were not strictly necessary for a news site, and that funding the site through advertising, or what TCF 2.0 prescribes, did not make them so. Those were only the publisher's own interests.
Read the Landgericht München I (Germany) publication about Operator of focus.de (name withheld in the published judgment)
Smaller companies
Chatwith.io Worldwide, S.L.
On the company's website, where lawyers advertise, more than half of about 130 vendors in the consent tool's vendor list had the legitimate-interest box ticked by default, and a visitor could only object one vendor at a time, down the whole list. There was an Accept all button but nothing to reject or object to everything. The AEPD treated this as a deceptive design and fined €5,000 for it under GDPR Art. 5(1)(a), with €2,000 for the privacy notice and €5,000 under Spain's cookie law, and ordered changes within a month. It said it was not deciding whether the legitimate interests themselves could be justified.
Read the AEPD (Spain) publication about Chatwith.io Worldwide, S.L.
How to fix it
The aim is a Reject all that leaves nothing on, in one click. These steps fit most consent tools.
- Refuse, then look. Open the site in a private window, click Reject all, then open the settings and the vendor or partner list. Any switch still on under “legitimate interest” or “object” is what a scan will report. On a site that runs the TCF, a developer can check the record in the browser console with
__tcfapi('addEventListener', 2, callback)and readpurpose.legitimateInterests,vendor.legitimateInterestsandpublisher.legitimateInterestsonceeventStatusisuseractioncomplete. - Turn legitimate interest off for every purpose. In the consent tool’s IAB settings, remove legitimate interest for purposes and vendors, or set publisher restrictions: “require consent” for vendors that registered a purpose as flexible, “not allowed” for the rest. Under TCF 2.2, purposes 1 and 3 to 6 can’t carry legitimate interest at all.
- Move your own purposes to consent. If the publisher segment lists your own purposes on legitimate interest, such as content personalisation or measurement that relies on cookies, switch them to consent.
- Make Reject all clear everything. If the tool keeps a legitimate-interest layer, set Reject all to object to it as well, so one click leaves nothing on. Then check the same after withdrawing consent through the settings link.
- Fix the words. Take “legitimate interest” out of the banner wherever it describes cookies, advertising, profiling, personalisation or audience measurement.
- Keep legitimate interest where it fits. Processing that stores nothing on the device and reads nothing from it, such as fraud checks on your own server, can still rest on Article 6(1)(f). Describe it in the privacy policy and tell people how to object, as Article 21(4) asks.
- Re-scan. Clear cookies and storage, reload, and run a scan again. The finding should go once Reject all leaves nothing on.
Whether a particular use of data can rest on legitimate interest is a question for your legal adviser. Peeky reports what the banner recorded and what it said.
Questions
What are legitimate interest cookies?
It's a label some cookie banners give to tracking that stays on unless you object, instead of staying off until you agree. EU law has no such category. Storing or reading a cookie needs consent unless it's strictly necessary, and the EDPB's cookie banner taskforce confirmed that the basis for placing or reading cookies cannot be the legitimate interests of the controller.
Can a website use legitimate interest instead of consent under the GDPR?
For some processing, yes. For cookies and other tracking on the device, no. GDPR Article 6(1)(f) is a basis for what a company does with personal data, but the ePrivacy rule on the device comes first, and it only allows consent or two narrow exceptions.
The EDPB's guidelines on legitimate interest add that where tracking needs consent, consent will normally be the basis for the later processing too.
What did TCF 2.2 change for legitimate interest?
Since 20 November 2023, vendors in the IAB framework can only use consent for purposes 3 to 6, the profiling and personalised advertising and content purposes. Legitimate interest is still on offer for purposes 2 and 7 to 11, such as measuring ad performance, and publishers' own purposes sit outside the framework's policies.
That's framework policy, not the law. A site can run TCF 2.2 and still make visitors refuse twice.
Is running the IAB TCF enough on its own?
No. IAB Europe's own audit check for Reject all only asks whether every consent signal is off, so legitimate-interest signals can stay on and still pass. Its FAQ for version 2.2 also says the framework doesn't require a reject button on the first layer, and points publishers to their national authority's rules. Peeky reads the framework's record and holds it against the law.
Isn't an object switch enough, since people have a right to object?
The right to object in GDPR Article 21 applies to processing that already rests on legitimate interest. It doesn't make cookies on legitimate interest possible in the first place. The taskforce also found that splitting refusal and objection across layers can leave people thinking they have to refuse twice. How a scan works shows where Peeky looks.
Filed with
The rule
ePrivacy Directive 2002/58/EC, Art. 5(3), as amended by Directive 2009/136/EC
Read the rule (ePrivacy Directive 2002/58/EC, Art. 5(3), as amended by Directive 2009/136/EC)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, Arts. 6, 21 and 83
Guidance
- EDPB, Report of the work undertaken by the Cookie Banner Taskforce, adopted 17 January 2023 (type H, paras. 20 to 25)
- EDPB, Guidelines 1/2024 on processing of personal data based on Article 6(1)(f) GDPR, version 1.0, adopted 8 October 2024 (version for public consultation)
- CNIL, Cookies et autres traceurs: FAQ, question 33 on legitimate interest (page dated 29 April 2026)
- Garante per la protezione dei dati personali, Linee guida cookie e altri strumenti di tracciamento, 10 June 2021, section 5
- Datenschutzkonferenz, Orientierungshilfe für Anbieter:innen von digitalen Diensten (OH Digitale Dienste), version 1.2, November 2024, paras. 68 and 69
Decisions and cases
- AEPD (Spain), resolution of sanctioning procedure PS/00080/2023 (Chatwith.io Worldwide, S.L.), in Spanish
- IMY (Sweden), Tillsynsbeslut Aller Media AB, IMY-2023-16452, 28 April 2025 (in Swedish, the authentic version)
- EDPB register, IMY final decision on Aller Media AB, unofficial English translation
- APD (Belgium), IAB Europe held responsible for a mechanism that infringes the GDPR (2 February 2022)
- APD (Belgium), The Market Court rules in the IAB Europe case (14 May 2025)
- LG München I, Endurteil of 29 November 2022, 33 O 14776/19 (cookies on focus.de), Bavarian state law portal, in German
Further reading
- Court of Justice of the EU, press release 113/23 on Case C-252/21 Meta Platforms and Others (4 July 2023)
- Court of Justice of the EU, press release 44/24 on Case C-604/22 IAB Europe (7 March 2024): the TC string is personal data
- IAB Europe, TCF v2.2 FAQ, updated 27 July 2023
- IAB Europe, Transparency and Consent Framework Policies (purposes and allowable lawful bases)
- IAB Europe, Controls Catalogue for TCF Policies version 5.0.a (check 2 on Reject all, check 9 on purposes 1 and 3 to 6)
- IAB Tech Lab, Consent Management Platform API v2 (addEventListener, eventStatus and legitimate-interest signals)
Last checked against the source:
For information only. Not legal advice.
