<?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; privacy policy</title> <atom:link href="http://www.cippguide.org/tag/privacy-policy/feed/" rel="self" type="application/rss+xml" /><link>https://www.cippguide.org</link> <description>Your Guide to the CIPP</description> <lastBuildDate>Tue, 07 Feb 2012 12:00:10 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>US Department of Homeland Security: Privacy Policies &amp; Practices</title><link>https://www.cippguide.org/2012/01/24/us-department-of-homeland-security-privacy-policies-practices/</link> <comments>https://www.cippguide.org/2012/01/24/us-department-of-homeland-security-privacy-policies-practices/#comments</comments> <pubDate>Tue, 24 Jan 2012 12:00:07 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[Chief Privacy Officer]]></category> <category><![CDATA[DHS]]></category> <category><![CDATA[FOIA]]></category> <category><![CDATA[PIA]]></category> <category><![CDATA[PII]]></category> <category><![CDATA[Privacy Act]]></category> <category><![CDATA[privacy policy]]></category> <category><![CDATA[PTA]]></category> <category><![CDATA[SORN]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2696</guid> <description><![CDATA[The US Department of Homeland Security (DHS) is often criticized for its privacy policies and practices, as it handles a vast amount of sensitive personal information. However, it is important to note how the DHS does attempt to protect personal privacy, in policy as well as practice. In addition to compliance with federal privacy legislation, such as the FOIA (Freedom of Information Act) and the Privacy Act, the Department consults with privacy professionals in order to evaluate new or potential programs, systems, technologies and certain rule-making procedures in order to appropriately handle personal information. This article takes a look at exactly how the Department of Homeland Security approaches privacy [...]]]></description> <content:encoded><![CDATA[<p>The US <a
href="http://www.dhs.gov/">Department of Homeland Security</a> (DHS) is often criticized for its privacy policies and practices, as it handles a vast amount of sensitive personal information. However, it is important to note how the DHS does attempt to protect personal privacy, in policy as well as practice. In addition to compliance with federal privacy legislation, such as the <a
href="http://www.cippguide.org/tag/foia/">FOIA</a> (Freedom of Information Act) and the <a
href="http://www.cippguide.org/tag/privacy-act/">Privacy Act</a>, the Department consults with privacy professionals in order to evaluate new or potential programs, systems, technologies and certain rule-making procedures in order to appropriately handle personal information. This article takes a look at exactly how the Department of Homeland Security approaches privacy protection.</p><p><strong>Compliance</strong></p><p>The DHS has a very specific privacy compliance process. The DHS Privacy Office is responsible for the assessment of all new or proposed Department activities in order to ensure responsible handling of <a
href="https://www.cippguide.org/tag/pii/">personally identifiable information</a> (PII) and to mitigate privacy risks.</p><p>The following explores the methods by which the Privacy Office ensures compliance in all departmental activities:</p><ul><li><a
href="http://www.dhs.gov/xlibrary/assets/privacy/privacy_pta_template.pdf"><strong>Privacy Threshold Analysis</strong></a><strong> (PTA)</strong> – The PTA is a required document that serves as the official determination by the Privacy Office in order to determine if a DHS program or system has privacy implications. Also, PTAs are used to determine of additional privacy compliance documentation is required. PTAs are designed into all DHS processes for technology investments and security. They expire every three years.</li></ul><p>PTAs serve the following objectives:</p><ul><li>Identify privacy-sensitive programs and systems</li><li>Demonstrate inclusion of privacy considerations during the review of a program or system</li><li>Provide the Privacy Office with a record of the program or system, as well as its privacy requirements</li><li>Demonstrate compliance with privacy laws and regulations</li><li><strong><a
href="https://www.cippguide.org/tag/pia/">Privacy Impact Assessment</a></strong><strong>(PIA)</strong> – The PIA is a decision-making tool that is used to identify and mitigate privacy risks at the start, as well as throughout the development lifecycle of a program or system. PIAs aid the public in understanding what PII the DHS is collecting, why the information is being collected, and how it will be used, shared, accessed and stored.</li></ul><p>PIAs are required for the following reasons:</p><ul><li>When developing or procuring any new DHS program or system that will handle or collect PII</li><li>For budget submissions to the <a
href="http://www.cippguide.org/tag/omb/">Office of Management and Budget</a> (OMB) that affect PII</li><li>With pilot tests that affect PII</li><li>When developing program or system revisions that affect PII</li><li>When issuing a new or updated rulemaking that involves collection, use and maintenance of PII</li><li><strong><a
href="https://www.cippguide.org/tag/sorn/">System of Records Notice</a></strong><strong>(SORN)</strong> – A `system of records’ is a group of records under the control of any federal agency from which information is retrieved by a unique personal identifier assigned to an individual. A SORN is a formal notice to the public that identifies the purpose for which PII is collected, from whom and what type of PII is collected, how the PII is shared externally (i.e. routine uses) and how to access or correct any PII maintained by the DHS.</li></ul><p><strong>DHS Privacy Office</strong></p><p>The <a
href="http://www.dhs.gov/xabout/structure/editorial_0510.shtm#contact">DHS Privacy Office</a> is the first statutorily created privacy office in the Federal government. The Office operates under the direction of the Chief Privacy Officer, a position that is discussed in further detail in the following section. The <a
href="http://www.dhs.gov/xabout/structure/editorial_0510.shtm#contact">mission</a> of the Privacy Office is: “… to preserve and enhance privacy protections for all individuals, to promote transparency of DHS operations, and to serve as a leader in the privacy community.”</p><p>The Privacy Office carries out the following activities:</p><ul><li>Requires compliance with the letter and spirit of Federal laws that protect privacy</li><li>Centralizes FOI and Privacy Act operations to provide policy and programmatic oversight and to support operational implementation within the DHS components</li><li>Provides education and outreach to build a culture of privacy and adherence to the Fair Information Practice Principles (FIPPs) across the DHS</li><li>Provides transparency to the public through published materials, formal notices, public workshops and meetings</li></ul><p>The Privacy Office is made up of the following operational teams:</p><ul><li>International Privacy Policy</li><li>Departmental Disclosure and FOIA</li><li>Privacy Compliances</li><li>Privacy Policy (includes communications and training)</li><li>Privacy Incidents and Inquiries</li><li>Privacy Technology and Intelligence</li><li>Legislative and Regulatory Analysis</li></ul><p><strong>Chief Privacy Officer, DHS</strong></p><p>The <a
href="http://www.dhs.gov/xabout/structure/bio_1236273286409.shtm">Chief Privacy Officer</a> (CPO) is a position within the DHS, appointed by the US Secretary of Homeland Security. The CPO also serves as the Chief Freedom of Information Act (FOIA) Officer at the DHS Privacy Office.</p><p>According to Section 222 of the Homeland Security Act of 2002, the CPO is primarily responsible for the privacy policy at the DHS. Duties include:</p><ul><li>Assuring that technologies used by the DHS to protect the US sustain, rather than erode, privacy protections related to the use, collection and disclosure of personal information</li><li>Assuring that the DHS complies with fair information practices set out in the Privacy Act of 1974</li><li>Conducting privacy impact assessments (PIA) of proposed rules at the DHS</li><li>Evaluating legislative and regulatory proposals involving the collection, use and disclosure of personal information by the Federal government</li><li>Preparing an annual report to Congress on DHS activities that affect privacy</li></ul><p><strong>Summary</strong></p><p>This article takes a look at the privacy policies and practices at the US Department of Homeland Security (DHS). In addition to compliance with federal privacy legislation, the DHS also has its own privacy guidance, which include security methodologies, as well as a Privacy Office that is responsible for the oversight of systems and programs that deal with personally identifiable information. The article takes a closer look at the DHS Privacy Office, the first statutorily created privacy office in the US federal government, as well as the unique role of the Chief Privacy Officer/Chief Freedom of Information Act (FOIA) Officer.</p><p><strong>CIPP Exam Preparation</strong></p><p>In preparation for the Certified Information Privacy Professional/US Government (CIPP/G) exam, a privacy professional should be comfortable with topics related to this post, including:</p><ul><li>Privacy Policy Approaches – Department of Homeland Security (II.A.e.ii.3.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2012/01/24/us-department-of-homeland-security-privacy-policies-practices/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Approaches to Privacy Policy Enforcement &#8211; US Federal Departments &amp; Agencies</title><link>https://www.cippguide.org/2012/01/17/approaches-to-privacy-policy-enforcement-us-federal-departments-agencies/</link> <comments>https://www.cippguide.org/2012/01/17/approaches-to-privacy-policy-enforcement-us-federal-departments-agencies/#comments</comments> <pubDate>Tue, 17 Jan 2012 12:00:45 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[Census Bureau]]></category> <category><![CDATA[DoD]]></category> <category><![CDATA[FOIA]]></category> <category><![CDATA[IRS]]></category> <category><![CDATA[Privacy Act]]></category> <category><![CDATA[privacy policy]]></category> <category><![CDATA[stewardship]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2694</guid> <description><![CDATA[Guided by privacy legislation and internal privacy policies, US federal government agencies and departments strive to protect citizens’ personal information and privacy rights. This article introduces the privacy practices of three federal departments: the US Census Bureau, the Internal Revenue Service (IRS) and the US Department of [...]]]></description> <content:encoded><![CDATA[<p>Guided by privacy legislation and internal privacy policies, US federal government agencies and departments strive to protect citizens’ personal information and privacy rights. This article introduces the privacy practices of three federal departments: the US Census Bureau, the Internal Revenue Service (IRS) and the US Department of Defense.</p><p><strong>US Census Bureau: Data Stewardship</strong></p><p>The Census Bureau’s objective is to produce accurate, relevant statistics on US economy and population. It is legally and ethically obligated to protect the privacy and confidentiality of the individuals who offer their data. According to the Bureau’s mission statement, “We honor privacy, protect confidentiality, share our expertise globally, and conduct our work openly.” One of the Bureau’s strategic goals is to “Foster an environment that supports innovation, reduces respondent burden, and ensures individual privacy.” The approach that the Census Bureau takes to maintain the trust of US citizens is referred to as “Data Stewardship.”</p><p>Data stewardship is the formal process by which the Bureau remains responsible and accountable for data protection throughout the data lifecycle. This is the time which someone responds to a survey, all the way to the release of statistical data products. Each survey and program under the Census Bureau’s responsibility is required to comply with data stewardship policies at every step in the process.</p><p>There are three ways that the Bureau protects personal information:</p><ol><li><strong>Federal Law</strong> – Federal law protects personal information. Title 13 of the US Code protects the confidentiality of all information provided to the Bureau. Violation of Title 13 results in severe penalties.</li><li><strong>Privacy Principles</strong> – In addition to federal legislation, the Bureau has developed its own set of privacy principles, which are guidelines for all its activities. Privacy principles include the Bureau’s responsibilities to protect personal information, as well as individuals’ rights as survey respondents.</li><li><strong>Statistics Safeguards</strong> – These include methods to ensure that statistics released by the Bureau do not identify individuals or businesses. All data products are extensively reviewed and analyzed. Disclosure avoidance methodologies (e.g. data suppression, data modification) are also applied.</li></ol><p><strong>IRS: Privacy Office</strong></p><p>Like other federal agencies, the IRS is committed to protecting Americans’ privacy rights. It notes that individuals’ privacy rights are protected by the following:</p><ul><li>Internal Revenue Code</li><li>Privacy Act of 1974</li><li>Freedom of Information Act</li><li>IRS policies and practices</li></ul><p>In addition to adhering to the above, the IRS also has a Privacy Office, which ensures that personal information entrusted with the IRS is protected appropriately. The Office addresses questions regarding IRS privacy policies and concerns regarding how the IRS uses and collects personal information.</p><p><strong>Department of Defense: Privacy Policy</strong></p><p>The Department of Defense (DoD) provides a <a
href="http://defense.gov/">website</a> as a public service by the Office of the Assistant Secretary of Defense – Public Affairs. Like other websites, there are options for individuals to offer the DoD personal information and the DoD is responsible for treating this information appropriately. The Dod maintains a wide variety of physical, electronic and procedural safeguards to protect personal information from unauthorized disclosure or data breach.</p><p>According to the DoD’s website <a
href="http://defense.gov/landing/privacy.aspx">Privacy Act Statement</a>:</p><p>“If you choose to provide us with personal information… we will only use that information to respond to your message or request. We will only share the information you give us with another government agency if your inquiry relates to that agency, or as otherwise required by law. We never create individual profiles or give it to any private organizations. Defense.gov never collects information for commercial marketing.”</p><p><strong>Summary</strong></p><p>This article takes a look at approaches to privacy protection at various agencies of the US federal government: the US Census Bureau, the Internal Revenue Service (IRS) and the US Department of Defense (DoD). Each department or agency is guided by federal privacy legislation, as well as internal policies and practices.</p><p><strong>CIPP Exam Preparation</strong></p><p>In preparation for the Certified Information Privacy Professional/US Government (CIPP/G) exam, a privacy professional should be comfortable with topics related to this post, including:</p><ul><li>Privacy Policy Enforcement – Sample Approaches (II.A.e.ii.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2012/01/17/approaches-to-privacy-policy-enforcement-us-federal-departments-agencies/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Apple’s Tracking Concerns: Location Database on the iPhone &amp; 3G iPad</title><link>https://www.cippguide.org/2011/09/20/apple%e2%80%99s-tracking-concerns-location-database-on-the-iphone-3g-ipad/</link> <comments>https://www.cippguide.org/2011/09/20/apple%e2%80%99s-tracking-concerns-location-database-on-the-iphone-3g-ipad/#comments</comments> <pubDate>Tue, 20 Sep 2011 17:00:45 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[Apple]]></category> <category><![CDATA[data breaches]]></category> <category><![CDATA[data collection]]></category> <category><![CDATA[GPS]]></category> <category><![CDATA[location data]]></category> <category><![CDATA[mobile devices]]></category> <category><![CDATA[privacy policy]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2587</guid> <description><![CDATA[In April 2011, there was increased public awareness regarding the collection and storage of location-based data on Apples iPhones and 3G iPads. The resulting responses ranged from outrage and fear to interest in the possible apps that could be developed using the information. [...]]]></description> <content:encoded><![CDATA[<p>In the last month or so, anyone with an interest in data privacy issues has been aware of the string of disturbing data breaches that have made headlines. <a
href="http://www.apple.com/">Apple</a> product users have certainly been following developments since the company’s data collection practices surfaced in April 2011.</p><p><strong>Apple’s Location Database</strong></p><p>It’s common knowledge that Apple’s iPhones and 3G-enabled iPads have been keeping track of their users’ location data. While Apple has publicly acknowledged that its iOS devices send location data back to the company, researchers have also revealed that the devices can record the history of the users’ movements for a year or more. Researchers found that Apple devices have been storing the location data in an unencrypted database, which was then backed up onto whatever computer the iPhone or iPad was syncing to.</p><p>This raised concerns, especially as this location database has been accessible to law enforcement and computer forensics communities as of last year. These communities have been using the database to gather evidence on individuals’ movements.</p><p>In response to the collection, there was understandable outrage over privacy violations. To many, it seemed unclear if users had agreed to this collection. Others also wondered where the information was ultimately being stored, how it was being used and why it hadn’t been protected better.</p><p>Other reactions were more positive. Many rushed to download the <a
href="http://petewarden.github.com/iPhoneTracker/">iPhone Tracker</a>, an open-source app that maps the location data being collected by users’ devices. Such users seemed unconcerned about the potential invasion of privacy, instead wanting to share their personal information with other users.</p><p><strong>Not really a surprise?</strong></p><p>Privacy concerns about Apple’s products are not new. Last June, Congress took the opportunity to question Apple CEO Steve Jobs over the company’s privacy policy and the collection of personal information. This was in response to Apple’s updated <a
href="http://www.apple.com/privacy/">privacy policy</a>, which stated that their devices will collect location data and share the data with third parties. The text read:</p><p>To provide location-based services on Apple products, Apple and our partners and licensees may collect, use, and share precise location data, including the real-time geographic location of your Apple computer or device. This location data is collected anonymously in a form that does not personally identify you and is used by Apple and our partners and licensees to provide and improve location-based products and services. For example, we may share geographic location with application providers when you opt in to their location services.</p><p>Proponents of location-based apps argue that such data can have legitimate uses and don’t necessarily have to be privacy-sensitive, if the information is anonymized properly. For instance, location data can be filtered to provide traffic data for navigation apps and to map Wi-Fi access points, in order to facilitate quick location fixes.</p><p><strong>The case for collection… </strong></p><p>In a recent interview given at the end of April 2011, Apple CEO Steve Jobs said the iPhone database that had many consumers up in arms was actually a piece of a global crowdsourced database that Apple uses to deliver location-based information. <a
href="http://mobilized.allthingsd.com/20110427/exclusive-apple-ceo-steve-jobs-on-how-the-iphone-does-and-doesnt-use-location-information/">According to Jobs</a>, “We haven’t been tracking anyone. The files they found on these phones, as we explained, it turned out were basically files we have built through anonymous, crowdsourced information that we collect from the tens of millions of iPhones out there.”</p><p>Jobs did admit that the company had found a bug in the program, which led to the location data cache to be stored on phones that had their location data switched off. He promised that this would be corrected in a future update and that a smaller amount of data would be stored on the phone. It was stressed that Apple did not track iPhone users’ locations, but instead, users needed to turn on their location-based information as well as allow such collection for each application. Jobs pointed out users had a way to see which applications have been using their location information, currently as well as over the past 24 hours.</p><p><strong>Summary</strong></p><p>This article takes a look at the privacy concerns raised when researchers discovered the collection and storage of location-based data on Apple’s iPhones and 3G iPads, during April 2011. This discovery resulted in a number of responses from the public, ranging from outrage and fear to interest in the possible apps that could be developed utilizing such information. Apple CEO Steve Jobs explained that the devices were not tracking users; rather the location database was built from anonymous crowdsourced information.</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>Personally Identifiable Information – PII (I.A.a.)</li><li>Methods of Data Collection (I.B.a.)</li><li>Consumer Privacy Concerns (II.A.a.)</li><li>Phone-Home Software (II.A.l.i.)</li><li>Prominent &amp; Inconspicuous Notice (IV.A.)</li><li>Location-Based Services (VI.E.)</li></ul><p>&nbsp;</p> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2011/09/20/apple%e2%80%99s-tracking-concerns-location-database-on-the-iphone-3g-ipad/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Components of a Privacy Policy</title><link>https://www.cippguide.org/2011/08/09/components-of-a-privacy-policy/</link> <comments>https://www.cippguide.org/2011/08/09/components-of-a-privacy-policy/#comments</comments> <pubDate>Tue, 09 Aug 2011 17:00:41 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[Information Security]]></category> <category><![CDATA[Notice]]></category> <category><![CDATA[opt-in]]></category> <category><![CDATA[PII]]></category> <category><![CDATA[privacy by policy]]></category> <category><![CDATA[privacy policy]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2593</guid> <description><![CDATA[Enterprise privacy policies and privacy programs are essential. While policies alone cannot prevent data breaches or misuse of personal information, they are a good step in ensuring transparency and privacy-friendly practices. A privacy policy should contain the following key components: notice; consumer choice; access and correction; security; and [...]]]></description> <content:encoded><![CDATA[<p>It seems that <a
href="http://en.wikipedia.org/wiki/Privacy_policy">privacy policies</a>, notices and statements are everywhere these days. Given the increased public interest and more stringent <a
href="https://www.cippguide.org/tag/legislation/">legislation</a> on <a
href="http://www.cippguide.org/tag/infosec/">information security</a> and privacy protection, these privacy-friendly mechanisms are becoming more and more important on websites and online services. Generally, privacy policies, privacy notices and privacy statements tend to follow a specific format, use the same vocabulary and style.</p><p>It’s important to ensure that website privacy policies correctly address specific legal issues and technical implications of the company. There are numerous types of privacy policies out there, some of which apply to online data; others apply to data collected by financial institutions; others that deal with the collection of information from children under the age of 13; and other policies that apply to individuals protected under foreign laws. There is no ‘one size fits all’ approach to developing a sound privacy policy.</p><p><strong>Enterprise Privacy Programs</strong></p><p>Developing and maintaining enterprise-wide privacy programs require top-down cooperation and collaboration of the different individuals in an enterprise.</p><p>According to United States privacy legislation, all companies involved in obtaining, maintaining, using and/or disclosing personal information about consumers ought to adopt a privacy policy. Privacy policies are documents in which companies state their information practices. Such documents keep organizations accountable to a set of formal privacy policies. Companies may be the subject of an <a
href="http://www.cippguide.org/tag/FTC/">FTC</a> action or a lawsuit if their privacy practices do not accurately reflect those stated in their privacy policy.</p><p>Standardization of enterprise privacy programs is becoming more and more of an issue in recent years. Even though the primary objective of enterprise privacy policies is for internal use, standardization of such policies brings numerous advantages:</p><ul><li>Technical parts of regulations could be encoded into a standardized language</li><li>Enterprises with heterogeneous repositories of personal data could develop consistent enforcement tools to ensure compliance with internal privacy practices</li></ul><p><strong>Components of a Privacy Policy</strong></p><p>There are three main categories of information in a privacy policy:</p><ol><li><strong>1. </strong><strong>Policy Identification Details</strong></li></ol><p>This section defines the policy name, version and description.</p><ol><li><strong>2. </strong><strong>P3P-Based Components</strong></li></ol><p>This defines policy attributes that would apply if the policy is exported to a <a
href="https://www.cippguide.org/tag/p3p/">P3P</a> format. Such attributes would include: policy URLs, organization information, <a
href="https://www.cippguide.org/tag/PII/">PII</a> access and dispute resolution procedures.</p><ol><li><strong>3. </strong><strong>Policy Statements and Related Elements: Groups, Purposes and PII Types</strong></li></ol><p>Policy statements define the individuals able to access certain types of information, for certain pre-defined purposes.</p><p>Another way to classify the components of a privacy policy is outlined below.</p><ul><li><strong>Notice</strong> – Companies should provide consumers with clear, conspicuous notice that accurately describe their information practices.</li><li><strong>Consumer Choice</strong> – Companies should provide consumers with the opportunity to decide (in the form of opting-out) if it may disclose personal information to unaffiliated third parties.</li><li><strong>Access and Correction</strong> – Companies should provide consumers with the opportunity to access and correct personal information collected about the consumer.</li><li><strong>Security</strong> – Companies must adopt reasonable security measures in order to protect the privacy of personal information. Possible security measures include: administrative security, physical security and technical security.</li><li><strong>Enforcement</strong> – Companies should have systems through which they can enforce the privacy policy. This may be managed by the company, or an independent third party to ensure compliance. Examples include <a
href="https://www.cippguide.org/tag/bbbonline/">BBBOnLine</a> and <a
href="https://www.cippguide.org/tag/truste/">TRUSTe</a>.</li></ul><p><strong>Consumer’s Point of View</strong></p><p>From a consumer’s point of view, just because a website has a privacy policy doesn’t necessarily guarantee the security of the personal information. No privacy policy can definitely ensure the security of your information, or bind a company to those specific practices; however, there are certain policies that are better than others. A privacy policy should provide the consumer with a sense of transparency regarding the company.</p><p>Some important things that a consumer should consider when looking for good privacy policy include:</p><ul><li>What personal information is being collected?</li><li>How will your personal information be used?</li><li>How will your personal information be stored?</li><li>Are there security measures protecting your personal information?</li><li>How long will your personal information be kept by the company?</li><li>Will your personal information be shared with others?</li><li>How can you contact the company?</li></ul><p><strong>Summary</strong></p><p>This article takes a look at the importance of an enterprise privacy policies and privacy programs. While policies alone cannot prevent data breaches or misuse of personal information, they are a good step in ensuring transparency and privacy-friendly practices. A privacy policy should contain the following key components: notice; consumer choice; access and correction; security; and enforcement. The article also lists some considerations consumers should take when assessing the reliability of a company’s privacy policy.</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>Personally Identifiable Information (PII) (I.A.a.)</li><li>Consumer privacy concerns (II.A.a.)</li><li>Organizational privacy practices (II.A.b.)</li><li>Prominent notice and opt-in consent (II.B.b.)</li><li>Privacy mechanisms – privacy by policy (III.A.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2011/08/09/components-of-a-privacy-policy/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> <item><title>COPPA: The Children&#039;s Online Privacy Protection Act</title><link>https://www.cippguide.org/2010/01/11/coppa-the-childrens-online-privacy-protection-act/</link> <comments>https://www.cippguide.org/2010/01/11/coppa-the-childrens-online-privacy-protection-act/#comments</comments> <pubDate>Mon, 11 Jan 2010 12:00:34 +0000</pubDate> <dc:creator>jbrook</dc:creator> <category><![CDATA[CIPP]]></category> <category><![CDATA[Compliance & Regulations]]></category> <category><![CDATA[Privacy]]></category> <category><![CDATA[Attorney General]]></category> <category><![CDATA[COPPA]]></category> <category><![CDATA[FTC]]></category> <category><![CDATA[Parental Consent]]></category> <category><![CDATA[privacy policy]]></category> <category><![CDATA[Safe Harbor]]></category> <category><![CDATA[SEC.1305]]></category><guid
isPermaLink="false">http://www.cippguide.org/?p=1190</guid> <description><![CDATA[The Children’s Online Privacy Protection Act was passed in 1998 by the FTC to protect the personal information of children. It specifically applies to websites that target children and provides guidelines for the collection, use and disclosure of personally identifiable information of children under the age of 13 who may not understand the dangers of disclosing personal information on the [...]]]></description> <content:encoded><![CDATA[<p>The Children’s Online Privacy Protection Act was passed in 1998 by the FTC to protect the personal information of children. It specifically applies to websites that target children and provides guidelines for the collection, use and disclosure of personally identifiable information of children under the age of 13 who may not understand the dangers of disclosing personal information on the Internet.</p><p><a
href="http://www.ftc.gov/privacy/privacyinitiatives/childrens.html">A website operator must be concerned with COPPA compliance if:</a></p><ul><li>The website targets children under the age of 13 through its subject matter, audio/visual content, advertising or use of other child-oriented features.</li><li>The website targets a general audience but has a separate child oriented section.</li><li>The website targets a general audience and children under the age of 13 are known to access the site.</li><li>The website is maintained outside the U.S. but targets children under the age of 13 in the U.S.</li><li>The website is operated by the Federal Government. Under the Office of Management and Budget, <a
href="http://www.whitehouse.gov/omb/memoranda_m00-13/">the U.S. Federal Government is required to comply with COPPA</a> on all of its websites targeting children</li></ul><p><a
href="http://www.coppa.org/comply.htm">COPPA Compliance</a></p><p>COPPA primarily uses the fair information practice principles of Notice and <a
href="../../../../../2009/12/21/choice-and-consent/">Consent</a> to protect children’s information.</p><p>In order to comply with COPPA, a website operator must:</p><p>1.  Provide parents with information about the website’s information collection and privacy practices. A privacy policy must be placed on the home page and on every page where data is collected in order to ensure adequate notice</p><p>2.  Obtain verifiable parental consent prior to collecting personal information</p><p>3.  Provide parents with a mechanism to access the information on record for their child and the ability to change consent options for future or third party use and disclosure</p><p>4.  Participation on the website may not be limited by requiring the collection of information that is not reasonably necessary</p><p>A COPPA compliant privacy notice must include:</p><ol><li>Legitimate contact information for the website operator/data owner</li><li>The type of information that is collected</li><li>How the information will be use</li><li>Notice of any third party disclosure</li></ol><p><a
href="http://www.ftc.gov/privacy/coppafaqs.shtm">Verifiable Parental Consent:</a></p><p>Depending on the information that is being collected and its intended use, different levels of parental consent must be obtained.</p><p><span
style="text-decoration: underline;"><a
href="http://www.coppa.org/comply.htm">Prior parental consent is not required to collect a child’s <em>name and email address only</em> if:</a></span></p><ul><li>The information is obtained in order to provide notice to the parent or obtain parental consent</li><li>The information is collected to respond once to a specific inquiry by the child and not used for further communications</li><li>The information is used to ensure the safety of a child and is not used for any other purposes</li><li>The information is used to protect the security of the website, protect against liability, participate in a law enforcement investigation or any other matters relating to public safety</li></ul><p>In all cases, parental consent should be obtained shortly after the information is collected. If parental consent cannot be obtained, the information may not be used for purposes other than those outlined above and the information must be deleted (with exceptions for ensuring the safety of the child)</p><p><span
style="text-decoration: underline;"><a
href="http://www.coppa.org/comply.htm">Parental Consent for Public Disclosure</a></span></p><p>If the website publicly links a child’s name or email address with their screen name in chat rooms, message boards, personal home pages, pen pal services or other similar social networking features they must obtain verifiable parental consent of public disclosure. This also applies to site which may disclose personal information to third parties for secondary uses and marketing purposes.</p><p>Consent options include:</p><ul><li>A printable form that can be signed then mailed or faxed back to the website operator</li><li>Obtain a parent’s credit card information in connection with a transaction which may include subscription fees, purchases or a credit card processing fee.</li><li>Provide a toll free line staffed by professionals to which parents may call and provide verbal consent</li><li>Obtain consent through an email that contains a digital signature that uses a public key that has been verified by one of the above methods.</li></ul><p><span
style="text-decoration: underline;"><a
href="http://www.coppa.org/comply.htm">Parental Consent for Internal Use</a><em> </em></span></p><p>If the website does not publicly disclose the child’s information either through disclosure to third parties or through the posting of information to chat rooms, message boards or similar features then the information will only be used within the site to contact the child.</p><p>Consent options include:<em> </em></p><ul><li>Any of the methods used for public disclosure<em> </em></li><li>The Email Plus option in which:<ul><li>An initial email is sent containing the privacy notice and asking the parent to respond with a phone, fax or mailing address to confirm consent through one of those methods; or</li><li>After a reasonable length of time has passed, a second email is sent asking for the parent to confirm consent. The privacy notice should again be included. This email informs the parent that their consent is implicit through their lack of response. The email should provide the the parent with information on how to revoke their consent.</li></ul></li></ul><p><a
href="http://www.ftc.gov/privacy/privacyinitiatives/childrens_enf.html"></a></p><p><a
href="http://www.ftc.gov/privacy/privacyinitiatives/childrens_enf.html">Enforcement of COPPA</a></p><p>COPPA is enforced by the Federal Trade Commission and through the a state’s Attorney General’s Office under SEC. 1305. COPPA allows for the creation of Safe Harbor programs which encourages industry self regulations.</p><p>There are several <a
href="../../../../../2009/12/28/online-assurance-programs/">online assurance programs</a> that offer a COPPA compliant Safe Harbor Program including:</p><ul><li><a
href="http://www.truste.com/privacy_seals_and_services/enterprise_privacy/childrens-online-privacy-seal.html">TRUSTe</a></li><li><a
href="http://www.caru.org/index.aspx">The Children’s Advertising Review Unit</a></li><li><a
href="http://www.esrb.org/privacy/">The Entertainment Software Rating Board</a></li></ul><p>Unlike other information privacy laws, the FTC has been diligent in enforcing COPPA. It has a <a
href="http://www.ftc.gov/privacy/privacyinitiatives/childrens_enf.html/">history of investigating privacy complaints</a> and taking action against website and companies violating the rule.</p><h2>Summary</h2><p>COPPA protects the privacy of personal information for children. It does not prevent children from accessing mature content. COPPA uses parental notice and consent to prevent the wrongful collection and misuse of children’t personal information. Any website that may be frequented by children under the age of 13, must comply with the COPPA ruling if personal information is collected.</p><h2><em>CIPP/G Candidate Preparation</em></h2><p>In preparation for the Certified Information Privacy Professional Government exam, a privacy professional should be comfortable with topics related to this post including:</p><ul><li>U.S. Public and Private Sector General Laws including COPPA (I.B.a.ii.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2010/01/11/coppa-the-childrens-online-privacy-protection-act/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Twitter is following your clicks</title><link>https://www.cippguide.org/2009/08/31/twitter-is-following-your-clicks/</link> <comments>https://www.cippguide.org/2009/08/31/twitter-is-following-your-clicks/#comments</comments> <pubDate>Mon, 31 Aug 2009 18:43:39 +0000</pubDate> <dc:creator>jbrook</dc:creator> <category><![CDATA[CIPP]]></category> <category><![CDATA[Privacy]]></category> <category><![CDATA[Beacon]]></category> <category><![CDATA[bit.ly]]></category> <category><![CDATA[Clear]]></category> <category><![CDATA[cookie]]></category> <category><![CDATA[COPPA]]></category> <category><![CDATA[disclosure]]></category> <category><![CDATA[PII]]></category> <category><![CDATA[privacy policy]]></category> <category><![CDATA[Twitter]]></category><guid
isPermaLink="false">http://www.cippguide.org/?p=959</guid> <description><![CDATA[Several Twitter users noticed a change in their service Tuesday.  It wasn't obvious to most, and might not represent a significant difference.  This examination of Twitter's privacy policy questions their [...]]]></description> <content:encoded><![CDATA[<p>Several <a
title="Twitter users noticed a tracking redirect" href="http://search.twitter.com/search?q=link_click_count" target="_blank">Twitter users noticed a change in their service</a> Tuesday.  It wasn&#8217;t obvious to most, and might not represent a significant difference.  Eric Schonfeld of TechCrunch managed to <a
title="TechCrunch author captures twitter's new redirect" href="http://www.techcrunch.com/2009/08/25/twitter-wants-to-track-your-clicks/" target="_blank">capture one of the redirect links</a>.</p><blockquote><p>http://twitter.com/link_click_count?url=http%3A%2F%2Fbit.ly%2F3omd6p&amp;linkType=web&amp;tweetId=3541772256&amp;userId=12798452.</p></blockquote><p><span
style="color: #0000ff;"><span
style="color: #000000;">If you look at this link, it turns out that twitter is redirecting to bit.ly.  Apparently, these links previously were completely handled by bit.ly.  bit.ly is a &#8220;simple link shortener&#8221;, that &#8220;o</span></span>ffers URL redirection service with  real-time link tracking&#8221;<span
style="color: #0000ff;"><span
style="color: #000000;">.  In addition, it includes a complete history of links shortened. Why would Twitter look to track links when they have a perfectly working relationship with their URL redirection provider? </span></span></p><p><span
style="color: #0000ff;"><span
style="color: #000000;">At 140 characters, tweets don&#8217;t provide much past commentary.  While you may <a
title="Congressman twitters location on secret mission to Iraq" href="http://www.cippguide.org/2009/02/09/congressman-twitters-security-breach/" target="_blank">update your location or time of arrival</a> in such a small space, you won&#8217;t be writing War and Peace or unveiling details of the latest scientific finding.  You do use it to add a bit of social commentary to a YouTube video &#8211; &#8220;check this out, it&#8217;s funny&#8221;, or &#8220;<a
title="Ashton Kutcher's Twitter post with picture link of Demi Moore" href="http://twitter.com/aplusk/status/1366791709" target="_blank">shhh, don&#8217;t tell wifey</a>&#8221; while sending a picture.<br
/> </span></span></p><p><span
style="color: #0000ff;"><span
style="color: #000000;">Tracking links fits in to the company&#8217;s long term goals, where <a
title="Twitters business goals and profit potential" href="http://digital.venturebeat.com/2009/08/20/twitter-to-roll-out-commercial-accounts-this-year-co-founder-stone-says/" target="_blank">Twitter will provide business services</a> including market research and customer prospecting.   Information analysis</span></span><span
style="color: #0000ff;"><span
style="color: #000000;"> only works when you hold the data. </span></span><span
style="color: #0000ff;"><span
style="color: #000000;">In order to provide some of the analytical services, such as which marketing tweets are promoting customer interest, Twitter will need to pull the bit.ly services in house.<br
/> </span></span></p><p><span
style="color: #0000ff;"><span
style="color: #000000;">Is collecting this information, and better still providing it to a third party outside a violation of a customer&#8217;s privacy?  We are not going to have the agreement between Twitter and bit.ly &#8211; they simply don&#8217;t publish those things.  However, we can examine selected passages from <a
title="Twitter's privacy policy" href="http://twitter.com/privacy" target="_blank">Twitter&#8217;s privacy policy</a> to glean the types and uses of information they collect, and a bit of what they may transfer to 3rd parties including bit.ly.</span></span></p><p><span
style="color: #0000ff;"><span
style="color: #000000;">Let&#8217;s delve a little deeper into Twitter&#8217;s privacy policy&#8230;<br
/> </span></span></p><h3>Selections from Twitter&#8217;s privacy policy</h3><blockquote><p>By using our Site you are <span
style="color: #ff0000;">consenting to our processing of your information </span>as set forth in this Privacy Policy now and as amended by us. <span
style="color: #ff0000;">&#8220;Processing&#8221; means using cookies</span> on a computer or <span
style="color: #ff0000;">using or touching information in any way, including, but not limited to, collecting, storing, deleting, using, combining and disclosing information</span>,</p></blockquote><p>Twitter may slice, dice and distribute any information you put into their system to anyone, anywhere.</p><blockquote><p>all of which activities will take place in the United States.<span
style="color: #ff0000;"> If you reside outside the U.S. your personally identifiable information will be transferred to the U.S., and processed and stored there under U.S. privacy standards.</span> <span
style="color: #ff0000;">By visiting our Site and providing information to us, you consent to such transfer to, and processing in, the US.</span></p></blockquote><p>Twitter is very clear that all information collected and processed occurs in the United States.  This allows citizens of the European Union and other like minded countries notice that they are opting in to monitoring and marketing &#8211; the protections afforded by local EU Data Protection Directive style laws will not apply.</p><blockquote><h3>Information Collection and Use</h3><p>Our primary goals in <span
style="color: #ff0000;">collecting personally identifiable information are to provide you with the product and services made available through the Site, including, but not limited, to the Service, to communicate with you, and to manage your registered user account</span>, if you have one.</p></blockquote><p>&#8220;The Service&#8221; is quite broad, and likely includes provisions for third party tracking and marketing (i.e. bit.ly).  Obviously, when Twitter introduces their own business services, this will extend &#8220;the Service&#8221; definition.</p><blockquote><p><strong>Information Collected Upon Registration</strong>. If you desire to have <span
style="color: #ff0000;">access to certain restricted sections of the Site, you will be required to become a registered user, and to submit certain personally identifiable information to Twitter</span>. This happens in a number of instances, such as <span
style="color: #ff0000;">when you sign up for the Service,</span> or if you <span
style="color: #ff0000;">desire to receive marketing materials</span> and information. Personally identifiable information that we may collect in such instances may <span
style="color: #ff0000;">include your IP address, full user name, password, email address, city, time zone, telephone number, and other information that you decide to provide us with, or that you decide to include in your public profile</span>.</p></blockquote><p>This section does imply that you must opt-in to receive marketing materials.  Obviously, anything placed on a public profile is not longer private, but apparently information it will not be disclosed.  Your user ID is not considered PII.</p><blockquote><p><strong>Additional Information</strong> Your full <span
style="color: #ff0000;">u</span><span
style="color: #ff0000;">ser name and your photo</span>, if you decide to upload one &#8230; you <span
style="color: #ff0000;">may provide additional information</span> in the profile section, including but not limited to your <span
style="color: #ff0000;">bio, your location, as well as your personal web site</span>, if you have one. Providing <span
style="color: #ff0000;">additional information</span> beyond what is required at registration is <span
style="color: #ff0000;">entirely optional</span>, but enables you to better identify yourself and find new friends and opportunities in the Twitter system. <span
style="color: #ff0000;">If you activate the mobile phone options</span> per the Terms of Service at <a
href="http://www.twitter.com/tos" target="_blank">www.twitter.com/tos</a>, we will collect your cellular phone number account information. &#8230; If you <span
style="color: #ff0000;">contact us by email</span> through the Site, we may <span
style="color: #ff0000;">keep a record of your contact information and correspondence</span>, and may use your email address, and any information that you provide to us in your message, <span
style="color: #ff0000;">to respond to you</span>.</p></blockquote><p>Again, anything provided past the required registration username is optional, but will be recorded and associated with the non-identifiable information Twitter collects.</p><blockquote><p><strong>Use of Contact Information</strong> In addition, we may <span
style="color: #ff0000;">use your contact information to market to you, and provide you with information about, our products and services, including but not limited to our Service</span>. If you decide at any time that you no longer wish to receive such information or communications from us, please follow the unsubscribe instructions provided in any of the communications.</p></blockquote><p>This suggests an opt-out for marketing and additional product information.  This seems like it may be in conflict with the earlier opt-in statement.</p><blockquote><p><strong>Log Data</strong> When you visit the Site, our <span
style="color: #ff0000;">servers automatically record information that your browser sends</span> whenever you visit a website (&#8220;Log Data&#8221; ). This Log Data may include information such as your I<span
style="color: #ff0000;">P address, browser type or the domain from which you are visiting, the web-pages you visit, the search terms you use, and any advertisements on which you click</span>. <span
style="color: #ff0000;">For most users</span> accessing the Internet from an Internet service provider the I<span
style="color: #ff0000;">P address will be different every time you log on</span>. We use Log Data to monitor the use of the Site and of our Service, and for the Site&#8221;™s technical administration. We <span
style="color: #ff0000;">do not associate your IP address with any other personally identifiable information</span> to identify you personally, except in case of violation of the Terms of Service</p></blockquote><p>Here&#8217;s the part directly affecting bit.ly and the new click redirect service.  You do not own the clicks &#8211; Twitter will record your Log Data, and although not directly associated with your PII, your IP address could be put together with your user ID, which does not constitute PII.</p><blockquote><h3>Cookies</h3><p>Like many websites, we also use <span
style="color: #ff0000;">&#8220;cookie&#8221; technology to collect additional website usage data</span> and to improve the Site and our service&#8230;</p></blockquote><p><a
title="About Google's behavioral advertising program" href="http://www.google.com/ads/preferences/html/about.html" target="_blank">Google recently faced scrutiny regarding their behavioral advertising</a> using cookies, and <a
title="Wikipedia: Facebook's Beacon program uses questionable privacy techniques" href="http://en.wikipedia.org/wiki/Facebook_Beacon" target="_blank">Facebook&#8217;s Beacon program</a>, which used a more nefarious technique, caused quite a stir late in 2008.</p><blockquote><h3>Information Sharing and Disclosure</h3></blockquote><blockquote><p><strong>Service Providers</strong> We engage <span
style="color: #ff0000;">certain trusted third parties to perform functions and provide services to us</span>, including, without limitation, hosting and maintenance, <span
style="color: #ff0000;">customer relationship</span>, database storage and management, and <span
style="color: #ff0000;">direct marketing campaigns</span>. We will <span
style="color: #ff0000;">share your personally identifiable information with these third parties</span>, but <span
style="color: #ff0000;">only to the extent necessary to perform these functions</span> and provide such services, and only pursuant to binding contractual obligations requiring such third parties to maintain the privacy and security of your data.</p></blockquote><p>This is where bit.ly (for now) comes in.   PII will be transferred, and the information updates will likely flow down to these third parties.  It does not mention anything regarding third parties updating Twitter&#8217;s information.</p><blockquote><p><strong>Business Transfers</strong> Twitter may <span
style="color: #ff0000;">sell, transfer or otherwise share some or all of its assets, including your personally identifiable information</span>, in connection with a merger, acquisition, reorganization or sale of assets or in the event of bankruptcy. You will have the opportunity to opt out of any such transfer if the new entity&#8217;s planned processing of your information differs materially from that set forth in this Privacy Policy.</p></blockquote><p>This is a big one.  The registered traveler program that <a
title="Bruce Schneier on the benefits of the Clear Registered Traveler program" href="http://www.schneier.com/blog/archives/2007/01/clear_registere.html" target="_blank">allowed people to move through a special, faster line at the airports</a>, hosted by the company <a
title="Clear declares lanes at airports closed" href="http://www.flyclear.com/" target="_blank">Clear, went bankrupt</a>. They want to sell the information they collected on users to the original parent company, Verified Identity Pass, or possibly a third party.  They are being fought tooth and nail by the users, for the simple fact that this is not just a user name, password and IP address or phone number.  Clear collected information such as Social Security Numbers, and even biometric info, like fingerprints and iris scans.  These data allowed Clear to perform such risk mitigation strategies as background investigations, criminal history checks and government watch list comparisons.  It is unclear what will happen to the data for users of Clear, but according to their <a
title="Clear's privacy policy requires securing of traveler's information" href="http://www.flyclear.com/clear_privacy.pdf" target="_blank">privacy policy</a>, the information may only be used for a similar registered traveler program.</p><blockquote><h3>Our Policy Towards Children</h3><p>The Site is not directed to persons under 13. If a parent or guardian becomes aware that his or her child has provided us with personally identifiable information without their consent, he or she should contact us at <a
href="mailto:privacy@twitter.com">privacy at twitter dot com</a>. We do not knowingly collect personally identifiable information from children under 13. If we become aware that a child under 13 has provided us with personal identifiable Information, we will delete such information from our files.</p></blockquote><p>Twitter, as well as any other online business, must follow the Federal Trade Commission&#8217;s COPPA, the <a
title="COPPA protects children under 13" href="http://www.coppa.org/" target="_blank">Children&#8217;s Online Privacy Protection Act</a>.  The idea being children will easily share much more information than necessary, potentially placing themselves in danger.</p><p>In all, Twitter&#8217;s well within their privacy policy and terms of service when sharing information.  Now, it&#8217;s just a question of how many people actually read it, or just skip it because it&#8217;s cool to be on Twitter.</p><h3><strong><em>CIPP Candidate Preparation</em></strong></h3><p>In preparation for the Certified Information Privacy Professional exam, a privacy professional should be comfortable with topics related to this post including:</p><ul><li>Introduction to Privacy:  Privacy as a factor in business risk management (Foundations: I.C.a.i.2),  Elements of Effective Privacy Management (Foundations: I.G.b.i) and Threats &amp; Vulnerabilities</li><li>Online Privacy:  Cookies (III.B.g.i) and Web Beacons (III.B.g.ii)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2009/08/31/twitter-is-following-your-clicks/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Amazon continues big business&#039; Big Brother thinking, with a very Orwellian twist</title><link>https://www.cippguide.org/2009/07/23/amazon-continues-big-business-big-brother-thinking-with-a-very-orwellian-twist/</link> <comments>https://www.cippguide.org/2009/07/23/amazon-continues-big-business-big-brother-thinking-with-a-very-orwellian-twist/#comments</comments> <pubDate>Thu, 23 Jul 2009 19:04:40 +0000</pubDate> <dc:creator>jbrook</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[Amazon]]></category> <category><![CDATA[Federal Trade Commission]]></category> <category><![CDATA[Orwell]]></category> <category><![CDATA[privacy policy]]></category> <category><![CDATA[Surveillance]]></category> <category><![CDATA[third party agreement]]></category><guid
isPermaLink="false">http://www.cippguide.org/?p=849</guid> <description><![CDATA[Seems Amazon has not been reading up on their recent history.  For some reason, most consumers don't like it when you quietly make changes without asking.  Amazon is re-learning the lesson through their Kindle electronic book readers and Whispernet service.   They removed unauthorized copies of books that made their way onto the Kindle store and end book readers, angering customers.  The author and book in question - George Orwell and [...]]]></description> <content:encoded><![CDATA[<div
id="identi-interface" class="ui-draggable ui-draggable-dragging" style="position: absolute; display: block; opacity: 0.9; left: 203px; top: -15px;"><table
id="identi-content-table" style="left: 576px; width: 1px;" border="0" cellspacing="0" cellpadding="0"><tbody><tr><td
width="370" valign="top"></td><td
width="200" valign="top"></td></tr></tbody></table></div><p>Seems Amazon has not been reading up on their recent history.  For some reason, most consumers don&#8217;t like it when you quietly make changes without asking.  In 2005, the <a
title="Wikipedia: Sony rootkit scandal" href="http://en.wikipedia.org/wiki/Sony_BMG_CD_copy_protection_scandal" target="_blank">Sony rootkit debacle was a case study</a> of how not to deal with customers.  It was 2007 when <a
title="Microsoft updates users computers without authorization" href="../2007/09/13/want-to-hack-anyones-computer-just-follow-microsofts-lead/" target="_blank">Microsoft decided their Windows Update service should update itself</a>, even with auto-update permissions turned off.  Now, here we are two years later, and Amazon is re-learning the lesson through their Kindle electronic book readers and Whispernet service.   Unauthorized copies of Orwell made their way onto the Kindle store through a provider self-service option.   The provider, MobileReference, posted &#8220;1984&#8243; and &#8220;Animal Farm&#8221; apparently without proper copy rights.</p><blockquote><p>“When we were notified of this by the rights holder, we removed the illegal copies from our systems and from customers’ devices, and refunded customers,&#8221; said Drew Herdener of Amazon.</p></blockquote><p>This <a
title="Amazon Kindle forum &quot;Mysterious George Orwell refunds&quot;" href="http://www.amazon.com/tag/kindle/forum/ref=cm_cd_pg_newest?_encoding=UTF8&amp;cdForum=Fx1D7SY3BVSESG&amp;cdPage=1&amp;cdSort=oldest&amp;cdThread=Tx1QUP1NLUY4Q5M&amp;displayType=tagsDetail" target="_blank">did not win Amazon any fans</a>.  Angry users noted that when they connected to Kindle&#8217;s Whispernet archive/bookshelf service, books were removed <em>from their devices</em>.  A customer using the nickname &#8220;Caffeine Queen&#8221; sarcastically warned,</p><blockquote><p>&#8220;I wonder if Amazon will sent representatives to customers&#8217; houses to retrieve dead tree copies? Orwell fans, lock your doors!&#8221;</p></blockquote><p>One user, Brian Wheeler, did give advice on how to avoid the situation entirely.</p><blockquote><p>&#8220;Actually, if you want to ensure that you are able to keep ALL copies of your Kindle books, make sure to ALWAYS download copies of your Kindle book purchases to your computer. That way, even if Amazon removes a book from your Kindle at any point that you have Whispernet on, you can reload that book onto your Kindle via the copy from your computer. Now, if it&#8217;s a pirated book that should never have been sold in the first place, that&#8217;s up to your own good conscientious as to what you should do. <img
src='https://www.cippguide.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> &#8221;</p></blockquote><p>The main issue should be that Amazon&#8217;s <a
title="Kindle terms of service" href="http://www.amazon.com/gp/help/customer/display.html?nodeId=200144530">terms of service</a> says nothing of deleting purchases or removing files from customer devices.  In fact, customers are granted a “permanent copy of the applicable digital content.”</p><blockquote><p>“It illustrates how few rights you have when you buy an e-book from Amazon,” said Bruce Schneier, computer security expert and chief security technology officer for British Telecom. “As a Kindle owner, I’m frustrated. I can’t lend people books and I can’t sell books that I’ve already read, and now it turns out that I can’t even count on still having my books tomorrow.”</p></blockquote><p>In addition to the changes in their publisher processes, Amazon has publicly said that in the future, when they are notified of an unauthorized book, they will remove it from the online store, but not remove it from archives or Kindle devices.</p><p>This should serve as a lesson in customer policy on two fronts.  First, did it make sense to reach past the store &#8211; most people probably would have considered the real world analog.  If a customer buys a counterfeit product unknowingly through legitimate channels, there is not manner to forcibly remove it from their possession.  Second, Amazon&#8217;s terms of service did not match their actions.  This is a real sticking point with the Federal Trade Commission, especially in situations where privacy policies are not followed.</p><p>Lastly, it is interesting that this isn&#8217;t the first time Amazon issued refunds and removed books from customers.  More importantly, why are third party rules and agreements would allow this to repeatedly happen.  It&#8217;s too bad it took a high profile, intrusive incident before they reviewed corporate procedures.  If they had simply put a trust/credibility status on providers before they could use the self service option, this whole debacle would probably have been avoided.</p><h3><strong><em>CIPP Candidate Preparation</em></strong></h3><p>In preparation for the Certified Information Privacy Professional exam, a privacy professional should be comfortable with topics found in this post including:</p><ul><li>Privacy policy development (Foundations:I.G.b) and Managing third parties (Foundations:II.G.c)</li><li>Enforcement of US Privacy &amp; Security Laws (CIPP: II.B)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2009/07/23/amazon-continues-big-business-big-brother-thinking-with-a-very-orwellian-twist/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced

Served from: www.cippguide.org @ 2012-02-09 04:52:45 -->
