General Data Protection Regulation

From Wikipedia, the free encyclopedia
Jump to: navigation, search

The European Commission plans to unify data protection within the European Union (EU) with a single law, the General Data Protection Regulation (GDPR). The current EU Data Protection Directive 95/46/EC does not consider important aspects like globalization and technological developments like social networks and cloud computing sufficiently and the Commission determined that new guidelines for data protection and privacy were required. Therefore a proposal for a regulation was released on 25 January 2012. Subsequently numerous amendments have been proposed in the European Parliament and the Council of Ministers. The EU's European Council aims for adoption in 2015/16 (see Timeline) and the Regulation is planned to take effect after a transition period of two years. An important point to note is that this is a Regulation not a Directive. The significance of this is that the EU Regulation will have immediate effect on all 28 EU Member States after the two-year transition period and does not require any enabling legislation to be passed by governments.

Summary[edit]

"The proposed new EU data protection regime extends the scope of the EU data protection law to all foreign companies processing data of EU residents. It provides for a harmonization of the data protection regulations throughout the EU, thereby making it easier for non-European companies to comply with these regulations; however, this comes at the cost of a strict data protection compliance regime with severe penalties of up to 2% of worldwide turnover." [1] Note: The current version contains increased fines up to 5%.[2] It should be noted that the European Parliament, the European Commission and the Council of Ministers are currently in what is known as trilogue negotiations over the precise wording of the GDPR and also the financial penalties for non-compliance have as yet to be finalised. In addition to global turnover, it is also being discussed that companies and organisations could be liable to a fine of €100m.

Content[edit]

The proposal for the European Data Protection Regulation contains the following key changes:[2] [3]

Scope[edit]

The regulation applies if the data controller or processor (organization) or the data subject (person) is based in the EU. Furthermore (and unlike the current Directive) the Regulation also applies to organizations based outside the European Union if they process personal data of EU residents. According to the European Commission "personal data is any information relating to an individual, whether it relates to his or her private, professional or public life. It can be anything from a name, a photo, an email address, bank details, posts on social networking websites, medical information, or a computer’s IP address." [4]

Single set of rules[edit]

A single set of rules applies to all EU member states and there will be one Single Data Protection Authority (DPA) responsible for each company depending on where the Company is based or which DPA it chooses (to be confirmed). A European Data Protection Board will coordinate the DPAs.

There is an exception for employee data that still might be subject to individual country regulations.

Responsibility and accountability[edit]

The notice requirements remain and are expanded. They must include the retention time for personal data and contact information for data controller and data protection officer has to be provided.

Privacy by Design and by Default (Article 23) require that data protection is designed into the development of business processes for products and services.

Privacy settings are set at a high level by default.

Data Protection Impact Assessments (Article 33) have to be conducted when specific risks occur to the rights and freedoms of data subjects. Risk assessment and mitigation is required and a prior approval of the DPA for high risks. Data Protection Officers (Articles 35–37) are to ensure compliance within organizations. They have to be appointed for all public authorities and for companies processing more than 5000 data subjects within 12 months.

Consent[edit]

Valid consent must be explicit for data collected and purposes data used (Article 7; defined in Article 4). Consent for children under 13 must be given by child’s parent or custodian, and should be verifiable (Article 8). Data controllers must be able to prove "consent" (opt-in) and consent may be withdrawn.[5]

Data Protection Officer[edit]

The forthcoming EU Regulation will force multi-national companies to appoint independent Data Protection Officers (DPOs) in order to comply with tougher regulations on data protection across all 28 Member States. A major point is that the DPO must be independent. The DPO is similar but not the same as a Compliance Officer as they are also expected to be proficient at managing IT processes, data security (including dealing with cyber-attacks) and other critical business continuity issues around the holding and processing of personal and sensitive data. The skill set required stretches beyond understanding legal compliance with data protection laws and regulations. Monitoring of DPOs will be the responsibility of the Regulator rather than the Board of Directors of the organisation that employs the DPO. The appointment of a DPO within a large organisation will be a challenge for the Board as well as for the individual concerned. There are a myriad of governance and human factor issues that organisations and companies will need to address given the scope and nature of the appointment. In addition, the post holder will need to create their own support team and will also be responsible for their own continuing professional development as they need to be independent of the organisation that employs them, effectively as a "mini-regulator".

Data breaches[edit]

Under the GDPR, the independent Data Protection Officer (DPO) will be under a legal obligation to notify the Supervisory Authority without undue delay and this is also still subject to negotiations at present. The reporting of a data breach is not subject to any de minimis standard and it is likely that the GDPR will provide that such breaches must be reported to the Supervisory Authority as soon as they become aware of the data breach (Article 31). Individuals have to be notified if adverse impact is determined (Article 32).

Sanctions[edit]

The following sanctions can be imposed:

  • a warning in writing in cases of first and non-intentional non-compliance
  • regular periodic data protection audits
  • a fine up to 1,000,000 EUR or up to 2% of the annual worldwide turnover in case of an enterprise, whichever is greater (Article 79, Number 6)

Right to erasure[edit]

A so-called right to be forgotten was replaced by a more limited right to erasure in the version of the GDPR adopted by the European Parliament in March 2014.[6][7] Article 17 provides that the data subject has the right to request erasure of personal data related to him on any one of a number of grounds including non-compliance with article 6.1 (lawfulness) that includes a case (f) where the legitimate interests of the controller is overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data (see also Google Spain SL, Google Inc. v Agencia Española de Protección de Datos, Mario Costeja González).

Data portability[edit]

A user shall be able to request a copy of personal data being processed in a format usable by this person and be able to transmit it electronically to another processing system. (Article 15)

Timeline[edit]

The preliminary schedule is [8]

Discussion & challenges[edit]

The proposal for the new regulation is not final yet and discussions are controversial. Thousands of amendments have been proposed.[9] The single set of rules and the removal of administrative requirements are supposed to save money. But critics point out some issues

  • The requirement to have a Data Protection Officer (DPO) is new for many EU countries and criticized by some for its administrative burden.
  • The GDPR was developed with a focus on social networks and cloud providers, but did not consider requirements for handling employee data sufficiently.
  • Data Portability is not seen as a key aspect for data protection, but more a functional requirement for social networks and cloud providers.
  • Language and staffing challenges for the Data Protection Authorities (DPA):
    • Non-European companies might prefer the UK/Irish DPA because of the English language. This will require extensive resources in those countries.
    • EU citizens no longer have a single DPA to contact for their concerns, but have to deal with the DPA the company chose. Communication problems due to foreign languages have to be expected.
  • The new regulation conflicts with other non-European laws and regulations and practices (e.g. surveillance by governments). Companies in such countries should not be acceptable for processing EU personal data anymore.
  • The biggest challenge might be the implementation of the GDPR in practice:
    • The European Commission and DPAs have to provide sufficient resources and power to enforce the implementation and a unique level of data protection has to be agreed upon by all European DPAs since a different interpretation of the regulation might still lead to different levels of privacy.
    • The implementation of the EU GDPR will require comprehensive changes of business practices for companies that did not implement a comparable level of privacy until now (especially non-European companies handling EU personal data).
    • There is already a lack of privacy experts and knowledge as of today and new requirements might worsen the situation. Therefore education in data protection and privacy will be a critical factor for the success of the GDPR. As the European Parliament, European Commission and the Council of Ministers become closer to reaching an agreement on the wording for the GDPR, there have been many organisations and companies within education and training that seek to provide support to many sectors that will be impacted by the GDPR.

References[edit]

External links[edit]