Switzerland does not require a cookie banner. It does require an easy way to refuse tracking.

The rule behind that is almost twenty years old. It is not in the 2023 data protection act but in the Telecommunications Act, where it has stood since 1 April 2007. It asks for less than many banners promise, and for more than one sentence in a privacy policy.

The real question in web analytics is not whether you need a banner. It is how much you need to know about your visitors to make your website better. The tool, the settings and your obligations all follow from that.

This article covers the legal position, the choice of tool and a lean tracking plan. Which metrics to look at in Google Analytics 4 and how to set up conversions is covered in Google Analytics 4 for SMEs. It is not legal advice.

What Switzerland requires for web analytics

The Swiss cookie rule sits in Article 45c of the Telecommunications Act (TCA). Processing data on a visitor's device is only allowed if visitors are told about the processing and its purpose and are informed that they can refuse it (our paraphrase; there is no official English version of the Telecommunications Act or the Federal Act on Data Protection, so all article references in this article are paraphrased).

The Federal Data Protection and Information Commissioner (FDPIC) sums up the difference from the EU in a fact sheet from March 2026: European law requires prior consent, while Swiss law focuses on transparent information and the right to object. For analytics cookies, Switzerland therefore generally works on opt-out, not opt-in, in principle before the cookies become active.

How that opt-out should look is set out in the FDPIC's guidelines on cookies of 22 January 2025, supplemented on 6 October 2025. The option to refuse belongs in a prominent place, must be easy to find on the first and every later visit, and must take only a few clicks. On that reading, a link buried in the privacy policy is not enough.

The guidelines are the supervisory authority's interpretation, not law. They do show what the FDPIC measures a website against.

Opt-out is the principle, not the only rule. Article 6(7) of the Federal Act on Data Protection (FADP) requires express consent for, among other things, processing sensitive personal data and high-risk profiling. For processing visitors would not expect, the FDPIC requires at least a particularly clear notice of the opt-out, and consent where the intrusion is high.

Its guidelines sort cookie use into risk levels:

Type of useWhat the FDPIC expects
Necessary cookies: shopping basket, login, form caching, storing the cookie choiceno opt-out; the only way to refuse is to leave the whole service
Functional cookies and uses with "normal" profilingopt-out
Qualified high-risk usesopt-in

According to the FDPIC there is no binding list of necessary cookies. Its fact sheet explicitly counts analytics cookies as not necessary.

If you work in healthcare, look more closely: health data counts as sensitive under Article 5 FADP. Whether a visit to a practice website already falls under that is not answered by the sources we checked. That calls for a case-by-case assessment.

Cookieless web analytics is often sold as a way out. The FDPIC sees it differently. Its guidelines explicitly count server-side tracking, browser fingerprinting and pixels among the "similar technologies" they cover.

Vendors say so openly too. Matomo states in its help pages that switching off cookies does not stop JavaScript-based tracking. Fathom writes that a privacy-focused tool does not make every use of analytics compliant automatically, and that hashing is not by itself a legal guarantee of anonymity.

Cookieless is a technical property, not a legal free pass. What counts is whether visitors can be identified or recognised again.

Anonymous beats personal

The most useful sentence for choosing a tool is in the FDPIC's guidelines. In essence: your interest in analysing visitor flows does not justify evaluating personal data if the same purpose can be met with anonymised data.

For pure statistics, the FDPIC says the legislator has already done the balancing, subject to conditions: Article 31(2)(e) FADP allows an overriding interest to be considered if you anonymise the data as soon as the purpose allows and publish only results from which no one can be identified. For websites, the FDPIC says that usually means immediately. With an external tool there is one more condition: the provider may not use the data for its own purposes, only on your behalf.

For an SME, that gives a simple order:

  1. What do you want to know? Usually where visitors come from, which pages they read and where they get in touch.
  2. Is an anonymous evaluation enough for that? For those three questions, often yes.
  3. Only if not do you need more, and with it come more obligations.

Google Analytics 4 in Switzerland

We have not found a blanket verdict from the FDPIC on Google Analytics 4, neither "allowed" nor "banned". What can be shown is what Google states and what the rules on transfers abroad say.

  • IP addresses: According to Google, GA4 does not log or store IP addresses of visitors from Switzerland. They are still transmitted; Google drops them after receipt and derives an approximate location from them.
  • Retention: For user-level data you choose 2 or 14 months. The setting affects explorations and funnel reports, not the standard reports. You find it under Admin, in Data Settings, Data Retention. Keeping data for less time follows the principle in Article 6(4) FADP: delete or anonymise data once it is no longer needed.
  • Data in the US: Since 15 September 2024 the Federal Council has listed the US as a country with adequate data protection, but only for companies certified under the Swiss-U.S. Data Privacy Framework. You check whether your provider is one of them on the participant list at dataprivacyframework.gov.

If your tool sits abroad, Article 19(4) FADP requires your privacy policy to name the country and, where applicable, the safeguards you rely on.

Google's Consent Mode comes in two versions:

  • Basic: the Google tag loads only after consent. If someone refuses, nothing is sent.
  • Advanced: the tag loads beforehand. After a refusal it sets no cookies, but according to Google it sends cookieless pings that may include the user agent, screen resolution and IP address.

With the advanced version, Google models the behaviour of visitors who refused. According to Google, that only applies once your property records at least 1,000 events per day without consent on at least 7 days and at least 1,000 daily users with consent on 7 of the previous 28 days. Your own user numbers show whether your website reaches that threshold.

