Swiss data protection law vs GDPR: key differences

Key takeaways

  • The FADP and GDPR can both apply to one business, so complying with one does not automatically satisfy the other.
  • The GDPR requires an Article 6 legal basis for every processing activity, while the FADP has no universal equivalent for private businesses.
  • GDPR breaches must be reported within 72 hours where feasible unless risk is unlikely, while the FADP requires prompt notice when high risk is likely.
  • The highest GDPR fines reach 20 million euros or 4% of worldwide turnover, while Swiss criminal fines reach CHF 250,000 and mainly target individuals.

Switzerland’s Federal Act on Data Protection (FADP) and the EU’s General Data Protection Regulation (GDPR) share core privacy principles, but differ in legal grounds, breach reporting, automated decisions, and penalties. A business may need to comply with both, so meeting one framework does not automatically satisfy the other. This comparison explains the practical differences, with particular attention to AI services. (fedlex.admin.ch)

Which law applies to your business?

The FADP governs personal-data processing by private businesses and Swiss federal bodies, and can apply to activities abroad that have effects in Switzerland. The GDPR applies to processing connected with an EU establishment and certain processing by businesses outside the EU that target people in the EU with goods or services or monitor their behavior there. These tests can overlap. (fedlex.admin.ch)

For example, a Swiss AI provider marketing subscriptions to people in France may face both frameworks. Under the GDPR’s targeting test, the individual’s location matters—not simply EU citizenship. Conversely, a website being accessible from the EU does not, by itself, establish intentional targeting. (edpb.europa.eu)

For data protection in Switzerland, distinguish private-sector processing from cantonal public-sector rules. This article focuses on private businesses; federal authorities have different legal-basis requirements under the FADP. (fedlex.admin.ch)

The key differences at a glance

When comparing Swiss data protection law vs GDPR, key differences emerge in the decisions teams must make before processing, after an incident, and when deploying automated systems.

Topic Swiss FADP EU GDPR
Grounds for private-sector processing No universal Article 6-style legal-basis requirement; unlawful infringements of personality rights need justification Every processing activity needs an applicable Article 6 legal basis
Regulator breach notification Likely high risk; notify as quickly as possible Notify unless risk is unlikely, without undue delay and, where feasible, within 72 hours
Significant automated decisions Information and human-review rights, subject to exceptions Generally prohibited unless an Article 22 exception applies
Data protection officer Generally voluntary for private businesses Mandatory when specified conditions apply
Financial penalties Certain intentional violations can attract criminal fines up to CHF 250,000, principally targeting responsible individuals The highest administrative-fine tier reaches €20 million or 4% of worldwide annual turnover, whichever is higher

These distinctions concern different legal mechanisms, not a simple ranking of which law is stricter. Swiss sanctions should not be treated as a smaller version of GDPR corporate fines. (fedlex.admin.ch)

Under the GDPR, businesses must identify an appropriate legal basis for each processing purpose. Consent is only one option: contractual necessity, legal obligations, and legitimate interests may also apply, depending on the circumstances. Processing special-category data, such as health information, requires an additional applicable condition. (edpb.europa.eu)

Swiss privacy law takes a different approach for private businesses. Processing must respect principles including proportionality, recognizable purposes, accuracy, and security. Where processing unlawfully infringes personality rights, justification may come from consent, an overriding private or public interest, or the law. (edoeb.admin.ch)

This does not mean Swiss businesses can collect anything until someone objects. Nor does sensitive-data processing always require consent. Where consent is required and relied upon, the FADP requires it to be explicit for sensitive personal data and private-sector high-risk profiling. (fedlex.admin.ch)

For an AI product, a practical approach is to separate account administration, inference, abuse monitoring, and model improvement into distinct purposes. Assess the applicable grounds for each rather than assuming that accepting the service authorizes every later use. (edpb.europa.eu)

Privacy notices and individual rights need local attention

A GDPR privacy notice is a useful starting point, but it should not be copied unchanged for Switzerland. The FADP requires information about destination countries when personal data is disclosed abroad and, where applicable, the safeguards or exceptions supporting disclosure. Its transparency duties also cover data obtained indirectly, subject to exceptions. (edoeb.admin.ch)

Both frameworks give people ways to access their data and seek correction or deletion, although the conditions and legal mechanisms differ. Swiss access requests are generally answered free of charge within 30 days. Avoid promising identical rights or deadlines worldwide unless your operational policy deliberately supports that commitment. (edoeb.admin.ch)

For an AI service, explain whether prompts, uploaded documents, and conversations are used for model improvement. The Swiss regulator specifically emphasizes transparency about AI purposes, functionality, and data sources, including whether users are interacting with a machine. (edoeb.admin.ch)

