Over the last 2 years we have often heard about the GDPR: the 2016/679 European regulation (GDPR for friends) came into force in the end of May 2018. In this post I will try to explain the key points of the regulation, in a simple way and without too many complicated details.
The name “General Data Protection Regulation” tells us it is a Regulation. It means that on the 25th of May 2018 it became de facto a law in all member states of the European Union. I make this clarification, because unlike the Directive, which asks member states to write a law in a certain direction, a regulation does not need any further passage.
The GDPR establishes the rules to protect the personal data of European citizens, so it should not be confused with company’s data like prototypes, projects, patents, financial statements or whatever. In practice, all subjects (companies, entities as well as other citizens), including those from outside the EU, who process personal data of the European citizens, must comply with the regulation.
Before getting to the heart of what the GDPR says, let us clarify some definitions:
Article 4 of the GDPR defines it as “any information concerning an individual identified directly or indirectly by reference to any other information”. It means a name, an address as well as car plate numbers are all personal data. It does not matter that the data is visible to everyone (think of the car plate numbers for example), as it is the combination of the plate number and the person that form the personal data.
Another important word to know is Processing. By this we mean “any operation or set of operations, carried out with or without the aid of automated processes and applied to personal data or sets of personal data, such as the collection, registration, organization, structuring, conservation, adaptation or modification, extraction, consultation, use, communication by transmission, diffusion or any other form of making available, comparison or interconnection, limitation, cancellation or destruction”.
The interested party is the owner of the data, i.e. every person is the interested party of his or her personal data.
The data controller is the person, company or entity that asks for personal data to be able to process it and decides how and why to process it. Attention is not to those who manages the data, but who makes decisions on data processing.
It is the natural, legal, public administration or body that processes personal data on behalf of the data controller.
Also known as DPO, an acronym for the English definition, this figure is designated by the owner and the person in charge of the treatment, to act as an expert on the subject (usually he is a lawyer). In practice, it deals with helping those who must process personal data, respecting the GDPR, providing opinions, informing, and supervising.
Before the GDPR this type of data was called sensitive and included racial or ethnic origin, political opinions, religious or philosophical beliefs, or union membership, as well as genetic data, biometric data intended to identify a unique individual, data relating to the health or sexual life or sexual orientation of a person.
The security breach that accidentally or unlawfully involves the destruction, loss, modification, unauthorized disclosure, or access to personal data transmitted, stored, or otherwise treated.
The word that may awaken fear but is simple. The processing of personal data so that it can no longer be attributed to a specific interested party without the use of additional information. Imagine having two registers, one with two columns: the first column contains the names of the people and the second a numerical code associated with each of them. The other register contains the numerical code in the first column and in the second column, the personal data to be protected. To understand who the data belongs to, it is necessary to correlate the information on the two registers. The personal data in the second register is “pseudonymized”.
After this long but necessary introduction, let us find out what the rights of European citizens are regarding personal data.
The most important article (there are 99 of them in total) is of course the first one. Point 2 in my opinion is the heart of the regulation saying: “This Regulation protects fundamental rights and freedoms of natural persons and in particular their right to the protection of personal data”. But what exactly does that mean? What are the rights and freedoms it protects? An entire chapter of the regulation is dedicated to the “Rights of the data subject”, that is divided into five sections. Let us quickly analyze them.
This section includes a single article (the 12th) entitled: “Transparent information, communication and modalities for the exercise of the rights of the data subject”. Basically the article says that the data controller (the one collecting the data) must communicate with the data subject in a clear manner, and must facilitate him in his requests (in relation to the personal data processed by the owner) and in general in exercising the rights provided by the regulation.
Here we get to the main part: before processing the data, the owner must tell you who and why processes the data, and how long the data is kept. He also says that you can ask to view, modify, or delete our personal data in his possession anytime.
It is your right to ask to change your data (rectification) or to request cancellation, the famous “right to be forgotten”. In fact, at any time you can withdraw consent to the processing and ask to be forgotten (useful for defending against some very aggressive marketing campaigns).
Right to data portability (article 20) is an interesting one, that allows the interested party to request the owner to provide all personal data referring to him “in a structured, commonly used and machine-readable format”. This article, in fact, is what forced Google, Facebook and the other web giants to provide their users with a link to request all data about an individual in their possession. It works, and I recommend you try it at least once here or here.
This goes hand in hand with the article on the right to be forgotten, but applies when it is not necessary to ask for permission to process personal data because “processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party” (art. 6, par.1, letter f).
Obviously, the EU can limit the rights and obligations established by the regulation to safeguard more important interests, such as national security, independence of the judiciary and judicial proceedings, public safety, protection of the data subject or the rights and freedoms of others, and other critical issues.
Chapter four describes the obligations of the owner and manager of the processing of personal data. In particular, they overview the compliance responsibilities of these two figures, including the obligation to protect the personal data they process (by encrypting them or applying pseudonymization), to keep a register of treatments, and to evaluate the impact of the treatments before proceeding.
The last aspect that deserves your attention is that of personal data breaches. Section 2 of Chapter 4 is dedicated to the security of the data processing, where Article 33 is certainly one of the most important and is dedicated to the “notification of a personal data breach to the supervisory authority”. Its first paragraph is the famous communication to the “Garante” (in Italy the supervisory authority is called “Garante per la protezione dei dati personali” ) in case of data breach:
“In the event of a personal data breach, the data controller notifies the competent supervisory authority pursuant to Article 55 of the violation without undue delay and, where possible, within 72 hours from the time when it became aware of it, to unless the breach of personal data is unlikely to present a risk to the rights and freedoms of individuals. If the notification to the supervisory authority is not made within 72 hours, it shall be accompanied by the reasons for the delay “.
Heavy administrative and pecuniary sanctions applied to the owners, who do not respect the regulation, certainly made it famous. Fines can vary depending on the violations but are still very relevant. They start from fines of up to 10 million euros or (for companies) to 2% of their turnover, for example, for not having a data controller appointed. The fine can reach € 20 million or 4% of the company turnover in case of more serious violations like failure to notify a data breach.
According to a study by DLA PIPER published in January 2020, since the GDPR entry into force there were about 160 000 personal data breaches discovered in Europe, imposed by 114 million euros of sanctions. Holland leads the rankings with 40 647 data breach incidents, followed by Germany (37 636 incidents), the United Kingdom (22 181 incidents), Ireland (10 516 incidents) and Denmark (9 806 incidents). As for the sanctions, France was fined for 51 million euros, followed by Germany (24.5 million euros) and Austria (18 million euros).
What about Italy? According to the same report, from the 25th of May 2018 to January 2020, the Guarantor was notified of 1 886 personal data violation cases (ranked 11) and imposed fines of 11.55 million euros (ranked 4).
In the end of May 2020, we expect a new report, that provides analysis of the 2-year period after the GDPR came into force.
Image by BiljaST
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gat_gtag_UA_150416163_1 | 1 minute | Set by Google to distinguish users. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
pardot | past | The pardot cookie is set while the visitor is logged in as a Pardot user. The cookie indicates an active session and is not used for tracking. |
visitor_id909942-hash | 10 years | No description |
Cookie | Duration | Description |
---|---|---|
lpv909942 | 30 minutes | No description |
visitor_id909942 | 10 years | No description |