Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

5/8/2012
01:40 PM
Connect Directly
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Myspace Settles FTC Privacy Complaint

Now faded social network must tell the truth about how it handles personal information and undergo privacy audits for the next two decades.

Use Facebook Apps To Woo Customers: 6 Examples
Facebook Apps In Action
(click image for larger view and for slideshow)
Myspace on Tuesday settled charges brought by the Federal Trade Commission that it made false promises about protecting user data.

In its privacy policy and public statements, the faded social network promised not to share users' personally identifiable information with third parties without first asking permission and promised not to use personally identifiable information to customize ads.

Myspace violated those promises, according to the FTC. The company provided third-party advertisers with users' Friend IDs, which are account numbers linked to basic personal information. In so doing, the company enabled advertisers to create profiles linked to individual identities.

The FTC is not claiming that any ad company has made such a profile and the agency declined to discuss whether it might investigate whether any advertising network has compiled personal profiles using data gathered from Myspace. The settlement addresses the gap between Myspace's words--its privacy policy--and its actions.

[ Read Google+ Hangouts On Air: Broadcasting For All. ]

Regardless, advertisers didn't need to create Myspace user profiles because Myspace provided assistance with the delivery of personally targeted ads.

From January 2009 through June 2010--a year before the social network was sold for $35 million to Specific Media and celebrity Justin Timberlake--most of the ads displayed on Myspace were delivered via the Fox Audience Network (FAN), an ad network affiliated with Myspace.

To enable FAN to target ads, Myspace included the Friend ID, age, and gender of Myspace users in ad requests from Myspace Web pages, the FTC complaint says. And it did so in unprotected plain text. When FAN's ad inventory had no ad to place, the ad request was handed off to a third-party ad network to be filled, and the same personal information was provided. None of this was permissible under the terms of the Myspace privacy policy.

The settlement requires that Myspace cease misrepresenting its privacy promises. It also requires that Myspace set up a privacy program to protect users' information and to submit to independent third-party privacy audits every two years for the next 20 years.

Myspace might want to work on scheduling a site visit immediately: With Facebook, Google, and Twitter, among others, already under FTC orders to submit to biennial privacy audits, finding an available privacy inspector could be something of a challenge.

The Enterprise 2.0 Conference brings together industry thought leaders to explore the latest innovations in enterprise social software, analytics, and big data tools and technologies. Learn how your business can harness these tools to improve internal business processes and create operational efficiencies. It happens in Boston, June 18-21. Register today!

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-14318
PUBLISHED: 2020-12-03
A flaw was found in the way samba handled file and directory permissions. An authenticated user could use this flaw to gain access to certain file and directory information which otherwise would be unavailable to the attacker.
CVE-2020-2320
PUBLISHED: 2020-12-03
Jenkins Plugin Installation Manager Tool 2.1.3 and earlier does not verify plugin downloads.
CVE-2020-2321
PUBLISHED: 2020-12-03
A cross-site request forgery (CSRF) vulnerability in Jenkins Shelve Project Plugin 3.0 and earlier allows attackers to shelve, unshelve, or delete a project.
CVE-2020-2322
PUBLISHED: 2020-12-03
Jenkins Chaos Monkey Plugin 0.3 and earlier does not perform permission checks in several HTTP endpoints, allowing attackers with Overall/Read permission to generate load and to generate memory leaks.
CVE-2020-2323
PUBLISHED: 2020-12-03
Jenkins Chaos Monkey Plugin 0.4 and earlier does not perform permission checks in an HTTP endpoint, allowing attackers with Overall/Read permission to access the Chaos Monkey page and to see the history of actions.