Breach reporting requires two separate assessments

Under the GDPR, a controller must notify the competent authority unless a personal-data breach is unlikely to create a risk to individuals’ rights and freedoms. Notification must occur without undue delay and, where feasible, within 72 hours of awareness. High-risk breaches generally also require communication to affected individuals, subject to exceptions. (edpb.europa.eu)

The FADP uses a higher regulator-notification threshold: a breach likely to create a high risk to personality or fundamental rights. Notification to the Federal Data Protection and Information Commissioner (FDPIC) must happen as quickly as possible. Affected people must be informed when necessary for their protection or when the FDPIC requires it. (edoeb.admin.ch)

Build one incident-response process with separate Swiss and EU decision points. Record when awareness arose, assess consequences for individuals, and document the notification decision. Do not assume Switzerland’s lack of a fixed 72-hour deadline permits waiting for a complete forensic investigation. (edpb.europa.eu)

What changes for AI companies?

For AI companies, the central differences concern automated decisions, transparency, and how processing risks are assessed. The FADP is technology-neutral and already applies to AI-supported personal-data processing. Comparing Swiss data protection law vs EU GDPR for AI companies therefore requires examining the actual use case—not merely whether the product carries an AI label. (edoeb.admin.ch)

Automated decisions need more than a disclosure

Swiss Article 21 addresses exclusively automated decisions with legal consequences or considerable adverse effects. It generally requires notification and, on request, an opportunity to express a view and obtain human review. Exceptions include explicit consent to automation and certain contractual decisions granting the person’s request. (edoeb.admin.ch)

GDPR Article 22 generally prohibits solely automated decisions producing legal or similarly significant effects unless a recognized exception applies. These include contractual necessity, authorization by law, or explicit consent, with applicable safeguards. A review button alone does not establish permission to automate a credit rejection or comparable consequential decision. (commission.europa.eu)

High-risk processing calls for an impact assessment

Both frameworks require data protection impact assessments when the relevant high-risk threshold is met. Under Swiss rules, the assessment describes planned processing, evaluates risks, and identifies protective measures. High residual risk can trigger consultation requirements; private controllers have an exception where they consult their qualifying data protection officer. (edoeb.admin.ch)

When assessing AI service compliance requirements under Swiss data protection law and GDPR, document data sources, potential disclosure through outputs, retention, and the consequences of inaccurate results. Use the assessment to change the design where necessary, rather than treating it as launch paperwork. (edoeb.admin.ch)

Cross-border AI services need a practical checklist

Swiss hosting does not resolve every international-transfer issue. Map where vendors and subprocessors receive or access personal data. Swiss transfers depend on the destination’s protection level or another permitted mechanism; evaluate GDPR transfer requirements separately where they apply. (edoeb.admin.ch)

Use this implementation checklist:

  • Map purposes and roles: Identify who determines each processing purpose and who acts on instructions; assess model-training uses separately.
  • Review vendor arrangements: Check security guarantees, processing instructions, subprocessors, and breach escalation. Swiss outsourcing rules require prior approval for further subcontracting.
  • Minimize data exposure: Remove unnecessary identifiers before transmission and choose retention settings that match the documented purpose.
  • Test user protections: Rehearse access requests, corrections, deletion handling, and any required human-review pathway before launch.

These controls translate data protection regulations into operational decisions rather than relying on a policy document alone. (fedlex.admin.ch)

Build one program with jurisdiction-specific rules

The practical takeaway is to share controls where possible while retaining separate legal assessments for Swiss and EU obligations. Prioritize purpose mapping, clear notices, vendor oversight, and tested incident handling; add jurisdiction-specific rules for consent, transfers, and automated decisions. This is general information, not a substitute for advice on a particular service or processing activity.

Sources

  1. Fedlex
  2. edpb.europa.eu: Edpb guidelines 3 2018 territorial scope after public consultation en 1
  3. Legal basis | European Data Protection Board
  4. edoeb.admin.ch: TOM EN
  5. Process personal data lawfully | Data protection guide for small business | European Data Protection Board
  6. Duty to provide information
  7. Knowing and asserting my rights
  8. AI and data protection
  9. Data breaches | Data protection guide for small business | European Data Protection Board
  10. edoeb.admin.ch: 2%20Leitfaden%20des%20ED%C3%96B%20betreffend%20die%20Meldung%20von%20Datensicherheitsverletzungen%20und%20Information%20der%20Betroffenen%20nach%20Art.%2024%20DSG EN
  11. Dealing with requests from individuals - European Commission
  12. Data protection impact assessment
  13. Cross-border transfer of personal data