In short: under the revised Federal Act on Data Protection (FADP), a data breach must be reported to the Federal Data Protection and Information Commissioner (FDPIC) as soon as possible once it is likely to result in a high risk for the people concerned. When in doubt, report first and complete later. The report contains seven items set out in the Data Protection Ordinance (DPO). Your customers must be informed if they need to take action. Keep the incident records for at least two years.
An export of your customer file is circulating outside the company, or ransomware has encrypted the server. For an SME, a data breach under the FADP is not a theoretical scenario: according to a Deloitte survey published in August 2026, 49% of the SME employees surveyed had experienced a serious cyber incident at their employer, and phishing is the most frequently reported threat (25%). Here is the checklist for the first hours.
When must a data breach be reported to the FDPIC?
As soon as the breach is likely to result in a high risk to the personality or fundamental rights of the people concerned, reporting to the FDPIC is mandatory, as soon as possible (art. 24 para. 1 FADP). If you cannot quickly rule out that risk, the FDPIC expects a report before your analysis is complete.
The FADP defines a data security breach (art. 5 let. h) as any accidental or unlawful loss, modification, deletion, destruction or disclosure of personal data, or unauthorised access to it. A lost USB stick, a misaddressed email, a hacking attack: all of these count. The law sets no deadline in hours. The FDPIC guide on art. 24 FADP specifies that ransomware should often be presumed, at first analysis, to involve a high risk.
| Situation | High risk? | Report to the FDPIC |
|---|---|---|
| Health data, identity documents or credit cards exposed | Often yes | Mandatory |
| Ransomware with possible exfiltration | Presumed at first | Mandatory, to be completed later |
| Effectively encrypted data, key not compromised | No (data anonymous to the third party) | No obligation |
| Data already public before the incident | Generally no | No obligation, voluntary report possible |
| Many people affected, low-sensitivity data | Not automatically | Voluntary report possible |
The number of people affected is not, on its own, enough to establish a high risk. Useful vocabulary is in our FADP glossary for SMEs.
What are the 10 actions to take, in order?
Contain first, establish the facts next, assess the risk, then report through the FDPIC portal and warn the people who need to protect themselves. Each step feeds the next: without a reliable list of the people and data affected, neither the report nor the customer notice will hold up.
- 1
Contain the breach
30 minCut off compromised access (passwords, sessions, public shares) and isolate the affected device.
- 2
Record the time of discovery
10 minOpen a dated log: who discovered what, when, and which measures were taken. It feeds the report and the records.
- 3
Preserve the evidence
30 minBack up the login and export logs before any restoration work.
- 4
Identify the people and data affected
60 minCategories of people and of data, with an approximate number for each.
- 5
Assess the risk
45 minSensitivity, encryption, cause, risk of identity theft or fraud. When in doubt, reporting is mandatory.
- 6
Alert your processors and your insurer
30 minAsk the provider concerned about the extent of the incident and check your cyber insurance policy.
- 7
Report to the FDPIC
60 minUse the databreach.edoeb.admin.ch portal with the seven items of art. 15 DPO; missing information is added later.
- 8
Inform the people concerned
90 minDirectly and in plain language, as soon as they have a protective step to take.
- 9
File a criminal complaint if the incident is criminal
60 minHacking or ransomware: file a complaint with the cantonal police.
- 10
Complete and close the file
75 minSupplementary information to the FDPIC, records, technical fixes.
The FDPIC reporting portal secures the transmission, issues a time-stamped confirmation and accepts follow-up information. The seven items of art. 15 DPO are: the nature of the breach; if possible, when it occurred and how long it lasted; the categories and approximate number of data records; the categories and approximate number of people; the consequences and risks; the measures taken or planned; a contact person.
A clarification to avoid confusion: the obligation to report a cyberattack to the National Cyber Security Centre within 24 hours, in force since 1 April 2025, applies to operators of critical infrastructure. For a fiduciary firm or a property management agency in French-speaking Switzerland, the report to the FDPIC is what counts.
Do you have to inform your customers after a data breach?
Yes, when it is necessary for their protection or when the FDPIC requires it (art. 24 para. 4 FADP). That is the case as soon as they need to act themselves: change a password, block a card, watch out for fraudulent emails. This obligation applies even if the risk is not high within the meaning of the reporting duty.
The message, in plain language, contains at least the nature of the breach, its consequences, the measures taken and a contact person (art. 15 para. 3 DPO). In principle, people are informed directly and individually. A public announcement is only allowed if it informs them in an equivalent way (art. 24 para. 5 FADP). After a leak of email addresses, warn your customers that phishing in your name is likely.
What should your CRM be able to tell you within an hour?
Three answers: who is affected, which data, which access. Without them, the report to the FDPIC stays vague and informing customers becomes impossible. A CRM that centralises contacts, logs exports and manages permissions per user provides these answers in minutes, whereas a shared Excel file leaves no trace.
Check today that your tool can produce:
- contacts by segment, with a count (number of people);
- the fields stored per record (categories of data);
- the login and export log (date, account used);
- permissions per user (what a compromised account could see);
- contact details (individual notification).
This is one of the limits of a CRM built on Excel: once copied as an attachment, the file no longer tells you who opened it.
Your provider matters too. A processor must report any data security breach to you, without first assessing the risk (art. 24 para. 3 FADP). Hosting in Switzerland avoids adding a foreign legal system to the equation, with data kept in the country and no transfer abroad. Our criteria for an FADP-compliant CRM list the clauses to check.
What should you document and fix after the incident?
Art. 15 para. 4 DPO requires breaches to be documented: facts, effects, measures taken. These records must be kept for at least two years from the date of the report. The FDPIC is active: in the 2025/26 reporting year, it received more than 2,000 reports of potential data protection breaches and conducted 22 preliminary investigations and 9 investigations.
Failing to report is not in itself punishable under the FADP: the FDPIC can order the omission to be remedied. The criminal risk lies elsewhere. Art. 61 let. c FADP punishes, upon complaint, a private person who intentionally fails to meet the minimum data security requirements with a fine of up to CHF 250,000. The report can only be used in criminal proceedings against you with your consent (art. 24 para. 6). See our explanation of FADP penalties for SME managers. To fix the problem at the source, read our guide to cybersecurity and CRM hosting.
Frequently asked questions
What is the deadline for reporting a data breach to the FDPIC?
There is no fixed deadline: the report must be made as soon as possible, without waiting for the clarifications to be complete if a high risk cannot be ruled out. Missing information is added afterwards.
Is an email sent to the wrong recipient a data security breach?
Yes, within the meaning of art. 5 let. h FADP. Reporting is only mandatory if the risk is likely to be high. Document the incident internally in every case.
My CRM provider was hacked: who has to report it?
You do, as the controller. The provider must report it to you as soon as possible (art. 24 para. 3 FADP); it is then up to you to assess the risk, report it and inform your customers.
Are reports to the FDPIC confidential?
No. According to the FDPIC guide, they are in principle official documents accessible under the Freedom of Information Act, subject to exceptions assessed case by case. Stick to the facts.
Does stolen encrypted data have to be reported?
Not if it was effectively encrypted and the key remained intact: the FDPIC treats it as anonymous to the third party. Data that was only pseudonymised, however, can trigger the obligation.
Three reflexes: report when in doubt, warn the customers who need to protect themselves, keep records for two years. An SME that can answer "who, what, which access" within an hour gets through a data breach without improvising. Helvee centralises your contacts in a CRM hosted 100% in Switzerland: a way to turn FADP compliance into a mark of trust.
