UK and Switzerland: cookie consent rules and what AdSense requires
Key takeaways
- Google's EU user consent policy and its certified CMP requirement cover the UK and Switzerland as well as the EEA, so personalized AdSense ads need a Google-certified TCF CMP in both countries.
- In the UK, PECR regulation 6 and its new Schedule A1, inserted on 5 February 2026 by the Data (Use and Access) Act 2025, keep consent as the rule for storing or accessing information on a device.
- Schedule A1 adds consent exceptions for statistics and for website appearance or functionality, with information and a free right to object, but advertising is not among them.
- Swiss law, according to the FDPIC's cookie guidelines, requires website operators to inform users and let them refuse cookies under Article 45c of the Telecommunications Act, in force since 1 April 2007.
- The FDPIC treats advertising cookies with normal profiling as needing at least an easy opt-out, and those leading to high-risk profiling, such as cross-site tracking, as needing consent.

For AdSense, the UK and Switzerland are treated like the EEA: Google requires a Google-certified TCF CMP to serve personalized ads there, and its EU user consent policy applies. The national laws differ. The UK keeps consent as the rule for advertising cookies, with new exceptions since February 2026. Swiss law starts from information and a right to refuse, but its regulator expects consent for high-risk ad profiling.
This guide compares the rules as of November 2026, from legislation.gov.uk, the Swiss FDPIC and Google’s policy pages. It is not legal advice; the UK regulator’s (ICO) guidance site could not be retrieved for this guide.
What does Google require in the UK and Switzerland?
Google’s rules do not distinguish between the three regions:
| Requirement | EEA | UK | Switzerland |
|---|---|---|---|
| EU user consent policy applies | Yes | Yes | Yes, since 31 July 2024 |
| Certified TCF CMP needed for personalized ads | Since 16 January 2024 | Since 16 January 2024 | Since 31 July 2024 |
| Request without TCF signal | Limited ads attempted (error 10.1) | Same | Same |
The policy help page says the policy “applies to end users located in the EEA, the UK and Switzerland” and “was last updated on 31 July 2024 to apply to users located in Switzerland”. The publisher requirement page sets the CMP dates. In practice, a CMP that geo-targets “the EU” and skips the UK or Switzerland breaks AdSense for those visitors. See the certified CMP guide.
What changed in UK cookie law in 2026?
UK cookie rules sit in the Privacy and Electronic Communications Regulations 2003 (PECR). Regulation 6 was substituted with effect from 5 February 2026, and now 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.”
Schedule A1, inserted by the Data (Use and Access) Act 2025, lists when storage or access is allowed:
| Ground in Schedule A1 | Conditions | Relevant to AdSense? |
|---|---|---|
| Consent | Clear and comprehensive information, and consent | Yes, the ground for ad cookies |
| Transmission of a communication | Sole purpose of transmission | No |
| Strictly necessary for a requested service | Examples: security, fraud prevention, fault detection, authentication, remembering selections | Not for ads |
| Statistical purposes | Sole purpose of improving your service or website, information, simple free objection, limited sharing | Possibly some analytics, not ads |
| Website appearance or functionality | Adapting to user preferences, information, simple free objection | No |
| Emergency assistance | Locating a user requesting help | No |
Two details are new. “Website” includes mobile apps and other platforms. And consent may be signified by “amending or setting controls on the internet browser” or “using another application or programme”, which opens the door to browser-level choices. Advertising is not among the exceptions, so the consent model for ad cookies, and Google’s TCF requirement, both remain.
How does Swiss law handle cookies?
Switzerland has two layers, as explained in the FDPIC’s cookie guidelines (version 1.1, 6 October 2025):
- Article 45c of the Telecommunications Act, in force since 1 April 2007, obliges website operators “to inform website visitors about the use of technologies of this kind and to state their purposes”, and to tell them they may refuse and how.
- The Federal Act on Data Protection (FADP) governs the personal data processed through cookies.
The guidelines then grade advertising cookies by risk:
| Type of advertising tracking | FDPIC position for private operators |
|---|---|
| “Normal” profiling (your own offers, your own site) | Minimum: users can immediately recognize how to opt out with a few clicks |
| High-risk profiling (tracking across several websites, third parties bidding for placements) | Notification, prominent disclosure and consent requirements apply |
| Cannot rule out high-risk profiling | Assume high risk |
Personalized AdSense ads rely on a third party embedded across many sites, which matches the FDPIC’s description of potential high-risk profiling. The FDPIC also refers to TCF-based CMPs as “a step in the right direction”. Its practical tips page is aimed at users and explains how to control cookies.
Can Swiss publishers skip consent for Purpose 1?
The TCF has a feature for this situation. Google’s TCF troubleshooting article explains that Purpose One Treatment (P1T) “allows publishers to indicate that consent for Purpose 1 isn’t required in the publisher’s country”, with legitimate interest as the legal basis. It adds: “As of December 2021, Google only supports P1T for Switzerland.”
In practice, if your CMP sets the P1T flag with a publisher country code of CH, Google will not treat a missing Purpose 1 consent as error 1.2. Google also asks Swiss publishers who do not request consent to set the PublisherCC and PurposeOneTreatment fields correctly. Two limits apply:
- P1T concerns Purpose 1 (storing or accessing information on a device) only. Personalization purposes still need the user’s choice under the TCF.
- It is tied to the publisher’s country code, not the visitor’s location. It is designed for publishers based in Switzerland, and does not remove the consent expectations that apply to their EEA or UK visitors.
Given the FDPIC’s position on high-risk profiling, check with an adviser before relying on P1T for advertising.
What happens without consent in each region?
| Visitor region | Legal baseline for ad cookies | Google’s requirement | Ads served without consent |
|---|---|---|---|
| EEA | Consent (ePrivacy Directive and national laws) | Certified TCF CMP | Non-personalized or limited ads |
| UK | Consent under PECR Schedule A1; no ad exception | Certified TCF CMP | Non-personalized or limited ads |
| Switzerland | Information and right to refuse; consent for high-risk profiling | Certified TCF CMP; P1T possible for Swiss publishers | Non-personalized or limited ads |
| Switzerland, P1T set by a Swiss publisher | As above | Certified TCF CMP | Purpose 1 not treated as an error; personalization still needs the user’s choice |
“Limited ads” assumes you keep them enabled in AdSense. With limited ads turned off and no valid signal, those visitors may see no ads at all.
How should an AdSense site set up consent for these visitors?
- Include the UK and Switzerland in your CMP’s geo-targeting, alongside all EEA countries (EU plus Iceland, Liechtenstein and Norway).
- Use a certified TCF CMP such as Google’s European regulations message, which covers all three regions.
- Decide on a “Do not consent” button per country. Google’s message lets you enable it by country. UK and Swiss expectations on equal prominence may differ from those of EU regulators; check local guidance.
- Keep limited ads on if you want refusing visitors to see contextual ads; see limited and non-personalized ads.
- Update your privacy policy with the information Article 45c TCA and the UK GDPR require; see privacy policy for AdSense.
- Test from each region with a VPN or Google’s
?fc=alwaysshow&fctype=gdprpreview.
Common mistakes
- Targeting only EU countries. The UK and Switzerland drop to limited ads.
- Reading “opt-out” Swiss law as “no banner needed”. Google’s requirement applies regardless.
- Assuming the UK reform exempted ads. The new exceptions cover statistics and functionality, not advertising.
- Using the UK statistics exception for analytics data shared for ads. The exception requires limited sharing.
- Treating TCF purposes as identical everywhere. The TCF string is the same, but your legal basis analysis per country may differ.
Frequently asked questions
Since Swiss law is opt-out, can I skip the consent banner for Swiss visitors?
Not if you want personalized AdSense ads. Google's certified CMP requirement has applied to Switzerland since 31 July 2024, whatever the local legal standard. Legally, the FDPIC also says cross-site advertising tracking can amount to high-risk profiling that requires consent. Most AdSense sites therefore show Swiss visitors the same TCF message as EEA visitors.
Did the Data (Use and Access) Act 2025 remove cookie consent for ads in the UK?
No. The new Schedule A1 to PECR, in force since 5 February 2026, creates exceptions for statistical cookies, appearance and functionality cookies, strictly necessary storage and emergency location, but advertising cookies still rely on consent. It also states that consent can be signified through browser controls or another application.
Can I use the UK statistics exception for Google Analytics?
The exception covers storage whose sole purpose is collecting statistics to improve your own service or website, with clear information and a simple, free way to object. Information collected must not be shared except to help with those improvements. Whether a given analytics setup fits, especially one linked to advertising features, needs a case-by-case assessment.
Does Google's policy treat the UK and Switzerland the same as the EU?
Yes, for its consent requirements. Google's EU user consent policy applies to end users in the EEA, the UK and Switzerland, and the certified CMP requirement covers all three. The policy help page says the policy was last updated on 31 July 2024 to apply to users in Switzerland.
Sources
- The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 6 · legislation.gov.uk
- The Privacy and Electronic Communications (EC Directive) Regulations 2003, Schedule A1 · legislation.gov.uk
- Guidelines on data processing using cookies and similar technologies (V. 1.1, 6 October 2025) · Federal Data Protection and Information Commissioner (FDPIC)
- Cookies: How to Stay in Control of Your Data – Practical Tips · FDPIC
- Help with the EU user consent policy · Google
- Google consent management requirements for serving ads in the EEA, the UK, and Switzerland (for publishers) · Google AdSense Help
Related guides
- Google's certified CMP requirement: what AdSense publishers need for EEA, UK and Swiss traffic
Since 2024 AdSense needs a Google-certified TCF CMP for personalized ads in the EEA, UK and Switzerland. Dates, what happens without one, how to check yours.
- AdSense Privacy & messaging: building the European regulations (GDPR) message
Build the GDPR consent message in AdSense Privacy & messaging: every setting, the two- vs three-button layout, testing, troubleshooting and what it cannot do.
- IAB TCF v2.3 for publishers: what Google requires, what changed from v2.2, and v2.4
TCF v2.3 is mandatory for TC strings created since March 1, 2026. What changed from v2.2, Google's dates, the purposes AdSense needs, and the v2.4 update.
- Writing a privacy policy for a site that shows AdSense ads
What a privacy policy must say on a site running AdSense: Google as a party, cookies, the link Google requires, consent withdrawal, US opt-outs and a template.
- Personalized, non-personalized and limited ads: the three AdSense serving modes compared
How AdSense picks personalized, non-personalized or limited ads from consent signals, what each mode still collects, the ad code switches and the setting to check.