TATITECH

Google Analytics and Swiss data protection: what wealth managers should know

Website analytics raises real data-protection questions for Swiss and UK wealth managers. A plain guide to the nFADP, consent practice, Consent Mode v2, US transfers and privacy-first alternatives.

· 5 min read · By Tati

Wealth managers want to know whether their website is doing its job: whether prospects find the team pages, read the investment philosophy and get in touch. Google Analytics 4 is the most common way to find out. For firms in Switzerland, and those serving Swiss, UK and EU clients, it also raises questions about personal data, consent and transfers to the United States.

This is a practical overview of those questions. It is not legal advice. How your firm applies the rules is a decision for your data-protection officer, compliance officer or lawyer, and the right answer depends on your circumstances.

The Swiss nFADP in brief

The revised Swiss Federal Act on Data Protection, often called the nFADP or revDSG, came into force on 1 September 2023. Several of its principles are directly relevant to website analytics:

  • Transparency. People must be told what personal data is collected, for what purpose and who receives it, including recipients abroad. In practice that means a clear, accurate privacy notice.
  • Proportionality. Collect only what is needed for the stated purpose, and keep it no longer than necessary.
  • Privacy by design and by default. Systems should be set up from the outset to limit the processing of personal data.
  • Cross-border disclosure. Sending personal data to another country is subject to specific conditions, discussed below.

Analytics tools typically process identifiers such as cookie IDs and device information. Whether a given set-up involves personal data, and how much, depends on how it is configured.

This is where practice differs most between jurisdictions, and where firms are best advised to take a considered position rather than copy a neighbour’s banner.

In the UK and the EU, the long-standing position under PECR and the ePrivacy rules is that non-essential cookies, including analytics cookies, require prior consent. Recent UK legislation has introduced limited exemptions for certain analytics cookies, subject to conditions such as clear information and a simple way to object. The details and their timing should be checked with your adviser before relying on them.

In Switzerland, the approach has traditionally centred on transparency and the ability to object, rather than a general requirement of prior opt-in consent for analytics. Swiss telecommunications law requires that users are informed about the use of cookies and how to refuse them. Explicit consent becomes more relevant in specific situations, such as sensitive data or high-risk profiling.

Many Swiss firms nevertheless choose a consent banner anyway, for good reasons:

  • Their website serves visitors from the UK and EU, where consent rules apply.
  • One consistent approach is simpler to explain and maintain than several.
  • Clients of a wealth manager tend to appreciate being asked.

Whichever approach you take, the banner should be honest: equal prominence for accepting and declining, no pre-ticked boxes and a clear way to change the choice later.

Consent Mode v2 is Google’s framework for passing a visitor’s consent choices to Google tags. It uses signals for analytics storage and advertising storage, and two further signals introduced with version 2 covering whether user data may be sent to Google for advertising and used for personalised advertising.

When a visitor declines, tags adjust their behaviour instead of collecting as normal. There are two broad implementations:

  • Basic mode, where Google tags do not load at all until consent is given.
  • Advanced mode, where tags load and send limited, cookieless signals when consent is refused, which Google may use for modelling.

Advanced mode yields more complete figures; basic mode sends less data. Which is appropriate is a judgement your data-protection officer should make with the technical details in front of them.

Data transfers to the United States

Google Analytics involves processing by Google, a US company. Under the nFADP, disclosing personal data abroad is permitted where the destination provides adequate protection, or where other safeguards such as appropriate contractual clauses are in place.

The Swiss–US Data Privacy Framework allows transfers to US companies that have certified under it. The Swiss Federal Council recognised it as providing adequate protection with effect from September 2024. The EU–US Data Privacy Framework plays the equivalent role for the EU, and the UK has its own extension for UK transfers.

These frameworks have been challenged before, and their predecessors were struck down. A sensible approach is to document which mechanism you rely on, mention the transfer in your privacy notice and keep an eye on developments.

IP addresses in GA4

Unlike its predecessor, GA4 does not log or store IP addresses, according to Google. IP addresses are used during collection to derive approximate location, then discarded. GA4 also lets you turn off granular location and device data collection by region, and adjust data retention periods.

These settings reduce what is held, but they do not remove the need for transparency, a lawful basis for transfers or an accurate privacy notice.

Privacy-first alternatives

Some firms prefer to avoid Google altogether. Privacy-first analytics tools, hosted in the EU or Switzerland, offer a different trade-off:

  • Aggregate figures such as page views, referrers and enquiries, often without cookies.
  • Data kept within Europe, which simplifies the transfer question.
  • Lighter scripts and simpler dashboards.

The cost is less detail. You will not get the depth of audience and journey analysis GA4 offers, and integration with advertising tools is limited. For many wealth managers, who do not advertise heavily, that is an acceptable exchange.

Measure fewer, better things

The most effective data-protection measure is often simply to collect less. A wealth manager’s website does not need dozens of events and audience segments. It needs to answer a few questions well:

  • How many genuine enquiries did the website produce?
  • Which pages do prospects read before they get in touch?
  • How do visitors find you: by name, by referral link or by search?
  • Are insights and commentary being read?

A short list of meaningful measures makes reporting clearer, configuration simpler and the privacy notice easier to write.

A practical checklist

  • Decide, with your data-protection officer, whether you will ask for consent for analytics in each market you serve.
  • Review your consent banner: equal choices, no pre-ticked boxes, easy to revisit.
  • Confirm Consent Mode v2 is implemented and choose basic or advanced mode deliberately.
  • Record the transfer mechanism you rely on for any US processing.
  • Set GA4 data retention and regional data collection to the minimum you need.
  • Update your privacy notice to describe tools, purposes and recipients accurately.
  • Agree the handful of measures that genuinely inform decisions, and remove the rest.

In closing

Good analytics for a wealth manager is modest by design: a few clear measures, collected transparently and reported plainly. Whether that means a carefully configured GA4 or a privacy-first tool hosted in Europe, the set-up should be documented so your advisers can review it with confidence. Our approach is described under privacy-first analytics and reporting.

Contact

Start a conversation

Tell us a little about your firm and what you have in mind. We will reply personally, and everything you share with us stays confidential.

Everything you share with us is treated as confidential, and we are happy to sign a non-disclosure agreement before any detailed discussion.

We use your details only to reply to you, and keep them confidential. Privacy policy