What counts as a data security breach under Swiss law?
What counts as a data security breach?
What counts as a data security breach under the revised Swiss Federal Act on Data Protection is any breach of security that leads to accidental or unlawful loss, alteration, unauthorised disclosure of, or access to personal data. That definition is in Art. 24 para. 1 FADP. The FDPIC explains notification and documentation in its breach guidance. The term is wider than “hacker attack” and narrower than “any office mistake”.
This glossary is for managers, finance and office staff in SMEs without a dedicated privacy team. You need shared language before someone says “data breach” and everyone reacts differently. A misaddressed email is a common case but has its own how-to: email sent to the wrong recipient. Here we cover everything else you still need to classify.
Typical cases in day-to-day office work
These situations appear often in companies with 20 to 250 people. Each can be a breach when personal data leave your control or become accessible to someone without a need to know.
Laptop left on a train
Customer files on an unencrypted disk. Loss is clear; who read them often is not.
Ransomware with exfiltration
Attackers claim they copied data. Treat it as a breach and document internally even if nothing obvious left the network.
Customer list in To, not Bcc
Every address visible to every recipient. No attachment required; still a disclosure.
Anyone-with-the-link sharing
SharePoint or cloud link open to the internet, invoices or applications inside.
CRM after someone leaves
Former employee still signs in because the account was not disabled.
Paper in recycling
Customer or payroll lists in a box without shredding. Paper counts like digital data.
If your SaaS vendor reports unauthorised access to their platform where your customer data sit, assess it as your incident too. Their postmortem does not replace your internal log. How to keep entries is covered in documenting a data breach.
What is usually not a breach
Not every mistake triggers Art. 24. The line is where data stay under your control and no unauthorised person sees them.
Often counts
- File sent to the wrong external address
- Open link with personal data
- Colleague opens a personnel file without a task
- Stolen phone with readable contacts
Usually does not
- Wrong row in CRM, internal only, no export
- Typo in a note nobody else opens
- Locked screen, nothing copied off it
- Test data with no link to real people
When unsure, note the date, what happened and who was informed. That helps when the “FDPIC yes or no” question comes later.
A breach can happen without the internet: a colleague opens a personnel file without a task, or someone photographs the customer list on screen. Access logs in HR software and shared drives help clarify, but they do not replace management’s judgement.
Notification is the second question
A breach triggers internal documentation. Notification to the FDPIC follows only when high risk to the personality or fundamental rights of the data subjects is likely, as fast as possible, not within 72 hours as under the GDPR. Many incidents are breaches but not FDPIC cases.
Health, financial or other sensitive data make high risk more plausible. See sensitive personal data under the FADP. If you process data about people in the EU, extra duties may apply. Whether the GDPR applies to Swiss companies depends on your market.
Criminal fines under the FADP are separate. They target natural persons with intent, not every breach by default (FADP fines and personal liability).
Organisational measures under Art. 8 FADP (shredder contracts, encryption, permissions) do not prevent every incident, but they show the firm takes security seriously. They do not replace the Art. 24 reporting assessment.
Report fraud, log privacy separately
Reporting phishing or CEO fraud to BACS is not the same as your privacy breach log. When staff report suspicious mail, the path belongs in your playbook: how to report phishing in Switzerland.
- Record the incident internally in brief (what, when, which data)
- Involve IT or your provider if devices or accounts are affected
- Assess whether high risk to affected people is likely
- If risk is high, inform the FDPIC and data subjects per guidance
Training helps staff recognise incidents early and escalate correctly: data protection awareness training.
Written by
Aurum Avis Labs
Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.
Related Articles
You might also be interested in these articles
FADP fines and personal liability in Switzerland
FADP fines up to CHF 250'000 target natural persons with intent, not every honest mistake. What owners and managers should know about Swiss penalties.
Sensitive personal data under the FADP: office examples
Sensitive personal data under the Swiss FADP includes health, beliefs and union membership. Everyday examples for SMEs and tighter handling rules.
Does the GDPR apply to Swiss companies?
Does the GDPR apply to Swiss companies? Art. 3(2) EU scope, Swiss home law, and signs your SME processes EU residents' data.