<?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>https://www.cippguide.org</link> <description>Your Guide to the CIPP</description> <lastBuildDate>Thu, 02 Feb 2012 12:00:03 +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>Online Behavioral Marketing</title><link>https://www.cippguide.org/2012/01/10/online-behavioral-marketing/</link> <comments>https://www.cippguide.org/2012/01/10/online-behavioral-marketing/#comments</comments> <pubDate>Tue, 10 Jan 2012 12:00:23 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[e-commerce]]></category> <category><![CDATA[FTC]]></category> <category><![CDATA[marketing]]></category> <category><![CDATA[OBM]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2671</guid> <description><![CDATA[Behavioral marketing is based on the idea that collecting data on what people do online can help advertisers learn about their interests and then effectively present ads to those who will be the most receptive. The advertising industry has touted the concept of behavioral marketing as a way to make ads increasingly relevant to [...]]]></description> <content:encoded><![CDATA[<p><a
href="http://www.cippguide.org/tag/OBM/">Behavioral marketing</a> is based on the idea that collecting data on what people do online can help advertisers learn about their interests and then effectively present ads to those who will be the most receptive. The advertising industry has touted the concept of behavioral marketing as a way to make ads increasingly relevant to consumers.</p><p>An example of behavioral marketing is advertising popular related items next to a news story that readers might find interesting. Another example is how large <a
href="https://www.cippguide.org/tag/e-commerce/">e-commerce</a> sites, such as Amazon, will list products that other customers have also purchased when browsing. The objective of behavioral marketing is to identify and advertise to your target audience, to ensure that marketing efforts are directed towards individuals who are most likely to purchase the product.</p><p><strong>FTC Report on OBM Principles</strong></p><p>On February 12, 2009, the <a
href="http://www.cippguide.org/tag/ftc/">FTC</a> issued its <a
href="http://www.ftc.gov/os/2009/02/P085400behavadreport.pdf">Staff Report on Self-Regulatory Principles for Online Behavioral Advertising</a>. The report defined online behavioral advertising as “the tracking of a consumer’s online activities over time – including the searches the consumer has conducted, the Web pages visited, and the content viewed – in order to deliver advertising targeted to the individual consumer’s interests.”</p><p>The report went on to outline principles that ensure:</p><ul><li>Transparency and consumer control</li><li>Reasonable security and limited data retention for consumer data</li><li>Affirmative express consent for material changes to existing privacy promises</li><li>Affirmative express consent to (or prohibition against) using sensitive data for behavioral advertising</li></ul><p>These principles apply equally in the context of mobile devices.</p><p><strong>Responses to FTC Report</strong></p><p>In response to the FTC’s guidelines, consumer privacy advocate groups began to claim that the document was not stringent enough and that the commission does not sufficiently investigate privacy threats and wrongful practices targeting children, adolescents and multicultural consumers. According to Pam Dixon, executive director of the <a
href="http://www.worldprivacyforum.org/">World Privacy Forum</a>,</p><p>“I think that the issue of self-regulation has been on the FTC’s plate for ten years and it’s disturbing that only one commissioner chose to question the self-regulatory model. I think my disappointment in the FTC approach is there weren’t specific renegotiations on the self-regulation model.”</p><p><a
href="http://www.mobilemarketer.com/cms/news/legal-privacy/2638.html">According to Chris Hoofnagle</a>, director of information privacy programs at the <a
href="http://www.law.berkeley.edu/bclt.htm">Berkeley Center for Law</a> and Policy Center, Berkley, CA. “The FTC failed to address the clearest examples of sensitive information and that there is certain user data that should never be used for targeting.”</p><p>Cory Wright, senior counsel and adjunct professor at <a
href="http://www.law.georgetown.edu/">Georgetown Law</a> <a
href="http://www.mobilemarketer.com/cms/news/legal-privacy/2638.html">commented</a>, “The commission’s report does not heed the concerns we have been having. The policy is not meaningful. The document fails to define children in terms of what age group can be referred to as children. The FTC says affirmative consent will work but does not go into detail about what that means. The guidelines don’t go far enough to protect kids.”</p><p><strong>Mobile OBM</strong></p><p>Many advertisers are looking eagerly at the potential of the online mobile market. Perhaps companies could then connect with clients on the go to let them know about their nearby products and services. In response, the FTC and Congress have voiced their concerns regarding the potential for abuse and misuse of consumer information in this context. Furthermore, there is a quickly-diminishing distinction between personally identifiable information (PII) and non-PII, including a user’s IP address and other computer/mobile device identifiers.</p><p>It has been discussed that the FTC’s guidelines regarding mobile marketing does not do enough to control applications. It is challenging to create effective disclosures, especially given the size limitations in the mobile context, as well as continuous developments in mobile-based products and services.</p><p><strong>Summary </strong></p><p>This article takes a look at online behavioural marketing practices and how these are used in e-commerce. The article explores the FTC’s report on Self-Regulatory Principles for Online Behavioral Advertising, which was released in early 2009. It also looks at responses to the principles, from privacy rights groups in the United States. Finally, the article explores possible privacy issues inherent to mobile online behavioural marketing.</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>Online Behavioral Marketing (OBM) (III.B.j.ii.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2012/01/10/online-behavioral-marketing/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Senate Investigates Mobile Data Collection, Companies Respond to Consumer Fears</title><link>https://www.cippguide.org/2011/10/04/senate-investigates-mobile-data-collection-companies-respond-to-consumer-fears/</link> <comments>https://www.cippguide.org/2011/10/04/senate-investigates-mobile-data-collection-companies-respond-to-consumer-fears/#comments</comments> <pubDate>Tue, 04 Oct 2011 12:00:03 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[data collection]]></category> <category><![CDATA[Do-Not-Track]]></category> <category><![CDATA[FTC]]></category> <category><![CDATA[GPS]]></category> <category><![CDATA[mobile devices]]></category> <category><![CDATA[regulators]]></category> <category><![CDATA[Senate]]></category> <category><![CDATA[SPI]]></category> <category><![CDATA[Surveillance]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2591</guid> <description><![CDATA[On May 19, 2001, a US Senate subcommittee met to discuss "Consumer Privacy &#38; Protection in the Mobile Market Place." As mobile phones and location-based apps are becoming more ubiquitous, this has raised a number of consumer concerns regarding the amount and type of sensitive information that is being collected, stored and shared by developers and third-parties. [...]]]></description> <content:encoded><![CDATA[<p>Both US and European regulators alike are turning the focus to mobile technology, especially the collection of location-based data and other consumer behavioral information. An <a
href="http://www.mobileforum.com/blogs/26-000-people-stalked-using-gps-devices-year-2006-119">American statistic</a> revealed that over 26,000 adults were stalked annually through the use of <a
href="http://www.cippguide.org/tag/GPS/">GPS</a> devices, including those on mobile phones. This number is from 2006, and today there are three times as many smartphones in use.</p><p>On May 19, 2011, the <a
href="http://commerce.senate.gov/public/">US Senate Committee on Commerce, Science and Transportation</a> had a hearing that focused on “Consumer Privacy &amp; Protection in the Mobile Market Place.” Present were representatives from Google, Apple and Facebook, as well as David Vladeck, director of the Bureau of Consumer Protection of the <a
href="http://www.cippguide.org/tag/FTC/">Federal Trade Commission</a> (FTC).</p><p><strong>Voicing Concerns</strong></p><p>At the subcommittee hearing, Senator John Rockefeller <a
href="http://www.clickz.com/clickz/news/2072622/growing-scrutiny-mobile-collection">expressed concerns</a> about the amount of information mobile devices are actually able to collect about their owners. He demanded stronger controls over how and when such personal data is shared, saying, “As smartphones become more powerful, more personal information is being concentrated in one place. Consumers want to understand and have control of their personal information. ” Senator Rockefeller is the chairman of the US Senate Committee on Commerce, Science and Transportation.</p><p><a
href="http://abcnewsradioonline.com/politics-news/senate-subcommittee-investigates-mobile-safety-data-collecti.html">According to Senator Al Franken</a>, the chairman of the judiciary subcommittee on Privacy, Technology and the Law, “Consumers have a fundamental right to know what data is being collected about them. I also believe they have a right to decide whether or not they want to share that information and with who they want to share it and when.”</p><p>Jessica Rich from the FTC <a
href="http://www.pointofview.net/site/News2?page=NewsArticle&amp;id=17115&amp;news_iv_ctrl=1201">expressed worries</a> about mobile device safety, saying, “These concerns stem from the always-on, always-with-you personal nature of mobile devices.” She also pointed out the possible hazards of “invisible collection and sharing of data with multiple parties, the ability to track consumers – including children and teens – to their precise location.”</p><p><strong>Responding to the Fears</strong></p><p>In response to the increased concerns regarding mobile data collection, Catherine Novelli, Apple’s VP of worldwide government affairs explained that the company currently provides tools allowing customers to control the collection and use of data on its mobile devices, including location data. <a
href="http://crashcollective.com/uncategorized/growing-scrutiny-of-mobile-data-collection/">Novelli said</a>, “Apple does not track users’ locations – Apple has never done so and has no plans to ever do so.” However, the recent flurry of activity over the company’s iPhone and 3G-enabled iPads speak to the contrary.</p><p>Alan Davidson, Google’s director of public policy for the Americas <a
href="http://crashcollective.com/uncategorized/growing-scrutiny-of-mobile-data-collection/">responded</a> that Google supports the development of a legal privacy framework that ensures broad-based user trust and that will support continued innovation.</p><p>Bret Taylor, the Chief Technology Officer of Facebook, <a
href="http://crashcollective.com/uncategorized/growing-scrutiny-of-mobile-data-collection/">warned</a> that too much regulation may stifle innovation amongst mobile technology and service providers: “Adopting overly restrictive policies will prevent our social features from functioning in the way that individuals expect and demand.”</p><p><strong>FTC Suggestions</strong></p><p>In its statement to the subcommittee, the FTC suggested extending the application of its <a
href="http://www.ftc.gov/opa/2010/12/dnttestimony.shtm">Do-Not-Track mechanism</a>. Introduced in December 2010, the Do Not Track feature for internet browsers would allow users to opt out of sharing browsing data completely and protect their privacy. This suggestion was made in order to give end users increased control over the amount and type of personal data stored by companies, preventing the sharing of sensitive data with third parties, or the use of sensitive data against the individual’s wishes.</p><p>The FTC recommended that this Do-Not-Track mechanism should apply to mobile and desktop devices: “At least for purposes of web browsing, the issues surrounding implementation of Do Not Track are the same on mobile devices and desk top computers.” Currently, FTC staff is developing ways to implement Do Not Track mechanisms on mobile apps.</p><p><strong>Summary</strong></p><p>This article takes a look at the May 19, 2011 Senate Subcommittee hearing on “Consumer Privacy &amp; Protection in the Mobile Market Place.” As mobile phones and location-based apps are becoming more ubiquitous, this has raised a number of consumer concerns regarding the amount and type of sensitive information that is being collected, stored and shared by developers and third-parties. The subcommittee hearing was an opportunity for those on both sides of the debate to express their opinions. The FTC suggested extending the Do Not Track mechanism for web browsers to include mobile devices as well.</p><p><strong>CIPP Exam Preparation</strong></p><p>In preparation for the Certified Information Privacy Professional/Information Technology (CIPP/IT) exam, a privacy professional should be comfortable with topics related to this post, including:</p><ul><li>Sensitive Personal Information (SPI) (I.A.b.)</li><li>Data accountability (I.B.c.)</li><li>Consumer privacy concerns (II.A.a.)</li><li>Government and citizen surveillance (II.A.k.)</li><li>Social networking services (VI.C.)</li><li>Location-based services (VI.E.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2011/10/04/senate-investigates-mobile-data-collection-companies-respond-to-consumer-fears/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Justice Department Pushes for Mandatory Data Retention</title><link>https://www.cippguide.org/2011/03/29/justice-department-pushes-for-mandatory-data-retention/</link> <comments>https://www.cippguide.org/2011/03/29/justice-department-pushes-for-mandatory-data-retention/#comments</comments> <pubDate>Tue, 29 Mar 2011 12:00:52 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[data retention]]></category> <category><![CDATA[Department of Justice]]></category> <category><![CDATA[Do-Not-Track]]></category> <category><![CDATA[FTC]]></category> <category><![CDATA[Internet Service Provider]]></category> <category><![CDATA[ISP]]></category> <category><![CDATA[Surveillance]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2451</guid> <description><![CDATA[On January 25, 2011, the US Department of Justice brought the issue of mandatory data retention to the House Subcommittee on Crime, Terrorism, and Homeland Security. Currently, there is no law requiring internet service providers (ISPs) to retain user data, and ISP retention practices are inconsistent in terms of type of data and retention period. Law enforcement authorities have long argued that mandatory data retention would advance criminal investigations, especially those dealing with child pornography and sexual predators. Critics argue that retention of user data would result in numerous privacy and freedom of speech [...]]]></description> <content:encoded><![CDATA[<h1><span
style="font-weight: normal; font-size: 13px;">In a House subcommittee hearing held January 25, 2011, the US <a
href="http://www.justice.gov/">Department of Justice</a> called for new legislation mandating internet service providers (ISPs) to retain customer usage data for up to two years. This has resulted in a number of concerns, ranging from individuals’ privacy worries, to ISP concerns regarding the storage of large amounts of data for long periods of time.</span></h1><h2>Crucial Evidence</h2><p>In his statement before the <a
href="http://judiciary.house.gov/about/subcrime.html">Subcommittee on Crime, Terrorism, and Homeland Security</a>, Jason Weinstein, deputy assistant attorney general at the Justice Department, <a
href="http://judiciary.house.gov/hearings/pdf/Weinstein01252011.pdf">pointed out</a> that retaining data from ISPs and cell phone service providers can help provide crucial evidence in cases “including child exploitation, violent crime, fraud, terrorism, public corruption, drug trafficking, online piracy, computer hacking, and other privacy crimes.”</p><p>According to Weinstein, many of the Justice Department’s current criminal investigations are being hindered by its inability to monitor and store the online activity of users. He provided numerous examples in which the retention policies of service providers were obstructing federal, state and local law enforcement investigations. Weinstein said, “These decisions by providers to delete records are rarely done out of a lack of desire to cooperate with law enforcement; rather, they are usually done out of an understandable desire to cut costs.  Some providers also seem to delete records out of a concern for customer privacy.”</p><h2>Current Practices</h2><p>At this point, ISPs are required to preserve usage data only at the request of law enforcement authorities. Many ISPs are also collecting and maintaining “non-content records,” for instance a subscriber’s login records, information on who is using their services and how. ISPs have widely varying policies and practices regarding the storage of non-content records. In some cases, it will be deleted within days, while others may retain the data for months. Weinstein would like to see this retention period standardized, so that authorities are guaranteed to be able to access such data, should they require it.</p><p>There is currently no law that requires ISPs to retain user data. However, the push for extensive data retention legislation is not a new issue. In the past, FBI director Robert Mueller requested that Congress consider such legislation for similar reasons.</p><h2>Critics Say…</h2><p>Undoubtedly, the January 25<sup>th</sup> hearing has brought to the surface a number of privacy and freedom of speech concerns. The notion of law enforcement authorities tracking and retaining large amounts of information on over 230 million Americans is an unacceptable outcome for many. This may significantly impact free and anonymous speech and will change how individuals use the internet.</p><p>Jim Harper, the director of information policy studies at the <a
href="http://www.cato.org/">Cato Institute</a>, commenting on the issue of mandatory data retention, says “I fail to see where the Fourth Amendment permits the government to require dragnet surveillance of Internet users.”</p><p>Another issue is that while the federal government is pushing for pro-privacy laws, it is also contradicting itself with anti-privacy laws, such as this data retention legislation. Recently, the <a
href="https://www.cippguide.org/2011/03/01/resisting-online-tracking-new-features-tools">FTC proposed</a> that browsers include Do-Not-Track features, which would help users ensure that their information is not being retained while they browse the internet. At the same time, the Justice Department has asked for more extensive retention laws, though the two are seemingly in conflict with each other.</p><p>According to John Morris, the general counsel for the Washington DC-based think-tank <a
href="http://www.cdt.org/">Center for Democracy and Technology</a>, the hearing does not necessarily mean that a data retention bill is on the way. It is also uncertain what kind of data ISPs would be expected to retain, or if other online services (e.g. e-mail providers) might be included in the new legislation. Morris said:</p><p>“In the best-case scenario, a data retention bill will only require ISPs to track and store Internet Protocol (IP) address allocation data to help law enforcement better link Internet use to specific users. In the worst-case scenario, it could require ISPs and all sorts of online service providers to store and track everything from IP addresses to source data involving e-mail, instant messaging (IM), social media interactions and Web sites visited.”</p><h3>Summary</h3><p>On January 25, 2011, the US Department of Justice brought the issue of mandatory data retention to the House Subcommittee on Crime, Terrorism, and Homeland Security. Currently, there is no law requiring internet service providers (ISPs) to retain user data, and ISP retention practices are inconsistent in terms of type of data and retention period. Law enforcement authorities have long argued that mandatory data retention would advance criminal investigations, especially those dealing with child pornography and sexual predators. Critics argue that retention of user data would result in numerous privacy and freedom of speech concerns.</p><h3>CIPP Exam Preparation</h3><p>In preparation for the Certified Information Privacy Professional/Information Technology (CIPP/IT) exam, a privacy professional should be comfortable with topics related to this post, including:</p><ul><li>Methods of Data Collection (I.B.a.)</li><li>Privacy Concerns – Consumer Perspective (II.A.a.)</li><li>Government and Citizen Surveillance (II.A.k.)</li><li>Privacy Expectations – Consumer Behaviors (II.B.a.)</li><li>Online Privacy (V.D.i.1.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2011/03/29/justice-department-pushes-for-mandatory-data-retention/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>The Red Flag Rule, Delayed Enforcement and Amendments</title><link>https://www.cippguide.org/2010/12/28/the-red-flag-rule-delayed-enforcement-and-amendments/</link> <comments>https://www.cippguide.org/2010/12/28/the-red-flag-rule-delayed-enforcement-and-amendments/#comments</comments> <pubDate>Tue, 28 Dec 2010 17:00:07 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[FACTA]]></category> <category><![CDATA[FCRA]]></category> <category><![CDATA[FTC]]></category> <category><![CDATA[Identity Theft]]></category> <category><![CDATA[legislation]]></category> <category><![CDATA[Red Flags Rule]]></category> <category><![CDATA[threats]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2405</guid> <description><![CDATA[<p>It has been estimated that up to nine million Americans are victims of identity theft each year. However, consumers are largely unable to prevent or detect identity theft, rather depend on businesses and organizations to spot anomalies. For this reason, the Red Flags Rule was developed in order to spot warning signs (“red flags”), prevent identity theft and limit the damage that may be done. This article takes a closer look at the Red Flags Rule, as well as a recently introduced bill that may have important implications for the Rule.</p><p>Background: The Red Flags Rule
The FTC’s Identity Theft Red Flags [...]]]></description> <content:encoded><![CDATA[<p>It has been estimated that up to nine million Americans are victims of <a
href="https://www.cippguide.org/tag/identity-theft/">identity theft</a> each year. However, consumers are largely unable to prevent or detect identity theft, rather depend on businesses and organizations to spot anomalies. For this reason, the Red Flags Rule was developed in order to spot warning signs (“red flags”), prevent identity theft and limit the damage that may be done. This article takes a closer look at the Red Flags Rule, as well as a recently introduced bill that may have important implications for the Rule.</p><p>Background: The Red Flags Rule<br
/> The <a
href="https://www.cippguide.org/tag/ftc/">FTC</a>’s Identity Theft Red Flags Rule became effective on January 1, 2008. It was then delayed and the FTC set a target date for enforcement as of December 31, 2010. The reason for the delay was to give Congress enough time to finalize legislation limiting the scope of businesses covered by the Red Flags Rule. Any legislation passed by Congress limiting the scope of the Red Flags Rule with an effective date earlier than December 31, 2010 will be enforced by the FTC as of that date.</p><p>The Red Flags Rule was developed under the <a
href="http://www.treasury.gov/offices/domestic-finance/financial-institution/cip/pdf/fact-act.pdf">Fair and Accurate Credit Transactions Act</a> (FACTA), which requires the FTC, amongst other agencies, to develop regulations that require creditors and financial institutions to address the risk of identity theft. FACTA addressed the need for businesses to be involved in identity theft protection. It obliges financial institutions, creditors and other businesses that use consumer reports to detect and resolve identity theft-related fraud.</p><p>What are the “red flags”?<br
/> The Red Flags Rule requires businesses and organizations to implement a formal Identity Theft Prevention Program. Such a program should detect the “red flags,” or warning signs that identity theft may be taking place. Red flags are defined as “suspicious patterns or practices, or specific activities, that indicate the possibility of an identity theft.”</p><p>The Rule sets out that the Identity Theft Prevention Program be composed of the following four elements:</p><p>1. <strong>Identify relevant red flags</strong>: The Program should be made up of policies and procedures for identifying red flags during day-to-day operations.</p><p>2. <strong>Detect red flags</strong>: The Program should be designed to detect the red flags that have been identified.</p><p>3. <strong>Prevent and mitigate identity theft</strong>: The Program must outline appropriate actions for dealing with red flags.</p><p>4. <strong>Update the Program</strong>: The Program should periodically be re-evaluated, in order to appropriately address the evolving threat of identity theft.</p><p>When identifying red flags, it is important for the business or organization to consider the types of accounts that it offers or maintains; how these accounts are opened; and how customers have access to these accounts. There are five categories of common red flags, as outlined below:</p><p>• <strong>Alerts, Notifications and Warnings from a Credit Reporting Company. </strong>Changes in credit reports or credit activity may point towards identity theft. Such changes may include: a fraud alert on a credit report; notice of address discrepancy; or a notice of a credit freeze when a credit report is requested.</p><p>• <strong>Suspicious Documents.</strong> Examples include: altered/forged identification; inconsistencies between the person presenting the ID and the photo/physical description on the ID; or applications that appear altered/forged.</p><p>• <strong>Suspicious Personal Identifying Information.</strong> This may include: inconsistencies with other personally identifying information; fraudulent addresses, phone numbers, etc.; contact information that have been used by other individuals to open accounts; or a person who is unable to provide authenticating information.</p><p>• <strong>Suspicious Account Activity.</strong> Usage of the account can also signal fraud. For example: an account that is being used inconsistently; new accounts that are used in ways generally associated with fraud; inactive accounts are suddenly being used; or information regarding unauthorized charges on the account.</p><p>• <strong>Notice from Other Sources.</strong> Information that an account is being used fraudulently may come from customers, victims or identity theft, law enforcement authorities, etc.</p><p>Who is covered by the Red Flags Rule?<br
/> The Red Flags Rule applies to financial institutions and creditors. Under the Rule, a financial institution includes:<br
/> •	A state or national bank<br
/> •	A state or federal savings and loan association<br
/> •	A mutual savings bank<br
/> •	A state or federal credit union<br
/> •	Any entity that directly or indirectly holds a transaction account that belongs to a consumer</p><p>Under the rule, creditors are defined as:<br
/> •	Businesses or organizations which provide goods or services to customers first and allow them to pay later. Examples include: utilities, health care providers, lawyers, accountants and telecommunications companies.<br
/> •	Businesses or organizations that grant or arrange loans; extend credit; and make credit decisions. Examples include: finance companies, mortgage brokers, auto dealers, retailers that offer financing and retailers that collect/process credit applications for third parties.<br
/> •	Anyone who participates in decisions to extend, renew, continue credit, or in setting the terms of credit. Examples would include third-party debt collectors who negotiate the terms of the debt.</p><p>According to the FTC, businesses or organizations that have a low risk of identity theft are permitted to complete a do-it-yourself prevention guide. Risk is assessed through the following questions:<br
/> 1.	Do you know your clients personally?<br
/> 2.	Do you usually provide your services at customers’ homes?<br
/> 3.	Have you ever experienced an incident of identity theft?<br
/> 4.	Are you in a business where identity theft is uncommon?</p><p>H.R. 6420<br
/> The <a
href="http://www.huntonfiles.com/files/webupload/PrivacyLaw_red_flags_bill.pdf">Red Flag Program Clarification Act of 2010</a> (also referred to as H.R.6420) was first introduced on November 17, 2010 by Representative John Adler (D-NJ). The H.R. 6420 was drafted to “amend the Fair Credit Reporting Act (FCRA) with respect to the applicability of identity theft guidelines to creditors.” The objective of the bill is to limit the scope of the FTC Identity Theft Red Flags Rule.</p><p>The H.R. 6420 would limit the definition of “creditor” to exclude those “that advance funds on behalf of a person for expenses incidental to a service provided by the creditor to that person.” This definition would also apply to other creditors, if “such creditor offers or maintains accounts that are subject to a reasonably foreseeable risk of identity theft.” The H.R. 6420 was developed in order to respond to concerns that the current definition of “creditor” extends the scope of the Red Flag Rule inappropriately. A number of members of Congress voiced their concern that the Rule may include attorneys, law firms and health providers.</p><p>Summary<br
/> This article takes a look at the Red Flag Rule, which was developed under the FACTA (Fair and Accurate Credit Transactions Act). The purpose of the Rule was to ensure that businesses and organizations were taking the appropriate steps to prevent and respond to identity theft. Although the Rule became effective on January 1, 2008, its enforcement date has been repeatedly been postponed. Currently, the FTC must begin enforcing the Rule on December 31, 2010. This delay is due to the amendments that have been made to the Rule, the most recent being the H.R. 6420, or the Red Flag Program Clarification Act of 2010.</p><p>CIPP Exam Preparation<br
/> In preparation for the Certified Information Privacy Professional (CIPP) exam, a privacy professional should be comfortable with topics related to this post, including:<br
/> •	Regulatory Authorities – Federal Trade Commission (CIPP; I.A.c.i.)<br
/> •	Fair Credit Reporting Act of 1970 (CIPP; I.B.a.v.1.)<br
/> •	Fair and Accurate Credit Transactions Act of 2003 (CIPP; I.B.a.v.1.)<br
/> •	Incident Response Programs (CIPP; II.C.c.)</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%2F28%2Fthe-red-flag-rule-delayed-enforcement-and-amendments%2F&amp;title=The%20Red%20Flag%20Rule%2C%20Delayed%20Enforcement%20and%20Amendments" 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/28/the-red-flag-rule-delayed-enforcement-and-amendments/feed/</wfw:commentRss> <slash:comments>1</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_4"><img
src="https://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2010/12/14/do-i-need-to-apply-for-safe-harbor/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Firesheep &amp; User Privacy</title><link>https://www.cippguide.org/2010/11/23/firesheep-user-privacy/</link> <comments>https://www.cippguide.org/2010/11/23/firesheep-user-privacy/#comments</comments> <pubDate>Tue, 23 Nov 2010 12:00:24 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Information Security]]></category> <category><![CDATA[Privacy]]></category> <category><![CDATA[cookies]]></category> <category><![CDATA[Federal Trade Commission]]></category> <category><![CDATA[FTC]]></category> <category><![CDATA[HTTP]]></category> <category><![CDATA[HTTPS]]></category> <category><![CDATA[online privacy]]></category> <category><![CDATA[SSL]]></category> <category><![CDATA[threats]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2383</guid> <description><![CDATA[<p>Privacy risks are inherent to browsing and interacting online. The recently developed tool, Firesheep, draws attention to user vulnerabilities in web sessions. This article discusses some threats of HTTP session hijacking, as well as potential methods of reducing such threats.</p><p>HTTP Session Hijacking
Typically, users logging into a web site are requested to submit their user name and password. The server then verifies this information with a matching account. Once verified, the server sends back a cookie that is used by the user’s browser for subsequent requests. This initial login process is normally protected through encryption, however, the rest of the HTTP [...]]]></description> <content:encoded><![CDATA[<p>Privacy risks are inherent to browsing and interacting online. The recently developed tool, <a
href="http://codebutler.github.com/firesheep/">Firesheep</a>, draws attention to user vulnerabilities in web sessions. This article discusses some threats of HTTP session hijacking, as well as potential methods of reducing such threats.</p><p>HTTP Session Hijacking<br
/> Typically, users logging into a web site are requested to submit their user name and password. The server then verifies this information with a matching account. Once verified, the server sends back a <a
href="https://www.cippguide.org/tag/cookies/">cookie </a>that is used by the user’s browser for subsequent requests. This initial login process is normally protected through encryption, however, the rest of the HTTP session is usually not protected in the same way.</p><p>The practice of <a
href="http://en.wikipedia.org/wiki/Session_hijacking">HTTP session hijacking</a>, also referred to as “sidejacking,” describes an attack in which hackers obtain user’s cookies, which means they can appear to be acting as a user on the web site. This makes users especially vulnerable on open wireless networks.</p><p>Unfortunately, many web sites do not incorporate adequate protection mechanisms for their users. At this time, the only effective prevention is full end-to-end <a
href="https://www.cippguide.org/tag/cryptography/">encryption </a>(HTTPS or SSL). This ensures that traffic between the user and destination is kept private.</p><p>Point-and-Click Sidejacking<br
/> Firesheep is a Firefox extension created by Eric Butler, a freelance Web application developer and released on October 24, 2010. It demonstrates the danger of HTTP session hijacking attacks through from public WiFi spots. It is free and open source for Mac OS X and Windows, with Linux on the way. Firesheep enables users, technical minded or not, to hijack others’ social network connections on Facebook.</p><p>Facebook, like many other websites, authenticates users with cookies. If a user logs on through an open, unencrypted WiFi connection, the cookies can be detected. Firesheep relies on wincap to access the authentication information for different user accounts, allowing individuals to sidejack the connection.</p><p>A user running Firesheep on any open WiFi network will be notified as soon as anyone on the network visits an insecure web site. Firesheep then allows users to log into that site using the other user’s credentials. There is a wide-ranging scope of what Firesheep considers to be “insecure web sites;” Firesheep is designed to identify cookies from various sites, including:</p><p>•	Facebook<br
/> •	Foursquare<br
/> •	Gowalla<br
/> •	Amazon.com<br
/> •	Basecamp<br
/> •	bit.ly<br
/> •	Cisco<br
/> •	CNET<br
/> •	Dropbox<br
/> •	Enom<br
/> •	Evernote<br
/> •	Flickr<br
/> •	Github<br
/> •	Google<br
/> •	HackerNews<br
/> •	Harvest<br
/> •	Windows Live<br
/> •	NY Times<br
/> •	Pivotal Tracker<br
/> •	Slicehost<br
/> •	tumblr<br
/> •	Twitter<br
/> •	WordPress<br
/> •	Yahoo<br
/> •	Yelp</p><p>For each of the above web sites, it reports the victim’s name, user ID and even their photo, where available. While Firesheep runs on Firefox, it is able to sidejack any user, regardless of their operating system or web browser.</p><p>In Response…<br
/> Soon after the release of Firesheep, Facebook made its official response to the exposure of its security shortcomings:<br
/> “We have been making progress testing SSL access across Facebook and hope to provide it as an option in the coming months. As always, we advise people to use caution when sending or receiving information over unsecured WiFi networks.”</p><p>The <a
href="https://www.cippguide.org/tag/FTC/">Federal Trade Commission</a> (FTC) also recommends that users take the necessary precautions when transmitting sensitive personal information over public networks:<br
/> “Be careful about the information you access or send from a public wireless network. To be on the safe side, you may want to assume that other people can access any information you see or send over a public wireless network. Unless you can verify that a hot spot has effective security measures in place, it may be best to avoid sending or receiving sensitive information over that network.”</p><p>What is BlackSheep?<br
/> Created by Julien Sobrier and released on November 8, 2010, <a
href="http://www.zscaler.com/blacksheep.html">BlackSheep</a> was designed to respond to the Firesheep threat. It is a Firefox plug-in that functions as an early warning system when web sessions are at risk of being sidejacked, or already sidejacked by someone running Firesheep. According to Sobrier:<br
/> “If you used BlackSheep and were on WiFi, you could see a warning that someone on the same wireless network was using Firesheep. You would know someone is spying on you and trying to sniff your session, so you shouldn’t go to Facebook… It warns you to be careful.”</p><p>BlackSheep is actually based on Firesheep source code, reusing the same network listening back-end, the list of targeted web sites and corresponding cookies.</p><p>While BlackSheep does not block or disable Firesheep, the actual level of user protection is doubtful. Critics point out that there are many shortcomings in BlackSheep’s detection. They also argue that as Firesheep is capable of detecting and reporting fake cookies as errors, educated Firesheep users would be able to detect a user running BlackSheep.</p><p><a
href="http://www.eff.org/https-everywhere">HTTPS-Everywhere</a><br
/> Some argue that a far better solution to the Firesheep threat may be the HTTPS-Everywhere tool, which is another Firefox extension. This tool is the product of a collaboration between <a
href="http://www.torproject.org/">The Tor Project</a> and the <a
href="http://www.eff.org/">Electronic Frontier Foundation</a>. The HTTPS-Everywhere extension encrypts communications with various major websites, including:<br
/> •	Google Search<br
/> •	Facebook<br
/> •	Twitter<br
/> •	Wikipedia<br
/> •	GMX<br
/> •	WordPress<br
/> •	NY Times<br
/> •	Paypal<br
/> The HTTPS-Everywhere extension addresses the issue of incomplete encryption, in which web sites only encrypt on certain pages, but will default to unencrypted HTTP. The tool rewrites all requests to such sites to HTTPS. However, many web sites display content from third party domains that are often unavailable over HTTPS. The user will be notified of this vulnerability.</p><p><a
href="https://addons.mozilla.org/en-US/firefox/addon/12714/">Force-TLS</a><br
/> Similar to the HTTPS-Everywhere tool, Force-TLS is a Firefox extension that allows the browser to convert HTTP to HTTPS on indicated sites. Users are able to indicate such sites in their Firefox Add On Preferences menu. This protects users’ log in information and ensures more secure connections to social networking web sites. By avoiding the HTTP protocol, Force-TLS makes user cookies invisible to Firesheep attacks. It requires that web sites make their requests over an SSL-secured channel.</p><p>Summary<br
/> This article explores the threat of HTML session hijacking, which takes advantage of public WiFi networks to access web cookies, potentially allowing perpetrators to commit identity theft without the user’s knowledge. The recently developed Firefox extension, Firesheep, allows even basic web users to sidejack HTML sessions. This article also looks at some potential solutions and responses to the Firesheep tool, including BlackSheep, HTTPS-Everywhere and Force-TLS. Such tools draw attention to the reality that even with security measures, sending or receiving sensitive information over public wireless networks can put users at risk of privacy attacks.</p><p>CIPP Exam Preparation<br
/> In preparation for the Certification Foundation (Foundations) exam; and the Certified Information Privacy Professional/Information Technology (CIPP/IT) exam, a privacy professional should be comfortable with topics related to this post, including:<br
/> •	Online Privacy – Online Identification Mechanisms – Cookies (Foundations; III.B.g.i.)<br
/> •	Privacy Concerns – Revealing Private Information to Other Users (CIPP/IT; II.A.i.)<br
/> •	Privacy-Enhancing Technologies – Web Cookies (CIPP/IT; III.B.c.i.)<br
/> •	Web Security Protocols – TLS, SSL, HTTPS (CIPP/IT: III.B.c.iv.)</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%2F11%2F23%2Ffiresheep-user-privacy%2F&amp;title=Firesheep%20%26%23038%3B%20User%20Privacy" id="wpa2a_6"><img
src="https://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2010/11/23/firesheep-user-privacy/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Phone-Home Software</title><link>https://www.cippguide.org/2010/10/12/phone-home-software/</link> <comments>https://www.cippguide.org/2010/10/12/phone-home-software/#comments</comments> <pubDate>Tue, 12 Oct 2010 12:00:18 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[CIPP]]></category> <category><![CDATA[Privacy]]></category> <category><![CDATA[activation]]></category> <category><![CDATA[anti-piracy]]></category> <category><![CDATA[CIPP/IT]]></category> <category><![CDATA[computraceone]]></category> <category><![CDATA[EULA]]></category> <category><![CDATA[FTC]]></category> <category><![CDATA[genuine]]></category> <category><![CDATA[iTunes]]></category> <category><![CDATA[phone home]]></category> <category><![CDATA[WAT]]></category> <category><![CDATA[WGA]]></category> <category><![CDATA[windows]]></category><guid
isPermaLink="false">http://www.cippguide.org/?p=2224</guid> <description><![CDATA[Phoning home is a controversial issue for software manufacturers, developers and end-users. Phoning home refers to communication between a user’s software or hardware and the manufacturer. Certain applications may collect and store information about the end user and transmit it back “home” to the manufacturer. However, phone-home software has a number of different applications that include malicious and non-malicious uses. This article will explore various uses of phone-home software, as well as the security questions that are [...]]]></description> <content:encoded><![CDATA[<h1><span
style="font-weight: normal;font-size: 13px">Phoning home is a controversial issue for software manufacturers, developers and end-users. Phoning home refers to communication between a user’s software or hardware and the manufacturer. Certain applications may collect and store information about the end user and transmit it back “home” to the manufacturer. However, phone-home software has a number of different applications that include malicious and non-malicious uses. This article will explore various uses of phone-home software, as well as the security questions that are raised.</span></h1><h2>Applications of phone-home software</h2><p>Phone-home features have been integrated into numerous software titles for reasons including:</p><ul><li>Anti-piracy measures</li><li>Tracking lost/stolen hardware</li><li><a
href="http://www.cippguide.org/2010/08/17/access-controls/" target="_blank">Access control</a></li><li>Marketing purposes</li></ul><p>Often, the traffic on the end-user’s network is encrypted, so it can be difficult to determine exactly what data is being transmitted back to the manufacturer.</p><p>A well-known example of phone-home software is <a
href="http://en.wikipedia.org/wiki/Windows_Genuine_Advantage" target="_blank">Windows Genuine Advantage</a> (WGA). In 2005, Microsoft launched this application as part of an anti-piracy program. The installation of the application was required if users wanted to download further Windows updates. It checked if users were working from a licensed copy of Windows XP. Should a user be running a pirated version, the user would receive notifications. Finally, if no action was taken, the user would be blocked from downloading some updates.</p><p>WGA garnered much criticism in mid-2006 as users learned that it would “phone home” on a daily basis, without informing users of this function. In response to the controversy, Microsoft made significant adjustments to the phone home activities of WGA. Once systems were validated, WGA would cease connection attempts altogether. Systems that could not be validated would be restricted from certain automatic updates, downloads, installation procedures and some program executions. Microsoft also changed its <a
href="http://en.wikipedia.org/wiki/Software_license_agreement#Enforceability_of_EULAs_in_the_United_States" target="_blank">End User License Agreement</a> (EULA) to include more explicit information regarding the WGA. The EULA presented users with the choice to accept or reject the WGA procedures.</p><p>Microsoft was not the only one receiving criticism for its phone home practices at this time. Users of Apple’s Mac OS X were also noticing network activity, which was supposedly for the purposes of verifying Dashboard widgets. According to users, Apple did not inform them of the new feature or its activities. Such activity was only determined through the use of firewalls, which informed users when the program would attempt to establish outgoing internet connections. Although it was unclear what exactly was being communicated between the client and the server, users were obviously uncomfortable with the fact that their computers were automatically checking in with Apple.</p><p>Another example of phone-home software is the iTunes MiniStore, which introduced a feature that suggested music from the iTunes Music Store based on users’ song selections. This was one of many downloadable updates from Apple. However, the EULA for iTunes did not inform users that the application would transmit information about the user’s music preferences back to Apple. With the new feature, whenever a user selected a song, iTunes connected to the internet to update the MiniStore. User information would be passed to Apple through a third party.</p><p>Although the iTunes MiniStore feature could be disabled easily enough (by closing the pane), users were enraged that their personal information was being passed through third party without their consent. Even though this information was relatively harmless, users demanded that Apple make this feature clear and explain how it could be turned off.</p><h2>Windows Activation Technologies</h2><p>In February 2010, Microsoft announced a new anti-piracy initiative, referred to as <a
href="http://www.zdnet.com/blog/bott/windows-activation-technologies-an-unauthorized-inside-look/1803" target="_blank">Windows Activation Technologies</a> (WAT) update KB971033 for Windows 7. This would involve an automatic phone-home procedure to Microsoft servers every ninety days. The purpose of the WAT is to ensure that users are not using pirated versions of Windows. Critics have voiced concerns regarding the repeated authentication checks. These quarterly checks would mean that systems need to meet a certain set of criteria, or be subject to restrictions, even if that same system had previously been verified.</p><p>This could result in previously verified systems being downgraded to a non-genuine level. Such systems would still be able to function normally, but users may face some annoying changes. For instance, desktop backgrounds will periodically change to black, users would only have limited access to updates and piracy notifications will appear frequently.</p><p>The incentive for downloading and running WAT is still unclear to many users. While it may be important to identify if systems are running illegitimate versions of Windows 7, the downgrade process is largely unnecessary. Certain users may be concerned if their system is running a pirated version of Windows, which may have a chance of allowing viruses or other malware into their system. However, it may be more common that people are using legitimate copies that simply have not been authenticated yet.</p><p>While Microsoft insists that the WAT upgrade is completely voluntary, critics argue that consumers should not be tied to application manufactures as a result of cradle-to-grave authentication processes. This sort of surveillance regime is an unacceptable intrusion on the privacy of individuals and could potentially harm a large number of innocent computer users.</p><h2>Other uses</h2><p>Not all phone home applications receive a negative response from end-users. Certain tracking technology allows police to locate stolen computers across the world. One of the most effective types of tracking software is embedded within the BIOS of a computer’s motherboard. This software cannot be wiped or removed from the system. If the stolen computer attempts to connect to the internet, the phone home software transmits information to a monitoring center, reports the IP address and allows law enforcement officials to find its location. One such application, ComputraceOne, created by Absolute Software, claims to have helped recovered over 5,000 stolen computers.</p><h3>Summary</h3><p>This article explores the issue of phone-home features embedded in certain software. While phone-home features are found in spyware and other forms of malware, they are also integrated in legitimate software, such as Microsoft Windows, Apple OS and other applications. The feature may be used as an anti-piracy measure, to track lost or stolen hardware, to control access or for collecting information for marketing purposes. Security issues that are raised by such a feature include lack of disclosure to users, lack of consent, scope of functionality and level of surveillance.</p><h3>CIPP/IT Preparation</h3><p>In preparation for the Certified Information Privacy Professional/Information Technology exam, a privacy professional should be comfortable with topics related to this post, including:</p><ul><li>Privacy concerns and the consumer perspective (II.A.a.)</li><li>System monitoring (II.A.l.)</li><li>Phone-home software (II.A.l.i.)</li><li>Privacy expectations and consumer behaviors (II.B.a.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2010/10/12/phone-home-software/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Price Discrimination</title><link>https://www.cippguide.org/2010/10/05/price-discrimination/</link> <comments>https://www.cippguide.org/2010/10/05/price-discrimination/#comments</comments> <pubDate>Tue, 05 Oct 2010 12:00:02 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[CIPP]]></category> <category><![CDATA[Compliance & Regulations]]></category> <category><![CDATA[Amazon]]></category> <category><![CDATA[CIPP/IT]]></category> <category><![CDATA[coupons]]></category> <category><![CDATA[dell]]></category> <category><![CDATA[ecommerce]]></category> <category><![CDATA[FTC]]></category> <category><![CDATA[price discrimination]]></category> <category><![CDATA[US PIRG]]></category><guid
isPermaLink="false">http://www.cippguide.org/?p=2222</guid> <description><![CDATA[Price discrimination is a strategy that is frequently used by commercial organizations as a way of distinguishing between different groups of customers. By separating consumers into subcategories, companies can charge different prices for the same goods or services.With the rapid growth of e-commerce, companies are able to experiment with and implement different price discrimination strategies. Online consumers consciously and unconsciously provide vendors with information that helps them to split the market into segments for price discrimination. This article introduces basic concepts involved in price discrimination, as well as some of the impacts on consumers’ [...]]]></description> <content:encoded><![CDATA[<h1><span
style="font-weight: normal;font-size: 13px">Price discrimination is a strategy that is frequently used by commercial organizations as a way of distinguishing between different groups of customers. By separating consumers into subcategories, companies can charge different prices for the same goods or services.</span></h1><p>With the rapid growth of <a
href="http://en.wikipedia.org/wiki/Electronic_commerce" target="_blank">e-commerce</a>, companies are able to experiment with and implement different price discrimination strategies. Online consumers consciously and unconsciously provide vendors with information that helps them to split the market into segments for price discrimination. This article introduces basic concepts involved in price discrimination, as well as some of the impacts on consumers’ privacy.</p><h2>What is Price Discrimination?</h2><p>Price discrimination is also referred to as yield management. This takes place when a company charges varying prices to different groups of customers, for the same goods or services. This variation in price is not related to the cost of the good or service provided. The different groups of customers are referred to as segmented markets.</p><p>Price discrimination is a strategy that is employed by almost every industry that has some power to determine prices. There are a number of different types of price discrimination:</p><ol><li>Optimal Pricing:  This is also referred to as perfect price discrimination. With this type of price discrimination, the vendor charges each individual the price that they are willing and/or able to pay. This heavily depends on how much information the vendor has regarding the consumer’s preferences. For the most part, this type of price discrimination is considered unattainable.</li><li>Second Degree Price Discrimination:  With this form of price discrimination, vendors sell a product that is surplus capacity at a lower price than the standard or advertised price. This type of price discrimination is independent of any personal information from consumers. An example of this is the sale of standby airline seats. Second degree price discrimination has been advanced by developments in e-commerce.</li><li>Third Degree Price Discrimination:  This is also referred to as multi-market price discrimination. With this type of price discrimination, the market is segmented, for instance in terms of time or geography. It is a common type of price discrimination that depends on charging different prices, depending on the segment of the market.</li></ol><p>Price discrimination is not a new strategy; it has been applied throughout history. However, it is often not publicized, as it incites negative public responses. However, proponents argue that despite the inequitable treatment of individuals, on a larger scale, the practice may offer a more efficient use of resources. With the development of new technologies, companies are finding ways to price discriminate that may not have been possible before.</p><h2>E-Commerce &amp; Price Discrimination</h2><p>With the rise of e-commerce, there has been a steady erosion of privacy. Privacy professionals and other observers have identified this as a continuing trend with the internet. The vast majority of privacy invasions stem from the private sector. Seemingly, with better information about consumers, vendors can more appropriately target their advertising dollars. In the past, companies needed to invest heavily into gathering personal information and monitoring the spending habits of consumers, current technology makes price discrimination a commercially feasible practice.</p><p>With <a
href="http://en.wikipedia.org/wiki/Ubiquitous_computing" target="_blank">ubiquitous computer systems</a>, vendors can engage in more “intelligent” transactions, recording information about the environment and consumer conditions. Information about consumers may be collected through repeated interactions between vendor and seller. For instance, cookies may be used to track consumer purchasing habits. This allows vendors to refine the information about their customer base and dynamically change pricing schemes to respond to the information.</p><p>This practice may bring about both positive and negative results. For instance, customers may enjoy personalized treatment, such as discounts, suggested products and individualized content. On the other hand, many customers are wary of <a
href="http://www.cippguide.org/2010/04/20/recommendations-for-identity-theft-related-data-breach-notification/" target="_blank">potential privacy invasions</a>. Consumers are generally not pleased to learn that a vendor engages in price discrimination; no one wants to pay more than someone else for the same item.</p><p>Common examples of price discrimination include:</p><ul><li>Dell Computers selling the same model laptop to different markets (i.e. individuals, small businesses, enterprises and governments) at different prices.</li><li>Vendors charging customers at different rates, depending on their IP address.</li><li>Amazon.com drawing on customer’s past purchases and spending habits to charge different prices for DVDs.</li></ul><h2>Web Coupons</h2><p>Coupons retrieved from the internet are a rapidly growing segment of the coupon industry. Such coupons are accessed and printed from the internet and may carry with them a lot of consumer information, such as their IP address, <a
href="http://www.cippguide.org/tag/PII/" target="_blank">personally identifiable information</a> and the search terms used to find the coupon. While this form of tracking may be invisible to consumers, vendors may be able to collect such information simply by scanning the bar code of the coupon.</p><p>Many web coupons are handled by third party service providers, who may collect and analyze vast amounts of information about clients for the retailers. Well-known web coupon companies include RevTrax, FatWallet and Ebates.com. Vendors may also be able to narrow down their customer base by sending specific keyword searches to different web addresses. These addresses may be invisible to the consumer, who may only be able to see a simple, standard web address. Information collected online may be combined with data from offline databases that could significantly be harmful to consumers. Such information is collected, not only without individual consent, but without any form of transparency or accountability.</p><h2>Legal Issues</h2><p>The issues that have been raised by e-commerce and other online practices have significant implications on law and technology. Currently, the US antitrust law specifically addresses price discrimination. The <a
href="http://en.wikipedia.org/wiki/Robinson%E2%80%93Patman_Act" target="_blank">Robinson-Patman Act of 1936</a> states that it is illegal for vendors to treat their customers differently, unless they have an acceptable legal justification for such treatment. However, the <a
href="http://www.cippguide.org/tag/FTC/" target="_blank">FTC </a>has hardly applied the Act in the recent past. The Robinson-Patman Act has even been considered irrelevant in terms of dynamic pricing in an e-commerce context.</p><p>Critics have argued that the Act is not really designed to protect consumer rights. This is highly problematic for privacy advocates, who believe that private sector interests are unfairly targeting and classifying individuals without their consent. Recently, the US PIRG (<a
href="http://www.uspirg.org/" target="_blank">United States Public Interest Research Group</a>) has partnered with the <a
href="http://www.democraticmedia.org/" target="_blank">Center for Digital Democracy</a> and <a
href="http://www.worldprivacyforum.org/" target="_blank">World Privacy Forum</a> in order to urge the FTC to review online consumer tracking practices.</p><h3>Summary</h3><p>This article explores the issue of price discrimination. It discusses three main types of the price discrimination practice: optimal pricing; second degree price discrimination and third degree price discrimination. The article examines how price discrimination has become more prominent with the developments in e-commerce and how practices such as web coupons intensify the risk of privacy intrusions. The lack of relevant, up-to-date legislation around this issue is also discussed.</p><h3>CIPP/IT Preparation</h3><p>In preparation for the Certified Information Privacy Professional/Information Technology exam, a privacy professional should be comfortable with topics related to this post, including:</p><ul><li>E-commerce personalization (II.A.d.)</li><li>Price discrimination (II.A.h.)</li><li>Privacy expectations and consumer behaviors (II.B.a.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2010/10/05/price-discrimination/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Identity Theft Task Force Recommendations</title><link>https://www.cippguide.org/2010/04/13/identity-theft-task-force-recommendations/</link> <comments>https://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>https://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>https://www.cippguide.org/2010/01/28/ftc-enforcement-gateway-learning/</link> <comments>https://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>https://www.cippguide.org/2010/01/28/ftc-enforcement-gateway-learning/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-04 13:27:38 -->
