
Cookie preferences: withdraw consent as easily as giving it
At a glance
EU-20MediumGDPR Arts. 4(11) and 7(3); ePrivacy Art. 5(3); EDPB Guidelines 05/2020, paras. 113 to 116; EDPB Cookie Banner Taskforce report (2023), paras. 31 to 35
Peeky says yes to your cookie banner, then looks on each page for a link or icon that brings the choices back, and counts the clicks it takes to say no again.
Last checked against the source:
The rule
The right to take consent back is written into the GDPR, and the ePrivacy Directive brings it to cookies. The law sets one standard and leaves the design to you: withdrawing has to be as easy as consenting was.
Article 7(3) of the GDPR reads: “The data subject shall have the right to withdraw his or her consent at any time.” It requires that people are told this before they consent, and it ends: “It shall be as easy to withdraw as to give consent.” Article 4(11) defines consent as a “freely given, specific, informed and unambiguous indication of the data subject’s wishes”.
Article 5(3) of the ePrivacy Directive allows information to be stored on, or read from, a visitor’s device only if the visitor “has given his or her consent, having been provided with clear and comprehensive information”. The European authorities’ cookie banner taskforce agreed that this reference to consent takes in both the GDPR’s definition in Article 4 and its conditions in Article 7 (para. 33). So the withdrawal rule covers cookie consent.
The EDPB’s consent guidelines spell out what “as easy” means on a website.
The GDPR “does not say that giving and withdrawing consent must always be done through the same action” (para. 113). But “when consent is obtained via electronic means through only one mouse-click, swipe, or keystroke, data subjects must, in practice, be able to withdraw that consent equally as easily”, and consent given on a website must be withdrawable “via the same electronic interface” (para. 114). The guidelines’ example is a ticket site where consent takes one click and withdrawal takes a phone call in office hours, which does not comply (para. 115). If the withdrawal right falls short, “the consent mechanism of the controller does not comply with the GDPR” (para. 116). After a withdrawal, “the controller must stop the processing actions concerned” (para. 117).
The taskforce report, adopted by the EDPB on 17 January 2023, applies this to the cookie banner.
Under the heading “No withdraw icon”, the taskforce says: “Website owners should put in place easily accessible solutions allowing users to withdraw their consent at any time, such as an icon (small hovering and permanently visible icon) or a link placed on a visible and standardized place” (para. 32). It names “three additional cumulative conditions”: the possibility to withdraw, the ability to do it at any time, and that “withdrawal of consent must be as easy as to give consent” (para. 34). It adds that website owners “cannot be imposed a specific withdrawal solution”, so each one is judged case by case on whether withdrawing ends up as easy as consenting (para. 35).
National authorities get more concrete about the place and the label. The CNIL’s recommendation, consolidated on 16 January 2026, suggests a link such as “gérer mes cookies” that’s available at any time, or a cookie icon on every page, for example at the bottom left. It says ease “can be measured in particular by the time spent and the number of actions needed” to withdraw (our translation). The Italian Garante’s guidelines of 10 June 2021 ask for a link in the site’s footer labelled “rivedi le tue scelte sui cookie” or something similar, and suggest an icon on each page that shows the visitor’s current choices.
Spain’s AEPD, in its guide updated in May 2024, treats withdrawal as easy enough when the visitor has “acceso sencillo y permanente” (simple and permanent access) to the cookie settings. The German authorities’ guidance for digital services, version 1.2 of November 2024, rules out making people open the privacy policy and scroll to find the way to withdraw. It notes that many sites show “einen stets sichtbaren Direktlink oder ein Icon” (an always visible direct link or an icon), and accepts a link that goes straight to the right spot in the policy (para. 62). The Belgian authority’s cookie checklist asks for a clearly visible link or button to withdraw “en un seul clic”, in a single click, and for the withdrawal to take effect.
On penalties, GDPR Article 83(5)(a) places the “conditions for consent” of Article 7 in the upper fine tier, up to EUR 20 million or 4% of worldwide annual turnover. Authorities don’t all use the same law for cookies: the AEPD’s Techpump decision applied Spain’s information society services law, while the Belgian and Hungarian decisions listed on this page applied the GDPR.
What PeekWell checks and how
EU-20 asks one question: once a visitor has said yes, can they take it back from any page, as easily as they gave it? The scan answers it from your pages as a visitor sees them, without signing in.
The scan is automated. In a clean browser it accepts your banner with the one action the first screen offers for saying yes, usually Accept all. Then it looks for a control that reopens the choices on your home page and on two other page templates, and notes each control’s label and where it sits. From a content page it follows the most visible one, counts the actions it takes to switch everything non-essential off and save, and takes screenshots of the control and of the reopened choices.
EU-20 is strictly pass or fail. It passes only when all four of these hold, and the finding names each one that doesn’t:
- W1. On every page template sampled, a control that reopens the choices is in view: a floating icon, or a link or button in the shared header, footer or menu whose text names cookies, consent or privacy choices. A link that sits only inside the text of the privacy or cookie policy, only in an account area, or only turns up through search doesn’t count.
- W2. Once the choices are open, switching everything non-essential off and saving takes no more actions than consenting did. A Reject all or Withdraw consent button in the reopened layer meets this. Switching off five toggles and then pressing save doesn’t.
- W3. The route asks for nothing else: no account, email, form, message to the company or browser setting.
- W4. The control works. On each page tried, it opens the choices. A control that opens nothing after three tries fails here.
Two parts of this are PeekWell’s reading, not the law’s words. The taskforce asks for a link “placed on a visible and standardized place”, and reading that as the shared header, footer or menu, or a floating icon, on every page is PeekWell’s own. Counting actions against the click that gave consent is PeekWell’s measure too, taken from the EDPB’s one-click example and the CNIL’s count of actions. The pass and fail rules are PeekWell’s. The authorities judge each case on its own facts.
With no banner, or a banner with no way to refuse, the answer depends on what the site loads. If anything non-essential is stored or read on any of the scan’s passes, EU-20 is a finding at medium severity, because there’s no consent a visitor could take back. If nothing non-essential turns up at all, the check passes, and the report says which passes showed it.
EU-20 stops at the route back. Whether tracking really stops after a no or a withdrawal is the question for EU-02. EU-03 compares yes and no on the banner’s first screen, and the UK version of this check is UK-18.
The scan has limits, and the report says so. It sees the public pages it sampled, after consent given in its own browser. A way to withdraw that lives inside an app, behind a sign-in or in a message to customer service isn’t seen, and wouldn’t count for W1 anyway. 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 Passed means the expected behaviour was observed on the pages scanned. It doesn’t say the site complies.
Why it matters for a company
In its decision of 25 May 2022 on the Knack and Le Vif news sites, the Belgian authority found that withdrawing consent took more steps than giving it. On knack.be the only route was a “cookie instellingen” link in the footer, and the cookies didn’t go down after a visitor returned to the minimum choices. On levif.be the consent tool froze on a black screen. Roularta Media Group blamed a misconfigured tool, and the authority found an infringement of Article 7(3) on both sites. Knack had a footer link. The steps behind it were the problem.
Spain’s AEPD found a similar setup at Techpump Solutions S.L. in a 2024 decision. Once a visitor had accepted, the settings panel could be reached only through a link in the cookie policy, and refusing there left third-party cookies in use, so the tool “no era operativa” (wasn’t working). The AEPD fined the company €30,000 for each of three websites, a sum that also covers its other cookie findings.
The largest fine in this list turned on what the way back said. The CNIL fined Yahoo EMEA Limited €10 million on 29 December 2023, partly because a message warned yahoo.com visitors, before they could withdraw, that withdrawing would cost them access to the products and services. The Conseil d’État upheld the fine on 7 October 2025. It agreed the withdrawal failure carried “particulière gravité”, because withdrawal is “intrinsèquement lié à la liberté de consentir”, bound up with the freedom to consent.
When the Irish DPC looked at 38 websites in 2019, most of them lacked tools to vary or withdraw consent, even where a consent platform was installed. The gap reaches the consent itself. The EDPB says that if withdrawal falls short, “the consent mechanism of the controller does not comply with the GDPR” (para. 116), and every yes the banner recorded rests on that mechanism.
Smaller companies and larger companies
Size doesn’t change the question, which is the same for a local shop and a national publisher: where’s the way back, and how many clicks does it take? What size changes is how the way back goes missing.
In a smaller company the banner usually comes from a plugin or a website builder, and the way back is a setting nobody switched on, usually the consent tool’s floating icon. The theme’s footer may carry a privacy policy link but no cookie settings link, which leaves a sentence in the cookie policy as the only route back. That’s the pattern the AEPD described at Techpump.
In a larger company the way back tends to exist on the main pages and go missing elsewhere. Checkout, campaign landing pages, a help centre or a blog on a subdomain can run their own templates without the shared footer. A new consent tool can leave the old link pointing at nothing, much like the black screen on Le Vif. And a reopened layer that offers only a long list of toggles turns one click of yes into ten clicks of no.
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
Yahoo EMEA Limited
The CNIL checked yahoo.com online on 7 October 2020 and 10 June 2021. Before visitors could withdraw their consent to cookies, a message told them that withdrawing would make it impossible to access the products and services, whether or not they had a Yahoo Mail account. The CNIL fined the company €10 million on 29 December 2023 (SAN-2023-024), also for cookies set without consent. On 7 October 2025 the Conseil d'État rejected Yahoo's appeal and agreed that the withdrawal failure carried particular gravity, because withdrawal is bound up with the freedom to consent.
Read the Conseil d'État (France) publication about Yahoo EMEA LimitedRoularta Media Group (Knack and Le Vif websites)
The authority's inspectors found that withdrawing consent took more steps than giving it. On knack.be, consent could only be changed through a 'cookie instellingen' link in the footer, and the number of cookies did not fall after a visitor went back to the minimum choices. On levif.be, the consent tool froze on a black screen when a visitor tried to withdraw. The publisher put both down to a misconfigured consent tool. The authority found an infringement of GDPR Article 7(3) on both sites.
Read the Gegevensbeschermingsautoriteit / APD (Belgium) publication about Roularta Media Group (Knack and Le Vif websites)TV2 Média Csoport Zrt. (tenyek.hu and tv2play.hu)
The NAIH found that the consent framework on both sites offered no way to withdraw that was as easy as giving consent, and no easily reachable option to withdraw, either for the data the company handled itself or for data passed to third parties. The information shown did not say in an easily accessible way how consent could be withdrawn. The decision also covers the information given to visitors and the lack of information about the sites' 754 partners.
Read the NAIH (Hungary) publication about TV2 Média Csoport Zrt. (tenyek.hu and tv2play.hu)Den Blå Avis A/S (dba.dk)
In a case it opened on its own initiative in June 2020, Datatilsynet found that information about withdrawing consent was not clear enough in the site's consent solution, because it was neither highlighted nor otherwise drew visitors' attention to the option. It also found that an earlier version counted a click on a link or image as consent, and that the purposes were bundled under one button.
Read the Datatilsynet (Denmark) publication about Den Blå Avis A/S (dba.dk)38 websites in the DPC's cookie sweep (operators not named)
From August to December 2019 the DPC examined popular websites in sectors from media and retail to insurance and the public sector. Its report of 6 April 2020 found that a lack of tools for users to vary or withdraw their consent choices was a factor on most of the sites reviewed, even where a consent management platform was in use, and that many sites had no visible way to change consent settings later.
Read the Data Protection Commission (Ireland) publication about 38 websites in the DPC's cookie sweep (operators not named)
Smaller companies
Techpump Solutions S.L.
In an inspection in December 2023, the AEPD found that a visitor who had accepted cookies could get back to the settings panel only through a link in the cookie policy. Clicking Reject all there, or switching the categories off and confirming, left the third-party cookies in use, so the AEPD found the withdrawal tool did not work. The decision also covers third-party cookies used before consent and missing information in the cookie policy.
Read the AEPD (Spain) publication about Techpump Solutions S.L.
How to fix it
The goal is a way back on every page, and a single action that switches everything non-essential off. Most consent tools can do both.
- Try it as a visitor. Open the site in a private window, click Accept all, then go to a product or article page. Find the way back and count the clicks it takes to switch everything off. If it’s more than one, or you had to open the cookie policy to find it, that’s what a scan will report.
- Switch on the floating icon, or add a footer link. Most consent tools have a setting for a persistent icon. If you’d rather use a link, put Cookie settings in the site-wide footer template, not on one page, and have it call the tool’s own function for reopening the banner, such as
Cookiebot.renew()orOneTrust.ToggleInfoDisplay(). - Put Reject all in the reopened layer. One button that switches every non-essential category off and saves. The toggles can stay for people who want to pick and choose.
- Ask for nothing else. No email, contact form or account just to withdraw. Visitors didn’t have to sign in to say yes, so they shouldn’t have to sign in to say no.
- Check every template. Look at checkout, landing pages, the blog, the help centre and any subdomain. If one runs its own footer, add the link there too.
- Make the no do something. Withdrawing should stop the tags, and EU-02 tests whether it does. Cookies already on the device are less settled. The CNIL and the Belgian authority want withdrawal to stop earlier cookies being read. The German guidance says the site has no duty to delete them from the device, as long as each one has an expiry date (paras. 142 and 143). We found no ruling that settles the point.
- Re-scan. Clear cookies and storage, accept, and run a scan again. The finding should show the control on every sampled page, and the same number of clicks for no as for yes.
Whether a design meets the rule in a given country is a question for your legal adviser. Peeky reports the way back it found and the clicks it counted.
Questions
How do I change cookie preferences on a website?
Look for a link in the footer called something like Cookie settings, Cookie preferences or Manage cookies, or for a small icon that stays in a bottom corner of the page. Clicking it should bring the banner's choices back, where you can switch things off.
If you run the site, that link or icon is what EU-20 looks for. The CNIL suggests a 'gérer mes cookies' link, or a cookie icon at the bottom left of the screen.
Does a website need a cookie consent icon?
No. The EDPB's cookie banner taskforce gives a small floating icon as one example and a link in a visible place as another, and says no specific solution can be imposed (para. 35). What the law asks is that withdrawing is as easy as consenting was.
EU-20 accepts either one: a floating icon, or a link in the header, footer or menu that every page shares.
Is a link in the privacy policy enough for managing cookie preferences?
Usually not. The German authorities' guidance says visitors who consented through a banner shouldn't have to open the privacy policy and scroll to find the way back, though a link that goes straight to the settings is fine. In its 2024 Techpump decision, the Spanish AEPD described a settings panel that could be reached only from the cookie policy, and that didn't work.
EU-20 doesn't count a link that sits only inside the policy's text.
How easy does the GDPR say withdrawing consent must be?
As easy as giving it. Article 7(3) says: 'It shall be as easy to withdraw as to give consent.' The EDPB reads that practically: if consent took one click, people must be able to withdraw it 'equally as easily', on the same website (Guidelines 05/2020, para. 114). The Belgian authority's cookie checklist asks for withdrawal in one click.
What should happen after someone revokes cookie consent?
The processing that rested on the consent has to stop. The EDPB says the controller 'must stop the processing actions concerned', and should delete the data if no other legal basis applies (para. 117). The CNIL adds that it may take specific measures to make sure trackers placed earlier are no longer read or written.
EU-20 checks the way back. Whether tracking really stops after a no is checked by EU-02.
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
- Regulation (EU) 2016/679 (GDPR), Article 7, as adopted (legislation.gov.uk copy of the EU text)
- Regulation (EU) 2016/679 (GDPR), Article 4, as adopted (legislation.gov.uk copy of the EU text)
- Regulation (EU) 2016/679 (GDPR), Article 83, as adopted (legislation.gov.uk copy of the EU text)
- Directive 2002/58/EC (ePrivacy Directive), Article 5, as amended by Directive 2009/136/EC (legislation.gov.uk copy of the EU text)
Guidance
- EDPB, Guidelines 05/2020 on consent under Regulation 2016/679, version 1.1, adopted 4 May 2020
- EDPB, Report of the work undertaken by the Cookie Banner Taskforce, adopted 17 January 2023
- CNIL, Recommandation sur les cookies et autres traceurs, consolidated version published 16 January 2026 (section 3, Retrait et gestion du consentement)
- Garante per la protezione dei dati personali, Linee guida cookie e altri strumenti di tracciamento, 10 June 2021
- AEPD (Spain), Guía sobre el uso de las cookies, updated May 2024 (section 3.2.9, Retirada del consentimiento)
- Datenschutzkonferenz (Germany), Orientierungshilfe für Anbieter:innen von digitalen Diensten (OH Digitale Dienste), version 1.2, November 2024 (para. 62)
- Autorité de protection des données (Belgium), Check-list cookies
Decisions and cases
- Conseil d'État (France), decision no. 494300 of 7 October 2025 (Yahoo EMEA Limited), upholding CNIL deliberation SAN-2023-024
- Gegevensbeschermingsautoriteit (Belgium), decision on the merits 85/2022 of 25 May 2022 on cookies on the Knack and Le Vif websites (in Dutch)
- NAIH (Hungary), decision NAIH-3195-11/2022 on the cookie consent framework of tenyek.hu and tv2play.hu (TV2 Média Csoport Zrt.)
- Datatilsynet (Denmark), serious criticism of Den Blå Avis' consent solution, 26 January 2022, j.nr. 2020-431-0085
- Data Protection Commission (Ireland), Report on the use of cookies and other tracking technologies, following a sweep from August to December 2019, dated 6 April 2020
- AEPD (Spain), Procedimiento PS/00524/2023, resolution against Techpump Solutions S.L. (2024)
Last checked against the source:
For information only. Not legal advice.
