The decisive question is not where the server is. It is who holds the key.

Picture this: you are sitting in a product demo for an AI tool that drafts medical reports. The salesperson says two sentences. “With us, everything stays in Switzerland.” And: “Patient data can only leave the country with explicit consent anyway.”

The first sentence may be a good argument. The second is not quite right. But the mistake is less dangerous than what it hides: the question of who can read your data in plain text.

What the Data Protection Act actually says.

Under Article 5 of the Swiss Federal Act on Data Protection (FADP), health data is sensitive personal data. It may still be disclosed abroad if the Federal Council has found that the destination country offers adequate protection. The list is in Annex 1 of the Data Protection Ordinance. Besides EU member states, the canton of Zurich notes that US companies certified under the Data Privacy Framework are also considered safe. Without such a decision, appropriate safeguards are needed, such as standard data protection clauses. Explicit consent appears in Article 17 as one of the exceptions, not the rule.

One distinction matters. Private clinics and practices without a public service mandate fall under the federal act. Hospitals with a public mandate fall under cantonal law, which differs in significant ways. The canton of Zurich also points out that a private clinic’s use of the cloud does not, in principle, require patients’ consent, provided they are informed about it.

The stricter rule is not in the Data Protection Act.

It is in the Criminal Code. Article 321 protects professional secrecy, and in its AI innovation sandbox the canton of Zurich spells out what that means for the cloud. If a provider can read your data in plain text, professional secrecy may stand in the way of using it, unless the provider is integrated contractually and organisationally to the point where it counts as an auxiliary. With large providers, the canton says, that is often difficult. The other solution is technical: encryption where the provider does not hold the key.

For data covered by professional secrecy that goes to the United States, the canton is specific. The provider must have no access, and the key must stay in Switzerland with the healthcare provider. Some areas also have their own rules. For the electronic patient record, for example, the canton cites a provision that prohibits storage abroad.

This leads to something you rarely hear in a sales meeting: a Swiss server does not solve the problem on its own. If the Swiss provider’s staff can read your reports in plain text, the professional secrecy question arises in exactly the same way.

A Swiss server is a good start. It is not an answer to professional secrecy.

What this has to do with your website.

More than most clinics think. According to the canton of Zurich’s analysis, even a person’s name in connection with a doctor, for example when they get in touch, is health data. The contact form, the booking tool, the website chat and the WhatsApp number all process sensitive data. Where does that data go? To a form service in the United States, a private inbox, a CRM in Ireland?

The law requires transparency. If data is disclosed abroad, the privacy notice must name the country and, where applicable, the safeguards. When a patient interacts directly with AI, a chatbot for instance, the canton says a duty to inform may arise from the principle of transparency. And for many medical AI applications that go beyond administration, a data protection impact assessment is likely to be required.

Where I stand.

I host my own website in Switzerland and recommend the same to clinics, because it simplifies a great deal. But I would never sell it as the answer to professional secrecy. A provider is chosen on its contract and on who holds the key. The flag on the data centre does not replace a contract.

What I would check.

• The website’s data flow. Form, booking, chat, newsletter: where each piece of information goes, who processes it and in which country.
• The contract with each provider. Purpose, security, location, subcontractors, audit rights and confidentiality, as the canton of Zurich lists them.
• The key. Who can see the data in plain text, at the provider and at its subcontractors.
• The privacy notice. Countries, safeguards and a notice when patients interact with AI.
• An impact assessment for every AI tool that does more than move appointments.

Before you introduce the next tool.

1. This week

   List every tool

   Every system that receives data from the website or the practice, with its provider and location.

2. This month

   Ask for the documents

   The data processing agreement, the list of subcontractors and who has plain-text access.

3. Before every AI project

   Impact assessment and the key question

   Document the risks and decide where the key sits.

4. Every year

   Review

   Adequacy decisions and political conditions can change quickly, as the canton also notes.

Think of the tool your clinic uses most: the calendar, the email or the patient records system. Now answer a single question, without looking at the contract. If tomorrow an employee of that provider wanted to read a specific record, could they?

If your answer is “I don’t know”, that is not carelessness on your part. It is the question almost nobody asks when signing. But it is worth knowing the answer before a patient asks it.

If you would like me to review your website and your tools from this angle, start with the Strategic Diagnostic. The legal assessment of a specific case is for your legal adviser or, in hospitals with a public mandate, the cantonal data protection authority.