<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
><channel><title>CIPP Guide &#187; EU</title> <atom:link href="http://www.cippguide.org/tag/eu/feed/" rel="self" type="application/rss+xml" /><link>https://www.cippguide.org</link> <description>Your Guide to the CIPP</description> <lastBuildDate>Tue, 07 Feb 2012 12:00:10 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>Privacy &amp; Intellectual Property</title><link>https://www.cippguide.org/2011/11/15/privacy-intellectual-property/</link> <comments>https://www.cippguide.org/2011/11/15/privacy-intellectual-property/#comments</comments> <pubDate>Tue, 15 Nov 2011 12:00:40 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[control]]></category> <category><![CDATA[copyright]]></category> <category><![CDATA[DCMA]]></category> <category><![CDATA[EU]]></category> <category><![CDATA[intellectual property]]></category> <category><![CDATA[property rights]]></category> <category><![CDATA[WIPO]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2663</guid> <description><![CDATA[This article takes a look at the relationship between privacy and intellectual property issues. Intellectual property is related to the control of data generated by an individual and is a creative work, while privacy is concerned with the control of non-creative data, which are generated by an individual. The article takes a look at regulations currently in effect, namely the US Digital Millennium Copyright Act (DMCA), and the EU’s Database Directive. [...]]]></description> <content:encoded><![CDATA[<p>In recent years, information privacy is being considered a scare commodity, as it is relatively convenient and simple to collect large amounts of information that can be identified to specific individuals. Many commentators have pointed out the relationship between intellectual property and privacy issues. For instance, both are concerned with the control of sensitive information.</p><p>Intellectual property is related to the control of data generated by an individual and is a creative work, while privacy is concerned with the control of non-creative data, which are generated by an individual. This article will consider the links between the two concepts from a privacy professional’s perspective.</p><p><strong>Introduction to Intellectual Property</strong></p><p>Certain economists and privacy advocates are encouraging giving individuals property rights in their personal data, in order to promote information security. From this perspective, proponents argue that this would allow individuals to negotiate with firms regarding the uses they would agree to for their personal data. This would also force businesses and organizations to internalize a higher proportion of societal costs of processing personal data.</p><p><strong>Regulations</strong></p><p>In October 1998, the US <a
href="https://www.cippguide.org/tag/DCMA/">Digital Millennium Copyright Act (</a>DMCA) was signed into law. This piece of legislation implemented two 1996 <a
href="http://www.wipo.int/portal/index.html.en">World Intellectual Property Organization</a> (WIPO) treaties, addressing a number of significant copyright-related issues. The Act effectively encouraged copyright owners to make their databases more available through digital distribution methods, by including technological protections in the form of penalties for copyright infringement, or piracy.</p><p>In January 1998, the EU’s Database Directive came into effect. This Directive provided two levels of protection:</p><ol><li>It offers copyright protection for original selection and arrangement of facts in a database</li><li>It offers <em><a
href="http://en.wikipedia.org/wiki/Sui_generis">sui generis</a></em> protection for non-original databases, thus prohibiting the unfair extraction of a substantial part of any database reflecting significant investment.</li></ol><p>Essentially, a database could receive both types of protection simultaneously. It could receive copyright protection for the selection and arrangement of data, as well as <em>sui generis</em> protection against the extraction of a substantial part of the data. <em>Sui generis</em> protection lasts for 15 years, while copyright protection lasts for the life of the author, plus 70 years.</p><p><strong>Critics Say… </strong></p><p>While the DMCA and EU Database Directive were substantial steps towards ensuring privacy, a study of over 750 e-commerce sites in the EU and the US showed that the websites were still selling products and services to consumers in a manner that fell short of international standards. For instance, most sites would collect personal information, but fail to tell consumers how their data would be used, how security is maintained and the rights that consumers would have over their won information.</p><p>In a March 2011 White House analysis of intellectual property legislation and enforcement, entitled <a
href="http://www.whitehouse.gov/sites/default/files/ip_white_paper.pdf"><em>Administration’s White Paper on Intellectual Property Enforcement Legislative Recommendations</em></a>, some trends were identified that may indicate that US governmental policy toward enforcement may be sacrificing privacy for copyright enforcement. In this analysis, the Administration recommended three legislative changes, which essentially give enforcement agencies the tools required to respond to infringement:</p><ol><li>Clarify that, in appropriate circumstances, infringement by streaming, or by means of other similar new technology, is a felony;</li><li>Authorize DHS, and its component US <a
href="http://www.cbp.gov/xp/cgov/home.xml">Customs and Border Protection</a> (CPB), to share pre-seizure information about, and samples of, products and devices with rightholders to help DHS to determine whether the products are infringing or the devices are circumvention devices; and</li><li>Give law enforcement authority to seek a wiretap for criminal copyright and trademark offenses.</li></ol><p>The document also pointed out a number of other legislative recommendations made by the office of IP Enforcement. However, networking technologies that are needed for the advancement of communication technologies and security are making it so that such legislation is increasingly difficult to enforce. This results in more lobbyists and government officials pushing for even more stringent privacy-violating legislation.</p><p><strong>Summary </strong></p><p>This article takes a look at the relationship between privacy and intellectual property issues. Intellectual property is related to the control of data generated by an individual and is a creative work, while privacy is concerned with the control of non-creative data, which are generated by an individual. The article takes a look at regulations currently in effect, namely the US Digital Millennium Copyright Act (DMCA), and the EU’s Database Directive.</p><p><strong>CIPP Exam Preparation</strong></p><p>In preparation for the Certified Foundation Examination (Foundations), a privacy professional should be comfortable with topics related to this post, including:</p><ul><li>Information types – intellectual property (IP) (I.A.c.ii.4.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2011/11/15/privacy-intellectual-property/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>EU Data Protection Directive &amp; Binding Corporate Rules</title><link>https://www.cippguide.org/2011/10/25/eu-data-protection-directive-binding-corporate-rules/</link> <comments>https://www.cippguide.org/2011/10/25/eu-data-protection-directive-binding-corporate-rules/#comments</comments> <pubDate>Tue, 25 Oct 2011 12:00:43 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[adequacy]]></category> <category><![CDATA[BCR]]></category> <category><![CDATA[data transfer]]></category> <category><![CDATA[EU]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2661</guid> <description><![CDATA[This article takes a look at Binding Corporate Rules (BCRs), as outlined by the EU Directive 95/46/CE for all transfers of personal data protected under a European law. The article takes a look at official as well as unofficial definitions of BCRs, the elements that consist of a BCR and US and EU perspectives on the implementation of [...]]]></description> <content:encoded><![CDATA[<p>Data protection laws at their essence outline certain basic privacy requirements involved in the processing of personal data. The main objective of data protection laws The <a
href="http://www.cippguide.org/tag/european-union-data-protection-directive/">EU Data Protection Directive</a> includes some of the strictest data protection limitations.</p><p><strong>Binding Corporate Rules</strong></p><p>Binding Corporate Rules (BCRs) is a loosely defined term and relates to a concept, rather than a distinct, clearly articulated vehicle. <a
href="http://ec.europa.eu/justice/policies/privacy/binding_rules/index_en.htm">According to the European Commission</a>, BCRs are,</p><p>“Internal rules (such as a Code of Conduct) adopted by multinational group of companies which define its global policy with regard to the international transfers of personal data within the same corporate group to entities located in countries which do not provide an adequate level of protection.”</p><p>In practice, BCRs must contain the following elements:</p><ol><li>Privacy principles (e.g. transparency, data quality, security, etc.)</li><li>Tools of effectiveness (e.g. audit, training, complaint handling systems, etc.)</li><li>An element that proves a BCR is binding</li></ol><p>Another way of describing <a
href="http://i-sight.com/uploads/Bender_Ponemon_Cross_Border_Data1.pdf">BCRs are as follows</a>:</p><p>“A code of conduct setting forth the privacy policy of the entire enterprise is drafted, to which each entity included in the enterprise subscribes, enabling data subjects and other entities to enforce that code against the entity/enterprise.”</p><p><strong>Who are they for?</strong></p><p>BCRs may offer a viable solution for various multinational companies involved in the export of personal data from the <a
href="http://www.cippguide.org/tag/eu/">European Economic Area</a> to other group entities located in third countries which do not ensure an adequate level of protection.</p><p>BCRs are to be used by multinational companies to develop <a
href="https://www.cippguide.org/2011/09/27/adequacy-in-the-eu-data-protection-directive/">adequate</a> safeguards for the protection of the privacy and fundamental right and freedoms of individuals within the meaning of Article 26 of the Directive 95/46/CE for all transfers of personal data protected under a European law. BCRs ensure that transfers of personal data are made within a group benefit from an adequate level of protection.</p><p>Global corporations have begun to take an interest in BCRs for two major reasons. First, they would like to diminish the amount of paper and effort involved to the legitimizing of their transfers. They also intend to impose less stringent requirements on their transfer activities. A number of global enterprises believe that codes of conduct should be sufficient for the cross-border transfer of personal data.</p><p><strong>An American Perspective</strong></p><p>From the perspective of a US-based multinational corporation (MNC), BCRs offer a number of advantages, as well as disadvantages. They are outlined as follows.</p><p>Advantages of BCRs:</p><ul><li>Possibility of developing a more flexible privacy regime than other methods of cross-border data transfer</li><li>Ensure compliance with principles included in Article 25 and 26 of the European Directive 95/46 for all flows of data within the scope of the BCR</li><li>Harmonize practices relating to the protection of personal data within a group</li><li>Prevent the risks resulting from data transfers to third countries</li><li>Avoid the need for a contract for each single transfer</li><li>External communication on the company’s data protection policy</li><li>Offer an internal guide for employees, with regard to personal data management practices</li><li>Ensure that data protection is integral to the way the company does business</li></ul><p>Disadvantages of BCRs:</p><ul><li>Uncertainty around the use of BCRs</li><li>Reduced efficiency as a result of substituting possibly hundreds of other documents for a single document</li></ul><p><strong>EU Perspective </strong></p><p>Since 2006, the EU has increased receptivity to BCRs. Its official publications indicate that it favors legitimizing this vehicle of data protection. However, in practice, it remains difficult to use BCRs for transfer from more than a single EU member state. BCRs are outlined in three documents, released by the Article 29 Working Party:</p><ol><li>WP 74 – This document states that BCRs offer a viable alternative for cross-border transfer, but suggests a regime that many multinational corporations would view as so burdensome that their main incentive would not be met.</li><li>WP 107 – This document sets out a general procedure, under which a corporate enterprise interested in using BCRs for export from more than one EU Member State may seek to do so.</li><li>WP 108 – Likewise, this document clarifies what was set out in WP 74.</li></ol><p><strong>Summary </strong></p><p>This article takes a look at Binding Corporate Rules (BCRs), as outlined by the EU Directive 95/46/CE for all transfers of personal data protected under a European law. The article takes a look at official as well as unofficial definitions of BCRs, the elements that consist of a BCR and US and EU perspectives on the implementation of BCRs.</p><p><strong>CIPP Exam Preparation</strong></p><p>In preparation for the Certified Foundation Examination (Foundations), a privacy professional should be comfortable with topics related to this post, including:</p><ul><li>EU Data Protection Directive – Binding Corporate Rules (BCRs) (I.D.c.i.4.b.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2011/10/25/eu-data-protection-directive-binding-corporate-rules/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Roles &amp; Responsibilities in Processing Personal Data</title><link>https://www.cippguide.org/2011/10/11/roles-responsibilities-in-processing-personal-data/</link> <comments>https://www.cippguide.org/2011/10/11/roles-responsibilities-in-processing-personal-data/#comments</comments> <pubDate>Tue, 11 Oct 2011 12:00:42 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[data controller]]></category> <category><![CDATA[data processor]]></category> <category><![CDATA[data subject]]></category> <category><![CDATA[DPO]]></category> <category><![CDATA[EDPS]]></category> <category><![CDATA[EU]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2659</guid> <description><![CDATA[This article takes a look at the legal roles of various parties, according to the Regulation (EC) 45/2010, namely: data subjects, data processors, data controllers, data protection officers and the European Data Protection Supervisor (EDPS). [...]]]></description> <content:encoded><![CDATA[<p>Personal data that is processed in accordance with <a
href="https://www.cippguide.org/tag/eu/">EU Data Protection Regulation</a> (EC) 45/2001 on the protection of individuals, regarding the processing of personal data must respect data protection roles. It is necessary to identify the Controller, Processor and their interaction, in order to determine “who is responsible for compliance with data protection rules, how data subjects can exercise their rights, which is the applicable national law and how effective Data Protection Authorities can operate.”</p><p><strong>European Data Protection Supervisor (EDPS)</strong></p><p>The <a
href="http://www.edps.europa.eu/EDPSWEB/">EDPS</a> is an independent supervisory authority whose primary objective is to ensure European bodies and institutions respect the right to privacy and data protection when they process personal data and develop new policies. The EDPS is also responsible for advising EC institutions and bodies on all matters that have an impact on the protection of personal data. This may apply to proposals for new EU legislation, as well as other instruments, such as communications of the European Commission. Finally, the EDPS is also responsible for intervening in cases before the Court of Justice, as well as cooperating with national supervisory authorities and supervisory bodies in the “<a
href="http://en.wikipedia.org/wiki/Three_pillars_of_the_European_Union">third pillar</a>” of the EU. This is in order to improve consistency in the protection of personal data.</p><p>The main duties of the EDPS are:</p><p><strong>I.                    </strong><strong>Supervision</strong></p><ul><li>Monitor the processing of personal data be EC institutions and bodies. This is typically done in cooperation with the Data Protection Officer (see below).</li><li>Hearing and investigating complaints, conducting inquiries (either initiated by the EDPS, or on the basis of a complaint).</li><li>Prior checking DPO’s notifications of processing operations, which could present risks to the data subjects.</li><li>Provide consulting services to EC institutions and bodies on administrative measures having to do with the processing of personal data.</li></ul><p><strong>II.                  </strong><strong>Consultation</strong></p><ul><li>Advise all EC institutions and bodies on matters that relate to the processing of personal data.</li><li>Intervene in cases related to data protection, before the Court of Justice.</li></ul><p><strong>III.                </strong><strong>Cooperation</strong></p><ul><li>Cooperate with national data protection authorities.</li><li>Cooperate with the supervisory data protection bodies.</li><li>Participate win regular international conferences on data protection (e.g. the European and the International Data Protection Conferences).</li></ul><p><strong>Data Protection Officer (DPO)</strong></p><p>Under Regulation (EC) 45/2001, each Community institution and body must have a <a
href="http://www.edps.europa.eu/EDPSWEB/edps/site/mySite/pid/74#data_protection_officer">data protection officer</a> (DPO). The DPO is responsible for ensuring the internal application of the Regulation, and that the rights and freedoms of the data subjects are not likely to be adversely affected by any processing operations. The DPO must also keep a register of processing operations notified by the controllers of the institution or body where he/she works.</p><p>Other DPO functions include:</p><ul><li>Ensuring controllers and data subjects are informed of their rights and obligations</li><li>Carrying out inquiries, when necessary</li><li>Notifying the EDPS of processing operations that may present specific risks</li><li>Responding to any requests from the EDPS and cooperating with the EDPS</li></ul><p>A full list of data protection officers is available <a
href="http://www.edps.europa.eu/EDPSWEB/edps/site/mySite/DPOnetwork">here</a>.</p><p><strong>Data Controllers</strong></p><p>The term “<a
href="http://www.edps.europa.eu/EDPSWEB/edps/site/mySite/pid/74#data_controller">data controller</a>” refers to an individual or legal person who controls and is responsible for the keeping and use of personal information on a computer, or in structured manual files. In essence, data controllers keep or process any information about living people. Any organizations that control or are responsible for personal data are also considered data controllers.</p><p>Examples of data controllers include:</p><ul><li>Companies</li><li>Government departments</li><li>Voluntary organizations</li><li>Individuals (e.g. general practitioners, pharmacists, politicians and sole traders)</li></ul><p><strong>Data Processors</strong></p><p><a
href="http://www.mwe.com/index.cfm/fuseaction/publications.nldetail/object_id/58d56e95-471b-43d5-a242-5c7b965ce2ae.cfm">Data processors</a> refer to anyone who holds or processes personal data, without exercising responsibility for/control over the personal data. In certain cases, it is possible for a single company/person to be both a data controller and data processor at the same time, in respect of distinct sets of personal data.</p><p>Examples of data processors include:</p><ul><li>Payroll companies</li><li>Accountants</li><li>Market research companies</li></ul><p><strong>Data Subject</strong></p><p>The data subject refers to the person whose <a
href="http://www.edps.europa.eu/EDPSWEB/edps/site/mySite/pid/84#personal_data">personal data</a> are collected, held or processed by the data controller.</p><p><strong>Summary </strong></p><p>This article takes a look at the legal roles of various parties, according to the Regulation (EC) 45/2010, namely: data subjects, data processors, data controllers, data protection officers and the European Data Protection Supervisor (EDPS).</p><p><strong>CIPP Exam Preparation</strong></p><p>In preparation for the Certified Foundation Examination (Foundations), a privacy professional should be comfortable with topics related to this post, including:</p><ul><li>Processing of personal data – roles (I.A.e.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2011/10/11/roles-responsibilities-in-processing-personal-data/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Adequacy in the EU Data Protection Directive</title><link>https://www.cippguide.org/2011/09/27/adequacy-in-the-eu-data-protection-directive/</link> <comments>https://www.cippguide.org/2011/09/27/adequacy-in-the-eu-data-protection-directive/#comments</comments> <pubDate>Tue, 27 Sep 2011 12:00:33 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[adequacy]]></category> <category><![CDATA[COE Convention]]></category> <category><![CDATA[EU]]></category> <category><![CDATA[OECD]]></category> <category><![CDATA[Safe Harbor]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2657</guid> <description><![CDATA[This article takes a look at the European Commission’s Directive on Data Protection (95/46/EC), and the establishment of the adequacy requirement, which prevents Member States from transferring data to a third country, unless the third country ensures an adequate level of protection. The Directive also explores certain related concepts, including the Working Party and data/information embargoes. Finally, the article takes a look at the US data protection approach and its ability to meet the EC’s adequacy standard. [...]]]></description> <content:encoded><![CDATA[<p>The <a
href="http://www.cippguide.org/tag/european-union-data-protection-directive/">EU Data Protection Directive (95/46/EC)</a> regulates the processing of personal data within the European Union.  The Directive was developed in response to increased threats to informational privacy, as a way of regulating the collection, storage, usage and dissemination of personal data.</p><p><strong>The Adequacy Standard</strong></p><p>The key purpose of the Directive was to harmonize EU Member States’ laws, so that each Member State could transfer data to other Member States, while still safeguarding the fundamental rights and freedoms of their citizens.  If data controllers in one State transferred data to a third country that failed to protect personal data, the State’s protection of personal data would be lost once the Member State transferred the data to the third country.</p><p>Article 25 of the Directive prohibits Member States from transferring data to a third country, unless the third country ensures an adequate level of protection. Article 26 of the Directive outlines exceptions to the requirement that a third country have adequate protection in third countries.</p><p>For example, if the laws of a third country (e.g. Canada) fails to provide adequate protection of personal data, then a data controller located in a Member State would be prohibited from transferring personal data to Canada, unless an exception happened to apply. Without this exception, a transfer of data could lead to a data or information embargo.</p><p><strong>Data Embargos </strong></p><p>A data or information embargo would result in serious consequences on both Member State and third country. The Member State government may be prohibited from sending information to the third country regarding individuals in that country.</p><p>For instance, a Member State might prevent a private bank in the Member State from transferring information about its customers to Canadian financial institutions. Or perhaps a Member State might prohibit a European employer from sending information about its employees to its Canadian subsidiaries.</p><p>Article 26 outlines a number of exceptions to any such data embargo. Specifically, even if a sector or activity is found to lack adequate private protection, the Directive would still permit the transfer of personal data out of the EU if:</p><ul><li>The party desiring to send the data has entered into a contract approved by the privacy office in the EU member country (thus committing the party to providing certain protections)</li><li>The individual has unambiguously consented to the data transfer</li><li>The transfer is necessary to complete a transaction</li><li>The data are otherwise public</li></ul><p>It’s worth mentioning that the American credit reporting industry’s privacy protections should certainly satisfy the EU Data Protection Directive. The US <a
href="http://www.cippguide.org/tag/FCRA/">Federal Credit Reporting Act</a> (FCRA) includes the types of protections that EU Member States have incorporated into their laws, namely notice to consumers and the opportunity for them to correct any incorrect or inaccurate information in their files.</p><p><strong>Working Party</strong></p><p>Article 29 of the Directive establishes that a Working Party will advise the Commission on data protection matters, as well as contribute to the uniform application of the national data protection measures. Essentially, the Working Party is an independent advisory group, composed of a representative from each Member State’s supervisory authority, a representative of the Community and a representative of the Commission.</p><p>The responsibilities of the Working Party include examination of Member States’ data protection laws, as well as consulting with the Commission on the level of protection available in Member States and third countries.</p><p><strong>Adequacy and US Data Protection</strong></p><p>The United States’ <a
href="http://www.cippguide.org/2010/06/01/comparing-the-co-regulatory-model-comprehensive-laws-and-the-sectoral-approach/">sectoral approach</a> to data protection is derived from the American philosophy that laws should ensure citizens’ access to government, while still protecting them from government. While this enables the US to extensively regulate its public sector, it generally prevents the federal government from limiting interactions between private citizens. As a result, the US commitment to the free flow of information also favors a narrow regulatory approach to data protection.</p><p>Essentially, whether the Directive prohibits certain data transfers to the US largely depends upon what constitutes an adequate level of protection. The Directive requires a standard of adequacy that should be assessed in light of all the circumstances surrounding the transfer, yet fails to elaborate about this standard. Earlier data protection measures require a standard of equivalency, rather than adequacy.</p><p>For instance, the <a
href="http://www.cippguide.org/tag/OECD/">OECD</a> Guidelines, as well as the <a
href="http://conventions.coe.int/">COE Convention</a> do not define or use an adequacy standard for data transfers to third countries. In the same vein, the traditional legislation of most European countries establishes a standard of equivalency, rather than adequacy.</p><p>However, since the October 2008 enactment of the European Commission’s Directive on Data protection, the Safe Harbor framework has been developed which bridges the gap between some US privacy laws and the EC’s adequacy requirements.</p><p><strong>Summary </strong></p><p>This article takes a look at the European Commission’s Directive on Data Protection (95/46/EC), and the establishment of the adequacy requirement, which prevents Member States from transferring data to a third country, unless the third country ensures an adequate level of protection. The Directive also explores certain related concepts, including the Working Party and data/information embargoes. Finally, the article takes a look at the US data protection approach and its ability to meet the EC’s adequacy standard.</p><p><strong>CIPP Exam Preparation </strong></p><p>In preparation for the Certified Foundation Examination (Foundations), a privacy professional should be comfortable with topics related to this post, including:</p><ul><li>EU Data Protection Directive – Adequacy (I.C.c.i.4.a.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2011/09/27/adequacy-in-the-eu-data-protection-directive/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Implementing the EU e-Privacy Directive: The Cookie Problem</title><link>https://www.cippguide.org/2011/04/12/implementing-the-eu-e-privacy-directive-the-cookie-problem/</link> <comments>https://www.cippguide.org/2011/04/12/implementing-the-eu-e-privacy-directive-the-cookie-problem/#comments</comments> <pubDate>Tue, 12 Apr 2011 12:00:44 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[cookies]]></category> <category><![CDATA[EU]]></category> <category><![CDATA[EU e-Privacy Directive]]></category> <category><![CDATA[legislation]]></category> <category><![CDATA[online privacy]]></category> <category><![CDATA[Surveillance]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2400</guid> <description><![CDATA[<p>This article explores the EU e-Privacy Directive, with a focus on the “Cookie Law,” which was passed late 2009. The Directive has yet to be fully implemented in all EU member states and the amendment of the “Cookie Law” has created additional roadblocks to harmonization of legislation across Europe.</p><p>Background: e-Privacy Directive
The European Commission’s Directive of Privacy and Electronic Communications 2002/58/EC (also referred to as the e-Privacy Directive) required that public communications providers (i.e. internet service providers and telecommunications companies) inform national regulatory authorities of any data security breach. Subscribers should also be notified if the personal data breach is likely [...]]]></description> <content:encoded><![CDATA[<p>This article explores the EU e-Privacy Directive, with a focus on the “Cookie Law,” which was passed late 2009. The Directive has yet to be fully implemented in all EU member states and the amendment of the “Cookie Law” has created additional roadblocks to harmonization of legislation across Europe.</p><p>Background: e-Privacy Directive<br
/> The European Commission’s <a
href="http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2002:201:0037:0047:EN:PDF">Directive of Privacy and Electronic Communications 2002/58/EC</a> (also referred to as the e-Privacy Directive) required that public communications providers (i.e. internet service providers and telecommunications companies) inform national regulatory authorities of any data security breach. Subscribers should also be notified if the personal data breach is likely to adversely affect the personal data or the privacy of the subscriber. The deadline for member states to implement this Directive is May 25, 2011.</p><p>The Cookie Law<br
/> On November 9, 2009, the European Parliament made additions to the e-Privacy Directive, which included an effort to regulate <a
href="https://www.cippguide.org/tag/cookies/">online cookies</a>. According to the previous law, web sites were required to allow consumers to opt-out of cookies, typically by selecting a setting on their web browsers. A Parliament committee determined that the practice be reversed; users should be presented with the opportunity to opt in before cookies are placed on their computers.</p><p>Under the new addition, companies are required to secure consent from users before tracking files, such as online cookies, are placed on the users’ computers. This addition is commonly referred to as the “cookie law:”</p><p>“The new e-Privacy Directive will include a provision requiring the EU Member States to ensure that the storing of information, or the gaining of access to information already stored, in the terminal equipment of a subscriber or user is only allowed on condition that the subscriber or user concerned has given his or her consent, having been provided with clear and comprehensive information, in accordance with Directive 95/46/EC, inter alia about the purposes of the processing.”</p><p>Although it does not directly mention cookies, commenters point out that the wording includes cookies as well as any other technologies which may be used to track users’ behavior through their internet browsers.</p><p>Cookie Law Controversy<br
/> The Cookie Law applies to cookies that collect personal data. Some experts have pointed out that certain cookies are not covered by this consent requirement. According to data protection authorities, persistent cookies that contain a unique user ID would qualify as personal data, thus subject to applicable data protection regulations. However, there are other types of cookies that do not meet such criteria.</p><p>Another uncertainty regarding the Cookie Law is the process by which <a
href="https://www.cippguide.org/tag/consent/">consent </a>should be obtained. The statement does not mention prior consent, rather suggests that users are presented with an opportunity to refuse cookies before they are delivered to their computers. The means by which consent should be obtained has given rise to a series of discussions between internet service providers, privacy advocates, advertisers, law makers and EU member states.</p><p>It is unclear if “consent” means that users need to agree to cookies when setting up their web browsers, or if they must give unambiguous consent for each and every cookie. Others have interpreted “consent” to mean a standardized plan that allows users to view and opt-out of data collected about them through cookies.</p><p>Advertising Outcry<br
/> Europe’s online advertising industry currently generates US$20.12 billion in advertising spending annually. The initial idea that cookie placement needed the user’s prior consent concerned industry executives, who argued it would be a costly and disruptive practice. As a result, the requirement of “prior consent” was moved to an addendum.</p><p>Rather than recurring pop-up windows requesting consent, advertising executives suggested placing icons on internet ads that rely on tracking tools. Users can click on the icon to view what data is being collected about them, or to block any cookies.</p><p>Dutch Telecommunications Act<br
/> On November 3, 2010, an <a
href="https://zoek.officielebekendmakingen.nl/kst-32549-2.pdf">amendment </a>to the Dutch Telecommunications Act was submitted to the Dutch Parliament. This was an effort to implement the EU e-Privacy Directive.</p><p>The proposed Bill requires telecommunications and internet service providers to give notification of data security breaches involving personal data to the Dutch Telecom Authority. If individuals’ privacy is likely to be compromised in a breach, service providers would also be obliged to notify the appropriate individuals.<br
/> The proposed Bill also requires that consent be secured before the use of cookies, in particular, prior to the use of third party cookies that are designed to track individuals’ web browsing activities for behavioral advertising purposes. In response to confusion regarding unambiguous consent (i.e. whether or not consent was required for placing individual cookies), the Bill indicates that browser consent would be sufficient. However, browser consent may not be enough in all situations.</p><p>Summary<br
/> This article discusses the European Union’s e-Privacy Directive, also referred to as the Directive of Privacy and Electronic Communications 2002/58/EC. The Directive is a continuation of the EU Data Protection Directive and deals with data protection and privacy issues relating to digital technologies. The article takes a look at the “Cookie Law,” an amendment to the Directive that requires user consent before cookies are placed on users’ computers. This amendment has given rise to controversial discussions between internet service providers, privacy advocates, advertisers, law makers and EU member states. Finally, the article takes a look at how the elements of the e-Privacy Directive are being implemented in the legislation of member states.</p><p>CIPP Exam Preparation<br
/> In preparation for the Certification Foundation exam (Foundations) and the Certified Information Privacy Professional/Information Technology (CIPP/IT) exam, a privacy professional should be comfortable with topics related to this post, including:<br
/> •	Online Privacy – Online Identification Mechanisms – Cookies (Foundations; III.B.g.i.)<br
/> •	Privacy-Enhancing Technologies – Web Cookies (CIPP/IT; III.B.c.i.)<br
/> •	Privacy &amp; Data Protection Regulation – Europe (Foundations; I.F.b.ii.)</p><p><a
class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=https%3A%2F%2Fwww.cippguide.org%2F2011%2F04%2F12%2Fimplementing-the-eu-e-privacy-directive-the-cookie-problem%2F&amp;title=Implementing%20the%20EU%20e-Privacy%20Directive%3A%20The%20Cookie%20Problem" id="wpa2a_2"><img
src="https://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2011/04/12/implementing-the-eu-e-privacy-directive-the-cookie-problem/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>EU Data Retention Directive: A Request for Repeal</title><link>https://www.cippguide.org/2011/01/04/eu-data-retention-directive-a-request-for-repeal/</link> <comments>https://www.cippguide.org/2011/01/04/eu-data-retention-directive-a-request-for-repeal/#comments</comments> <pubDate>Tue, 04 Jan 2011 17:00:11 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[EU]]></category> <category><![CDATA[EU Data Retention Directive]]></category> <category><![CDATA[legislation]]></category> <category><![CDATA[online privacy]]></category> <category><![CDATA[Surveillance]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2398</guid> <description><![CDATA[<p>Data retention has been an important issue for law enforcement agencies and privacy rights organizations alike. Governments have made efforts to require telecommunications service providers to record and retain information, such as telephone calls, emails, or other communications. This article examines the European Union Directive on Mandatory Retention of Communications Traffic Data, which was enacted in March 2006. The article goes on to look at criticisms of the Directive as well as recent efforts calling for the repeal of this Directive.</p><p>Background: The 2006 EU Data Retention Directive
The EU Data Retention Directive 2006/24/EC required that operators of public electronic communication networks [...]]]></description> <content:encoded><![CDATA[<p>Data retention has been an important issue for law enforcement agencies and privacy rights organizations alike. Governments have made efforts to require telecommunications service providers to record and retain information, such as telephone calls, emails, or other communications. This article examines the European Union Directive on Mandatory Retention of Communications Traffic Data, which was enacted in March 2006. The article goes on to look at criticisms of the Directive as well as recent efforts calling for the repeal of this Directive.</p><p>Background: The 2006 EU Data Retention Directive<br
/> The <a
href="http://register.consilium.eu.int/pdf/en/05/st03/st03677.en05.pdf">EU Data Retention Directive 2006/24/EC</a> required that operators of public electronic communication networks store specific data for the investigation, detection and prosecution of serious crime. The Directive requires that Internet service providers operating in Europe retain telecom and Internet traffic data about all their clients’ communications for at least six months, to a maximum of two years from the date of the communication. This is for the potential use of law enforcement authorities. Retained data includes the traffic and location data, but not the contents of the communications.</p><p>Of specific concern to privacy professionals was that the retained data included the following:<br
/> •	Fixed network telephony<br
/> •	Mobile telephony<br
/> •	Internet access<br
/> •	Internet email<br
/> •	Internet telephony</p><p>The data retention regulations listed four data security principles, applicable to the retained data. These regulations are outlined below:<br
/> 1.	The data must have the same security levels when retained and must remain the same quality.<br
/> 2.	Security measures (both technical and organizational) must be enacted to protect against accidental or unlawful disclosure, access, alteration or loss of the data.<br
/> 3.	The retained data should only be accessible by authorized persons.<br
/> 4.	All retained data must be appropriately destroyed at the end of the retention period.</p><p>As part of the terms of the Directive, the data could only be made available to competent national authorities in particular cases, in line with national law. EU member states are responsible to ensure that any intentional access or transfer of this data is punishable by administrative or criminal penalties. Member states were also required to have a public authority responsible for implementing and monitoring the Directive within 18 months after it was introduced. Each state developed their own version of the Directive, which was integrated into their national laws.</p><p>Controversy Surrounding the Directive<br
/> For public communications providers throughout the EU, the Directive presented a number of different challenges. Service providers were mandated to retain communications data to allow requested access for investigations. This meant that they were faced with the challenge of harmonizing their data center with hundreds of storage devices and petabytes of data. This significantly increased the size of IT infrastructures. Many critics argued that the mandated retention practices made organizations more vulnerable to privacy risks.</p><p>Observers also argued that the requirements of the Directive amounted to a type of surveillance. The Directive requires member states to collect personal data about citizens, without the consent of the citizens. It also allows the states to apply the data to monitor and control citizens, by applying criminal penalties.<br
/> For these and other reasons, many European privacy activists have strongly <a
href="http://www.edri.org/campaigns/dataretention">opposed </a>the Directive.</p><p>One example was the <a
href="http://www.vorratsdatenspeicherung.de/content/view/46/42/lang,en/">Freedom Not Fear</a> movement, which organized protests in major cities across Europe. These demonstrations aimed to raise public awareness of increased surveillance and data retention practices. The Freedom Not Fear movement also demanded the following:<br
/> •	Cutbacks on surveillance measures<br
/> •	Evaluation of existing surveillance powers<br
/> •	Moratorium on new surveillance powers<br
/> •	Ensure the freedom of expression, dialogue and information on the Internet</p><p>During 2007, the <a
href="http://www.vorratsdatenspeicherung.de/index.php?lang=en">German Working Group on Data Retention</a> represented 35 000 people and filed a class-action lawsuit against data retention laws. The court found the laws unconstitutional, which led to requirements for the immediate deletion of all data retained under the law.</p><p>During 2009, the Romanian Constitutional Court ruled that the Directive was in direct violation of <a
href="http://www.hri.org/docs/ECHR50.html#C.Art8">Article 8</a> of the European Convention on Human Rights, guaranteeing the right to respect for private life and correspondence. The Court held that data retention turns all those who use public communication networks into potential criminals.</p><p>Also during 2009, the European Commission initiated a lawsuit with the Swedish government, which had refused to implement the Data Retention Directive within the required time frame. Political leaders argued that the Directive was inconsistent with the European Convention on Human Rights, as well as being an expensive and ineffective means of protecting citizens’ rights and freedoms. In addition to Sweden’s non-cooperation with the Directive, Austria, Greece, Ireland, the Netherlands and Poland also did not implement data retention laws within the April 2009 deadline stipulated by the Directive.</p><p>Calls to repeal the Directive<br
/> During the <a
href="http://www.privacyconference2010.org/">32nd Annual Conference of Data Protection and Privacy Commissioners</a>, which was held during October 27-29, 2010, privacy authorities called for the repeal of the Data Retention Directive.</p><p>A vocal participant in this discussion was the <a
href="http://www.eff.org/work">Electronic Frontier Foundation</a> (EFF), which has protested the indiscriminate collection of traffic data. According to the EFF, there is no clear link between data retention and effective law enforcement. Rather, such retention leads to abuse of authorities, including excessive tracking and over-collection. Furthermore, many of the retention practices pose a serious violation of individuals’ rights and freedoms.</p><p>Summary<br
/> This article explores the 2006 European Union Data Retention Directive, which required member states to implement laws requiring communications service providers to retain data from anywhere between six months to two years. This was supposedly to facilitate law enforcement efforts, particularly anti-terrorist programs. The Directive was met with widespread public outcry, given the potential for surveillance, monitoring and abuse, in addition to arguments that it was a violation of rights and freedoms. The article explores a number of different responses to the Directive, including citizens’ movements throughout Europe, national court rulings against the Directive and non-compliance issues.</p><p>CIPP Exam Preparation<br
/> In preparation for the Certification Foundation (Foundations) exam and the Certified Information Privacy Professional/Information Technology (CIPP/IT) exam, a privacy professional should be comfortable with topics related to this post, including:<br
/> •	Data Retention &amp; Destruction – Period of Retention (CIPP/IT; I.E.a.)<br
/> •	Privacy Concerns – Government Surveillance (CIPP/IT; II.A.k.)<br
/> •	Modern Principles of Privacy – Europe (Foundations; I.D.a.ii.)<br
/> •	Privacy &amp; Data Protection Regulation – Europe (Foundations; I.F.b.ii.)</p><p><a
class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=https%3A%2F%2Fwww.cippguide.org%2F2011%2F01%2F04%2Feu-data-retention-directive-a-request-for-repeal%2F&amp;title=EU%20Data%20Retention%20Directive%3A%20A%20Request%20for%20Repeal" id="wpa2a_4"><img
src="https://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2011/01/04/eu-data-retention-directive-a-request-for-repeal/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Safe Harbor in Action: CARU Example</title><link>https://www.cippguide.org/2010/12/21/safe-harbor-in-action-caru-example/</link> <comments>https://www.cippguide.org/2010/12/21/safe-harbor-in-action-caru-example/#comments</comments> <pubDate>Tue, 21 Dec 2010 12:00:24 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[CARU]]></category> <category><![CDATA[Consent]]></category> <category><![CDATA[COPPA]]></category> <category><![CDATA[EU]]></category> <category><![CDATA[European Union Data Protection Directive]]></category> <category><![CDATA[Safe Harbor]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2377</guid> <description><![CDATA[The EU-US Safe Harbor framework was developed to facilitate the cross-border transmission of information, as well as ensure high standards of privacy protection. This article explores the implementation of these principles in context of the Children’s Advertising Review Unit (CARU) Safe Harbor [...]]]></description> <content:encoded><![CDATA[<p>The <a
href="https://www.cippguide.org/tag/safe-harbor/">EU-US Safe Harbor framework</a> was developed to facilitate the cross-border transmission of information, as well as ensure high standards of privacy protection. This article explores the implementation of these principles in context of the <a
href="http://www.caru.org/">Children’s Advertising Review Unit </a>(CARU) Safe Harbor Program.</p><p>Safe Harbor in a nutshell<br
/> During October 1998, the European Commission’s Directive on Data Protection was enacted, prohibiting the transfer of personal data from <a
href="https://www.cippguide.org/tag/EU/">European Union</a> (EU) member states to non-EU nations that did not meet the privacy protection standard. In order to facilitate the transfer of information between EU-based organizations and US-based organizations, the Safe Harbor framework was developed.</p><p>US-based organizations may qualify for Safe Harbor statues in two different ways. They may join self-regulatory privacy programs following the requirements of Safe Harbor. Alternatively, they may choose to develop organization-specific self-regulatory privacy policies, in line with the requirements of Safe Harbor.</p><p>What is CARU?<br
/> In 1974, the Children’s Advertising Review Unit (CARU) was created in order to promote responsible advertising to children. CARU was developed as a component of a strategic alliance amongst the major US advertising trade associations, including the <a
href="http://www.aaaa.org/">American Association of Advertising Agencies</a> (AAAA), <a
href="http://www.aaf.org/">American Advertising Federation</a> (AAF), <a
href="http://www.ana.net/">Association of National Advertisers</a> (ANA) and the <a
href="http://www.bbb.org/">Council of Better Business Bureaus</a> (CBBB).</p><p>CARU is in charge of children’s advertising issues within the advertising industry’s self-regulation program. It assesses the truthfulness, accuracy and consistency of child-directed advertising and assists advertisers in dealing with child audiences responsibly. CARU does so by advancing compliance with its Self-Regulatory Guidelines for Children’s Advertising, the Children’s Online Privacy Protection Act of 2000 (COPPA) and other relevant laws.</p><p>The CARU Safe Harbor Program<br
/> As of January 2001, the CARU self-regulatory program was approved as Safe Harbor-compliant, under the <a
href="https://www.cippguide.org/tag/coppa/">Children’s Online Privacy Protection Act</a> (COPPA). It was also the first such program to the FTC-approved. Organizations that comply with CARU Guidelines are also in compliance with the COPPA, thus insulated from FTC enforcement action.</p><p>Compliance with CARU’s Safe Harbor Program is dependent on the following elements:<br
/> •	Adhering to the requirements in the CARU Safe Harbor Compliance Checklist<br
/> •	Compliance with the CARU Self-Regulatory Guidelines for Children’s Advertising<br
/> •	Review by CARU staff of the web site’s information practices; completion of Initial Website Review &amp; Seeding form<br
/> •	Continuous monitoring of web site by CARU staff to ensure compliance with the Safe Harbor framework<br
/> •	Completion of CARU Self-Assessment Form and Attestation by Safe Harbor participant</p><p>CARU Safe Harbor Compliance Checklist<br
/> This checklist makes up a critical component of the Safe Harbor compliance, as discussed above. The checklist includes the Safe Harbor principles and is specific to web sites advertising to child audiences. The following elements are on the CARU Safe Harbor Compliance Checklist:<br
/> 1.	Provide notice<br
/> 2.	Obtain verifiable parental <a
href="https://www.cippguide.org/tag/consent/">consent</a><br
/> 3.	Limit collection, use and disclosure of personal information collected from children<br
/> 4.	Provide access upon verification of parental identity<br
/> 5.	Maintain reasonable security</p><p>The elements of the checklist are explored in greater detail below:<br
/> <strong><br
/> 1.	Provide Notice</strong><br
/> In accordance with the Safe Harbor principles, privacy notices should be clearly written and easily understandable. They should not contain irrelevant, confusing or contradictory statements. There are two different types of notices that are required of CARU Safe Harbor participants: a Notice of Information Practices and a Direct Notice to Parents.</p><p>The Notice of Information Practices is also referred to as the “Web Site Notice,” or “Children’s Privacy Policy.” Such a notice requires a prominent link on the site’s home page and in each area where personal information is collected from children. This notice must state all of the following information:<br
/> •	Name, address, phone number and email of the operators responsible for the collection and maintenance of personal information collected from children through the site.<br
/> •	Types of personal information that is collected from children.<br
/> •	Identification of the means of collection of the information (i.e. directly or passively).<br
/> •	How the personal information is being used, or will be used.<br
/> •	If the personal information will be disclosed to third parties. If this is being done, then the notice must state the types of businesses in which third parties are engaged; the purpose of such personal information; and if the third parties are committed to maintaining the security and confidentiality of the information collected.<br
/> •	An option for the parent to agree to the collection and use of the child’s information, that is not dependent on consent for disclosing information to third parties.<br
/> •	The child cannot be required to disclose more information than reasonable necessary to participate in the web site activities.<br
/> •	The parent has the right to review the child’s personal information, request that it be deleted, and prevent any further collection or use of the personal information.<br
/> •	Procedures for the parent to review or delete their child’s personal information and prevent ongoing use or disclosure.</p><p>The Direct Notice to Parents must include the following information:<br
/> •	The same information stated in the Notice of Information Practices (as listed above).<br
/> •	The web site operator wishes to collect personal information from the child.<br
/> •	Request for the parent’s consent to collect this personal information. This consent is required for the collection, use and disclosure of personal information.<br
/> •	Methods for providing parental consent.</p><p>2. <strong>Obtain Verifiable Parental Consent</strong><br
/> Web site operators are obliged to obtain verifiable parental consent before the collection, use or disclosure of children’s personal information. Such consent may be obtained in the following ways:<br
/> •	When personal information is being collected for internal use only. In this case, email may be used to obtain parental consent. This also requires the additional steps of a follow-up email, letter or phone call to verify the consent. This method was used prior to April 21, 2002.<br
/> •	When personal information is being made publicly available, such as in a chat room, message board, personal home page, profile, or email account. OR, when personal information is being disclosed to third parties.</p><p>In such cases, website operators are obliged to employ a more reliable means of securing parental consent. This may include: (a) A form with a parent’s signature through postal mail or fax; (b) A credit card number in connection with a transaction; (c) A toll-free phone number managed by trained personnel; (d) Email consent in conjunction with a digital signature from a parent; (e) Email consent in conjunction with a PIN or password; (f) Consent through a CARU-approved method. After April 21, 2002, only these methods were acceptable for securing parental consent.</p><p>3. <strong>Limit Collection, Use and Disclosure of Personal Information Collected from Children</strong><br
/> Web site operators are prohibited from conditional a child’s participate on the basis of disclosing more personal information than is reasonably necessary to participate. The collection of personal information from a child ought to be limited to that which is reasonable for participation. For instance, a web site operator cannot offer a prize for greater disclosure of personal information. Parents should also be given the option to consent to the collection and use of their children’s personal information. They should also be permitted to prevent disclosure of such information to third party affiliates.</p><p>4. <strong>Provide Access upon Verification of Parental Identity</strong><br
/> Upon parental request, web site operators are obliged to disclose both the type of information collected from children and the specific information that has been collected. Parents are permitted, at any time, to refuse further use or future collection of personal information from their child. They can also ensure the deletion of their child’s personal information. However, before this happens, operators must verify the identity of the parent in the same methods used for securing parental consent (i.e. those listed in “2. Obtain Verifiable Parental Consent”).</p><p>5. <strong>Maintain Reasonable Security</strong><br
/> Web site operators are obliged to create and implement reasonable mechanisms for protecting the confidentiality, security and integrity of children’s personal information. Examples of such mechanisms include:<br
/> •	Appropriately destroying unnecessary personal information.<br
/> •	Limiting employee access to personal information.<br
/> •	Ensuring physical security of servers.<br
/> • <a
href="https://www.cippguide.org/tag/cryptography/">Encrypting </a>data during transmission.<br
/> •	Using firewalls.</p><p>Summary<br
/> This article looks at the EU-US Safe Harbor framework in light of the CARU Safe Harbor Program, which aims to protect children’s online privacy and meet the requirements of the COPPA (Children’s Online Privacy Protection Act). The CARU program is partially based on the Safe Harbor Compliance Checklist. This checklist is made of the following five elements: (1) Provide Notice; (2) Obtain Verifiable Parental Consent; (3) Limit Collection, Use and Disclosure of Personal Information Collected from Children; (4) Provide Access upon Verification of Parental Identity; and (5) Maintain Reasonable Security.</p><p>CIPP Exam Preparation<br
/> In preparation for the Certified Information Privacy Professional (CIPP) exam; the Certified Information Privacy Professional/Canada (CIPP/C) exam; the Certification Foundation (Foundations) exam; and the Certified Information Privacy Professional/Government (CIPP/G) exam, a privacy professional should be comfortable with topics related to this post, including:<br
/> •	E.U. Data Protection Directive (95/46/EC) (Foundations: I.D.a.ii.2.)<br
/> •	E.U. Data Protection Directive – Safe Harbor Status (CIPP/C; II.A.b.iii.)<br
/> •	International Data Transfers (CIPP; II.C.e.)<br
/> •	Multinational Compliance – E.U. Data Protection (CIPP; II.C.f.)<br
/> •	Regulatory Authorities – U.S. Department of Commerce (CIPP; I.A.c.iii.)<br
/> •	Children’s Online Privacy Protection Act of 2000; COPPA (CIPP/G; I.B.a.ii.)</p> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2010/12/21/safe-harbor-in-action-caru-example/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Is Safe Harbor necessary?</title><link>https://www.cippguide.org/2010/12/14/do-i-need-to-apply-for-safe-harbor/</link> <comments>https://www.cippguide.org/2010/12/14/do-i-need-to-apply-for-safe-harbor/#comments</comments> <pubDate>Tue, 14 Dec 2010 12:00:28 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[EU]]></category> <category><![CDATA[European Union Data Protection Directive]]></category> <category><![CDATA[Federal Trade Commission]]></category> <category><![CDATA[FTC]]></category> <category><![CDATA[PII]]></category> <category><![CDATA[Safe Harbor]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2375</guid> <description><![CDATA[<p>The Safe Harbor framework deals with privacy protection around the transfer of personal data between organizations in European Union (EU) member states to organizations located in the United States. This article explores the purposes and requirements of the Safe Harbor framework. It also provides information for US-based organizations who may participate in the Safe Harbor framework.</p><p>What is Safe Harbor?
In October 1998, the European Commission Directive on Data Protection went into effect. The Directive prohibited the transfer of personal data from EU member states to non-EU nations that did not meet the adequacy standard of privacy protection. There are significant differences [...]]]></description> <content:encoded><![CDATA[<p>The Safe Harbor framework deals with privacy protection around the transfer of personal data between organizations in <a
href="https://www.cippguide.org/tag/eu/">European Union</a> (EU) member states to organizations located in the United States. This article explores the purposes and requirements of the <a
href="https://www.cippguide.org/tag/safe-harbor/">Safe Harbor</a> framework. It also provides information for US-based organizations who may participate in the Safe Harbor framework.</p><p>What is Safe Harbor?<br
/> In October 1998, the European Commission <a
href="https://www.cippguide.org/tag/european-union-data-protection-directive/">Directive on Data Protection</a> went into effect. The Directive prohibited the transfer of personal data from EU member states to non-EU nations that did not meet the adequacy standard of privacy protection. There are significant differences between the US and EU approaches to privacy protection. The US takes a sectoral approach to privacy protection that involves legislation, regulation and self-regulation. In contrast, the EU has enacted comprehensive privacy legislation that involves government data protection agencies, registration of databases with these agencies and pre-approval before the processing of personal data.</p><p>As the EU Directive is significantly more rigorous than the privacy protection system currently found in the United States, it was necessary to develop a streamlined and cost-effective means for organizations and businesses in the US to achieve compliance with the EU adequacy standard.</p><p>Seven Principles of Safe Harbor<br
/> The Safe Harbor Framework was thus developed as a joint effort between the <a
href="http://www.commerce.gov/">US Department of Commerce</a> and the <a
href="http://ec.europa.eu/index_en.htm">European Commission</a>. The Safe Harbor Principles were established in order to prevent accidental or unauthorized information disclosure or loss. US organizations can meet Safe Harbor requirements by adhering to the following seven principles:</p><p>1. <strong>Notice </strong>– Organizations are required to notify individuals of the purposes for collecting and using personal information. Individuals should also be provided with the organizations’ contact information, should they have inquiries or complaints. Individuals should be aware of third parties and methods for limiting use/disclosure of personal information.</p><p>2. <strong>Choice </strong>– Individuals should have the right to opt-out (to choose) whether they want their personal information to be disclosed to a third party or used for other purposes. Opt-in choice is required for sensitive information.</p><p>3. <strong>Onward Transfer </strong>– This principle refers to transfers of personal information to third parties. Notice and choice principles apply to third parties handling personal information. Organizations should ensure that the third party adheres to Safe Harbor principles, is subject to the EU Directive, or provides an adequate level of privacy protection.</p><p>4. <strong>Access </strong>– Individuals should have access to any personal information about them held by an organization, for the purposes of correction, amendment or deletion.</p><p>5. <strong>Security </strong>– Organizations are obliged to take reasonable precautions in order to protect personal information from loss; misuse; and unauthorized access, disclosure, alteration and destruction.</p><p>6. <strong>Data Integrity</strong> – Organizations are obliged to take reasonable steps in order to ensure that the personal information is reliable and relevant for its intended use. This means that the data should be accurate, complete and current.</p><p>7. <strong>Enforcement </strong>– This includes independent recourse mechanisms; procedures for verifying the organization’s commitments to the above principles; and obligations to remedy compliance failures.</p><p>Why Safe Harbor?<br
/> Safe Harbor participation offers several benefits to US-based organizations:<br
/> •	EU member states are bound by the European Commission’s adequacy finding<br
/> •	Organizations under Safe Harbor meet the adequacy standard, allowing data flows to continue<br
/> •	EU member state requirements for approval of data transfers will be waived, or automatically approved<br
/> •	Claims by EU citizens against US organizations will be heard in the US</p><p>The Safe Harbor framework also offers several benefits to EU-based organizations, as they can ensure privacy protection standards through a list of Safe Harbor-compliant organizations in the US</p><p>Participating in Safe Harbor?<br
/> The first step in participating in the Safe Harbor framework is determining if your organization is covered by the United States-European Union Safe Harbor framework. Businesses that are covered by the Safe Harbor framework must meet the following criteria:</p><p>1.	Its business practices fall under the jurisdiction of the <a
href="https://www.cippguide.org/tag/ftc/">Federal Trade Commission</a> (FTC) or the Department of Transportation (DoT). Such organizations may include US air carriers and ticket agents.</p><p>Organizations that are usually not under the jurisdiction of the FTC include financial institutions (e.g. banks, investment houses, credit unions, savings and loan institutions, etc.); telecommunication common carriers; labor associations; non-profit organizations; agricultural cooperatives; and meat processing facilities.</p><p>2.	It receives or processes <a
href="https://www.cippguide.org/tag/pii/">personally identifiable information</a> (PII) directly or indirectly from EU member states. This also includes subsidiaries and affiliates that process PII in the US.</p><p>These organizations may collect, store or process PII for a wide variety of reasons, including: determining, evaluating, or implementing employment-related actions or obligations; designing, evaluating or administering compensation, benefits, or other human resources programs; evaluating employee performance; maintaining business records that relate to past, present or potential employees; supporting relationships with clients and vendors; and facilitating business communications and compliance with contractual or legal obligations.</p><p>Organizations have two options for qualifying for Safe Harbor. They may choose to join a self-regulatory privacy program which follows the requirements of Safe Harbor. Or, they may choose to develop an organization-specific self-regulatory privacy policy which conforms to Safe Harbor.</p><p>Developing &amp; Establishing Safe Harbor Mechanisms<br
/> Prior to certifying to the Safe Harbor framework, organizations should also develop and implement supporting mechanisms. These are discussed below:</p><p>• <strong>Safe Harbor-Compliant Privacy Statement</strong> – Developing a Safe Harbor-Compliant Privacy Statement is a necessary step before submitting a self-certification form to the Department of Commerce. The organization’s privacy policy statement must be compliant to Safe Harbor, meaning that it needs to conform to the seven privacy principles listed above. The statement should also reference the organization’s compliance with Safe Harbor. The statement should be available to the public.</p><p>• <strong>Independent Recourse Mechanism</strong> – This step ensures compliance with the seventh Safe Harbor principle (enforcement). The organization’s independent recourse mechanism is responsible for investigating unresolved privacy complaints. This mechanism may be a private sector dispute resolution program, such as BBB OnLine, TRUSTe, Direct Marketing Association, AICPA WebTrust, etc. As an alternative, the organization may also cooperate with the European Data Protection Authorities (DPAs) for dispute resolution.</p><p>• <strong>Verification Mechanism</strong> – This mechanism verifies the organization’s compliance with the Safe Harbor framework. This may involve a self-assessment program, or a third-party assessment program.</p><p>• <strong>Contact Point</strong> – Organizations are obliged to provide an internal contact point responsible for questions, complaints, access requests, or other issues encompassed by Safe Harbor. For instance, this may be the corporate officer responsible for Safe Harbor, or the organization’s Chief Privacy Officer.</p><p>Safe Harbor Fees<br
/> As of March 1, 2009, the US Department of Commerce introduced fees meant to support the operation of the US-EU Safe Harbor framework. New registrants to the Safe Harbor framework must pay a fee of $200.00. Self-certified organizations are required to pay a $100.00 annual fee to recertify their compliance with the Safe Harbor framework.</p><p>Summary<br
/> This article explores the purposes of the US-EU Safe Harbor framework, which allows data transfers between organizations based in EU member states and organizations based in the US. It looks at some of the benefits for certifying under the Safe Harbor and well as the requirements of an organization for certification. According to the US Department of Commerce, organizations may choose to join a self-regulatory privacy program which follows the requirements of Safe Harbor. Or, organizations may develop a self-regulatory privacy policy which conforms to Safe Harbor.</p><p>CIPP Exam Preparation<br
/> In preparation for the Certified Information Privacy Professional (CIPP) exam; the Certification Foundation (Foundations) exam; and the Certified Information Privacy Professional/Canada (CIPP/C) exam, a privacy professional should be comfortable with topics related to this post, including:<br
/> •	E.U. Data Protection Directive (95/46/EC) (Foundations: I.D.a.ii.2.)<br
/> •	E.U. Data Protection Directive – Safe Harbor Status (CIPP/C; II.A.b.iii.)<br
/> •	International Data Transfers (CIPP; II.C.e.)<br
/> •	Multinational Compliance – E.U. Data Protection (CIPP; II.C.f.)<br
/> •	Regulatory Authorities – U.S. Department of Commerce (I.A.c.iii.)</p><p><a
class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=https%3A%2F%2Fwww.cippguide.org%2F2010%2F12%2F14%2Fdo-i-need-to-apply-for-safe-harbor%2F&amp;title=Is%20Safe%20Harbor%20necessary%3F" id="wpa2a_6"><img
src="https://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2010/12/14/do-i-need-to-apply-for-safe-harbor/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Data Protection Laws Around the Globe</title><link>https://www.cippguide.org/2009/12/06/data-protection-laws-around-the-globe/</link> <comments>https://www.cippguide.org/2009/12/06/data-protection-laws-around-the-globe/#comments</comments> <pubDate>Sun, 06 Dec 2009 12:00:18 +0000</pubDate> <dc:creator>jbrook</dc:creator> <category><![CDATA[CIPP]]></category> <category><![CDATA[Compliance & Regulations]]></category> <category><![CDATA[Privacy]]></category> <category><![CDATA[APEC]]></category> <category><![CDATA[Argentina]]></category> <category><![CDATA[Asia]]></category> <category><![CDATA[Brazil]]></category> <category><![CDATA[Canada]]></category> <category><![CDATA[Chile]]></category> <category><![CDATA[EU]]></category> <category><![CDATA[European Union Data Protection Directive]]></category> <category><![CDATA[Habeas Data]]></category> <category><![CDATA[Japan]]></category> <category><![CDATA[Latin America]]></category> <category><![CDATA[Paraguay]]></category> <category><![CDATA[PIPEDA]]></category><guid
isPermaLink="false">http://www.cippguide.org/?p=1145</guid> <description><![CDATA[Information Privacy is an International concern. Today, most countries have laws protecting personal data from misuse and destruction. Regulation and enforcement of data protection varies from country to country. However, despite such differences, almost every country uses the same basic privacy concepts and principles– notice, access, consent, data integrity, disclosure and accountability– to develop data protection [...]]]></description> <content:encoded><![CDATA[<p>Information Privacy is an International concern. Today, most countries have laws protecting personal data from misuse and destruction. Regulation and enforcement of data protection varies from country to country. However, despite such differences, almost every country uses the same basic privacy concepts and principles– notice, access, consent, data integrity, disclosure and accountability– to develop data protection laws.</p><h2>Data Protection in Europe</h2><p>The European Union has the most extensive and comprehensive data protection laws in the world. In 1995, the European Commission instituted their most significant body of law known as the Data Protection Directive (95/45/EC). The directive applies to all entities that process personal data in all member states of the European Union.</p><h3>E.U. Data Protection Directive Privacy Principles</h3><p>The Data Protection Directive outlines privacy principles for the processing of data which include:</p><p>1)  Notice– <a
href="http://aspe.hhs.gov/DATACNCL/eudirect.htm%23ART10">(Article 10) </a>The data subject must be provided with the identity of the data controller, the purposes for which data is collected and third party recipients</p><p>2)  Choice– <a
href="http://aspe.hhs.gov/DATACNCL/eudirect.htm%23ART14">(Article 14)</a> The data subject may object to the processing of their personal data for the purpose of direct marketing and the disclosure of data for third parties or uses.</p><p>3)  Access and Correction– <a
href="http://aspe.hhs.gov/DATACNCL/eudirect.htm%23ART12">(Article 12) </a>The data subject may request to view data an entity has on record about them and rectify, erase of block the processing of data if incorrect or incomplete.</p><p>4)  Data Quality–<a
href="http://aspe.hhs.gov/DATACNCL/eudirect.htm%23ART6">(Article 6</a>) Data should be processed lawfully. It should be collected and processed for specific and legitimate purposes. Data should be timely, accurate and complete. Data that is no longer necessary should be kept in a format that is not personally identifiable.</p><p>5)  Data Security– <a
href="http://aspe.hhs.gov/DATACNCL/eudirect.htm%23ART17">(Article 17)</a> Appropriate steps must be taken to protect against accidental loss, and unauthorized access, use or destruction.</p><h3>Enforcement</h3><p>The E.U. data directive requires the creation of a <a
href="http://aspe.hhs.gov/DATACNCL/eudirect.htm%23ART28">National Data Protection Authority f</a>or all member states. This supervisory authority must regulate and implement data protection laws within its country as well as investigate privacy violations.<a
href="http://aspe.hhs.gov/DATACNCL/eudirect.htm%23ART18"> Every data controller must register with a supervisory authority before processing personal data. </a></p><h3><a
href="http://en.wikipedia.org/wiki/Data_Protection_Directive%23Transfer_of_personal_data_to_third_countries">Onward Transfer</a></h3><p>In order to protect personal data when transferred to countries outside the European Union, <a
href="http://aspe.hhs.gov/DATACNCL/eudirect.htm%23ART25">the Data Protection Directive prohibits onward transfer to entities in non-member states</a> unless they meet an equivalent level of protection. Agreements like <a
href="http://www.export.gov/safeharbor/">Safe Harbor between the United States and the E.U.</a> allow businesses to participate in a program that allows unrestricted international data flow as long as a businesses institutes similar privacy principles to those of the E.U.</p><p>The Data Protection Directive also has special regulations for the transfer of <a
href="http://ec.europa.eu/youreurope/nav/en/citizens/services/eu-guide/data-protection/index_en.html%2311464_8">sensitive data</a> such as racial or ethnic origins, political or religious beliefs, sexual orientation, trade union membership and other similar characteristics. <a
href="http://aspe.hhs.gov/DATACNCL/eudirect.htm%23ART8">The E.U. requires explicit, affirmative consent from a data subject</a> in order to disclose sensitive information to third parties, not matter whether the third party is within or outside the European Union.</p><h3>Privacy and Electronic Communications Directive</h3><p>In 2003, the <a
href="http://en.wikipedia.org/wiki/Directive_on_Privacy_and_Electronic_Communications">Directive on Privacy and Electronic Communications Directive</a> (<a
href="http://www.opsi.gov.uk/si/si2003/20032426.htm">2002/58</a>)was developed to complement the Data Protection Directive. It deals specifically with data protection and with regard to marketing messages and the growing use of digital technology and electronic communications. <a
href="http://www.ico.gov.uk/what_we_cover/privacy_and_electronic_communications/the_basics.aspx">The Privacy and Electronic Communications Directive requires explicit consent from a data subject to send marketing messages unless all of the following criteria are met:</a></p><p>1)  The provider already has information on the data subject on file from a previous service or transaction</p><p>2)  The marketing message is in relation to similar services or products</p><p>3)  The data subject is given the opportunity to opt-out of further marketing messages.</p><p>The E-Privacy Directive also places restrictions on the use of marketing messages through telemarketing, automated telephone calls and faxes. The directive also requires a mechanism to <a
href="http://en.wikipedia.org/wiki/Directive_on_Privacy_and_Electronic_Communications%23Cookies">opt-out of the use and receipt of cookies</a>.</p><h2>Data Protection in Canada</h2><p>Canada is one of the countries closest to the European Union in terms of comprehensive  information privacy law. It uses a coregulatory framework between the government and the privacy sector to enforce data protection.</p><h3><a
href="http://en.wikipedia.org/wiki/Privacy_Act_%2528Canada%2529">The Privacy Act of 1983</a></h3><p><a
href="http://laws.justice.gc.ca/en/P-21/index.html">The Privacy Act of 1983 regulates the use of personal information by the Canadian Federal Government.</a> The Privacy Act requires:</p><ul><li> Notice– the data subject must be notified of the information collected and its uses</li><li>Access– a data subject has the right to view what personal information is held by a government institution and rectify erroneous information</li><li>Consent–  data subject must provide explicit consent before information is disclosed to parties outside the control of a government institution (with a few exceptions)</li><li>Limited Use– collected information must directly relate to the activities of a government program and may only be used for the purposes it was originally collected (with a few exceptions)</li><li>Enforcement– <a
href="http://en.wikipedia.org/wiki/Privacy_Commissioner_of_Canada">the Privacy Commissioner of Canada</a> must investigate and complaints it receives regarding privacy violations to data subjects.</li></ul><h3><a
href="http://en.wikipedia.org/wiki/PIPEDA">The Personal Information Protection and Electronic Documents Act</a></h3><p><a
href="http://laws.justice.gc.ca/en/P-8.6/FullText.html">PIPEDA</a> deals with information privacy in the private sector of Canada which includes financial and health institutions. It protects all information that may identify an individual used in the course of rendering commercial services including those of nonprofit organizations.</p><p><a
href="http://www.media-awareness.ca/english/resources/educational/handouts/privacy/csa_privacy_code_guide.cfm"> PIPEDA incorporates the ten privacy principles outlined by the Canadian Standards Association</a> which include: Accountability, Identifying Purposes, Consent, Limiting collection, Limiting use, disclosure and retention, Accuracy, Safeguards, Openness, Individual Access, Challenging compliance. PIPEDA requires explicit consent from individuals in order to use, process or disclose their personal information (with a few exceptions)</p><p>PIPEDA is enforced through the<a
href="http://www.priv.gc.ca/aboutUs/mm_e.cfm%23contenttop"> Office of the Privacy Commissioner of Canada</a> or similar territorial privacy commissioners. The Commissioner is required, by PIPEDA, to investigate any privacy complaints lodged against a commercial institution and create a report of their findings.The report is sent to the organization against whom the complaint was filed with recommendations. The report is also returned to the complainant who can then pursue the matter further in the Federal Courts.</p><h2>Data Protection in Asia</h2><p>Data Protection across Asia is varied depending on the development and political beliefs of each country, however even counties that grant the least amount of protection have shown a concern for Data Protection and the way it affects the free flow of information.</p><p><a
href="http://www.jonesday.com/pubs/pubs_detail.aspx?pubID=S2920">Japan and the Law Concerning the Protection of Personal Information</a></p><p>Data Protection in Japan is covered under the <a
href="http://www5.cao.go.jp/seikatsu/kojin/foreign/act.pdf">Law Concerning the Protection of Personal Information</a>. It was put into effect in 2005. Enforcement is regulated by ministries of each industry sector (i.e.: Ministry of Health enforces the Law in the Health industry) Each industry may place additional restrictions on the use of personal information.</p><p>Like many data protection laws, Japan’s Law requires specific and limited use of information, adequate data security and integrity, data subject notice of purpose of use, as well as access to and correction of information held by an institution. One major different in Japan’s Law is in their policies regarding disclosure. Explicit consent is required for all disclosure of information to third parties, even if the third party is affiliated with the data controlling entity.</p><h3>The Asia-Pacific Economic Cooperation</h3><p>APEC is a non-binding cooperative agreement between countries along the coast of the Pacific to facilitate regional trade. In 2004, APEC developed a Privacy Framework, recognizing the need for strong data protection laws to allow multinational and international business and trade to continue. <a
href="http://www.apec.org/apec/member_economies.html">Members of APEC</a> include: Australia, Canada, Chile, China, Japan, Peru, Russia, the United States, as well as others.</p><p><a
href="http://epic.org/redirect/apf12407.html">APEC’s Privacy Framework outlines 9 privacy principles:</a></p><p>1)  Preventing Harm– Above all privacy regulations should prevent harm to data subjects from the unauthorized or misuse collection, use or disclosure of personal information.</p><p>2)  Notice– An individual should be notified regarding the personal information including what, why, how and to whom their information is collected, used or disclosed. They must also be given the choice and means to limit the use and disclosure of their information</p><p>3)  Collection Limitation– Collected information should be used for specific and limited purposes.</p><p>4)  Uses of Personal Information–Person Information should be collected with consent of the data subject and when necessary to render a service or transaction</p><p>5)  Choice– Individuals must be provided with unambiguous mechanisms to control the collection, use and disclosure of their personal information.</p><p>6)  Integrity of Personal Information– Personal Information should be complete, timely and accurate</p><p>7)  Security Safeguards–Safeguards should be created to protect against data loss as well as unauthorized, access, use, disclosure, destruction and other misuses.</p><p>8)  Access and Correction– Individuals must be able to obtain the personal information a data controller may hold about them in a timely and reasonable manner and be allowed to challenge the accuracy of the information.</p><p>9)  Accountability– Entities controlling personal information must be accountable for complying with privacy principles.</p><p>APEC is non-binding which means that there is no single supervisory authority for enforcing compliance in member states. Each member state is responsible for creating and enforcing their own information privacy regulations that adhere to the APEC Privacy Framework.</p><h2>Data Protection in Latin America</h2><p>Like, Asia, data protection in Latin America is inconsistent. However, many Latin American countries along the Pacific are members of APEC and comply with the APEC Privacy Framework. Furthermore, many countries have included some forms of data protection in their constitutions under the writ of Habeas Data</p><h3><a
href="http://en.wikipedia.org/wiki/Habeas_Data">Habeas Data</a></h3><p>Habeas Data literally translates to “[we command] you have the data.” It protects the right of an individual file complaints to a constitutional court regarding violations to their image, honor, privacy, and freedom of information. Legally this has translated to information privacy regulations for the government. Often similar regulations have been extended to the private sector. Habeas Data requires that an individual be able to view information on record about their person and correct any false information. Furthermore it holds a data controlling entity accountable for the integrity of data. <a
href="http://en.wikipedia.org/wiki/Habeas_Data%23Implementation">The 1988 Brazilian Constitution was the first to include the writ of Habeas Data.</a></p><h3>Argentina</h3><p>Argentina is the only Latin American country considered <a
href="http://ec.europa.eu/justice_home/fsj/privacy/thridcountries/index_en.htm">adequate under the E.U. Data Protection Directive. </a> The Argentine Constitution contains the writ of Habeas Data. In 2000, a comprehensive data protection law called the <a
href="http://www.habeasdata.org/Data-Protection-Act-Argentina-Law-25326">Personal Data Protection Act</a> was implemented to protect personal data in both the public and private sector.</p><p>Under the Act, data must be collected for “certain, appropriate, pertinent and not excessive” purposes and must be collected lawfully. Data must be accurate, complete, secure and destroyed once it is no longer necessary for the purposes it was originally collected. Furthermore any activities surrounding personal data must receive explicit consent from the individual with a few specific exceptions <a
href="http://www.habeasdata.org/Data-Protection-Act-Argentina-Law-25326">(section 5)</a>.</p><p>The Act also prohibits the creation of files linking sensitive data with identifiable individuals and requires that no person may be compelled to share sensitive data. Much like the E.U. Data protection directive, the Act requires other countries to have adequate levels of protection before transferring data.</p><h3>Chile</h3><p>In 1999, Chile was the first Latin American country to implement a data protection law.  Chile uses a comprehensive law called <a
href="http://www.ibls.com/internet_law_news_portal_view.aspx?s=latestnews&amp;id=2140">The Law for the Protection of Private Life</a> to govern the public and private sectors. While the Law guarantees the rights of a data subject’s to access, correction, notice, and judicial control,<a
href="http://www.privacyinternational.org/survey/phr2003/countries/chile.htm"> there is no supervisory authority and compliance is largely self enforced. </a>Furthermore, the Law provides no protection for international transfers.</p><h3>Paraguay</h3><p>Paraguay includes Habeas Data in <a
href="http://servat.unibe.ch/icl/pa00000_.html%23A135_">Article 135</a> of its constitutions which states:</p><p>“Everyone may have access to information and data available on himself or assets in official or private registries of a public nature. He is also entitled to know how the information is being used and for what purpose. He may request a competent judge to order the updating, rectification, or destruction of these entries if they are wrong or if they are illegitimately affecting his rights.” Paraguay also has its own privacy law to govern information privacy during the course of commercial business. Additionally it <a
href="http://www.madrid.org/cs/Satellite?c=CM_Revista_FP&amp;cid=1142318581808&amp;esArticulo=true&amp;idRevistaElegida=1142317009940&amp;language=en&amp;pag=1&amp;pagename=RevistaDatosPersonalesIngles%252FPage%252FRDPI_home_RDP&amp;siteName=RevistaDatosPersonalesIngles">protects sensitive data and economic status information</a> by requiring explicit, written consent of the data subject unless it is required by law.</p><h2>In Conclusion</h2><p>As technology progresses and the unrestricted flow of information across borders becomes increasingly important, countries will no longer have the luxury of avoiding data protection. In order to protect the data of their citizens, governments like the E.U. and Argentina require similar levels of protection when they transfer their information to other countries. To allow such trade to continue, countries around the globe must implement privacy policies of their own and consider how they will protect the information of their citizens as well as the personal information they receive through onward transfer. With the growth of electronic technology, information privacy has become an international issue that cannot be ignored.</p><h1>CIPP Candidate Preparation</h1><p>In preparation for the Certified Information Privacy Professional exam, a privacy professional should be comfortable with topics related to this post including:</p><ul><li>Privacy and Data Protection Regulation (Foundations: I.F.b.ii-v.) including Europe, Canada, Asia and South America</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2009/12/06/data-protection-laws-around-the-globe/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Safe Harbor Compliance</title><link>https://www.cippguide.org/2009/11/30/safe-harbor-compliance/</link> <comments>https://www.cippguide.org/2009/11/30/safe-harbor-compliance/#comments</comments> <pubDate>Mon, 30 Nov 2009 12:00:21 +0000</pubDate> <dc:creator>jbrook</dc:creator> <category><![CDATA[CIPP]]></category> <category><![CDATA[Compliance & Regulations]]></category> <category><![CDATA[Privacy]]></category> <category><![CDATA[Consumer Protection]]></category> <category><![CDATA[EU]]></category> <category><![CDATA[European Union Data Protection Directive]]></category> <category><![CDATA[Federal Trade Commission]]></category> <category><![CDATA[FTC]]></category> <category><![CDATA[Safe Harbor]]></category><guid
isPermaLink="false">http://www.cippguide.org/?p=1136</guid> <description><![CDATA[Safe Harbor is an advantageous agreement between the United States and the European Union that governs the protection of data during transfer from the E.U. to the U.S.  American companies wishing to do business with companies in the E.U. may receive certification, stating they have implemented data protection principles that are similar and equal to those of the E.U. Data Protection Directive, and are then allowed unrestricted data transfers with entities in the E.U. Recently, the FTC– the U.S. body governing enforcement of Safe Harbor– has begun to crack down on U.S. companies claiming Safe Harbor compliance, but failing to implement the required protection standards. Multi-national companies must now take a strong look at their privacy policies and notices to ensure they are Safe Harbor compliant and avoid Federal [...]]]></description> <content:encoded><![CDATA[<p>Safe Harbor is an advantageous agreement between the United States and the European Union that governs the protection of data during transfer from the E.U. to the U.S.  American companies wishing to do business with companies in the E.U. may receive certification, stating they have implemented data protection principles that are similar and equal to those of the <a
href="http://en.wikipedia.org/wiki/Data_Protection_Directive">E.U. Data Protection Directive</a>, and are then allowed unrestricted data transfers with entities in the E.U. Recently, the<a
href="http://www.ftc.gov/"> FTC</a>– the U.S. body governing enforcement of Safe Harbor– has begun to crack down on U.S. companies claiming Safe Harbor compliance, but failing to implement the required protection standards. Multi-national companies must now take a strong look at their privacy policies and notices to ensure they are Safe Harbor compliant and avoid Federal scrutiny.</p><p><strong>What is Safe Harbor?</strong></p><p>In 1995, the E.U. implemented a comprehensive law, the <a
href="http://www.cdt.org/privacy/eudirective/EU_Directive_.html">Data Protection Directive</a>, which created strong standards and principles governing the use and protection of data. Any data transferred within the E.U. or the European Economic Area would be protected under the law. However, personal data transferred to other countries would not be guaranteed the same protection. The Data Protection Directive restricts the transfer of data with other countries unless they meet a comparable level of data protection.</p><p>Data protection in the United States, which is more commonly known as information privacy, is governed by a number of sectoral laws that protect data within specific industries, ie: <a
href="http://www.hhs.gov/ocr/privacy/hipaa/understanding/index.html">HIPAA</a> protects personal health information, <a
href="http://en.wikipedia.org/wiki/Fair_and_Accurate_Credit_Transactions_Act">FACTA</a> protects personal information in the financial sector. The U.S. has no central or comprehensive data protection regime and therefore, the E.U. finds data protection in the U.S. to be inadequate.</p><p>To facilitate unrestricted, data transfer between the United States and the European Union, the Safe Harbor agreement was created to allow U.S. companies the opportunity to raise their level of data protection and achieve “adequate” status, thus meeting the restriction rules for onward transfer to third parties under the E.U. Data Directive.</p><p><strong><a
href="http://www.export.gov/safeharbor/eu/eg_main_018476.asp">The Benefits of Safe Harbor Compliance</a></strong></p><p>In 2000, when the Safe Harbor agreement was developed between the E.U. and the U.S., data transfers accounted for over <a
href="http://www.export.gov/safeharbor/eu/eg_main_018474.asp">$ 300 Billion dollars in trade</a>. Safe Harbor allows such exportation and importation of data to continue while still protecting the personal data of European citizens. Though the Safe Harbor agreement requires stricter privacy standards for U.S. companies, than is required by U.S. law it is really to the benefit of both sides that such an agreement exists.</p><p>Participating U.S. companies enjoy the privilege of the Safe Harbor Agreement which demands that all E.U. member states allow unrestricted data transfers with any and all Safe Harbor certified participants. This means that certified companies may not be denied transfers by individual data controllers or Data Protection Authorities according to their own agendas.</p><p>Furthermore, complaints brought against a U.S. entity by European citizens regarding the protection of their personal data are heard in U.S. courts and the Safe Harbor program is under U.S. enforcement.</p><p>Safe Harbor also eliminates the need, or grants automatic approval for, data transfers creating a more cost and time efficient system. Companies may choose not to join the Safe Harbor agreement and make individual agreements or model contracts with a Data Protection Authority, but this may increase the time and energy needed to allow for the unrestricted transfer of data.</p><p><strong><a
href="http://www.export.gov/safeharbor/eu/eg_main_018474.asp">How Does a Company Become Safe Harbor Compliant?</a></strong></p><p>The Safe Harbor program is voluntary. In order to participate, an entity must complete a self certification process annually with the Department of Commerce. To do this a company may join a self regulatory privacy program such as the <a
href="http://www.bbb.org/us/european-union-dispute-resolution/">BBB online</a>, which audits companies to review their privacy policies and business operations to provide certificates of compliance with Safe Harbor. Or an entity may choose to create their own self-regulatory privacy policy which adheres to all Safe Harbor principles. Furthermore, the entity must publicly state in their privacy notice that they are Safe Harbor compliant.</p><p><strong><a
href="http://en.wikipedia.org/wiki/Safe_harbor">The Safe Harbor Principles</a></strong></p><p>The following principles must be included in a <strong><a
href="http://www.export.gov/safeharbor/eu/eg_main_018474.asp">Safe Harbor compliant privacy policy</a></strong>.</p><p><em>Notice</em></p><ul><li>The data subject must be notified about the purposes for which personal information is collected and used.</li><li>The data subject must be notified about contact methods to file inquiries and complaints.</li><li>The data subject must be notified about the types of third parties to whom personal information may be disclosed.</li><li>The data subject must be provided with their choices and means of limiting disclosure of their personal data.</li><li>Notice should be provided at the time when information is first collected or shortly thereafter and must be provided before data is processed or disclosed.</li></ul><p><em>Choice</em></p><ul><li>The data subject must be able to opt-out of third party disclosures.</li><li>The data subject must be able to opt-out of secondary usage of information.</li><li>The data subject must give affirmative consent (opt-in) for the disclosure or use of <strong><a
href="http://ec.europa.eu/youreurope/nav/en/citizens/services/eu-guide/data-protection/index_en.html%2311464_8">sensitive information</a></strong>.</li></ul><p><em>Onward Transfer</em></p><ul><li>All third parties to whom data may be transferred must follow the Safe Harbor principles or Data Directive compliant. The same level of protection must be guaranteed no matter how many times data is transferred.</li></ul><p><em>Security</em></p><ul><li>Entities that process data in any stage of its life cycle (collection, use, analysis, storage) must take reasonable measures to protect against data loss, destruction, misuse and unauthorized access.</li></ul><p><em>Data Integrity</em></p><ul><li>Data may only be processed or used as it is related and proportional to the purposes for which it was originally collected.</li><li>An entity should take reasonable steps to ensure data is accurate, timely and complete.</li></ul><p><em>Access</em></p><ul><li>Data subjects must be able to view the information an organization holds about them.</li><li>Data subjects must be able to correct, add to, or delete inaccurate information.</li></ul><p><em>Enforcement</em></p><ul><li>A recourse mechanism must be in place for data subjects to file complaints, have disputes investigated, and resolved.</li><li>An entity must have a mechanism to verify that the stated privacy policy and business operations are compliant with the Safe Harbor agreement. Audits should be completed annually.</li><li>It is the obligation and responsibility of the entity to remedy any problems with compliance in a timely fashion.</li></ul><p><strong><em><a
href="http://www.export.gov/safeharbor/eu/eg_main_018481.asp">Enforcing Safe Harbor</a></em></strong></p><p><strong> </strong></p><p>U.S. compliance with Safe Harbor is largely self regulated. Entities may choose to complete self verification of compliance and investigate complaints internally. Companies also have the option of using private, third party dispute resolution mechanisms, that have gained a reputation of trustworthiness to verify their compliance and investigate disputes.</p><p>Some well known, third party dispute resolution service providers include:</p><ul><li><em><a
href="http://www.bbb.org/us/Dispute-Resolution-Services/">The Better Business Bureau Online</a></em></li><li><em><a
href="http://www.the-dma.org/services/MediationArbitrationService.shtml">The Direct Marketing Association</a></em></li><li><em><a
href="http://www.esrb.org/privacy/privacy_enforcement.jsp">The Entertainment Software Rating Board</a></em></li></ul><p><strong> </strong></p><p>Third party dispute resolution providers are self regulated and not certified by the Department of Commerce or the FTC. Therefore, it is the legal responsibility of the entity to choose a program that is Safe Harbor compliant.</p><p>Though, Safe Harbor has not been strictly enforced in the past, there are regulations within the privacy and trade law to punish violators. <a
href="http://www.export.gov/safeharbor/eu/eg_main_018476.asp">Misuse of the Safe Harbor agreement can qualify as “unfair or deceptive trade practices” under Section 5 of the Federal Trade Commission Act</a>. The FTC may take action against offenders including conducting formal hearings, and issuing cease and desist or temporary restraining orders. Failing to comply with an FTC order may carry a penalty of up to $11,000 for every day of continued violation and any entity that knowingly violates an FTC rule may be subject to the same penalty.</p><p><strong>Safe Harbor in the News</strong></p><p>Historically, the FTC has done very little to enforce Safe Harbor compliance. However, that has begun to change. <strong><em><a
href="http://privacylaw.proskauer.com/2009/09/articles/european-union/ftc-enforces-useu-safe-harbor-program-for-first-time/">In August 2009, the FTC publicly announced a suit against a California based company, Balls of Kryptonite,</a> </em></strong>which purposely misled UK consumers to believe it was an E.U. company by using a .co.uk domain address. Furthermore, the company stated in its privacy policy that it was Safe Harbor compliant though no certification had ever been filed.</p><p><strong><em><a
href="http://privacylaw.proskauer.com/2009/10/articles/european-union/ftc-continues-safe-harbor-enforcement-streak-with-six-new-proposed-settlements/">Then, in October 2009, the FTC filed settlement complaints against six multinational companies</a></em></strong> that had lapsed in their compliance but failed to alter their privacy policies to notify data subjects of the change. The recent enforcement has sent the message to business owners that the FTC may no longer rely on private, self-regulation to provide adequate enforcement. Since Safe Harbor compliance requires a public statement in privacy notices stating participation in the program, the FTC needs only to compare their current list of Safe Harbor participants with the privacy notice of an entity to gain evidence of unfair or deceptive trade practices. <strong><em><a
href="http://privacyblog.littler.com/2009/10/articles/data-security/multinationals-certified-to-the-useu-safe-harbor-agreement-beware-the-federal-trade-commission-has-bared-its-enforcement-teeth/">There is also speculation that the audits may be conducted in the future</a></em></strong> for companies with current certifications, to verify full compliance with all Safe Harbor regulations. <strong><em> </em></strong></p><p>Data protection, especially with regard to onward transfer, continues to remain a significant issue in International politics. <a
href="http://www.dhs.gov/journal/leadership/2009/11/us-and-eu-agree-on-data-protection.html">In the first week of November 2009, the United States and European Union</a>, recognizing the weaknesses in current regulation, joined together to create a common set of principles to govern the transfer of personal data. <a
href="http://www.google.com/hostednews/afp/article/ALeqM5gC_3suiQ5PQX2Quq6BtyeNYRpTpw">That same week, privacy representatives from around the world met in Madrid </a>for the International Data Protection and Privacy to create a universal standard of privacy and data protection, in the hopes of eventually creating a universal data protection law.</p><p><strong>In Conclusion:</strong></p><p>Companies wishing to conduct legal and successful business on a multinational level must be concerned with the protection of data both when it is transferred to and from the United States. Agreements, like Safe Harbor, allow the United States and the European Union to continue a mutually beneficial trade relationship, however, the agreement alone does not guarantee data protection. Participating U.S. companies need to ensure Safe Harbor compliance to build trust in their organization, as well as in the program to allow such agreements to continue in the future, despite the differing approaches the U.S. and the E.U. take regarding data protection.</p><p><strong><em>CIPP Candidate Preparation</em></strong></p><p><strong><em> </em></strong></p><p>In preparation for the Certified Information Privacy Professional exam, a privacy professional should be comfortable with topics related to this post including:</p><ul><li>The Collective View of Privacy Principles (Foundations I.E) including Notice, Consent, Access, Security, and Quality</li><li>Privacy and Data Protection Regulation (Foundations: I.F) including Onward Transfer, Safe Harbor, and the E.U. Data Protection Directive</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2009/11/30/safe-harbor-compliance/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced

Served from: www.cippguide.org @ 2012-02-09 06:50:17 -->
