[{"titre":"The FTC's Google settlement: What's the buzz?","url":"https://www.ftc.gov/business-guidance/blog/2011/04/ftcs-google-settlement-whats-buzz","pubDate":"Tue, 06 Oct 2026 14:06:39 +0200","source":"FTC USA Business Blog Posts","description":"The FTC's Google settlement: What's the buzz? wfg-adm109 April 1, 2011 | 4:28PM The FTC's Google settlement: What's the buzz? By Lesley Fair “Sweet!  Check out Buzz.” “Nah, go to my inbox.” That was the intriguing choice facing Gmail users last year when Google launched Google Buzz, its social network. But according to a settlement announced this week by the FTC, the company violated the privacy promises it made to Gmail users and used deceptive tactics in the Buzz rollout. The story starts with Google’s privacy policy. From October 2004 until October 2010, Gmail users were told, \"Gmail stores, processes and maintains your messages, contact lists and other data related to your account in order to provide service to you.\"  On the subject of the choices users had about the use of their personal information in all of Google’s products, including Gmail, the privacy policy said, \"When you sign up for a particular service that requires registration, we ask you to provide personal information. If we use this information in a manner different than the purpose for which it was collected, then we will ask for your consent prior to such use.\"  According to the FTC, statements like that conveyed that Google would use information from people signing up for Gmail only for the purpose of providing them with email service and that Google would ask for their consent before using their info for any other purpose. So far, so good. But then came the roll-out of Google Buzz. The service allows users to share updates, comments, pictures, videos, and the like through “buzzes” made either publicly or privately to individuals or groups of users. When Buzz was launched, Gmail users were taken to a welcome screen that announced the new service and presented the “Sweet!” or “Nah” choice. If users clicked “Nah,” the FTC complaint alleges that their info was nonetheless shared in a number of ways. First, the user could still be “followed” by Gmail users who enrolled in Buzz. Second, if the Gmail user had previously created a Google profile, he or she could appear on the public Google profiles of Buzz enrollees who were following them. Third, a link to Buzz would show up on the list of links on the user’s Gmail page. If the user clicked on that link, he or she would be taken to the Buzz welcome screen and would be automatically enrolled in Buzz without any disclosure of that fact. In other words, users would be enrolled in certain features of Buzz even if they didn’t sign up. So much for “Nah.” The FTC’s complaint alleges that despite what it said in its privacy policy, Google didn’t use information from people signing up for Gmail just for the purpose of providing email service. Rather, the company used it to populate Buzz. Thus, said the FTC, the representations in Google’s privacy policy were false or misleading. Furthermore, the agency alleged that despite the promise in its privacy policy that Google would ask for consumers’ consent before using their information for another purpose, Google went ahead and used it to populate its social network without getting their permission. The FTC charged that was false or misleading and constituted a deceptive practice. The next part of the story:   The not-so-sweet results when users clicked the “Sweet!”","id":3200009},{"titre":"Speaking of Spokeo: Part 2 â The companyâs allegedly bogus endorsements","url":"https://www.ftc.gov/business-guidance/blog/2012/06/speaking-spokeo-part-2-companys-allegedly-bogus-endorsements","pubDate":"Sat, 03 Oct 2026 14:06:13 +0200","source":"FTC USA Business Blog Posts","description":"Speaking of Spokeo: Part 2 — The company’s allegedly bogus endorsements wfg-adm109 June 13, 2012 | 12:25PM Speaking of Spokeo: Part 2 — The company’s allegedly bogus endorsements By Lesley Fair The lawsuit against data broker Spokeo is the FTC’s first Fair Credit Reporting Act case addressing the collection of online info — including data from social networking sites — when used in the context of employment screening.  But that’s not the only way the Spokeo settlement touches on social media.  The FTC also charged that Spokeo violated Section 5 by having employees post glowing recommendations of the company’s services on news and technology websites without disclosing their true identity. Perhaps just the work of a rogue cubicle occupant?  No, said the FTC.  According to the complaint , Spokeo directed its employees to write the comments.  Spokeo managers then edited what they wrote and had the staffers post the endorsements using account names provided by Spokeo.  The purpose, says the FTC, was to give readers the misleading impression that the laudatory words had been posted by independent consumers or business users of Spokeo. The FTC’s revisions to its Endorsement Guides made headlines a few years ago.  Ironically enough, the provision that seemed to attract the most attention is one that didn’t change.  It’s the law — and it’s always been the law under Section 5 — that consumers have a right to know when there’s a material connection between an advertiser and an endorser.  Here’s how the Guides put it:  \"When there exists a connection between the endorser and the seller of the advertised product that might materially affect the weight or credibility of the endorsement ( i.e., the connection is not reasonably expected by the audience), such connection must be fully disclosed.\" According to the FTC, by posting comments that conveyed the untruthful impression that they came from satisfied users of Spokeo’s services, Spokeo engaged in false and misleading practices.  To settle the endorsement count in the lawsuit, Spokeo has agreed that it won’t misrepresent, expressly or by implication, the status of any user of a product or service — for example, that someone is an independent, ordinary endorser if that’s not the case.  The company also will clearly and prominently disclose any material connection between an endorser and Spokeo (or any other entity advertising, selling, or promoting a product) when a connection exists.  What about the bogus endorsements already posted?  Spokeo has seven days to take all reasonable steps to pull them down. Looking for more about complying with the Endorsement Guides?  Read The FTC’s Revised Endorsement Guides: What People are Asking and watch this video: While you’re at it, share this post and those resources with your marketing staff, your ad agency, your PR firm, and anyone else who plays a role in your publicity and promotions. Next:  What the Spokeo settlement means for your business, your next ad campaign, and your job search","id":3195787},{"source":"FTC USA Business Blog Posts","id":3194910,"description":"Practice Fusion case suggests 6 health privacy pointers lfair June 8, 2016 | 9:01AM Practice Fusion case suggests 6 health privacy pointers By Lesley Fair Combine two of the most talked-about consumer protection topics – health privacy and consumer-generated online content – and what do you get? A proposed FTC settlement with Practice Fusion, the largest cloud-based electronic health records company in the country, and six compliance tips for others in the industry. One of San Francisco-based Practice Fusion’s primary products is an electronic records system for outpatient providers. In 2009, the company launched “Patient Fusion,” an online portal where patients whose providers were already using Practice Fusion could view or download their health information or transmit it to another provider. Patient Fusion also let patients send and receive secure messages from their providers. Fast forward several years and the company decided to expand Patient Fusion to include a public directory where current and prospective enrollees could search for doctors geographically or by specialty, read patient reviews of providers, and request appointments. But Practice Fusion had to ask itself a question familiar to many online companies: How do we get the content – in this case, patient reviews? That’s the focus of the FTC’s lawsuit. According to the complaint , Practice Fusion solicited data in a misleading way that led some patients to believe they were sending follow-up messages directly to their doctors about their diagnosis, medical treatment, prescriptions, etc. – and not contributing content to a public website. Practice Fusion, however, populated its new site with the information those people provided, some of which was highly sensitive. Here’s what happened. After appointments with their doctors, patients received emails titled “How was your visit?” The message continued, “To help improve your service in the future, please let us know how your visit went” and included a link with rating stars. The message ended this way: Thank you, Dr. [Name] In a footer, the message said “This email was sent to you by Patient Fusion®, a tool Doctor [Name] uses to deliver the highest quality of care to patients.” Below that in smaller print it said “Sent on behalf of Doctor [Name]’s office by: Practice Fusion.” If patients clicked the link, they were taken to a page that asked for feedback about things like how long they had to wait for their appointment, the doctor’s bedside manner, and whether their medical concern was addressed. There also was a text box where patients were invited to “leave a review for your provider.” Below that was a pre-checked box with the phrase “Keep this review anonymous.” What did some people put in that box? Highly sensitive information directly addressed to their doctors, not evaluations meant to be shared publicly. Here are just a few examples: “Dr [name], My Xanax prescription that I received on Monday was for 1 tablet a day but usually it’s for 2 tablets a day. I have not taken it to the pharmacy yet. Can I pick up a new one, or can I get a prescription called into a pharmacy? Thanks, [patient’s full name] “I called today and left a message regarding my daughter and no one has returned my call. I think she is depressed and has stated several times this week that she wishes she was dead. Could someone please call me [phone number]?” “The cefuroxime axetil does not seem to be doing anything for me. I did a little research and I think I have a yeast infection called candida. Not sure what to do about it yet. I guess I will first try to change my diet. Medication? [patient’s full name] “I would like to make an appointment for my back pain and possible shingles. Can you please call me @ [phone number]? Thank you! [patient's full name]” “I HAVE NO INFECTION [healthcare provider name].  EVERYTHING WENT","pubDate":"Sat, 03 Oct 2026 08:09:37 +0200","titre":"Practice Fusion case suggests 6 health privacy pointers","url":"https://www.ftc.gov/business-guidance/blog/2016/06/practice-fusion-case-suggests-6-health-privacy-pointers"}]