Comwil

Compliance

Swiss data protection law: a checklist for IT teams

What the revised Swiss Data Protection Act means for IT: data inventory, security measures, breach reporting and providers. General guidance, not legal advice.

Published 8 November 20267 min readCompliance

Key takeaways

  • The revised Swiss Data Protection Act (FADP, in German nDSG) has applied since 1 September 2023 to companies that process personal data.
  • IT’s part is mostly practical: know where personal data is, protect it in proportion to the risk, handle breaches and control service providers.
  • Breaches that are likely to lead to a high risk must be reported to the data protection authority (FDPIC) as soon as possible.
  • This is general information, not legal advice. Ask a data protection lawyer about your specific duties.

What changed in 2023

The revised law brought Swiss data protection closer to the European GDPR, while keeping its own character. It strengthens transparency toward the people whose data you process, adds duties such as privacy by design and by default, and introduces a duty to report certain data breaches.

A notable difference from the GDPR is that fines target responsible individuals rather than the company, up to CHF 250,000, and that the law punishes intentional breaches of specific duties. That makes it worth knowing who is responsible for what inside your organisation.

The IT checklist

  • Know where personal data lives. List systems, cloud services and file shares that hold personal data of customers, employees and applicants. This inventory is the base for everything else. Smaller companies are partly exempt from keeping a formal record of processing activities, but the inventory is still the best place to start.
  • Protect it in proportion to the risk. Access control with least privilege, multi-factor authentication, encryption of devices, patching, backups and logging are the standard technical and organisational measures.
  • Control your service providers. If a cloud or IT provider processes personal data for you, you need a contract that covers security and sub-processors, and you need to know where the data is processed.
  • Check cross-border transfers. Sending personal data to a country without an adequate level of protection needs safeguards such as recognised standard contractual clauses.
  • Have a breach process. Detect, assess and decide quickly, and document the decision. If a breach is likely to lead to a high risk for the people concerned, report it to the FDPIC as soon as possible and inform them where needed.
  • Be ready for requests. People can ask what data you hold about them. You generally have 30 days to answer, so you must be able to find the data.
  • Delete what you no longer need. Define retention periods and make sure deletion actually happens, including in backups over time.
  • Think of privacy early in projects. For new systems and processes that carry high risk, assess the impact before launch.

What the law does not require

There is no general obligation to appoint a data protection officer, and no mandatory certification. Many obligations are scaled to the risk, so a ten-person company is not expected to run the same programme as a bank. Proportionate, documented and consistently applied measures are the aim.

Where to start

Begin with the inventory, then fix the obvious gaps: MFA, backups, access rights and provider contracts. Write a one-page breach procedure and test it once. Keep a simple log of decisions so you can show what you did and why.

This article is general information and not legal advice.

We help with the technical side: security services for measures and monitoring, and IT consulting for inventories, policies and provider reviews.

Let’s talk about your IT

Tell us what you need. We will come back with a clear proposal and a named contact.