Compliance
Swiss nFADP and AI: the revised Data Protection Act, personal fines and AI providers
Short answer
The revised Swiss FADP, in force since 1 September 2023, applies directly to AI. Sending client data to an AI provider is processing by a processor and usually a disclosure abroad. Intentional breaches can mean criminal fines of up to CHF 250,000 for the responsible individual. Masking identifiers such as AHV numbers before prompts leave Switzerland cuts that exposure.
A relationship manager in Zurich drafts a client letter with ChatGPT. In goes the client's name, AHV number 756.1234.5678.97, the IBAN CH93 0076 2011 6238 5295 7 and a note about a CHF 2,400 transfer. Under the revised Swiss data protection law, the question isn't only whether the bank is exposed. It's whether a named person inside the bank is.
The revised Federal Act on Data Protection (FADP, SR 235.1), often called the nFADP or revFADP, has been in force since 1 September 2023, together with the Data Protection Ordinance. It's close to the GDPR in structure, with Swiss differences that matter for AI: personal criminal liability, its own transfer list and a regulator that has said clearly where it stands on AI.
Does the FADP apply to AI?
Yes, directly. The Federal Data Protection and Information Commissioner (FDPIC) first said so in November 2023 and repeated it in an updated statement on 8 May 2025: because the FADP is technology-neutral, it governs AI-supported processing without new rules. The FDPIC expects transparency about the purpose, functioning and data sources of AI processing, a data protection impact assessment where the risk is high, and respect for people's right to object to automated processing and to ask for human review of automated decisions.
Switzerland has no AI-specific statute in force as of October 2026. The Federal Council has said it will amend Swiss law so the country can ratify the Council of Europe's AI Convention, which it signed in March 2025. Until that happens, the FADP, sector rules such as banking secrecy and FINMA supervision are what apply.
Which FADP duties matter most when you use AI models?
| Article | Duty | What it means for prompts and API calls |
|---|---|---|
| Art. 6 | Proportionality, purpose limitation, data minimization | Don't send the AHV number when the model only needs to draft a letter |
| Art. 7 | Privacy by design and by default | Build masking into the integration rather than relying on staff discipline |
| Art. 8 | Appropriate data security | Technical measures against unauthorized disclosure, including to the AI provider |
| Art. 9 | Processing by processors only under contract, with prior approval for sub-processors | Sign processor terms with the AI provider and with any masking layer |
| Art. 16 and 17 | Disclosure abroad only to adequate countries or with safeguards | US providers need the Swiss-US DPF or contractual safeguards |
| Art. 19 | Duty to inform, including the countries data goes to | Privacy notices must name the destination countries |
| Art. 21 | Information about automated individual decisions | Tell people when a decision about them is made by AI alone |
| Art. 22 | Data protection impact assessment for high-risk processing | Expect one for client data in AI workflows |
| Art. 24 | Report breaches to the FDPIC as soon as possible | Client data pasted into a consumer AI account may be one |
Who pays the fine under the Swiss FADP?
This is the part that gets a compliance officer's attention. The FADP's sanctions in Articles 60 to 63 are criminal fines of up to CHF 250,000, and they're aimed at the responsible natural persons, not the company. They require intent, which includes accepting a known risk, and negligence isn't punishable. Under Article 64, the company can be fined up to CHF 50,000 instead when identifying the responsible person would take disproportionate effort.
Two offences in Article 61 map straight onto AI use: disclosing personal data abroad without meeting the conditions of Articles 16 and 17, and handing processing to a processor without meeting Article 9. A manager who knowingly lets a team paste client files into a consumer AI account is in the zone the law describes. That's why Swiss teams tend to want a technical control, not just a policy.
How does cross-border disclosure work for US AI providers?
The Federal Council keeps a list of countries with adequate protection in Annex 1 of the Data Protection Ordinance. Since 15 September 2024, US organizations certified under the Swiss-US Data Privacy Framework are on it. For a provider that isn't certified, you need safeguards such as the EU standard contractual clauses with the Swiss adaptations the FDPIC recognizes, plus your own assessment of the destination.
Check the Swiss part of the DPF list, which is separate from the EU and UK entries. And remember the bank-specific layer: client-identifying data under banking secrecy (Art. 47 of the Banking Act) is a separate question from data protection, and many Swiss banks treat it as a hard line for any foreign service. That's covered in more detail on our DORA and FINMA page.
What does Maskflare detect for Switzerland?
The Switzerland country pack detects AHV/AVS social security numbers (the 756 prefix, with checksum validation, dotted or not), Swiss IBANs, Swiss phone numbers in international and national formats and postal codes in German, French and Italian context. Combined with the global pack (email, cards, IP addresses, street addresses), person names in German, French, Italian, English and Spanish, and the credentials pack, that covers what usually turns up in Swiss client correspondence.
Before: Letter to Ada Lovelace, AHV 756.1234.5678.97, about the CHF 2,400 transfer
to CH93 0076 2011 6238 5295 7.
Sent: Letter to mf_mask_8c1e..., AHV mf_mask_2a93..., about the CHF 2,400 transfer
to mf_mask_4d07....Be aware of two limits. There's no one-click FADP profile yet: the built-in profiles are HIPAA Safe Harbor, GDPR (EU/EEA), UK GDPR, PCI DSS and US personal data, so for Switzerland you switch on the Switzerland, global, names and credentials packs yourself. And for client lists, structure isn't enough: a client number in your own format, or a family name that's also a place, needs Exact Data Match, which matches keyed hashes of your own records so the clear values never leave your environment.
FADP requirements, what Maskflare does, and what stays your job
| Requirement | What Maskflare does | What stays your job |
|---|---|---|
| Proportionality and minimization (Art. 6) | Masks AHV numbers, IBANs, names and contact data before the provider sees them, restores them in answers | Decide which workflows may use client data at all |
| Privacy by design (Art. 7) | One policy across apps, browsers, desktops and agents | Make AI access go through it |
| Data security (Art. 8) | No prompt logging; values behind tokens encrypted for 30 days; maker-checker for rule changes | Access control, staff training, breach process |
| Processors (Art. 9) | Acts as a processor; EU-hosted by default, on-premises for enterprise | Processor contracts with Maskflare and each AI provider |
| Disclosure abroad (Art. 16, 17) | Keeps identifiers out of what crosses the border | Check the Swiss DPF list or use safeguards; name countries in your notice |
| DPIA (Art. 22) | Rule history and audit export as evidence | Write and own the DPIA |
| Personal liability (Art. 60 to 64) | A technical control you can point to | Assign responsibility and document decisions |
A practical checklist for Swiss organizations
- List AI tools in use and, for each, the countries where the provider processes data.
- Check each US provider against the Swiss part of the DPF list. Otherwise put SCCs with Swiss adaptations in place.
- Sign processor terms and approve sub-processors as Article 9 requires.
- Turn on the Switzerland, global, names and credentials packs, and load your client list into Exact Data Match.
- Update privacy notices with the destination countries and, where relevant, automated decisions.
- Run a DPIA for client-data workflows and keep the rule history and audit export with it.
- Name who is responsible for AI use. Under the FADP, that person carries real exposure.
What masking doesn't solve under the FADP
Masking catches identifiers, not context. A sentence like "the client who owns the bakery on Bahnhofstrasse" identifies someone without a single detectable value. Person-name detection, even with the named-entity layer, should be tested on your own documents. And masking doesn't settle banking secrecy questions, which turn on whether any client-identifying information leaves the bank, not just whether it's tokenized. Maskflare is a strong safeguard, not a substitute for the contracts, assessments and decisions the FADP expects.
Frequently asked questions
When did the revised Swiss FADP come into force?
On 1 September 2023, together with the revised Data Protection Ordinance. There was no transition period for most duties.
Can individuals really be fined under the FADP?
Yes. Articles 60 to 63 provide criminal fines of up to CHF 250,000 for intentional breaches, aimed at the responsible natural persons. A company can be fined up to CHF 50,000 instead when finding the responsible individual would be disproportionate.
What has the FDPIC said about AI?
That the FADP applies directly to AI-supported processing. Its statement of November 2023, updated on 8 May 2025, stresses transparency about purpose, functioning and data sources, DPIAs for high-risk processing and the rights to object and to human review.
Can we send personal data to US AI providers from Switzerland?
Yes, if the provider is certified under the Swiss-US Data Privacy Framework (adequate since 15 September 2024) or you use recognized safeguards such as adapted SCCs. Masking reduces how much personal data is disclosed in the first place.
Does Maskflare detect Swiss AHV numbers?
Yes. The Switzerland pack detects AHV/AVS numbers with the 756 prefix and checksum validation, plus Swiss IBANs, phone numbers and postal codes.
About the author
Articles on GDPR, the EU AI Act and sector rules, written by the people at Maskflare who answer customers' data protection questions. They're general information, not legal advice; we cite the regulator or the provider's own terms wherever we can.