Regulatory & Compliance
Analysis of the Changes Introduced by the RGPD
Patricia Lalanda ·
1. Introduction
On 5 May 2016, Regulation (EU) 2016/679, of 27 April 2016, on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation or “RGPD”) entered into force. It replaces the former Data Protection Directive, which laid down minimum requirements and allowed states to decide how to fulfil its objectives. The RGPD establishes the data protection regime directly applicable to all states of the European Union. However, it allows a period of two years for those processing the personal data of natural persons and for data protection agencies to adapt to the new system, and therefore does not apply until 25 May 2018.
Current Spanish legislation, and in particular Organic Law 15/1999, of 13 December, on the Protection of Personal Data (“LOPD”), and Royal Decree 1720/2007, of 21 December, approving the Implementing Regulation of Organic Law 15/1999, of 13 December, on the protection of personal data (“RLOPD”), is among the most protective in Europe. Accordingly, the new RGPD does not introduce as many differences from the previous regime as in other countries, although there remain a number of additional obligations that must be fulfilled from 25 May 2018.
2. Application of the RGPD
The General Data Protection Regulation, as a regulation, will have general application. It will be binding in its entirety and directly applicable in each Member State, as if it were a national law. It will therefore be directly applicable by national courts and by the Spanish Data Protection Agency (“AEPD”) to companies and other persons affected.
The existing legislation, essentially the LOPD and the RLOPD, will not be completely repealed by the RGPD; rather, the latter will displace the legislation currently in force in this area. In other words, the principal applicable instrument will be the General Data Protection Regulation, while the provisions of the LOPD and its implementing regulation may only apply where they regulate matters not covered by the Regulation, and insofar as they do not contradict it. However, when the RGPD becomes applicable from 25 May 2018, the Spanish legislature will most likely repeal the LOPD or amend it to bring it into line with the RGPD.
3. Changes Introduced by the RGPD
The RGPD is based on the concept of accountability, whereby the responsibility of those processing personal data does not arise only in the event of an infringement; rather, they must exercise diligence in adopting all measures necessary for regulatory compliance. To that end, the Regulation enshrines the principle of privacy by design, or privacy by design, whereby personal data protection measures are applied from the point at which processing is designed, to ensure compliance with the legislation. Furthermore, in accordance with the principle of privacy by default, the use and retention of data, as well as access to them, will be limited to the minimum necessary to carry out the processing. Specifically, the main changes introduced by the Regulation consist of the extension of its territorial scope, the strengthening of the data subject's consent, the introduction of the right to be forgotten and the right to portability, the strengthening of the duty to provide information, the obligation to notify security breaches, obligations to be fulfilled within the company, the end of the obligation to notify filing systems, and changes concerning the powers of supervisory authorities, security measures and penalties.
3.1. Extension of Territorial Scope
Article 3 of the Regulation provides that it “applies to the processing of personal data in the context of the activities of an establishment of a controller or a processor in the Union, regardless of whether the processing takes place in the Union or not.” Furthermore, as a new provision, the Regulation also applies “to the processing of personal data of data subjects who reside in the Union by a controller or processor not established in the Union, where the processing activities are related to the offering of goods or services to such data subjects in the Union, irrespective of whether a payment by those data subjects is required; or the monitoring of their behaviour insofar as their behaviour takes place within the Union.” This constitutes an extension of the territorial scope of European data protection legislation, insofar as, in addition to controllers or processors with an establishment in the Union, it applies to those in third countries processing the data of European citizens, whether with a view to offering goods or services or to monitoring their behaviour (insofar as this takes place within the EU), even if they have no physical presence within the territory of the Union. Thus, companies of this kind, which were previously not bound by European data protection legislation, become directly responsible and must comply with all the obligations laid down by the Regulation.
3.2. Strengthening of Consent
Under the LOPD, the data subject's consent was “any freely given, unambiguous, specific and informed indication of wishes by which the data subject consents to the processing of personal data relating to him or her.” However, the Regulation adds the requirement that such consent be given “by a statement or by a clear affirmative action”. Thus, in cases where the data subject's consent is required, the implied consent that was sometimes permitted, particularly on the internet, is no longer acceptable; instead, there must be a positive action on the data subject's part. For example, consent will no longer be deemed to have been given merely by browsing a website.
The LOPD requires consent to be explicit in respect of personal data referring to racial origin, health and sex life, and this regime will therefore be maintained under the RGPD. Furthermore, in the case of personal data revealing ideology, trade union membership, religion and beliefs, the LOPD requires consent to be explicit and in writing. On this point, it remains to be seen whether it is considered permissible under the RGPD for the LOPD to introduce this additional requirement for obtaining consent in respect of specially protected data.
In addition, the RGPD sets out the conditions under which consent given by minors is acceptable, establishing a special regime for children under the age of 16 (which Member States may lower to 13), under which consent must be given or authorised by the holder of parental responsibility or guardianship over the child. The implementing regulation of the LOPD lowers the age to 14, and it is therefore expected to remain as it is at present.
3.3. Right to Be Forgotten and Right to Portability
The General Data Protection Regulation not only recognises the traditional rights of access, rectification, cancellation and objection, with certain terminological differences, but also regulates two new rights: the so-called right to be forgotten and the right to data portability.
The right to be forgotten is regulated in Article 17 of the RGPD and allows the data subject, in a number of cases, to obtain from the controller the erasure of personal data concerning him or her without undue delay. It is simply a manifestation of the traditional rights of objection and cancellation, but strengthened and also guaranteed in the internet environment. It thus enshrines the right recognised by the Court of Justice of the European Union in Case C‑131/12, Mario Costeja v Google, in which the search engine was ordered to de-index personal data that had lost their informational relevance. Its principal limitation, therefore, is that those data remain relevant in accordance with the right to freedom of expression and information. Under the Regulation, the right is recognised beyond the sphere of internet news search engines and extends to any controller. In Spain, given that the right to be forgotten recognised in the Costeja case is regularly applied, and that the rights of objection and cancellation cover a wide range of situations outside the online sphere, this does not represent a major change beyond terminology, but it strengthens legal certainty and guarantees that the same rights can be exercised throughout the European Union.
The right to data portability under Article 20 of the RGPD allows the data subject to receive the personal data concerning him or her which he or she has provided to a controller by automated means, in a structured, commonly used and machine-readable format, and to transmit those data to another controller without hindrance from the first controller. Furthermore, the data subject will have the right to have the personal data transmitted directly from one controller to another where technically feasible. This right facilitates electronic contracting and switching service providers, simplifying the transfer of personal data to the new provider and ensuring that the previous provider does not retain the data subject's personal data. Article 22 also includes the right not to be subject to behavioural profiling, with certain exceptions.
3.4. Strengthening of the Duty to Provide Information
The LOPD establishes what information must be provided to the data subject when data are collected, but the RGPD strengthens this obligation by introducing new matters that must be communicated under Article 13. Before data are obtained from the data subject, he or she must, as a new requirement, be informed, among other things, of the contact details of the data protection officer, where applicable; the legal basis for the processing; the recipients or categories of recipients of the personal data; the controller's intention to transfer personal data to a third country or international organisation and the existence or absence of an adequacy decision by the Commission; the period for which the personal data will be stored or, where this is not possible, the criteria used to determine that period; etc.
In Article 14, the Regulation also extends and specifies the information to be provided where personal data have not been obtained from the data subject. This must be provided no later than one month after the personal data have been obtained, or at the time of the first communication with the data subject; and before they are disclosed to another recipient. This reduces the period, which was three months under the LOPD. In addition to the matters already included in the LOPD, such as the existence of a personal data filing system or processing, the purpose of collecting the data and the recipients of the information; the possibility of exercising the rights of access, rectification, cancellation and objection; the identity and address of the controller or, where applicable, its representative; the content of the processing; or the source of the data; much more information must be provided, such as the contact details of the data protection officer, where applicable; the legal basis for the processing; the categories of personal data concerned; where applicable, the controller's intention to transfer personal data to a recipient in a third country or international organisation and the existence or absence of an adequacy decision by the Commission; the period for which the personal data will be stored or, where this is not possible, the criteria used to determine that period; or the right to lodge a complaint with a supervisory authority.
3.5. Obligation to Notify Security Breaches
The RGPD includes an obligation on the controller to notify any personal data breach both to the supervisory authority and to the data subjects. Under Article 33, the security breach must be notified to the supervisory authority competent “without undue delay and, where feasible, not later than 72 hours after having become aware of it, unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons. Where the notification to the supervisory authority is not made within 72 hours, it shall be accompanied by reasons for the delay.” That notification must describe the nature of the personal data breach, including the categories and approximate number of data subjects concerned and the categories and approximate number of personal data records concerned; communicate the name and contact details of the data protection officer or other contact point where more information can be obtained; describe the likely consequences of the personal data breach; and describe the measures taken or proposed to be taken by the controller to address the personal data breach. If the security breach occurs at the processor, it must notify the controller of the breach without undue delay, so that the controller can make the corresponding notifications.
Article 44 of the RGPD further provides that the controller must communicate to the data subjects, without undue delay, breaches of the security of their personal data where these entail a high risk to the rights and freedoms of natural persons. This must be done in clear and plain language, communicating the contact details of the data protection officer; describing the likely consequences of the personal data breach; and the measures taken or proposed to address the personal data breach. This communication will not be necessary if appropriate protection measures have been adopted and applied to the personal data affected, in particular those involving data encryption; if subsequent measures have been taken to ensure that the high risk to the data subject's rights and freedoms is no longer likely to materialise; or if it would involve disproportionate effort. In that case, a public communication or similar measure will be used instead, whereby the data subjects are informed in an equally effective manner.
3.6. Obligations Within the Company: Records of Activities, PIAs and DPO
The RGPD transfers responsibility for the adequate protection of personal data to the companies carrying out the relevant processing. Thus, first, companies and organisations employing more than 250 people, those which process data frequently in a manner that may entail a risk to rights and freedoms, or whose processing includes specially protected personal data or data relating to criminal convictions and offences, must keep a record of processing activities carried out under their responsibility. This internal record, which must be kept by both controllers and processors, must be in writing and contain detailed information on each instance of data processing they carry out.
Secondly, under Article 35 of the RGPD, in certain circumstances where processing is likely to result in a high risk to the rights and freedoms of natural persons, particularly through the use of new technologies, the controller must, before processing, carry out an impact assessment (data protection impact assessment) of the processing operations on the protection of personal data. This must contain a description of the envisaged processing operations, the purposes, an assessment of the necessity and proportionality of the operations, an assessment of the risks to the rights and freedoms of data subjects, and the measures envisaged to address the risks. A single assessment may address a set of similar processing operations that present similar high risks. Where the impact assessment concludes that the processing would result in a high risk, the controller must consult the supervisory authority before proceeding with the processing, and the authority will provide advice on it.
Thirdly, companies acting as controllers or processors whose core activities consist of processing operations which, by virtue of their nature, scope and/or purposes, require regular and systematic monitoring of data subjects on a large scale; or consist of processing on a large scale of special categories of personal data and/or data relating to criminal convictions and offences, must appoint a Data Protection Officer (or Data Protection Officer). Other companies may designate one if they so wish, and a group of undertakings may appoint a single data protection officer for the whole group. The data protection officer may be a member of staff or engaged externally, and must be designated on the basis of professional qualities and, in particular, expert knowledge of data protection law and practice and the ability to perform his or her duties. The officer must be involved in all matters relating to data protection and be the person whom data subjects contact to manage their rights. Thus, the officer is responsible for informing and advising the controller and the employees carrying out processing of their obligations under data protection legislation, monitoring compliance with that legislation and with the data protection policies in place within the company, carrying out impact assessments, and cooperating and maintaining contact with the supervisory authority. The officer's activities must comply with the duty of confidentiality and secrecy and be independent of the controller and processor, from whom the officer may not receive instructions, reporting to the highest management level of the company. In any event, if an infringement occurs, liability will continue to rest with the controller, not with the data protection officer.
In many cases, the introduction of the data protection officer will not entail a major change within the company, as there will already be a specific person or body responsible for managing data protection activities. In such cases, it will be necessary to designate who is to be regarded as the data protection officer, regardless of whether that person works individually or as part of a team. The implementing regulation of the LOPD establishes the obligation to designate a security officer to coordinate and monitor the security measures applied to personal data. Although this represents a precursor to the data protection officer, it normally involves personnel whose knowledge is primarily IT-related or technical. The data protection officer must be a person whose duties relate solely to personal data protection within the company, and may work with the cooperation of the security officer, or be the same person, if he or she combines technical and IT knowledge with specific data protection knowledge.
As a counterpart to the additional monitoring obligations within companies themselves, the RGPD removes the obligation to notify filing systems to the supervisory authorities. However, the obligation remains until the Regulation enters into force on 25 May 2018.
3.7. Data Protection Authorities
As a major change introduced by the RGPD, the rules on the territorial competence of data protection authorities change substantially. At present, the Spanish Data Protection Agency is responsible for applying the LOPD where processing is carried out in Spanish territory, at an establishment of the controller, or using equipment situated in Spanish territory. However, the RGPD establishes common legislation for all Member States and seeks to ensure uniform application to each company. It therefore designates as the lead supervisory authority that of the territory in which the main or sole establishment of the controller or processor is located. Thus, each company is subject to the competence of the data protection authority of its main establishment, irrespective of how many states it operates in and whether it carries out cross-border processing.
If a data subject lodges a complaint with a supervisory authority other than the lead authority, that authority may handle it if it relates solely to an establishment in its Member State or substantially affects data subjects only in its Member State, informing the lead supervisory authority accordingly. At that point, the lead supervisory authority may decide to handle the case itself, for which purpose it will cooperate with the supervisory authority concerned which notified it of the complaint. To ensure protection for the data subject who lodged the complaint, even though the decision is taken by the lead supervisory authority, it is formally adopted by the supervisory authority concerned with which the complaint was lodged, so that the data subject may challenge it before the courts of his or her own state. The system established by the Regulation seeks to ensure cooperation between supervisory authorities, which may request mutual assistance and even conduct joint operations, to ensure consistent application of the new legislation.
3.8. Security Measures and Penalties
Unlike the current LOPD, the RGPD does not establish a list of security measures, but merely states that those adopted must be “appropriate” to the risk. In this regard, the breakdown of measures in the LOPD is merely purposive, setting out measures that should suffice to comply with data protection obligations; accordingly, once the RGPD applies, that list may serve as guidance for companies in assessing their compliance, as it has until now.
The amount of penalties in the event of an infringement is, however, amended more substantially. The Regulation introduces a much more flexible system, with numerous factors to be taken into account in determining the penalty, without setting minimum amounts, but with much higher maximum amounts which take into account the company's total worldwide annual turnover for the preceding financial year. Thus, in the case of minor infringements, the penalty may reach 2% of that turnover, and in the case of the most serious infringements, 4%.
4. Conclusions
The General Data Protection Regulation, which enters into force on 25 May 2018, will change the data protection landscape for companies. They will have to exercise greater diligence in the proper processing of personal data and will have to guarantee more rights for data subjects. The data protection officer emerges as a key figure, who must be appointed in most companies and will be responsible for ensuring compliance with all the obligations imposed by the new legislation and for ensuring that data subjects' rights are guaranteed. In the event of an infringement, liability continues to rest with the controller, and penalties may be much higher than at present, being linked to the company's turnover.
It is therefore advisable that, before the deadline arrives, the company reviews its internal structure to ensure that it has the necessary mechanisms to enable the data protection officer to perform his or her duties properly, that its employees are familiar with the data protection protocols required for their roles, and that all data processing is carried out appropriately. Furthermore, it would be advisable for data collection to comply with the new information duties under the RGPD as soon as possible, so that, when it becomes applicable, data obtained previously and ongoing processing already comply with the personal data protection rules under the Regulation.
To find out how you can adapt your company to the RGPD, you may contact the LOYRA ABOGADOS team through Patricia Lalanda : patricia.lalanda@loyra.com.