Skip to content
PeekWellThe Handbook
Join now

Cookie settings link: withdrawing consent in the UK

At a glance

UK-18MediumPECR reg. 6 and Sch. A1 para. 2 (DUAA 2025 s. 112 and Sch. 12); UK GDPR Arts. 4(11) and 7(3); ICO guidance on storage and access technologies (29 April 2026)

Peeky accepts your cookie banner, then checks each page for a Cookie settings link or icon and counts how many clicks it takes to turn that yes back into a no.

Last checked against the source:

I need to fix thisI need the rule

The rule

UK-18 is about the way back. Once someone has said yes to cookies on your site, can they say no again with the same effort? UK law gets there through the meaning of consent.

Regulation 6(1) reads: “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.” Section 112 of the Data (Use and Access) Act 2025 substituted it from 5 February 2026. Paragraph 2 of Schedule A1 then allows the storage or access where the user “is provided with clear and comprehensive information about the purpose of the storage or access” and “gives consent to the storage or access”.

Under regulation 2, consent “corresponds to the data subject’s consent in the UK GDPR”. Article 7(3) of the UK GDPR gives the right “to withdraw his or her consent at any time”, says the person must be told so before consenting, and adds: “It shall be as easy to withdraw as to give consent.”

Two of the exceptions added in February 2026 point the same way. Schedule A1 now lets storage run without consent when its only purpose is collecting statistics to improve a service (para. 5), or adapting a website’s appearance or functions to the user’s preferences (para. 6). Each still needs the user to be “given a simple means of objecting, free of charge, to the storage or access” and not to object. Someone who changes their mind later needs a route for that too.

The ICO’s guidance says: “You must therefore ensure that any consent mechanism has the technical capability to allow users to withdraw their consent with the same ease that they gave it. If your mechanism cannot do this, then it does not comply with the UK GDPR’s consent requirements.” It goes on: “You must also provide information about how people can withdraw consent within your consent mechanism, and ensure that any storage and access technologies that have already been set can be removed.” Its checklist for consent mechanisms includes “Our consent mechanism informs users about how they can revisit their preferences”, shown with a “settings” icon in the bottom left corner of a page.

Neither PECR nor the ICO says where the way back has to sit. The ICO’s own worked example is a travel site’s customer who “clicks a link in their profile to manage their settings”. In the EU, the data protection authorities’ cookie banner taskforce suggests “a small hovering and permanently visible icon” or “a link placed on a visible and standardized place” (para. 32). That report doesn’t bind anyone in the UK, and it’s quoted here only for comparison.

The guidance above is the ICO’s, from before 30 September 2026. On that day the Information Commission (ICO) took over the Information Commissioner’s functions, under section 117 of the Data (Use and Access) Act 2025 as commenced by SI 2026/1015.

What PeekWell checks and how

UK-18 asks whether a visitor who said yes can take it back from any page, with no more effort than the yes took. The scan works from your public pages as someone who isn’t signed in sees them, because that’s where your banner asked.

It’s automated. A clean browser accepts your banner with the single action the first screen offers, usually Accept all. On your home page and two other page templates, the scan looks for a control that reopens the choices and records its label and place. Then, from a content page, it follows the most visible control, counts the actions needed to switch everything non-essential off and save, and keeps screenshots of the control and the reopened choices.

The check is strictly pass or fail, and all four of these must hold:

  • W1. Every sampled template shows a control that reopens the choices: a floating icon, or a link or button in the shared header, footer or menu that names cookies, consent or privacy choices. A link found only inside the privacy or cookie policy’s text, only in an account area, or only by searching doesn’t count.
  • W2. With the choices open, turning everything non-essential off and saving takes no more actions than consenting did. A Reject all or Withdraw consent button there meets it. Five toggles and then a save button don’t.
  • W3. Nothing else is asked for: no account, email, form, message to the company or change to browser settings.
  • W4. The control works, opening the choices on each page tried. One that opens nothing after three tries fails.

The finding names every item that failed.

Much of this is PeekWell’s reading. The law doesn’t say where the way back goes, and UK-18 treats “easy” as a control in the shared header, footer or menu, or a floating icon, on every page. That reading is PeekWell’s own, borrowed from the EU taskforce’s “visible and standardized place”, a phrase the ICO’s page on managing consent doesn’t use. So the ICO’s example of a link in a customer’s profile wouldn’t pass W1 by itself. Counting actions against the consent click, and the pass and fail rules, are PeekWell’s own as well.

When a site has no banner, or a banner with no way to refuse, UK-18 looks at what loads. Anything non-essential stored or read on any pass makes it a finding at medium severity, since there’s no consent to take back. If nothing non-essential shows up, the check passes, and the report says which passes showed it.