Here lies a real trade-off that none of the sources we checked settles: the advanced version still sends data to Google after a refusal. Under Article 30(2)(b) FADP, a breach of privacy occurs in particular when personal data is processed against a person's express wishes. If you choose the advanced version, settle that question deliberately, not in passing.

How many visitors refuse is not a fixed number. An overview of user studies on LINC, the innovation lab of the French data protection authority CNIL (N. Bielova, 2023), found acceptance rates of 53 to 72 per cent, depending on the study, when "accept" and "reject" buttons looked the same. Whether those figures carry over to the Swiss opt-out approach has not been measured.

When the GDPR applies to your Swiss business

The GDPR does not apply just because people in Germany can open your website. Under Article 3(2) GDPR it applies to a business outside the EU when it offers goods or services to people in the EU or monitors their behaviour there.

For offering, Recital 23 gives indications: the mere accessibility of a website is not enough. A language or currency used in a member state, combined with the option to order in it, or mentions of customers in the EU, do point to an offer. Euro prices with an option to order, or "customers in Austria" on your website, are exactly such signs.

The second half is open: whether ordinary audience measurement already counts as "monitoring" is not settled by the sources we checked. Recital 24 looks at whether internet activity is tracked, particularly for profiling. If you deliberately target customers in the EU, settle that question with a specialist. What the GDPR and the FADP mean for AI tools is covered in AI and data protection in Switzerland.

Measuring without a banner

Three sources give you numbers without setting cookies on your website:

  • Google Search Console: it measures not on your website but in Google Search: how often you appear, how often you are clicked and at which position. Google hides rare queries to protect the people searching. Setting it up requires confirming that you own the site.
  • Server log files: they are created anyway. They do contain IP addresses, which can be personal data, so the FADP's rules on purpose and deletion apply here too.
  • Cookieless tools: some come from Switzerland, such as Friendly Analytics, based on Matomo and hosted in Switzerland. Plausible and Simple Analytics say they set no cookies and store no IP addresses. Those are vendor statements, and the section above applies: no cookie does not mean no tracking.

There is deliberately no ranking of the "best" tools here. The right tool is the one that answers your questions with as little personal data as possible.

The tracking plan on one page

A tracking plan does not need to be long. It answers six questions, in this order:

  1. Purpose of each measurement: what do you want to know, and why? Every measurement needs a purpose visitors can recognise (Article 6(3) FADP).
  2. Tool: is an anonymous evaluation enough, or do you need more? See above.
  3. Basis: opt-out under Swiss law, opt-in for high risk, and EU rules as well if you deliberately target the EU.
  4. Information: what goes in the privacy policy and in the notice on the website?
  5. Retention: how long is data kept, and when is it deleted or anonymised?
  6. Test: does refusing work? Refuse in the banner, reload the page and check in your browser's developer tools whether analytics requests still go out.

The sixth point is the one most people skip. A banner whose refusal does nothing technically is worse than none: it promises a choice that does not exist.

What belongs in your privacy policy

Under Article 19(2) and (4) FADP you inform people at least about:

  • who you are and how to reach you
  • why you process the data
  • to whom you pass data, such as the analytics provider
  • for data going abroad: the country and, where applicable, the safeguards

Under Article 60 FADP, anyone who intentionally fails to inform can be fined up to CHF 250,000 on complaint. Who within a business is fined is governed by Article 64 FADP via administrative criminal law; details are in AI and data protection in Switzerland.

What ALPENIQ does here

With a website from ALPENIQ, measurement from day one is part of the scope: we set it up as part of the website project so you can see where enquiries come from. A website without measurement is an opinion.

One limit belongs here: we do not give legal advice. For health data, deliberate EU business or profiling, a data protection lawyer belongs at the table.

Conclusion

In Switzerland you may generally run web analytics without prior consent, as long as you inform visitors and offer an easy way to refuse. The less personal data your tool needs, the fewer obligations you carry. A one-page plan and a test that the refusal actually works make the difference between a banner and a solution.

Further reading

Frequently asked questions (FAQ)

Swiss law does not expressly require a banner. Under Article 45c of the Telecommunications Act you must, however, inform visitors about the processing and its purpose and tell them they can refuse it. The FDPIC expects that refusal to be in a prominent place and to take only a few clicks. In practice many websites solve this with a notice or banner.

Is Google Analytics allowed in Switzerland?

We have not found a blanket verdict from the FDPIC on Google Analytics. The general rules apply: inform visitors, let them refuse, keep data no longer than necessary and, for data going to the US, check whether the provider is certified under the Swiss-U.S. Data Privacy Framework. High-risk processing needs consent.

Necessary cookies, for example for a shopping basket or login, need no consent. For ordinary audience measurement, Switzerland generally requires a clear notice and an opt-out. Google Search Console data comes from search, not from your website. You need consent for sensitive data and high-risk profiling; for processing visitors would not expect, the FDPIC expects at least a particularly clear notice.

Does the GDPR apply to my Swiss website?

Not merely because people in the EU can open it. Under Article 3(2), the GDPR applies when you deliberately offer goods or services to people in the EU or monitor their behaviour there. Signs of an offer include euro prices, ordering from the EU or mentions of customers there.

What belongs in a tracking plan?

A tracking plan answers six questions: the purpose of each measurement, the tool and whether anonymous evaluation is enough, the legal basis, how visitors are informed, how long data is kept and a test that refusing actually works. It fits on one page and is worth writing before the first script goes on the website.