{"id":1143,"date":"2023-08-30T20:07:59","date_gmt":"2023-08-30T18:07:59","guid":{"rendered":"https:\/\/www.voxlegal.ch\/the-revised-dpa-comes-into-force-on-september1\/"},"modified":"2023-12-21T16:49:40","modified_gmt":"2023-12-21T15:49:40","slug":"the-revised-dpa-comes-into-force-on-september1","status":"publish","type":"post","link":"https:\/\/www.voxlegal.ch\/en\/the-revised-dpa-comes-into-force-on-september1\/","title":{"rendered":"The revised DPA comes into force on September 1st<\/sup>!"},"content":{"rendered":"\n

The long-awaited revision of the Federal Data Protection Act (“DPA”) comes into force this Friday. Contrary to what we often see when legislation is passed, this revision does not provide for a transitional period. This means that from September 1, 2023, a number of new obligations will apply to the processing of personal data covered by art. 2 of the DPA<\/a>. But in concrete terms, what are these new features for you?<\/p>\n\n

<\/div>\n
\n\t\n\n
\n\t\t\t
\n\t\t\t\n\n
\n
\n
\"\"
Image generated with Midjourney<\/figcaption><\/figure>\n<\/div>\n<\/div>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n\n

Are you concerned<\/u>?<\/strong><\/h3>\n\n

As a preliminary point, a distinction must be made between the situation of entities that were already complying with the obligations arising from the General Data Protection Regulation (“GDPR”), and entities that were not affected by it.<\/p>\n\n

Indeed, for many Swiss companies, compliance with the GDPR has already been necessary, for example because they were processing personal data targeting European residents. For these companies, implementing the requirements of the DPA is not normally problematic, as the GDPR is deemed, with a few exceptions, to be more protective of personal data than the DPA.<\/p>\n\n

On the other hand, for companies that have not had to comply with the GDPR, some adjustments to their processes are likely to be necessary. It should be noted from the outset that for private individuals, personal use is not covered by the scope of the DPA (art. 2 al. 2 let. a LPD<\/a>).<\/a><\/p>\n\n

What is “personal” data?<\/span> <\/strong>?<\/h3>\n\n

This is nothing new in the DPA, but it is worth remembering that only personal data is concerned. For data to be personal<\/span>, it must relate to an identified or identifiable <\/span> natural person (watch out for “pseudomnymization”). In practical terms, this could be contact details or any other personal information. The definition is extremely broad, and even includes IP addresses, for example, where these can be used to identify a user.<\/p>\n\n

On the other hand, anonymous data is not covered by the DPA. However, when the data subject is identifiable, even if only with difficulty, the data is not anonymous.<\/p>\n\n

What is a treatment<\/span>?<\/strong><\/h3>\n\n

The law defines processing as “any operation relating to personal data, whatever the means and procedures used, in particular the collection, recording, storage, use, modification, communication, archiving, erasure or destruction of data”. Although this is nothing new, it is worth remembering that this definition is extremely broad in scope.<\/p>\n\n

What’s new<\/span>?<\/strong><\/h3>\n\n

Below are some of the most important changes brought by the revision of the DPA. These are just a few examples, and are not intended to be exhaustive.<\/p>\n\n

Increased focus on data protection<\/span>:<\/p>\n\n

As in European regulations, the DPA adopts the principles of “Privacy by Design” and “Privacy by Default”(art. 7 DPA<\/a>).<\/p>\n\n

The “Privacy by Design” principle means that privacy concerns must be taken into account right from the design stage of a new product or service.<\/p>\n\n

The “Privacy by Default” principle implies that a new product or service must be configured to respect the privacy of its users. In other words, users should not have to change their settings to protect themselves against the use of their personal data.<\/p>\n\n

Greater transparency<\/span>:<\/p>\n\n

The collection of personal information must now be notified in advance to the persons concerned (art. 19 LPD<\/a>). Until now, this has only been the case for sensitive data.<\/p>\n\n

Obligation to keep a register of processing activities<\/span>:<\/p>\n\n

It is now compulsory to keep a register of processing activities (art. 12 LPD<\/a>). Companies with fewer than 250 employees, which do not engage in large-scale processing or high-risk profiling, are exempt from this obligation.<\/p>\n\n

However, even for exempt companies, there are good reasons to keep a register, so as to be better able to meet the other requirements of the DPA.<\/p>\n\n

Obligation to report violations promptly<\/span>:<\/p>\n\n

In the event of a security breach likely to create a high risk for the personal rights and fundamental entitlements of the data subject, the company must inform the Federal Data Protection and Information Commissioner as soon as possible (art. 24 DPA<\/a>).<\/p>\n\n

New criminal penalties<\/span>:<\/p>\n\n

Under the DPA, fines of up to CHF 250,000 can be imposed for failure to comply with the law (art. 60 DPA<\/a>). Unlike the RGPD, it’s the individual responsible for the damage who gets fined, not the company.<\/p>\n\n

Other news<\/span>:<\/p>\n\n

We will also mention the following points without going into them in detail:<\/p>\n\n