UK-18 only tests the way back. Whether tracking stops once a visitor says no, or withdraws, is decided by UK-04. UK-02 compares yes and no on the banner’s first screen, and the EU version of this check is EU-20.

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 back that only exists inside an app, behind a sign-in or through customer service isn’t seen, and wouldn’t count for W1. 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

The ICO links the way back to the consent itself. A mechanism that can’t let people withdraw with the same ease “does not comply with the UK GDPR’s consent requirements”, in the guidance’s words. Without valid consent, the cookies that needed it have no basis under PECR.

The ICO’s recent cookie work has run through letters and preliminary enforcement notices. Its work on the top 1,000 UK websites tested three things: advertising cookies before a choice, a reject option as easy as accept, and advertising cookies placed without consent. By December 2025, 979 sites met those checks, 564 of them only after the ICO got involved, and 17 had received preliminary enforcement notices. The way back wasn’t among the published tests. As of 4 November 2026 we found no action on it from the regulator, before or after it became the Information Commission. The ICO said it would keep testing the top 1,000 sites from time to time. It didn’t say whether the way back would join the tests.

EU authorities have already acted on the way back. For comparison, the Belgian authority’s 2022 decision on the Knack and Le Vif news sites found that withdrawing took more steps than consenting. On knack.be the only route was a footer link, and on levif.be the consent tool froze on a black screen. In France, the CNIL fined Yahoo €10 million in 2023 partly over a message that put people off withdrawing, and the Conseil d’État upheld it in October 2025. Neither decision binds a UK regulator. They do show how an authority reads a way back that’s hard to use. And the UK stakes went up on 5 February 2026: since then, the ICO’s commencement statement says, PECR fines can reach 17.5 million pounds or 4% of global turnover.

Smaller companies and larger companies

Article 7(3) applies whatever the size of the business. The ICO’s cookie testing has focused on the 1,000 most visited UK sites, but nothing in PECR or the UK GDPR exempts a smaller one.

A small business usually gets its banner from a plugin or a website builder. Saying yes works fine. The way back depends on a floating icon someone has to switch on in the consent tool, or on someone adding a Cookie settings link to the footer, and nobody tests it because nobody goes back.

A bigger organisation usually has the link, just not everywhere. The main site’s footer carries it, while the shop, the careers site, campaign pages or a help centre on another platform use their own templates. Several brands may share one consent tool, and a change to that tool can break the link on some of them. And with a long vendor list behind the settings screen, saying no can mean working through dozens of toggles.

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

  • Top 1,000 UK websites (operators not named)

    ICO (United Kingdom), 2025No fine published

    The ICO tested the UK's top 1,000 websites for advertising cookies stored before visitors could choose, for whether rejecting was as easy as accepting, and for advertising cookies placed without consent. By December 2025, 979 met its checks, 564 of them after first failing, and 17 had received preliminary enforcement notices. The published tests did not cover the way back to withdraw consent.

    Read the ICO (United Kingdom) publication about Top 1,000 UK websites (operators not named)
  • Roularta Media Group (Knack and Le Vif websites)

    Gegevensbeschermingsautoriteit / APD (Belgium, EU data protection authority), 2022€50,000, for this and other findings

    An EU decision, listed for comparison. The Belgian authority 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. It found an infringement of GDPR Article 7(3) on both sites.

    Read the Gegevensbeschermingsautoriteit / APD (Belgium, EU data protection authority) publication about Roularta Media Group (Knack and Le Vif websites)
  • Yahoo EMEA Limited

    Conseil d'État (France, on a decision of the CNIL, an EU data protection authority), 2025€10 million CNIL fine, upheld

    An EU decision, listed for comparison. Before yahoo.com visitors could withdraw their consent to cookies, a message told them that withdrawing would make it impossible to access the products and services. The CNIL fined the company €10 million in December 2023, also for cookies set without consent. On 7 October 2025 the Conseil d'État upheld the fine and agreed that the withdrawal failure carried particular gravity.

    Read the Conseil d'État (France, on a decision of the CNIL, an EU data protection authority) publication about Yahoo EMEA Limited

Smaller companies

As of 4 November 2026 we found no decision by the ICO, or by the Information Commission (ICO) since it took over on 30 September 2026, about an organisation of any size that turns on the way to withdraw cookie consent. For comparison, the Spanish AEPD's 2024 decision on Techpump Solutions S.L., where the cookie settings could be reopened only from the cookie policy and refusing there left cookies in use, is listed on EU-20.

How to fix it

