<?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; FTC</title>
	<atom:link href="http://www.cippguide.org/tag/ftc/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cippguide.org</link>
	<description>Your Guide to the CIPP</description>
	<lastBuildDate>Tue, 27 Jul 2010 12:00:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Identity Theft Task Force Recommendations</title>
		<link>http://www.cippguide.org/2010/04/13/identity-theft-task-force-recommendations/</link>
		<comments>http://www.cippguide.org/2010/04/13/identity-theft-task-force-recommendations/#comments</comments>
		<pubDate>Tue, 13 Apr 2010 12:00:56 +0000</pubDate>
		<dc:creator>jbrook</dc:creator>
				<category><![CDATA[CIPP]]></category>
		<category><![CDATA[Compliance & Regulations]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[biometrics]]></category>
		<category><![CDATA[CIPP/G]]></category>
		<category><![CDATA[Combatting ID Theft]]></category>
		<category><![CDATA[Department of Homeland Security]]></category>
		<category><![CDATA[DHS]]></category>
		<category><![CDATA[Executive Order]]></category>
		<category><![CDATA[Federal Trade Commission]]></category>
		<category><![CDATA[FTC]]></category>
		<category><![CDATA[Identity Theft Task Force]]></category>
		<category><![CDATA[OMB]]></category>
		<category><![CDATA[Privacy Act]]></category>
		<category><![CDATA[Social Security Number]]></category>
		<category><![CDATA[SSN]]></category>

		<guid isPermaLink="false">http://www.cippguide.org/?p=1441</guid>
		<description><![CDATA[In May 2006, an Executive Order of the President created the Identity Theft Task Force. The Task Force includes members of several Federal agencies and departments. In September 2006, the Task Force released a number of recommendations ahead of the May 2007 document “Combatting ID Theft: Strategic Plan” in order to help agencies get a head start on the growing problem of identity [...]]]></description>
			<content:encoded><![CDATA[<p>In May 2006, an Executive Order of the President created the <a href="http://www.idtheft.gov/">Identity Theft Task Force</a>. The Task Force includes members of several Federal agencies and departments. In September 2006, the Task Force released a number of recommendations ahead of the May 2007 document “<a href="http://www.idtheft.gov/reports/StrategicPlan.pdf">Combatting ID Theft: Strategic Plan</a>” in order to help agencies get a head start on the growing problem of identity theft.</p>
<p>The memorandum issued the following recommendations:</p>
<p><strong>Data Breach Guidance to Agencies</strong></p>
<p>The Office of Management and Budget should issue a memorandum guiding agencies on when and how notice must be given to individuals at risk for identity theft due to a security breach. The suggested memorandum, titled “<a href="http://www.whitehouse.gov/OMB/memoranda/.../task_force_theft_memo.pdf">Recommendations for Identity Theft Related Data Breach Notification</a>” was released almost concurrently with the Task Force’s memorandum.</p>
<p><strong>Development of Universal Police Report for Identity Theft Victims</strong></p>
<p>Identity theft victims my require official police reports to contest fraudulent information on their credit reports. A universal identity theft police report ensures that all necessary information is collected. It also allows identity theft victims to print the report from online, fill it out and bring it to their local enforcement agency for verification. Currently, individuals may also <strong><a href="http://www.ftc.gov/bcp/edu/microsites/idtheft/consumers/filing-a-report.html">file an official complaint</a></strong> with the Federal Trade Commission on the FTC website. A universal form of filing complaints, reduces the strain on law enforcement agencies and  allows streamlining of investigations.</p>
<p><strong>Extending Restitution for Victims of Identity Theft</strong></p>
<p>The Task Force recommended to Congress that defendants be required to pay their identity theft victims monetarily for the time lost due to investigating, responding to and correcting fraudulent activity on their credit reports. This created extra penalties for committing identity theft, as well as allowed some renumeration to be paid to identity theft victims for their troubles, in addition to settling any financial disputes related to the fraudulent activity.</p>
<p><strong>Reducing Access of Identity Thieves to Social Security Numbers</strong></p>
<p>All agencies in the public sector should limit the use of Social Security Numbers as an individuals main identifier in an information system. The Office of Personnel Management was instructed to assign employee identification numbers for common use to <strong><a href="http://www.cippguide.org/2010/03/29/guidance-on-protecting-federal-employee-social-security-numbers-and-combating-identify-theft/">eliminate the widespread use of SSN as the primary identifier for government employees</a></strong>. The OPM was also instructed to develop policies for the appropriate use and protection of Social Security Numbers. Further more all agencies were asked to review their use of SSNs in physical and electronic records systems to eliminate and restrict its usage where possible.</p>
<p><strong>Developing Alternative Methods of Authentication Identities</strong></p>
<p>The Task Force recommended that agencies confer with privacy and security experts in the private sector to create and implement technologies that use identifiers such as biometrics to authenticate identity. Biometric identifiers are harder for identity thieves to replicate or abuse. Using biometric identifiers in order to access personally identifiable information would significantly increase the protection to sensitive data.</p>
<p><strong>Improving Data Security in the Government</strong></p>
<p>The Task Force asked that the Office of Management and Budget and the Department of Homeland Security work together to investigate privacy practices in the Federal government and develop a list of the top mistakes that affect an agency’s ability to adequately protect data. This document was published in 2007 under the title <a href="http://www.cippguide.org/2010/03/22/common-risks-impeding-the-adequate-protection-of-government-information/">“Common Risks Impeding the Adequate Protection of Government Information.” </a></p>
<p><strong>Improving the Agencies’ Ability to Respond to Data Breaches in the Government</strong></p>
<p>Agencies were instructed to develop and publish a “routine use” policy for their systems of records under the <strong><a href="http://www.cippguide.org/2010/02/10/privacy-act-of-1974/">Privacy Act</a>. </strong>These “routine use” policies would allow agencies to share PII–without the prior consent of the individual–with other agencies in order to respond effectively to security breaches.</p>
<p><strong>Summary</strong></p>
<p>In 2006, the Presidential Identity Theft Task Force allowed the U.S. Government to quickly analyze federal information security practices and create appropriate recommendations and plans to increase protection. Of the seven recommendations put forth by the Identity Theft Task force in 2006, several have been fulfilled and/or implemented in to government practice. Today, the Task Force continues to discuss ways in which the U.S. Government can increase the protection of its data holdings to prevent unauthorized disclosure and expose citizens to the threat of identity theft. While only the Federal Government was required to implement many of the guidelines, they serve as a model for institutions in the private sector concerned with identity theft.</p>
<p><em>CIPP/G Candidate Preparation</em></p>
<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>Recommendations of the Identity Theft Task Force, September 2006</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.cippguide.org/2010/04/13/identity-theft-task-force-recommendations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FTC Enforcement : Gateway Learning</title>
		<link>http://www.cippguide.org/2010/01/28/ftc-enforcement-gateway-learning/</link>
		<comments>http://www.cippguide.org/2010/01/28/ftc-enforcement-gateway-learning/#comments</comments>
		<pubDate>Thu, 28 Jan 2010 12:00:56 +0000</pubDate>
		<dc:creator>jbrook</dc:creator>
				<category><![CDATA[Privacy]]></category>
		<category><![CDATA[FTC]]></category>
		<category><![CDATA[Gateway Learning]]></category>
		<category><![CDATA[Hooked on Phonics]]></category>
		<category><![CDATA[privacy policy]]></category>

		<guid isPermaLink="false">http://www.cippguide.org/?p=1243</guid>
		<description><![CDATA[Under the Federal Trade Commission Act, the FTC has the authority to take enforcement actions for the use of “unfair trade practices.” In 2004, the FTC used the fairness principle to enforce privacy law for the first time by launching a case against the Gateway Learning company, owner of the popular “Hooked on Phonics” product [...]]]></description>
			<content:encoded><![CDATA[<p>Under the Federal Trade Commission Act, the FTC has the authority to take enforcement actions for the use of “unfair trade practices.” In 2004, the FTC used the fairness principle to enforce privacy law for the first time by launching a case against the Gateway Learning company, owner of the popular “Hooked on Phonics” product line.</p>
<p><strong><a href="../../../../../2010/01/18/fair-information-practices-principles/">FTC and Fair Information Practices</a></strong></p>
<p>The Federal Trade Commission developed a set of guidelines to govern the collection, use, maintenance, and disclosure of personal information in order to protect personal privacy. While the principles in themselves are not law, they have been incorporated into many privacy laws which allow the principles to be enforced. The Gateway Learning Company was found to be in violation of the first two principles, notice and consent.</p>
<p>The <a href="http://www.ftc.gov/reports/privacy3/fairinfo.shtm">Fair Information Practice Principles</a> require:</p>
<ul>
<li><em>Notice</em> to the individual regarding the privacy policies of the organization including how information is used and any disclosure to third parties. Notice must also be provided to the individual for any alteration in the privacy policies.</li>
<li><em>Consent</em> from the individual regarding the use of their information for secondary uses and its disclosure to third parties.</li>
</ul>
<p><strong><a href="http://www.ftc.gov/opa/2004/07/gateway.shtm">Allegations</a></strong></p>
<p>The FTC brought the following allegations against the Gateway Learning Company:</p>
<ul>
<li>That they violated their own privacy policies by renting personally identifiable information (PII) collected from customers to third parties without the customer’s consent.</li>
<li>That they violated their own privacy policies by renting personal information (age/gender) about children under the age of 13 to third parties without the customer’s consent.</li>
<li>They committed unfair trade practices by retroactively applying a new privacy policy to information collected under the old privacy policy.</li>
<li>They committed unfair trade practices by failing to provide adequate notice to consumers regarding privacy policy changes.</li>
</ul>
<p><strong><a href="http://www.ftc.gov/os/caselist/0423047/0423047cmpexhac0423047.pdf">The Privacy Policies in Question</a></strong></p>
<p><em>The original privacy policy stated:</em></p>
<blockquote><p>We do not sell, rent or loan any personally identifiable information regarding our consumers with any third party unless we receive a customer’s explicit consent. We do share information with third parties that help us run our operations or provide services to customers (e.g., credit card processing and shipping companies), but only to the extent necessary to provide these services.</p></blockquote>
<p>It also stated the following regarding children’s personal information:</p>
<blockquote><p>The Site does not sell products for purchase by children; we sell children’s products for purchase by adults. Children under 13 years of age may not submit personal information without the consent of their parents. We do not provide any personally identifiable information about children under 13 years of age to any third party for any purpose whatsoever.</p>
<p>We may in the future offer products to be used by children online, some of which may require you to enter additional information such as a child’s age, gender or reading ability in order to deliver a quality experience. A child’s participation in such a program will be entirely at your discretion. Again, no personally identifiable information about children under 13 years of age will be shared with any third party for an purpose whatsoever.</p></blockquote>
<p>It also stated the following regarding changes to the privacy policy:</p>
<blockquote><p>If at some future time there is a material change to our information usage practices that affect your personally identifiable information, we will notify you of the relevant changes on this Site or by email. You will then be able to opt-out of this information usage by sending an email to: <a href="mailto:webmaster@hop.com">webmaster@hop.com</a>. You should also check this privacy policy for changes.</p></blockquote>
<p>In April, 2003 the Gateway Learning Company violated its privacy policies by disclosing, name, address, telephone numbers, purchasing history, and the names and ages and genders of the customer’s children with telemarketers and direct mail marketers.</p>
<p><em>On June 20, 2003 a new privacy policy was placed in effect:</em></p>
<p>The new privacy policy did not alter its policies regarding the use of children’s personal information or providing notice regarding changes to the policy. It did however change the policies regarding sharing information with third parties.</p>
<blockquote><p>From time to time, we may provide your name, address, and phone number (not you e-mail address) to reputable companies whose products or services you may find of interest. If you do not want us to share this information with these companies, please write to us at: Gateway Learning Corporation, 2900 South Harbor Blvd., Suite 202, Santa Ana, CA 92704, call 1-800-544-7323 or e-mail us at <a href="mailto:webmaster@hop.com">webmaster@hop.com</a> with the word do-no-share in the subject line.</p></blockquote>
<p>Despite their stated privacy policies, no email was sent or special notices posted to the website to alert customers to a change in the policies.</p>
<p><em>On July 17, 2003 another revised policy was posted:</em></p>
<p>The new policy changed the process for opting out of third party disclosures.</p>
<blockquote><p>From time to time, we may provide your name, address, and phone number (not you e-mail address) to reputable companies whose products or services you may find of interest. If you do not want us to share this information with these companies, please write to us at: Gateway Learning Corporation, 2900 South Harbor Blvd., Suite 202, Santa Ana, CA 92704, call 1-800-544-7323 or e-mail us at <a href="mailto:do-not-rent@hop.com">do-not-rent@hop.com</a> with your full name in the subject line. Please be sure to include your first name, last name, address, city, state, zip code and phone number to ensure we can process your request. We will process your request promptly. Please be aware that  you may receive another contact before your name removal takes effect. We regret any inconvenience this may cause.</p></blockquote>
<p>The new policy also changed its statement regarding children’s privacy.</p>
<blockquote><p>The Site is not targeted to children, and we not knowingly collect personally-identifiable information from children under the age of 13 on this site. We do not sell products for purchase by children; we sell children&#8217;s products for purchase by adults. This site is entirely aimed at adults.</p></blockquote>
<p><strong><a href="http://www.ftc.gov/os/caselist/0423047/040707agree0423047.pdf">FTC Consent Agreement</a></strong></p>
<p>After investigations, the FTC found the Gateway Learning Corporation to have used unfair and deceptive trade practices and brought enforcement actions against the company. The Consent Agreement was the settlement reached to resolve the issue.</p>
<p><em>Bar on Misrepresentation</em></p>
<p>The bar on misrepresentation reinforces the rules regarding the Fair Information Practice principles which the company had violated. Under the agreement, Gateway Learning was banned from:</p>
<ul>
<li>Misrepresenting the use of collected information including whether it is sold, rent, or loaned to third parties</li>
<li>Misrepresenting whether information about children under the age of 13 will be disclosed to third parties</li>
<li>Misrepresenting how customers will be notified by changes to privacy policies</li>
<li>Misrepresenting how the company will collect, use or disclose information</li>
</ul>
<p><em>Ban on Disclosure of Personal Information to Third Parties</em></p>
<p>The ban on disclosure reinforced the protection of privacy for consumers whose personal information was collected prior to June 20, 2003 when the privacy policy was changed. The ban requires:</p>
<ul>
<li>Express, affirmative (opt-in) consent of the individual prior to the disclosure of any information to third parties</li>
<li>The new privacy policies may not be applies to information collected prior to the June 20, 2003 policy change without the express affirmative consent of the individual.</li>
</ul>
<p><em>Maintenance of Relevant Documents</em></p>
<p>This part of the agreement set up a way to ensure compliance for a period of 5 years. Under this provision, Gateway Learning must provide the FTC with the following documents:</p>
<ul>
<li> A copy of each different privacy statement or communication including the date, full text, URL and graphics</li>
<li>A copy of the document sent to consumers to obtain their express affirmative consent and any documents provided by customers confirming their consent</li>
<li>All invoices, communications and documents that relate to the disclosure of personally identifiable information to third parties.</li>
</ul>
<p><em>Delivery of Order</em></p>
<p>This part of the agreement dealt with the administrative task of ensuring enforcement in the work force.  The Gateway Learning companies was required to deliver a copy of the FTC agreement to all present and future employees with managerial responsibility related to the subject matter of the order.</p>
<p><em>Reporting</em></p>
<p>This part of the agreement requires Gateway Learning to notify the FTC 30 days before a corporate change which might affect compliance with the order. It also required Gateway Learning to file a report with the FTC setting forth their compliance within 60 days of service of the order and periodically after that, as requested.</p>
<p><em>Duration</em></p>
<p>Unless otherwise indicated, the order terminates after 20 years. Each violation of the final order may result in a civil penalty of up to $11,000</p>
<p><em>Fine</em></p>
<p>Gateway Learning was fined $4,608 which was the total profits received from the renting of personal information.</p>
<p><strong>In Conclusion:</strong></p>
<p>The Gateway Learning Case holds a significant place in privacy law because it demonstrated that the Federal Trade Commission is willing to pursue and enforce privacy violations. Since the Gateway Learning Case the FTC has continued to enforce privacy issues, especially any violations of the <em><a href="../../../../../2010/01/11/coppa-the-childrens-online-privacy-protection-act/">Children’s Online Privacy Protection Ac</a></em>t which protects the personal information of children.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.cippguide.org/2010/01/28/ftc-enforcement-gateway-learning/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>COPPA: The Children&#039;s Online Privacy Protection Act</title>
		<link>http://www.cippguide.org/2010/01/11/coppa-the-childrens-online-privacy-protection-act/</link>
		<comments>http://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>http://www.cippguide.org/2010/01/11/coppa-the-childrens-online-privacy-protection-act/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Choice and Consent</title>
		<link>http://www.cippguide.org/2009/12/21/choice-and-consent/</link>
		<comments>http://www.cippguide.org/2009/12/21/choice-and-consent/#comments</comments>
		<pubDate>Mon, 21 Dec 2009 12:00:29 +0000</pubDate>
		<dc:creator>jbrook</dc:creator>
				<category><![CDATA[CIPP]]></category>
		<category><![CDATA[Compliance & Regulations]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[CAN-SPAM]]></category>
		<category><![CDATA[Choice]]></category>
		<category><![CDATA[Code of Fair Information Practices]]></category>
		<category><![CDATA[Consent]]></category>
		<category><![CDATA[EU Data Protection Directive]]></category>
		<category><![CDATA[FTC]]></category>

		<guid isPermaLink="false">http://www.cippguide.org/?p=1170</guid>
		<description><![CDATA[The development of information privacy and data protection laws has sought to give data subjects greater control over their personal information. The concepts of choice and consent have been key to granting data subjects such control by allowing them the opportunity to make informed choices regarding who has access to their information and how it may be [...]]]></description>
			<content:encoded><![CDATA[<p>The development of information privacy and data protection laws has sought to give data subjects greater control over their personal information. The concepts of <em>choice </em>and <em>consent</em> have been key to granting data subjects such control by allowing them the opportunity to make informed choices regarding who has access to their information and how it may be used.</p>
<p><strong>What is Choice/Consent?</strong></p>
<p>Choice/Consent is the second of five <a href="http://www.ftc.gov/reports/privacy3/fairinfo.shtm">Fair Information Practices</a> published by the FTC to guide the collection, use and disclosure of personal information. The FTC states,“At its simplest, choice means giving consumers options as to how any personal information collected from them may be used.”</p>
<p>There are two forms of consent exercised by individuals.</p>
<p><em><a href="http://en.wikipedia.org/wiki/Opt_in_e-mail">Opt-in</a> </em>requires the affirmative consent of the individual. The user must take action to allow a business to process their information and provide a product or service. For example, a user may visit a website and submit their email or check a box with their registration to receive the site’s email newsletter.</p>
<p><em><a href="http://en.wikipedia.org/wiki/Opt-out">Opt-out</a></em> requires the implicit consent of an individual. Since a user has not taken action to stop the processing of their information, they are said to give implicit (unspoken or assumed) consent. When a user receives marketing messages in their mailbox they no longer wish to receive, they may unsubscribe from the newsletter. This is consider opting-out.</p>
<p>The use of the choice/consent mechanism as the main regime for protecting personal information has been widely criticized. It is believed that many consumers are not aware or educated enough in privacy law to understand their rights and ability to control information.</p>
<p><strong>Secondary Use of Information</strong></p>
<p>The FTC defines secondary use as <em><a href="http://www.ftc.gov/reports/privacy3/fairinfo.shtm">“uses beyond those necessary to complete the contemplated transaction.”</a></em> Companies are required by law to state in their privacy policies any secondary uses of information including whether it may be disclosed to third parties.</p>
<p>The control of personal information with regard to marketing is the most common implementation of choice/consent. It is used to control the receipt of marketing messages, the use and disclosure of information to third parties, and the collection of information through cookies in order to create tailored advertising. Though the disclosure of information may be necessary to complete a transaction with a company, an individual is allowed to object to any and all secondary use or disclosure of their information.</p>
<p><strong><em><a href="http://formulate.com.au/articles/mandatory-versus-optional-fields/">Mandatory vs. Optional Data Collection</a></em></strong></p>
<p>Mandatory is any information that is necessary to complete the immediate transaction. Optional information includes any information an entity may wish to collect about an individual for internal purposes, but is not required to complete the immediate transaction. <em><a href="http://theemailwars.com/2009/11/30/giving-thanks/">In a web form</a></em>, mandatory field must be filled in before the form can be submitted. Optional fields may be left blank or unanswered and the form will still process. By completing optional information fields, an individual is giving their consent to the collection and use of such information.</p>
<p>Businesses practicing responsible information privacy will limit the collection of information, especially that which is optional because the more information collected, the greater the risk to privacy.</p>
<p><strong>Choice/Consent and Regulations</strong></p>
<p>The <a href="http://www.ftc.gov/bcp/edu/pubs/business/ecommerce/bus61.shtm">CAN-SPAM Act</a> of 2003 regulates email marketing messages in the U.S. In addition to content regulations, the CAN-SPAM Act requires all marketing messages to have an unsubscribe mechanism at the bottom and that consumer requests be honored with ten days.</p>
<p>The <a href="http://aspe.hhs.gov/DATACNCL/eudirect.htm">European Data Directive</a> addresses consent in <a href="http://aspe.hhs.gov/DATACNCL/eudirect.htm%23ART7">Article 7</a> which requires data subject consent for the processing of data, though consent is not required for a few, specific situations. It is also addressed in <a href="http://aspe.hhs.gov/DATACNCL/eudirect.htm%23ART14">Article 14 </a>which guarantees the data subjects right to object to the processing of data. Furthermore, <a href="http://aspe.hhs.gov/DATACNCL/eudirect.htm%23ART8">Article 8</a> requires the explicit consent of a data subject to process sensitive information such as racial or ethnic origins, political or religious beliefs, sexual orientation, health information, or trade union membership.</p>
<p>Almost all data protection laws allow individuals the opportunity to make choices regarding the use of their personal information.</p>
<p><strong>In Conclusion:</strong></p>
<p>Choice/Consent deals with an individual’s ability to control the use of their information. Because, as of now, the choice/consent regime is the major framework for protecting privacy in many industries, it is the duty of the consumer to read privacy practices and make informed decisions regarding how they wish their information to be used.</p>
<p><em>CIPP Candidate Preparation</em></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: Choice/Consent (I.E.ii)</li>
<li>Privacy Considerations Online including choice and consent, secondary use of data and mandatory vs. optional information. (III.B.c.i-iii.)</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.cippguide.org/2009/12/21/choice-and-consent/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Safe Harbor Compliance</title>
		<link>http://www.cippguide.org/2009/11/30/safe-harbor-compliance/</link>
		<comments>http://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>http://www.cippguide.org/2009/11/30/safe-harbor-compliance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Proposed bill shows State&#039;s Rights sometimes fall to bad federal legislation</title>
		<link>http://www.cippguide.org/2009/05/27/proposed-bill-shows-states-rights-sometimes-fall-to-bad-federal-legislation/</link>
		<comments>http://www.cippguide.org/2009/05/27/proposed-bill-shows-states-rights-sometimes-fall-to-bad-federal-legislation/#comments</comments>
		<pubDate>Wed, 27 May 2009 16:17:07 +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[Bobby Rush]]></category>
		<category><![CDATA[breach notification]]></category>
		<category><![CDATA[Consumer Protection]]></category>
		<category><![CDATA[Data Accountability and Trust Act]]></category>
		<category><![CDATA[Encryption]]></category>
		<category><![CDATA[Federal Trade Commission]]></category>
		<category><![CDATA[FTC]]></category>
		<category><![CDATA[HR 2221]]></category>
		<category><![CDATA[Maine]]></category>
		<category><![CDATA[state's rights]]></category>
		<category><![CDATA[unfair and deceptive trade practices]]></category>

		<guid isPermaLink="false">http://www.cippguide.org/?p=664</guid>
		<description><![CDATA[Proposed legislation H.R. 2221 by Illinois Representative Rush seeks to preempts more restrictive privacy laws on the books in several states.  While the Data Accountability and Trust Act handles several important information privacy issues, the State's Rights infringement could hurt citizens' [...]]]></description>
			<content:encoded><![CDATA[<p><span><span>In the United States, we’re dependent on the overlapping and sometimes confusing patchwork of legislation and regulations because the US employs a <a title="FCC's warning includes highlights of sectoral privacy approach" href="http://www.cippguide.org/2009/03/03/fcc-to-telecoms-protect-customers-privacy-or-expect-fines/" target="_blank">sectoral</a> versus </span></span><span><span><a title="EU Legal action brought against UK highlights comprehensive privacy approach" href="http://www.cippguide.org/2009/04/16/eu-begins-legal-action-against-uk-over-privacy/" target="_blank">comprehensive</a> approach to privacy.<span>  </span>This legal patchwork sometimes includes state laws in addition to federal, which most see as simply another hurdle towards doing business in that state.<span>  In some cases</span>, related but more stringent laws in the state were already passed.  In those situations only minor modifications are needed for state compliance with a newly signed federal statute.</span></span></p>
<p class="MsoNormal"><span>The Federal Trade Commission and State Attorneys General enforce federal and state laws of consumer privacy protection for Unfair or Deceptive Trade Practices (UDTP).</span><span>  </span>One recent example was the <a title="Example of state consumer protection laws more restrictive than federal laws" href="http://www.cippguide.org/2008/12/31/consumer-protection-laws-states-trump-federal/" target="_blank">State of </a><a title="Example of state consumer protection laws more restrictive than federal laws" href="http://www.cippguide.org/2008/12/31/consumer-protection-laws-states-trump-federal/" target="_blank">Maine</a><a title="Example of state consumer protection laws more restrictive than federal laws" href="http://www.cippguide.org/2008/12/31/consumer-protection-laws-states-trump-federal/" target="_blank">’s consumer protections, which are more restrictive than the federal laws</a> with respect to cigarette labeling.<span>  </span>The State brought suit against a tobacco manufacturer for violating the state’s deceptive trade law, which the manufacturer argued was out of line due to the Federal Cigarette Labeling Act.<span>  </span>The <a title="Supreme Court decision upholds State's Right to pass legislation more restrictive than federal law" href="http://www.supremecourtus.gov/opinions/08pdf/07-562.pdf" target="_blank">Supreme Court decision upheld the State’s right to pass more restrictive legislation</a>, pointing out:<span>  </span></p>
<blockquote>
<p class="CM4"><span>Neither the Labeling Act’s pre-emption provision nor the Federal Trade Commission’s actions in this field pre-empt respondents’ state law fraud claim. Pp. 5–20. </span></p>
<p class="Default"><span><span> </span>(a) <strong>Congress may indicate pre-emptive intent</strong><strong> </strong>through a statute’s express language or through its structure and purpose. See <em>Jones </em>v. <em>Rath Packing Co., </em>430 U. S. 519, 525. When the text of an express pre-emption clause is susceptible of more than one plausible reading, courts ordinarily “accept the reading that disfavors pre-emption.” </span></p>
</blockquote>
<p class="Default">The rationale in (a) requires express language for a federal law to negate a State’s right to create more restrictive legislation.<span>  </span>The first citing by the high court becomes the <a title="New York Times' opinion that House Bill 2221 bad for State's Rights and consumer privacy in general" href="http://www.nytimes.com/2009/05/25/opinion/25mon2.html" target="_blank">contentious issue for House Bill H.R. 2221</a>, proposed by Illinois Representative Bobby Rush.<span>  </span>The bill tackles several tough interstate commerce issues, placing the FTC in charge of disposal regulations for <a title="Examples of abandoned paper records containing personal information" href="http://www.cippguide.org/2009/04/09/abandoned-medical-records-happen-will-abandoned-ehr-happen-more/" target="_blank">obsolete or abandoned paper records containing personal information</a>, <a title="Interview offers breach notification opinion from IBM Privacy Partner and former IRS Privacy Director Barbra Symonds" href="http://www.cippguide.org/2008/06/12/an-interview-with-barbra-symonds-ibm-associate-partner-in-security-privacy-it-governance" target="_blank">breach notifications</a> and verification requirements for information brokers.<span>  </span>Section 6 of the so-called <a title="Proposed House Bill HR 2221 proposed by Illinois Representative Bobby Rush" href="http://thomas.loc.gov/cgi-bin/query/z?c111:H.R.2221:" target="_blank">Data Accountability and Trust Act</a> includes a provision reading:</p>
<blockquote>
<p class="MsoNormal"><span> (a) …This Act supersedes any provision of a statute, regulation, or rule of a State or political subdivision of a State, with respect to those entities covered by the regulations issued pursuant to this Act, that expressly&#8211;</span></p>
<ol>
<li>requires information security practices and treatment of data in electronic form containing personal information similar to any of those required under section 2; and</li>
<li>requires notification to individuals of a breach of security resulting in unauthorized acquisition of data in electronic form containing personal information.</li>
</ol>
<p class="MsoNormal"><span>(b) Additional Preemption-</span></p>
<ol>
<li>IN GENERAL- No person other than the Attorney General of a State may bring a civil action under the laws of any State if such action is premised in whole or in part upon the defendant violating any provision of this Act. </li>
</ol>
</blockquote>
<p class="Default">This would strike several of the state privacy and notification laws (possibly including California&#8217;s SB 1386), stripping the State’s rights and growing Washington’s power.<span>  </span>It also bars the State Attorneys General from bringing suit, possibly in an effort to avoid a double jeopardy situation.<span>  </span>There are numerous case studies of the FTC and State Attorneys General working hand-in-hand for consumer protection; why this law tries to hamstring the situation is a bit of a mystery.</p>
<p class="Default">One more interesting note on Representative Rush’s proposal &#8211; the bill also places an encryption exemption on breach notification.<span>  </span>As we noted in a recent post on <a title="Corporate disposal policies should include provisions for security obsolescene such as old encryption implementations" href="http://www.cippguide.org/2009/05/19/hey-stupid-dont-just-throw-that-out-corporate-disposal-policies-keep-your-organization-out-of-the-headlines/" target="_blank">corporate disposal policies</a>, hackers and researchers seem to notice protection missteps and use them to bypass security provisions just like encryption.</p>
<blockquote>
<p class="Default">The encryption of data in electronic form shall establish a presumption that no reasonable risk of identity theft, fraud, or other unlawful conduct exists following a breach of security of such data. Any such presumption may be rebutted by facts demonstrating that the encryption has been or is reasonably likely to be compromised.</p>
</blockquote>
<p class="Default">The law has a 10 year lifespan, which should be a decent requirement before the <a title="Wikipedia: Advanced Encryption Standard controls confidentiality through cryptography" href="http://en.wikipedia.org/wiki/Advanced_Encryption_Standard" target="_blank">Advanced Encryption Standard (AES)</a>, currently the de-facto encryption standard (and as yet to be compromised), ages beyond its effectiveness.</p>
<p class="Default">Update: President Obama&#8217;s <a title="Presidential Memo on preemption says States' Rights are very important" href="http://www.whitehouse.gov/the_press_office/Presidential-Memorandum-Regarding-Preemption/" target="_blank">May 20th, 2009 Memorandum on the Subject of Preemption</a> and State&#8217;s Rights quotes Justice Brandeis saying, &#8221;[i]t is one of the happy incidents of the federal system that a single courageous state may, if its citizens choose, serve as a laboratory; and try novel social and economic experiments without risk to the rest of the country.&#8221;</p>
<h3>CIPP Candidate Preparation</h3>
<p class="MsoNormal">In preparation for the Certified Information Privacy Professional exam, a privacy professional should be comfortable with several topics found in this post including:</p>
<ul>
<li>Regulatory Authorities (CIPP: I.A.c) including: The Federal Trade Commission</li>
<li>Enforcement of U.S. Privacy and Security Laws (CIPP: II.B.d, I.A.c) including: Unfair and Deceptive Trade Practices (UDTP), and enforcement powers under the FTC Act section 5 </li>
<li>Privacy and Data Protection Regulation (Foundations: I.F.a, I.F.b) including: Sectoral legal framework </li>
<li>National data protection regimes (Foundations: I.F.b) including: State&#8217;s Rights </li>
<li>Specific Privacy and Security laws (CIPP: I.B.g) including: Breach notification</li>
<li>Information Security (Foundations: II.C) including: Encryption</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.cippguide.org/2009/05/27/proposed-bill-shows-states-rights-sometimes-fall-to-bad-federal-legislation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Federal Trade Commission to target EULAs</title>
		<link>http://www.cippguide.org/2009/02/25/ftc-target-eulas/</link>
		<comments>http://www.cippguide.org/2009/02/25/ftc-target-eulas/#comments</comments>
		<pubDate>Wed, 25 Feb 2009 10:09:34 +0000</pubDate>
		<dc:creator>jbrook</dc:creator>
				<category><![CDATA[CIPP]]></category>
		<category><![CDATA[Compliance & Regulations]]></category>
		<category><![CDATA[Consumer Protection]]></category>
		<category><![CDATA[EULA]]></category>
		<category><![CDATA[Federal Trade Commission]]></category>
		<category><![CDATA[FTC]]></category>

		<guid isPermaLink="false">http://blog.cippguide.org/2009/02/04/ftc-target-eulas/</guid>
		<description><![CDATA[Even though most software and service providers are legitimately creating EULAs without deceptive intent, they are difficult to understand for the typical consumer.  Then there are those that simply aren't cooperating.  Is it time to limit the "legal-ese" and construct simple, plain language [...]]]></description>
			<content:encoded><![CDATA[<p>There have been quite a few examples of the Federal Trade Commission  in action over the past few months.  <a title="FTC Behavioral Advertising Guidelines" href="http://blog.cippguide.org/2009/02/18/ftc-issues-behavioral-advertising-guidelines/" target="_blank">Behavioral Advertising</a>, <a title="FTC: Digital Rights Management" href="http://blog.cippguide.org/2009/02/04/federal-trade-commission-looks-at-drm/" target="_blank">Digital Rights Management</a>, <a title="State of Maine consumer protection law" href="http://blog.cippguide.org/2008/12/31/consumer-protection-laws-states-trump-federal/" target="_blank">assisting state consumer protection</a> and <a title="FTC: Statutes protecting consumers" href="http://www.ftc.gov/ogc/stat3.shtm" target="_blank">numerous other statutes</a> all relate to the Federal Trade Commission&#8217;s job of protecting consumers.  Since 1983, the FTC has made it quite clear of their <a title="FTC: Policy on deceptive acts" href="http://www.ftc.gov/bcp/policystmt/ad-decept.htm" target="_blank">policy on deceptive acts</a>.</p>
<p>One item receiving only cursory treatment: End User License Agreements (EULAs).  At the initial peak of the Peer-to-peer file sharing in 2004, the FTC solicited input from industry through one of their workshops.  Several points brought up during that conference surrounded EULAs and how <a title="FTC: P2P file sharing conference presentation" href="http://www.ftc.gov/bcp/workshops/filesharing/presentations/miller_2.pdf" target="_self">file sharing products such as eDonkey and Gnutella</a> included quite extensive licenses.  This resulted in recommendations such as search-ability and slide bars to avoid hiding potential monitoring or questionable privacy practices within agreement.  In the FTC&#8217;s <a title="FTC: Guidance on Dot Com Disclosures" href="http://www.ftc.gov/bcp/edu/pubs/business/ecommerce/bus41.pdf" target="_blank">Guidance for Dot Com Disclosures</a> the name of the game is visibility :</p>
<blockquote><p>Making the disclosure available somewhere in the ad so that consumers who are looking for the information might find it doesn’t meet the clear and conspicuous standard.</p></blockquote>
<p>This could easily carry over to the EULA.  It has been recently <a title="FTC could begin regulating EULAs" href="http://www.joystiq.com/2009/01/30/lgj-ftc-could-target-eulas/" target="_blank">speculated by those in the gaming industry</a> that the FTC could place begin regulating licenses.  Apparently, even though most software and service providers are legitimately creating the agreements without deceptive intent, they are difficult to understand for the typical consumer.  Then there are those that simply aren&#8217;t cooperating.  Is it time to limit the &#8220;legal-ese&#8221; and construct simple, plain language agreements?</p>
<p><a href="https://secure.commentworks.com/ftc-DRMtechnologies/"><br />
</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.cippguide.org/2009/02/25/ftc-target-eulas/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FTC Issues Behavioral Advertising Guidelines</title>
		<link>http://www.cippguide.org/2009/02/18/ftc-issues-behavioral-advertising-guidelines/</link>
		<comments>http://www.cippguide.org/2009/02/18/ftc-issues-behavioral-advertising-guidelines/#comments</comments>
		<pubDate>Wed, 18 Feb 2009 19:08:21 +0000</pubDate>
		<dc:creator>jbrook</dc:creator>
				<category><![CDATA[CIPP]]></category>
		<category><![CDATA[Compliance & Regulations]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Add new tag]]></category>
		<category><![CDATA[Behavioral Advertising]]></category>
		<category><![CDATA[Federal Trade Commission]]></category>
		<category><![CDATA[FTC]]></category>

		<guid isPermaLink="false">http://blog.cippguide.org/?p=228</guid>
		<description><![CDATA[Last week, the FTC provided guidance for online advertising.  Most regulatory agencies issue guidelines as a precursor for regulations.  The consensus is that the self regulation within the online advertising community is not [...]]]></description>
			<content:encoded><![CDATA[<p>As most of the privacy professionals are painfully aware, the Federal Trade Commission is congressionally empowered to protect consumers from deceptive trade practices.  Last week, the <a title="FTC: Online Advertising Guidance" href="http://www.ftc.gov/opa/2009/02/behavad.shtm" target="_blank">FTC provided guidance for online advertising</a>.  Most regulatory agencies issue guidelines as a precursor for regulations.  The consensus is that the self regulation within the online advertising community is not working.</p>
<blockquote><p>&#8220;This is the industry&#8217;s last chance to get self-regulation right,&#8221; said Leslie Harris, President and CEO of the Center for Democracy &amp; Technology. &#8220;The FTC report makes clear that the industry&#8217;s own efforts in this area have fallen short and must do more.&#8221;</p></blockquote>
<p>The FTC held a &#8220;Behavioral Advertising&#8221; Town Hall in November 2007.  According to the FTC, Behavioral Advertising &#8220;is the practice of tracking an individual’s online activities in order to deliver advertising tailored to his or her interests.&#8221;  There are obvious privacy concerns with this sort of practice, as in order to create an individualized advertisement experience, a profile must be created.  That profile obviously incorporates some sort of marker, whether its a user name, cookie, serial number, or some other factor.</p>
<p>Will regulation foster better practices, similar to the Deceptive Trade Protections offered by the FTC, or will it simply mire the industry in more compliance quagmire?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.cippguide.org/2009/02/18/ftc-issues-behavioral-advertising-guidelines/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Federal Trade Commission looks at DRM</title>
		<link>http://www.cippguide.org/2009/02/04/federal-trade-commission-looks-at-drm/</link>
		<comments>http://www.cippguide.org/2009/02/04/federal-trade-commission-looks-at-drm/#comments</comments>
		<pubDate>Thu, 05 Feb 2009 00:23:06 +0000</pubDate>
		<dc:creator>jbrook</dc:creator>
				<category><![CDATA[CIPP]]></category>
		<category><![CDATA[Compliance & Regulations]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Digital Rights Managment]]></category>
		<category><![CDATA[DRM]]></category>
		<category><![CDATA[Federal Trade Commission]]></category>
		<category><![CDATA[FTC]]></category>
		<category><![CDATA[FTC Act]]></category>
		<category><![CDATA[Section 5]]></category>
		<category><![CDATA[Walmart Music]]></category>

		<guid isPermaLink="false">http://blog.cippguide.org/?p=185</guid>
		<description><![CDATA[The Federal Trade Commission (FTC) looks toward the Privacy Professional community for a town hall workshop discussion of the Digital Rights Management (DRM).  The FTC will accept comments and research until February 9th, [...]]]></description>
			<content:encoded><![CDATA[<p>The Federal Trade Commission (FTC) looks toward the Privacy Professional community for a <a title="Federal Trade Commission (FTC) examines Digital Rights Management (DRM)" href="https://secure.commentworks.com/ftc-DRMtechnologies/">town hall workshop discussion of the Digital Rights Management (DRM)</a>.  The FTC will accept comments and research until February 9th, 2009.</p>
<p>This may have something to do with <a title="Wal-Mart DRM reversal might have prompted FTC examination" href="http://news.cnet.com/8301-1023_3-10063331-93.html" target="_blank">WalMart, Yahoo and Microsoft&#8217;s music services threatening pulling the plug on their DRM servers</a>.  Customers purchasing a good (digital music) with known limitations of use (no mp3/music file copying) and no expiration date suddenly were told their investments would be worthless.  This seems perfectly in line with the announced purpose: &#8220;improve disclosures to consumers about DRM limitations&#8221;.</p>
<p>As a CIPP, privacy professionals should understand the FTC&#8217;s Congressionally appointed powers under the FTC Act to protect consumers, enforcing corporate promises on matters such as privacy and suitability of purpose through <a title="FTC Act Section 5 - Enforcement" href="http://www.ftc.gov/privacy/privacyinitiatives/promises.html" target="_blank">Section 5 of the Act</a>.  The FTC typically brings action against unruly corporations under deceptive trade practices, with a variety of fines, process controls and reporting requirements.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.cippguide.org/2009/02/04/federal-trade-commission-looks-at-drm/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>COPPA &#8211; The Children’s Online Privacy Protection Act</title>
		<link>http://www.cippguide.org/2009/01/11/coppa-the-children%e2%80%99s-online-privacy-protection-act/</link>
		<comments>http://www.cippguide.org/2009/01/11/coppa-the-children%e2%80%99s-online-privacy-protection-act/#comments</comments>
		<pubDate>Sun, 11 Jan 2009 12:00:04 +0000</pubDate>
		<dc:creator>System Admin</dc:creator>
				<category><![CDATA[CIPP]]></category>
		<category><![CDATA[Compliance & Regulations]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Children's Online Privacy Protection Act]]></category>
		<category><![CDATA[CIPP/G]]></category>
		<category><![CDATA[COPPA]]></category>
		<category><![CDATA[Federal Trade Commission]]></category>
		<category><![CDATA[FTC]]></category>
		<category><![CDATA[Parental Consent]]></category>
		<category><![CDATA[TRUSTe]]></category>

		<guid isPermaLink="false">http://www.cippguide.org/?p=1183</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">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>
<p>Conclusion:</p>
<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>
<p><em>CIPP/G Candidate Preparation</em></p>
<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>http://www.cippguide.org/2009/01/11/coppa-the-children%e2%80%99s-online-privacy-protection-act/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
