How fast must a data breach be reported under the FADP?
Direct answer
As quickly as possible. Article 24 of the Swiss Federal Act on Data Protection (FADP) requires the controller to notify the FDPIC as quickly as possible of a breach of data security that is likely to result in a high risk for the people concerned. The FADP sets no fixed 72-hour deadline, unlike the GDPR.
The notice is filed through the FDPIC’s online portal, databreach.edoeb.admin.ch.
What Article 24 asks
- The threshold. A notice is due when a breach of data security is likely to result in a high risk for the people concerned. Not every breach reaches it.
- The timing. The wording of the law is "as quickly as possible". It names no number of hours.
- The channel. The controller files through the FDPIC’s portal at databreach.edoeb.admin.ch.
- The people affected. The controller also informs them when that is needed to protect them.
FADP and GDPR compared
| Point | Swiss FADP | GDPR |
|---|---|---|
| Deadline | As quickly as possible, no fixed hours | Without undue delay and, where feasible, within 72 hours |
| Authority | FDPIC | The competent EU supervisory authority |
| Article | Article 24 FADP | Article 33 GDPR |
A company under both laws works to both. Many use the GDPR’s 72 hours as their working clock and treat the FADP notice with the same urgency. See the GDPR 72-hour breach notification rule.
What to do
- Decide who judges whether a breach is likely to result in a high risk, and record the reasoning either way.
- Ask your processors to tell you about any breach as quickly as possible. See does a processor have to notify the FDPIC?
- Check whether the same incident also needs an ISA report. See ISA report and FADP breach notice.
This is general information, not legal advice: scope depends on your facts, so confirm it with a qualified lawyer. The FADP is one of several laws with a breach or incident clock: see what a Swiss company must comply with, the Swiss FADP guide and Swiss FADP compliance software.
Tracking a breach in Acuna GRC
In Data Privacy in Acuna GRC, the breach wizard records the breach type, the risk to rights and the affected activities, assets and third parties. A live clock counts down 72 hours, the GDPR deadline, and turns amber then red; Mark supervisor notified records the exact time, and a notice for the authority is generated. The clock is not an FADP deadline, and Acuna GRC does not file with the FDPIC. See Data privacy management.
How Acuna GRC handles it
In Acuna GRC, the Data Privacy breach wizard runs a live 72-hour clock, the GDPR deadline, and records the exact time the authority was notified.
- Module
Data Privacy
Processing activities, data inventory and flows, DPIAs, DPAs, TIAs, data subject requests and breaches, with a public privacy portal.
- Solution
Swiss FADP
Meet your revFADP duties: a record of processing, impact assessments for high-risk processing, access requests and breach reports to the FDPIC, with the GDPR.
- Service
DPO as a service
An external DPO from Swiss experts: your record of processing, DPIAs, data subject requests and breaches, run in Acuna GRC for the GDPR and the Swiss FADP.
Sources
- Federal Act on Data Protection (FADP, SR 235.1)
- FDPIC, data breach reporting portal
- Regulation (EU) 2016/679 (GDPR), Article 33
This page explains the rules in general terms and is not legal advice.
Frequently asked
Is there a 72-hour rule for data breaches in Switzerland?
Not in the FADP. Seventy-two hours is the GDPR deadline. The FADP asks for a notice as quickly as possible.
Must every data breach be reported to the FDPIC?
No. The duty applies when the breach is likely to result in a high risk for the people concerned.
Who files the notice, the controller or the processor?
The controller. A processor informs the controller as quickly as possible of any breach (Article 24(3) FADP).
See how Acuna GRC runs this.
Tell us your frameworks and your team. We show you how Acuna GRC runs the program.
Hosted in Switzerland, the EU or the US
.png&w=3840&q=75&dpl=dpl_96PxuEbyzwoWxjweCh9wLaGaDCHP)