The ICO’s checklist gives the target: a consent mechanism that “informs users about how they can revisit their preferences”, and that lets them withdraw “with the same ease that they gave it”.

  1. Say yes, then try to say no. In a private window, accept your banner, open a product or article page, and look for the way back. Count the clicks to switch everything off. If it’s more than it took to say yes, a scan will report it.
  2. Give every page a way back. Turn on your consent tool’s floating icon, or add a Cookie settings link to the shared footer template. Have the link call the tool’s own function for reopening the banner, so it can’t drift out of sync.
  3. Add Reject all to the reopened screen. One action should switch off every non-essential category and save. Keep the toggles for people who want to choose.
  4. Don’t add hurdles. No email, form or sign-in just to withdraw.
  5. Cover your exceptions. If you rely on the statistics or appearance exceptions, make sure the same screen lets visitors object, and that objecting stops the storage.
  6. Check the other templates. Shop, blog, careers, help centre, campaign pages and any subdomain. Each one needs the link or the icon.
  7. Re-scan, then check what stops. Clear cookies and storage and run a scan again. UK-04 then tells you whether the tags really stop after the no.

Whether a particular setup satisfies the ICO is a question for your legal adviser. Peeky reports the way back it found and the clicks it counted.

Questions

How do I get to my cookie settings on a website?

Look in the footer for a link called something like Cookie settings or Manage cookies, or for a small icon that stays in a bottom corner of every page. Clicking it brings the cookie choices back so you can change them. Your browser's own cookie settings are a separate control.

If you run the site, that link or icon is what UK-18 looks for.

Does the ICO say withdrawing consent must be as easy as giving it?

Yes. Its guidance on storage and access technologies, finalised on 29 April 2026, says a consent mechanism must allow users to 'withdraw their consent with the same ease that they gave it', and that a mechanism that can't 'does not comply with the UK GDPR's consent requirements'. That follows Article 7(3) of the UK GDPR.

Is a floating cookie icon required in the UK?

No. PECR and the UK GDPR don't say where the way back has to go. The ICO's checklist asks that your consent mechanism tells people how they can revisit their preferences, and its good-practice picture shows a settings icon in the bottom left corner.

UK-18 accepts an icon, or a link in the header, footer or menu that every page shares. That reading is PeekWell's own.

Do I need a way to change cookie settings if I only use the statistics exception?

You need a way to object. Since 5 February 2026, PECR lets storage used only for statistics that help improve a site, or for adapting how it looks to a visitor's preferences, run without consent. Both exceptions still require clear information and 'a simple means of objecting, free of charge'. A Cookie settings link that reaches that choice is the natural place for it.

Has the ICO acted against a website over the right to withdraw consent to cookies?

Not that we found, as of 4 November 2026. The ICO's published tests of the UK's top 1,000 websites covered cookies set before a choice, whether rejecting was as easy as accepting, and cookies placed without consent, but not the way back. We found nothing on it from the Information Commission (ICO) either, since it took over on 30 September 2026.

In the EU, the Belgian authority fined a news publisher in 2022 partly because withdrawing took more steps than consenting.

Filed with

The rule

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

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

A case

Top 1,000 UK websites (operators not named)

ICO (United Kingdom), 2025

Read the decision (Top 1,000 UK websites (operators not named))

Your site

Is your website affected? Join now to find out.

Join now

Sources

The law

  1. PECR 2003 (SI 2003/2426), regulation 6, as in force from 5 February 2026
  2. PECR 2003, Schedule A1 (storage and access exceptions), version of 5 February 2026
  3. PECR 2003, regulation 2 (definition of consent)
  4. UK GDPR, Article 7 (conditions for consent)
  5. Data (Use and Access) Act 2025, section 112 (storing information in terminal equipment)
  6. Data (Use and Access) Act 2025, section 117 (the Information Commission), s. 117(4)(a) in force 30 September 2026 by SI 2026/1015

Guidance

  1. ICO, How do we manage consent in practice? (guidance on the use of storage and access technologies)
  2. ICO, Guidance on the use of storage and access technologies (final, 29 April 2026)
  3. ICO, Statement on the commencement of the Data (Use and Access) Act (5 February 2026)
  4. EDPB, Report of the work undertaken by the Cookie Banner Taskforce, adopted 17 January 2023 (EU, for comparison)

Decisions and cases

  1. ICO, ICO action secures increased cookie compliance (4 December 2025)
  2. Gegevensbeschermingsautoriteit (Belgium), decision on the merits 85/2022 of 25 May 2022 on cookies on the Knack and Le Vif websites (in Dutch; EU, for comparison)
  3. Conseil d'État (France), decision no. 494300 of 7 October 2025 (Yahoo EMEA Limited), upholding CNIL deliberation SAN-2023-024 (EU, for comparison)
  4. AEPD (Spain), Procedimiento PS/00524/2023, resolution against Techpump Solutions S.L. (2024; EU, for comparison)

Further reading

  1. GOV.UK, Information Commission succeeds the ICO as UK's data protection regulator (30 September 2026)

Last checked against the source:

For information only. Not legal advice.