Analiza Data Protection Regulation
Analiza Data Protection Regulation
Chapter 6A
PROPOSED
EU DATA PROTECTION REGULATION
Francoise Gilbert1
§6A.01 Background
[A] Historical Milestones
[B] A Regulation, Not a Directive
[1] Shortcomings of Directives
[2] Benefits of Regulations
1
© 2012 IT Law Group – All Rights Reserved. Francoise Gilbert, JD, CIPP/US, focuses her legal practice
on information privacy and security, cloud computing, and data governance. She was voted one of the
country’s top legal advisors on privacy matters in a recent industry survey and, for several years, has been
recognized by Chambers, Best Lawyers, and Ethisphere as a leading lawyer in the field of information
privacy and security. Gilbert is the author and editor of the two-volume treatise Global Privacy &
Security Law (2,900 pages; Aspen Publishers, Wolters Kluwer Law and Business)
([Link]), which analyzes the data protection laws of 65 countries on all continents.
She is the managing attorney of the IT Law Group ([Link]) and serves as the general
counsel of the Cloud Security Alliance. She also keeps a blog on domestic and international data privacy
and security issues ([Link]) and is a contributing expert to
[Link].
She can be reached at (650) 804-1235 or fgilbert@[Link]
1
§6A.05 Protected Individuals
2
[B] Judicial Remedy against Data Controllers or Processors
[C] Judicial Remedy against Supervisory Authorities
[D] Class Action-Like Initiatives
§6A.01 BACKGROUND
On January 25, 2012, the European Commission published a series of legislative texts
that are intended to create a new data protection framework as part of a sweeping reform of the
protection of personal data processed by private and public entities. One of these texts is a
proposed General Data Protection Regulation on the protection of individuals with regard to the
processing of personal data and on the free movement of such data (Proposed Regulation).2 This
proposed document is intended to supersede Directive 95/46/EC. Before delving into the detailed
analysis of the provisions of the Proposed Regulation, it is important to look at the historical
background and the unique rules of operation of the European Union. Both of these explain the
choices made, and the intent of the drafters.
2
[Link]
3
different cultures, history and personalities, it ended up creating a patchwork of national laws that
had some resemblance to the base directive, but also their own personality – at times very
different personalities and requirements. These inconsistencies and discrepancies created a
difficult setting for companies operating in several Member States.
The ratification of the Treaty of Lisbon in late 2009 was a very important milestone in the
morphing of the European Union as a united power.3 It marked a critical step in the evolution of
the Union, creating deep changes in its rules of operation, increasing the power of the European
Commission and the European Parliament, removing the three-pillar system that fragmented the
operations, and moving the federation into a closer, tighter structure. With the Treaty of Lisbon,
the European Union moved towards more cohesion, more consistency, and more unity.
Shortly after the ratification of the Treaty of Lisbon, in November 2010, taking advantage
of the new structure and new expanded powers, the European Commission announced its intent to
reform the data protection regime in effect in the European Union and detailed its plans and goals
in a lengthy document. The document, Communication (COM) 609,4 outlined its plan to reform
the data protection regime in the European Union to take advantage of the new structures created
by the Treaty of Lisbon and to take into account the numerous major technological changes and
cultural changes of the recent years.5 Most of the key elements described in the November 2010
document that presented the blue print for the reform are found in the proposed legislative texts
that were published in January 2012 and especially in the Proposed Regulation with respect to the
protection of personal data with regard to the processing of personal data.
One of the concerns that were stressed in Communication 609 was the lack of harmony
and consistency between the national data protection laws adopted by the 27 Member States.
Communication 609 stressed that it was necessary to enhance the internal market dimension and
there were significant divergences between the national data protection laws in a large number of
sectors. These divergences were hampering the free flow of personal data and created legal
uncertainties both for the individuals and for the custodians of personal data. The Commission
stressed in particular that it intended to explore different possibilities for harmonization and
simplification. It also indicated that it wished to provide the EU data subjects with the same level
of protection regardless of the geographic location of the data controller.
3
On the Treaty of Lisbon, see Chapter 4, “The Byzantine Process of European Data Protection Law
Making”; see also [Link]
4
See Chapter 5, §5.05 “2010 Plan to Overhaul the Privacy Framework.”
5
[Link]
[Link].
4
[1] Shortcomings of Directives
For a long time since the creation of the European Union, directives have been used to
bring different national laws in-line with each other. However, directives prescribe only an end
result that must be achieved in every Member State. The form and methods of implementing the
principles set forth in a directive are a matter for each Member State to decide for itself. Once a
directive is passed at the European Union level, each Member State must implement or
“transpose” the directive into its legal system, but can do so in its own words. A directive only
takes effect through national legislation that implements the measures.
5
Forgotten” and the “Right to Data Portability.” Some of the key components of the Proposed
Regulation are discussed below.
The Regulation would also not apply to the processing of personal data:
• In the course of activities that fall outside the scope of Union law, such as national
security;
• By the Union institutions, bodies, offices and agencies;
• By the Member States when carrying out activities that fall within the scope of the rights
reserved to the States;
• By competent authorities for the purposes of prevention, investigation, detection or
prosecution of criminal offenses or the execution of criminal penalties.
6
Proposed Regulation, Art. 3(1).
6
the processing is performed by a controller that is not established in the Union, if the processing
activities are related to:7
The Regulation would also apply to the processing of personal data by a controller that is
not established in the Union, if the processing occurs in a place where the national law of a
Member State applies by virtue of public international law.8
7
[2] Biometric Data
Biometric data would require special attention. If the processing would involve personal
data in large scale filing systems that include biometric data, a data protection impact assessment
would be required to ensure that the processing is strictly limited to the activities permitted under
the Regulation.11 The term “biometric data” is defined to include any data relating to the physical,
physiological or behavioral characteristics of an individual that allow their unique identification,
such as facial images, or dactyloscopic data.12
The notion of what constitutes “sensitive data” would continue to be significantly different
from that which is used in the United States. In the United States, data that are generally
identified as “sensitive” tend to be those that would result in identity theft in case of a loss or
breach of security; for example, credit card or driver’s license information. In the European
Union, the data that are deemed “sensitive” are those that might cause embarrassment or intrusion
into a person’s intimacy if the data were lost or exposed (for example, information about health or
sexual preference) or that may cause discrimination or retaliation (for example, information about
religion or trade union membership).
For these specific types of data, Member States would have the freedom to enact their
own laws, consistent with their own culture and past practices.
11
Proposed Regulation, Art. 33(2)(d).
12
Proposed Regulation, Art. 4(11).
13
Proposed Regulation, Art. 9.
8
§6A.05 PROTECTED INDIVIDUALS
The protected individuals would be people in general or “data subjects,” with special
rules for the protection of children under 13. Individuals are protected to the extent that they are
an “identified natural person” or a “natural person or a natural person who can be identified,”
directly or indirectly, by means reasonably likely to be used by the controller or by any other
natural or legal person, in particular by reference to an identification number, location data,
online identifier or to one or more factors specific to the physical, physiological, genetic, mental,
economic, cultural or social identity of that person.14
14
Proposed Regulation, Art. 4(1).
15
Proposed Regulation, Art. 5.
9
• Processed lawfully, fairly, and in a transparent manner;
• Collected for specified, explicit, and legitimate purposes, and not further processed in
ways incompatible with these purposes;
• Adequate, relevant and limited to the minimum necessary;
• Only processed if, and as long as, the purposes of the processing could not be fulfilled by
processing information that does not involve personal data;
• Accurate, kept up-to-date, with incorrect data being erased or rectified;
• Kept in a form that permits identification of the data subjects for no longer than
necessary;
• Processed under the responsibility and liability of the data controller, who must ensure
and demonstrate for each operation its compliance with the Regulation.
Under the new regime, when consent is the basis for the legitimacy of the processing, it
will have to be “specific, informed, and explicit” (Article 7). The controller would have to bear
the burden of proving that the data subjects have given their consent to the processing of their
personal data for specified purposes. For companies, this means that they may have to find ways
to keep track of the consent received from their customers, users, visitors and other data subjects,
or will be forced to ask again for this consent.
This evolution is consistent with the way the European laws have changed in past few
years, with the new stringent requirements for cookies under the 2009 amendments to Directive
2002/58/EC.16 The amendment to Section 5(3) of the 2002 ePrivacy Directive has caused the EU
Member States to modify their national laws to require that the user’s specific (opt-in) consent be
obtained before cookies, other than technical cookies, can be sent to the user’s computer. Before
the 2009 amendments, cookies were subject to less stringent restrictions, and could be used
without a formal consent of the user. It was only necessary to inform them of their right to refuse
the use of cookies and their ability to block access to their computers.
[A] Accountability
16
See Chapter 7, “2002 EU Directive on Privacy and Electronic Communications.”
10
Article 22 addresses the accountability of the controllers. This concept is a new one, and
slightly resembles the concept of accountability found in the APEC Privacy Framework.17
Under the Proposed Regulation, accountability would require that the data controller
adopt policies, and implement appropriate measures to ensure, and be able to demonstrate, that
the processing of personal data is performed in compliance with the Regulation. These measures
would include, for example, the following obligations for the data controller:
Article 23 stresses in particular that the data controller must ensure that by default personal
data are not made accessible to an indefinite number of individuals. This provision would affect,
for example, social networks, which tend to set default setting to choices that would make
individuals’ personal data available to large circles of individuals, if not, the public at large.
17
See Chapter 10, “Asia Pacific Region.”
11
[3] More to Come
The entire scope of the proposed requirements for “privacy by design” and “privacy by
default” is not yet fully clear, and should be clarified through additional writings. Article 23(3)
and (4) allow the European Commission to adopt “delegated acts” in order to specify any further
criteria and requirements for appropriate measures and mechanisms, such as requirements that
would be applicable across sectors, products and services, or new technical standards.
Article 33 would require controllers and processors to carry out a data protection impact
assessment if the proposed processing is likely to present specific risks to the rights and freedoms
of the data subjects by virtue of its nature, scope, or purposes. Examples of these activities
include: monitoring publicly accessible areas, use of the personal data of children, use of genetic
data or biometric data, processing information on an individual’s sex life, the use of information
regarding health or race, or an evaluation having the effect of profiling or predicting behaviors.
Article 26 would build on Article 17(2) of Directive 95/46/EC and increase the
obligations of the data processors. It would add a very important element: a processor who
processes data beyond the instructions provided by the controller would be considered a joint
controller. This very important clarification is consistent with Working Paper WP 169 issued by
the Article 29 Working Party in March 2010. In this paper, the Article 29 Working Party
discussed when a data processor becomes a joint controller with the initial data controller.
12
This clarification is likely to generate significant changes in the relations between a
company and its service providers – such as outsourcers and cloud service providers. In numerous
contracts, the service providers require the client to agree that the service provider retains the
freedom to make many changes or to make decisions such as when or where to modify the
application, to back up data, or to locate a disaster recovery site. On the other hand, most cloud
service providers have insisted on the client agreeing to a contractual provision in which the
client acknowledges that the cloud service provider is a data processor and not a data controller.
If a cloud service provider choses to move a data center or disaster recovery center to a different
location without consulting with the client, would it become a joint controller if the provisions of
this new Article 26 were applied?
Companies will welcome the fact that the rules for handling requests for access or
deletion would be the same in all Member States. In the current regime, the time frames for
responding to such requests are different, with some Member States requiring action within very
short periods of time, and others allowing up to two months for responding.
Article 13 would provide rights for data subjects in relation to recipients. This provision
is based on Article 12(c) of Directive 95/46/EC. It would require the data controller to
communicate any rectification or erasure carried in connection with the data subject’s right to
correction and blocking to each recipient to whom the data have been disclosed. Like under
Directive 95/46/EC, there would be a limit to this obligation when this communication would
prove impossible or involve a disproportionate effort. The notion of “recipient” includes all
natural or legal persons, public authority, agency, or other body to whom the data would have
been disclosed, including joint controllers and processors of the personal data.
13
length of the period during which the data controller intends to hold their data. They would also
have to be informed of their right to lodge a complaint, of the proposed crossborder transfers of
personal data, and of the source from which the data are originating.18
18
Proposed Regulation, Art. 14.
19
Proposed Regulation, Art. 15.
20
See Chapter 7, “2002 EU Directive on Privacy and Electronic Communications.”
14
who has made the personal data public would have to inform third parties of the data subject’s
request to erase any links to the personal data and any copy or replication of the personal data.
The “right to be forgotten” and the “right to portability” reflect the pressure of the current
times. There have been numerous reports of the unexpected consequence of the use of social
media. Users of social networks have found out, to their detriment, that the ease of use of a social
network and the access to the service for no fee was tied to a price: that their personal data could
be used in forms or formats that they had not contemplated, would be shared with, or disclosed to,
others, and that the service provider would resist a user’s attempt to move to another service.
From a company’s perspective it is not clear how and to what extent the right to be
forgotten and the right to data portability could be implemented. The right to be forgotten poses
significant practical problems. Once data, statements, photographs, have been published on the
Internet, they can be quickly disseminated, copied, integrated in other content or databases. The
social network or other service that served as the publisher of the items in question would have no
way to know who copied or republished that item, and would have no ability to identify these
third parties or to exercise control over these third parties. Data may also be stored in archives or
on back up media, or duplicated on a host site for disaster recovery and business continuity
purposes. On the other hand, content that was intentionally provided to subcontractors, service
providers or co-marketers might be more easily traceable, for example, if the company keeps a
log of its data transfers.
15
[B] Security Breach Disclosure
In addition, the Proposed Regulation introduces an obligation to provide notification of
“personal data breaches.” The term “personal data breach” is defined as “a breach of security
leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or
access to, personal data transmitted, stored or otherwise processed”.21
21
Proposed Regulation, Art. 4(9).
22
Proposed Regulation, Art. 31.
23
Proposed Regulation, Art. 32.
24
Proposed Regulation, Preamble, Recital 67.
16
25 and 26 of the 1995 Directive.25 Simply put, the transfer of personal data out of the EU or EEA
is prohibited unless the recipient country provides “adequate protection” to personal data and the
privacy rights of individuals. Only a handful of countries have been deemed by the European
Commission to provide “adequate protection.” For transfers of data to the other countries, the
recipient must enter into a written contract in which the recipient of the data commits to doing, or
to refrain from doing, certain acts. The European Commission has approved certain forms of
contracts. In addition, a majority of the EU Member States – but not all of them – currently
recognize “binding corporate rules” as a way for a group of companies to express their
commitment to provide and ensure the required “adequate protection” even when the recipient is
located in a country that does not offer this “adequate protection”.
In the Proposed Regulation, the conditions of, and restrictions to, data transfers to third
countries or international organizations, including onward transfers, would be defined in Articles
40 through 45. For transfers to third countries that have not been deemed to provide “adequate
protection,” Article 42 would require that the data controller or data processor adduce
appropriate safeguards, such as through standard data protection clauses, binding corporate rules,
or contractual clauses. It should be noted, in particular, that:
• Standard data protection clauses may also be adopted by a supervisory authority and be
declared generally valid by the Commission;
• Binding corporate rules are specifically introduced as a legitimate ground for allowing for the
transfer of personal information out of the European Economic Area. Currently they are only
accepted in about 17 Member States while in other Member States they are illegal;
• The use of contractual clauses other than the standard clauses would be subject to prior
authorization by the supervisory authorities.
Article 44 would spell out and clarify the derogations for a data transfer. These
conditions are based on Article 26 of Directive 95/46/EC. In addition, under limited
circumstances, a data transfer may be justified on a legitimate interest of the controller or
processor, but only after having assessed and documented the circumstances of the proposed
transfer.
Article 45 would provide for international cooperation mechanisms for the protection of
personal data between the European Commission and the supervisory authority of third countries.
It should be noted that Article 42 of the prior draft of the Regulation (Draft 56 of the Proposed
Regulation, dated November 29, 2011), has been removed. This article provided that foreign
judgments requiring a controller or processor to disclose personal data would not be recognized
or be enforceable in any manner, without prejudice to a mutual assistance treaty or an
international agreement in force between the requesting third country and the Union or a Member
State. It required a controller or processor to immediately notify the supervisory authority of the
request and to obtain prior authorization for the transfer. It is not clear why the provision was
removed and whether this issue will be addressed separately.
25
See Chapter 9, “Transferring Personal Data out of the European Union and European Economic Area.”
17
Binding corporate rules would take a prominent place in the Proposed Regulation. Their
required content is outlined in Article 43. An organization’s binding corporate rules would have
to contain the following information:
Instead of the notification requirement, the Proposed Regulation would require both data
controllers and data processors to keep substantial records, written policies, and other
information, and to promptly respond to inquiries by the data protection supervisory authorities.
18
Article 28 would detail the obligation for controllers and processors to maintain
documentation of the processing operations under their responsibility. This obligation would
replace the current requirement to “notify” the local data protection supervisory authority by
providing a description of the company’s data processing practices, as required by the national
laws that implement Articles 18 and 19 of Directive 95/46/EC.
This removal of the notification requirement reflects a significant shift in the attitude of
the European Commission, which is expressed throughout the Proposed Regulation: a switch
from tight supervision and reporting to a concept of accountability. In exchange for abolishing the
cumbersome and costly notification requirement, the new Regulation would require that data
controllers and data processors be “accountable.” They would be trusted to create their own
structures, but they would have to document them thoroughly. They would also have to be
prepared to respond to any inquiry from the Data Protection Authority, to promptly produce the
set of rules with which they have committed to comply, and to show that they do actually comply
with the provisions of the Regulation.
Article 28 identifies a long list of documents that would have to be created and
maintained by data controllers and data processors. The information required is somewhat similar
to the information that is currently provided in the notifications to the data protection
authorities―for example, the categories of data and data subjects affected, or the categories of
recipients. There are, however, also new requirements such as the obligation to keep track of the
transfers to third countries, or to keep track of the time limits for the erasure of the different
categories of data.
19
before the processing of personal data in order to ensure that the intended processing complies
with the Regulation. This would be the case, in particular, where a data protection impact
assessment indicates that processing operations might present a high degree of specific risks, or if
the supervisory authority deems it necessary to carry out a prior consultation on processing
operations that are likely to present specific risks to the rights and freedoms of data subjects by
virtue of their nature, scope or purpose.
Under the current data protection regime, several EU Member States, such as Germany,
already require organizations to hire a Data Protection Officer, who is responsible for the
company’s compliance with the national data protection law. In the United States, numerous laws
and FTC consent decrees require entities to appoint a Data Protection Officer to be responsible
for all matters pertaining to data protection within the entity.
20
indicates clearly that action may be filed against the data controller or data processor and would
provide individuals with a choice of courts. The action could be brought in a court of the Member
State where the defendant is established or where the data subject is residing.
These additions are very important. They would open the door to actions similar to a
class action suit, a form of action that is currently seldom used in the European Union, but with
which U.S. companies are familiar. Many of the class actions currently filed in the United States
cause great expenses to companies, and frequently bring little relief to the actual injured parties or
the named plaintiffs. Damages, if any, awarded against a company frequently consist in the
payment of funds that benefit research institutions, non-profit privacy advocates or consumer
organizations and the payment of the plaintiff’s attorney fees. The injured parties or the parties
directly affected by an incident may only receive a very small amount of money compared to the
large settlement amount.
26
Proposed Regulation, Art. 73.
21
The individual’s right to compensation is set out in Article 77 of the Proposed
Regulation. Under the new rule, individuals would be entitled to receive damages from data
controllers, data processors, joint controllers, and joint processors, as applicable, for the
damages suffered. When more than one entity is involved in the processing, the controllers and
processors would be held jointly and severally liable for the entire amount of the damages.
Article 79 would grant each data protection authority the power to impose administrative
sanctions. The criteria to be used in determining the amount of the administrative sanction would
include:
• Nature, gravity, and duration of the violation;
• Intentional or negligent character of the infringement;
• Degree of responsibility of the natural or legal person;
• Previous breaches of the law;
• Technical, organizational and administrative measures implemented to protect the
security of personal information; and
• Degree of cooperation with the supervisory authority in order to remedy the violation,
infringement, or breach of the law.
The Proposed Regulation would specify significant sanctions for violation of the law.
Organizations would be exposed to penalties of up to 1 million Euros or up to 2% of the global
annual turnover of an enterprise. This is much more than the penalties currently in place
throughout the European Union. Apart from a few cases, the level of fines that have been
assessed against companies that violated a country’s data protection laws has been low, even
though it has periodically increased. The Proposed Regulation signals an intent to pursue more
aggressively the infringers and to equip the enforcement agencies with substantial tools to ensure
compliance with the law.
22
breach of security, failure to comply with the restrictions on the cross border transfers of
personal data.
Article 49 would grant each of the Member States the freedom to establish their data
protection supervisory authority within the guidelines provided by the Regulation. This may
result in inconsistency in the way the data protection authorities are governed and managed. For
example, the Member States would have the freedom to determine the qualifications required for
the appointments of the members of the DPAs, and the regulations governing the duties of the
members and staff of the DPA.
Article 51 would set out the competence of the DPAs while Article 52 and 54 would
define their duties and Article 53 their powers. The competence of each DPA would be limited to
its own national territory in most cases. However, in the case of data processors or data
controllers established in several countries, the DPA of the principal establishment of the
corporate group would acquire a new competence as the lead authority for that corporate group.
As this is currently the case, the duties of the DPAs would include hearing and
investigation of complaints, raising public awareness of the rules, safeguards and rights, and
preparing annual reports.28 The proposed powers of the DPA would be very similar to those that
are set forth in Article 28(3) of Directive 95/46/EC and Regulation (EC) 45/2001, with some
additional powers, such as the power to sanction administrative offenses.
27
Proposed Regulation, Art. 20, 47, 48.
28
Proposed Regulation, Art. 52 and 54.
23
ensuring unity of application with respect to data processing that may concern data subjects in
several Member States. In some cases, unity and consistency may be obtained through opinions
of the European Data Protection Board, discussed below.29 There are also provisions giving the
European Commission the power to intervene.30
Articles 65 and 66 clarify the independence of the European Data Protection Board and
describe its expanded role and responsibilities. Article 68 sets out its decision-making procedures,
which includes the obligation to adopt rules of procedure. Article 71 sets out a Secretariat of the
European Data Protection Board. The service would be provided by the European Data Protection
Supervisor.
The United States may be an example of this constant quagmire. The United States has
numerous federal laws that are intended to apply uniformly in all of its states and territories.
However, interpretations may vary significantly from one geographic area to another due to the
cultural, economic and other numerous circumstances. Even though for more than 220 years, the
U.S. Supreme Court has been trying to remove these discrepancies and even out the field, the
same laws continue to be interpreted differently throughout the U.S. States and territories as
evidenced by the frequent attempts at forum shopping by shrewd plaintiffs. It would not be
surprising if the data protection commissioners, the government agencies, and the judicial system
in each EU Member State also have differing interpretations of the same text.
29
Proposed Regulation, Art. 58.
30
Proposed Regulation, Art 59 to 63.
31
Proposed Regulation, Art. 64.
24
The Proposed Regulation provides for checks and balances in the form of cooperation
and oversight so that the discrepancies between these interpretations should be less significant or
less numerous than those that are currently found among the Member State data protection laws.
Nevertheless, once the final text becomes effective, it will be imprudent and very risky to act as if
there were total uniformity.
Article 21 grants the Member States the power to restrict through legislative measures
certain rights and obligations provided for in the Directive in order to safeguard, as necessary:
• Public security;
• The prevention, investigation, detection and prosecution of criminal offenses;
• Important economic or financial interests of the Members State or of the European
Union, such as monetary, budgetary and taxation matters, and the protection of market
stability and integrity;
• The prevention, investigation, detection or prosecutions of breaches of ethics for
regulated professions;
• The monitoring, inspection or regulatory function connected with the above; or
• The protection of the data subjects or the rights and freedom of others.
The scope of this carve out is significant. It could drastically affect the hope for unity and
consistency. Article 21 would allow Member States to make restrictions to the basic data
protection principles that are set forth in:
• Article 5, which details the seven basic principles relating to the processing of personal
data. For example: the obligation to process the data fairly and lawfully, and in a
transparent manner, to collect only the minimum necessary, or to store the data only for
as long as necessary;
• Articles 11 to 20, which define the basic rights of the data subjects. This includes the
right to information, right of access, right of rectification, right of erasure, right to be
forgotten, right to data portability, right to object, right not to be subject to a measure
based on profiling; and
• Article 32, which would provide for an obligation of the data controller to notify the data
subjects in case of a breach of security.
While this carve out may generally be consistent with the current Article 13 of Directive
95/46/EC, it might gain a new life, and a new interest from Member States who may take
advantage of the provision to regain some of their past freedom and use it as a loophole to
25
introduce or re-introduce their own provisions. Since January 25, 2012, we have heard several
reports of critics made by Data Protection Authorities against the Regulation. For example, the
French Data Protection Authority, CNIL, is opposing the Proposed Regulation because it says
that the Regulation would largely deprive citizens of the protections offered by their national
authorities. The UK Data Protection Commissioner has also complained that the Draft Regulation
needed to be strengthened and that it would create compliance and enforcement problems.
With the door widely open by Article 21 to create amendments, restrictions and carve
outs, it is likely that there will be divergence and inconsistency in the actual implementation and
the interpretation of the document by the various Member States. The extent of these divergences
is, of course, difficult to predict at this point.
32
Proposed Regulation, Art. 80.
33
Proposed Regulation, Art. 81.
34
Proposed Regulation, Art. 82.
35
Proposed Regulation, Art. 84.
36
Proposed Regulation, Art. 85.
26
under Article 74, the Member States would be responsible for enforcing final court decisions
against their local data protection supervisory authority.
[F] Penalties
There may be differences, as well, with respect to the assessment of penalties. Article 78
would grant to the Member States the authority to lay down the rules on penalties applicable to
infringements of the Regulation. Member States would also have the authority to take the
measures necessary to implement these rules.
If the current provisions subsist in the final draft, the new Regulation will increase the
rights of the individuals and the powers of the supervisory authorities. While the Regulation
would create additional obligations and accountability requirements for organizations, the
adoption of a single rule throughout the European Union would help simplify the information
governance, procedures, record keeping, and other requirements for companies unless the
Member States take advantage of the numerous loopholes in the Proposed Regulation to reinstate
the provision of their own laws that have been superseded by the Regulation.
It should also be remembered that Directive 95/46/EC has been a significant driving force
in the adoption of data protection laws throughout the world. In addition to the 30 members of the
European Economic Area, numerous other countries, such as Switzerland, Peru, Uruguay,
Morocco, Tunisia, or the Dubai Emirate (in the Dubai International Financial District) have
adopted data protection laws that follow closely the terms of Directive 95/46/EC. It remains to be
seen what effect the adoption of the Regulation will have on the data protection laws of these
other countries.
27