<?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; Safe Harbor</title> <atom:link href="http://www.cippguide.org/tag/safe-harbor/feed/" rel="self" type="application/rss+xml" /><link>https://www.cippguide.org</link> <description>Your Guide to the CIPP</description> <lastBuildDate>Sat, 11 Feb 2012 07:47:27 +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>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>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_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/2010/12/14/do-i-need-to-apply-for-safe-harbor/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>COPPA: The Children&#039;s Online Privacy Protection Act</title><link>https://www.cippguide.org/2010/01/11/coppa-the-childrens-online-privacy-protection-act/</link> <comments>https://www.cippguide.org/2010/01/11/coppa-the-childrens-online-privacy-protection-act/#comments</comments> <pubDate>Mon, 11 Jan 2010 12:00:34 +0000</pubDate> <dc:creator>jbrook</dc:creator> <category><![CDATA[CIPP]]></category> <category><![CDATA[Compliance & Regulations]]></category> <category><![CDATA[Privacy]]></category> <category><![CDATA[Attorney General]]></category> <category><![CDATA[COPPA]]></category> <category><![CDATA[FTC]]></category> <category><![CDATA[Parental Consent]]></category> <category><![CDATA[privacy policy]]></category> <category><![CDATA[Safe Harbor]]></category> <category><![CDATA[SEC.1305]]></category><guid
isPermaLink="false">http://www.cippguide.org/?p=1190</guid> <description><![CDATA[The Children’s Online Privacy Protection Act was passed in 1998 by the FTC to protect the personal information of children. It specifically applies to websites that target children and provides guidelines for the collection, use and disclosure of personally identifiable information of children under the age of 13 who may not understand the dangers of disclosing personal information on the [...]]]></description> <content:encoded><![CDATA[<p>The Children’s Online Privacy Protection Act was passed in 1998 by the FTC to protect the personal information of children. It specifically applies to websites that target children and provides guidelines for the collection, use and disclosure of personally identifiable information of children under the age of 13 who may not understand the dangers of disclosing personal information on the Internet.</p><p><a
href="http://www.ftc.gov/privacy/privacyinitiatives/childrens.html">A website operator must be concerned with COPPA compliance if:</a></p><ul><li>The website targets children under the age of 13 through its subject matter, audio/visual content, advertising or use of other child-oriented features.</li><li>The website targets a general audience but has a separate child oriented section.</li><li>The website targets a general audience and children under the age of 13 are known to access the site.</li><li>The website is maintained outside the U.S. but targets children under the age of 13 in the U.S.</li><li>The website is operated by the Federal Government. Under the Office of Management and Budget, <a
href="http://www.whitehouse.gov/omb/memoranda_m00-13/">the U.S. Federal Government is required to comply with COPPA</a> on all of its websites targeting children</li></ul><p><a
href="http://www.coppa.org/comply.htm">COPPA Compliance</a></p><p>COPPA primarily uses the fair information practice principles of Notice and <a
href="../../../../../2009/12/21/choice-and-consent/">Consent</a> to protect children’s information.</p><p>In order to comply with COPPA, a website operator must:</p><p>1.  Provide parents with information about the website’s information collection and privacy practices. A privacy policy must be placed on the home page and on every page where data is collected in order to ensure adequate notice</p><p>2.  Obtain verifiable parental consent prior to collecting personal information</p><p>3.  Provide parents with a mechanism to access the information on record for their child and the ability to change consent options for future or third party use and disclosure</p><p>4.  Participation on the website may not be limited by requiring the collection of information that is not reasonably necessary</p><p>A COPPA compliant privacy notice must include:</p><ol><li>Legitimate contact information for the website operator/data owner</li><li>The type of information that is collected</li><li>How the information will be use</li><li>Notice of any third party disclosure</li></ol><p><a
href="http://www.ftc.gov/privacy/coppafaqs.shtm">Verifiable Parental Consent:</a></p><p>Depending on the information that is being collected and its intended use, different levels of parental consent must be obtained.</p><p><span
style="text-decoration: underline;"><a
href="http://www.coppa.org/comply.htm">Prior parental consent is not required to collect a child’s <em>name and email address only</em> if:</a></span></p><ul><li>The information is obtained in order to provide notice to the parent or obtain parental consent</li><li>The information is collected to respond once to a specific inquiry by the child and not used for further communications</li><li>The information is used to ensure the safety of a child and is not used for any other purposes</li><li>The information is used to protect the security of the website, protect against liability, participate in a law enforcement investigation or any other matters relating to public safety</li></ul><p>In all cases, parental consent should be obtained shortly after the information is collected. If parental consent cannot be obtained, the information may not be used for purposes other than those outlined above and the information must be deleted (with exceptions for ensuring the safety of the child)</p><p><span
style="text-decoration: underline;"><a
href="http://www.coppa.org/comply.htm">Parental Consent for Public Disclosure</a></span></p><p>If the website publicly links a child’s name or email address with their screen name in chat rooms, message boards, personal home pages, pen pal services or other similar social networking features they must obtain verifiable parental consent of public disclosure. This also applies to site which may disclose personal information to third parties for secondary uses and marketing purposes.</p><p>Consent options include:</p><ul><li>A printable form that can be signed then mailed or faxed back to the website operator</li><li>Obtain a parent’s credit card information in connection with a transaction which may include subscription fees, purchases or a credit card processing fee.</li><li>Provide a toll free line staffed by professionals to which parents may call and provide verbal consent</li><li>Obtain consent through an email that contains a digital signature that uses a public key that has been verified by one of the above methods.</li></ul><p><span
style="text-decoration: underline;"><a
href="http://www.coppa.org/comply.htm">Parental Consent for Internal Use</a><em> </em></span></p><p>If the website does not publicly disclose the child’s information either through disclosure to third parties or through the posting of information to chat rooms, message boards or similar features then the information will only be used within the site to contact the child.</p><p>Consent options include:<em> </em></p><ul><li>Any of the methods used for public disclosure<em> </em></li><li>The Email Plus option in which:<ul><li>An initial email is sent containing the privacy notice and asking the parent to respond with a phone, fax or mailing address to confirm consent through one of those methods; or</li><li>After a reasonable length of time has passed, a second email is sent asking for the parent to confirm consent. The privacy notice should again be included. This email informs the parent that their consent is implicit through their lack of response. The email should provide the the parent with information on how to revoke their consent.</li></ul></li></ul><p><a
href="http://www.ftc.gov/privacy/privacyinitiatives/childrens_enf.html"></a></p><p><a
href="http://www.ftc.gov/privacy/privacyinitiatives/childrens_enf.html">Enforcement of COPPA</a></p><p>COPPA is enforced by the Federal Trade Commission and through the a state’s Attorney General’s Office under SEC. 1305. COPPA allows for the creation of Safe Harbor programs which encourages industry self regulations.</p><p>There are several <a
href="../../../../../2009/12/28/online-assurance-programs/">online assurance programs</a> that offer a COPPA compliant Safe Harbor Program including:</p><ul><li><a
href="http://www.truste.com/privacy_seals_and_services/enterprise_privacy/childrens-online-privacy-seal.html">TRUSTe</a></li><li><a
href="http://www.caru.org/index.aspx">The Children’s Advertising Review Unit</a></li><li><a
href="http://www.esrb.org/privacy/">The Entertainment Software Rating Board</a></li></ul><p>Unlike other information privacy laws, the FTC has been diligent in enforcing COPPA. It has a <a
href="http://www.ftc.gov/privacy/privacyinitiatives/childrens_enf.html/">history of investigating privacy complaints</a> and taking action against website and companies violating the rule.</p><h2>Summary</h2><p>COPPA protects the privacy of personal information for children. It does not prevent children from accessing mature content. COPPA uses parental notice and consent to prevent the wrongful collection and misuse of children’t personal information. Any website that may be frequented by children under the age of 13, must comply with the COPPA ruling if personal information is collected.</p><h2><em>CIPP/G Candidate Preparation</em></h2><p>In preparation for the Certified Information Privacy Professional Government exam, a privacy professional should be comfortable with topics related to this post including:</p><ul><li>U.S. Public and Private Sector General Laws including COPPA (I.B.a.ii.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2010/01/11/coppa-the-childrens-online-privacy-protection-act/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> <item><title>EU begins legal action against UK over privacy</title><link>https://www.cippguide.org/2009/04/16/eu-begins-legal-action-against-uk-over-privacy/</link> <comments>https://www.cippguide.org/2009/04/16/eu-begins-legal-action-against-uk-over-privacy/#comments</comments> <pubDate>Thu, 16 Apr 2009 22:56:29 +0000</pubDate> <dc:creator>jbrook</dc:creator> <category><![CDATA[CIPP]]></category> <category><![CDATA[Compliance & Regulations]]></category> <category><![CDATA[Privacy]]></category> <category><![CDATA[Behavioral Advertising]]></category> <category><![CDATA[Britain]]></category> <category><![CDATA[EU]]></category> <category><![CDATA[European Union Data Protection Directive]]></category> <category><![CDATA[Federal Trade Commission]]></category> <category><![CDATA[Information Privacy]]></category> <category><![CDATA[ISP]]></category> <category><![CDATA[phorm]]></category> <category><![CDATA[PII]]></category> <category><![CDATA[Safe Harbor]]></category> <category><![CDATA[Surveillance]]></category> <category><![CDATA[UK]]></category> <category><![CDATA[United Kingdom]]></category><guid
isPermaLink="false">http://blog.cippguide.org/?p=316</guid> <description><![CDATA[The Europeans value privacy; it is a fundamental human right in their eyes.  The European Commission began legal action against the United Kingdom Tuesday for failure to “ensure, among other things, the confidentiality of communications by prohibiting interception and surveillance without the user's [...]]]></description> <content:encoded><![CDATA[<p>The Europeans value privacy; it is a fundamental human right in their eyes.  Every country which forms the European Union joined <a
title="Stipulations for joining the European Union" href="http://ec.europa.eu/enlargement/the-policy/index_en.htm" target="_blank">agreeing to several stipulations</a>. One of those surrounds human rights and privacy, and is a very popular topic for a CIPP. <a
title="European Union Data Protection Directive" href="http://www.cdt.org/privacy/eudirective/EU_Directive_.html" target="_blank">The European Union’s Data Protection Directive 95/46/EC</a> constitutes a comprehensive privacy model, promoting an EU citizen’s data privacy regardless of who holds it, for what reasons or uses, or when it was collected.  In particular, Article 7 of the Directive asserts:</p><blockquote><p>Member States shall provide that personal data may be processed only if:</p><ul><li> (a) the data subject has <strong>unambiguously given his consent</strong>; or</li><li>(b) processing is necessary for the <strong>performance of a contract</strong> to which the data subject is party or in order to take steps at the request of the data subject prior to entering into a contract; or</li><li>(c) processing is necessary for <strong>compliance with a legal obligation</strong> to which the controller is subject; or</li><li>(d) processing is necessary in order to <strong>protect the vital interests</strong> of the data subject; or</li><li>(e) processing is necessary for the performance of a task carried out in the <strong>public interest</strong> or in the exercise of <strong>official authority</strong> vested in the controller or in a third party to whom the data are disclosed; or</li><li>(f) processing is necessary for the purposes of the <strong>legitimate interests</strong> pursued by the controller or by the third party or parties to whom the data are disclosed, except where such interests are overridden by the interests for fundamental rights and freedoms of the data subject which require protection under Article 1 (1).</li></ul></blockquote><p>This treatment of personal information held quite a bit of headache for multi-national companies with sensitive HR data or customer relationship information.  These problems were eventually ironed out between the EU and the US Department of Commerce through the <a
title="US EU Safe Harbor Program Allows cross border private information sharing" href="http://www.export.gov/safeharbor/SH_Overview.asp" target="_blank">passage of the Safe Harbor program in 2000</a>.  The Center for Democracy and Technology gives a tidy <a
title="Center for Democracy and Technology: The European Union Data Protection Directive " href="http://www.cdt.org/privacy/eudirective/" target="_blank">summary of the Directive and international responses</a>.</p><p>Intra-EU privacy was supposed to be quite well understood.  Except by the British it appears. <a
title="Wikipedia - European Commission" href="http://en.wikipedia.org/wiki/European_Commission" target="_blank">The European Commission</a> began legal action against the United Kingdom Tuesday for failure to “ensure, among other things, the confidentiality of communications by prohibiting interception and surveillance without the user&#8217;s consent.”  In other words, not following Article 7.  To be fair, the 27 EU Members have had 90 cases of some sort of action brought against them, so the British are not in the minority.</p><p>The action, says EU Telecoms Commissioner Viviane Reding, relates to behavioral advertising company <a
title="Wikipedia - Phorm, behavioral advertising and surveillance" href="http://en.wikipedia.org/wiki/Phorm" target="_blank">Phorm</a>, and <a
title="New York Times: British ISPs use Phorm and violate privacy" href="http://www.nytimes.com/2008/02/18/technology/18target.html?_r=1&amp;ex=1360990800&amp;en=107e2b605f53cc6d&amp;ei=5090&amp;partner=rssuserland&amp;emc=rss" target="_blank">Internet Service Providers (ISPs) usage of the technology</a>.  Apparently, British Internet users complained about interception and surveillance of their surfing habits.  <a
title="FTC Behavioral Advertising Guidelines" href="http://blog.cippguide.org/2009/02/18/ftc-issues-behavioral-advertising-guidelines/" target="_blank">The Federal Trade Commission brought similar behavioral US marketing problems to light in February.</a></p><blockquote><p>&#8220;Technologies like Internet behavioural advertising can be useful for businesses and consumers but they must be used in a way that complies with EU rules,&#8221; Reding said in a statement.  &#8220;We have been following the Phorm case for some time and have concluded that there are problems in the way the UK has implemented parts of the EU rules on the confidentiality of communications.&#8221;</p></blockquote><p>For the United Kingdom, there has to be some question of sovereignty mixed in with the privacy lapses.  EU Member States “cede part of their sovereignty under <a
title="Treaties forming the European Union" href="http://eur-lex.europa.eu/en/treaties/index.htm" target="_blank">treaties</a> which empower the EU institutions to adopt laws”.  If Britain fails to come in line with the privacy protections from the Directive, Reding has the <a
title="European Commission privacy infringement powers" href="http://ec.europa.eu/information_society/policy/ecomm/implementation_enforcement/infringement/index_en.htm" target="_blank">power to force the country to appear before the EU’s highest court, the European Court of Justice.</a> The Court of Justice can thereby force Britain’s compliance.</p> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2009/04/16/eu-begins-legal-action-against-uk-over-privacy/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-11 04:06:10 -->
