Risk
2/25/2011
05:14 PM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Facebook Proposes 'Data Use' Policy To Replace 'Privacy Policy'

It's not an official change, but if enough Facebook users approve, it could become one.

Facebook on Friday acknowledged what privacy advocates have been saying for years: Privacy policies are too difficult to understand.

"Our own privacy policy has been criticized as being '5830 words of legalese' and 'longer than the U.S. constitution -- without the amendments,' the company said in a blog post. "Okay, you're right. We agree that privacy policies can and should be more easily understood, and that inspired us to try something different."

The social networking site, which seems to be competing with Google to see which company can make headlines for the most privacy-related gaffes every year, wants to make privacy policies easy to understand, more visual and interactive, and more relevant to users' concerns.

Toward that end, Facebook has re-imagined its privacy policy and presented the results for user comment.

Most remarkably, the proposed design dispenses with the term "Privacy Policy" and replaces it with "Data Use Policy." Privacy advocates have long complained that the term "Privacy Policy" is misleading because privacy policies generally describe how and when data is shared.

This isn't an official change however: Facebook's Privacy Policy continues to represent the company's official position.

The proposed revision is undeniably more visually appealing. It's no longer a tower of impenetrable text. Instead, the "Data Use Policy" has been broken up into multiple pages. This makes it much more readable.

But what's gained in readability is lost in navigation: Each of the six primary sections on the Data Use Policy page leads to multiple subsections on the linked page, and many of these subsections require further navigation via disclosure icons. Navigating through all this is a chore.

Aza Raskin, formerly the design lead for Mozilla's Firefox and and more recently the co-founder of health startup Massive Health, framed the problem with privacy policies thus: "We need to reduce the complexity of privacy policies to an indicator scannable in seconds."

Complexity is not just a matter of words per page. It's a matter of time to comprehension. And unfortunately, Facebook's "Data Use Policy" remains irreducibly complex because Facebook and its platform developers employ user data in many different ways. The company admits that is has "tried not to change the substance of the policy..."

And therein lies Facebook's problem: Neither its "Privacy Policy" nor its "Data Use Policy" includes an option for actual privacy, which is to say unidentified use.

"If you want to completely block applications from getting your information, you will need to turn off all Platform applications," the company explains. "This means that you will no longer be able to use any games, applications or Web sites." And even then, Facebook still knows who you are, unless you're violating the site's Terms of Service. Facebook requires that users submit accurate personal information.

Contrast this with a post by Alma Whitten, Google's director of privacy for products and engineering, on Friday describing how Google supports three modes of use: unidentified, pseudonymous and identified.

Facebook needs an anonymity policy.

Even if Facebook remains unwilling to allow users to embrace anonymous use, its Data Use Policy could do with further refinement. The company's designers may find it worthwhile to review Raskin's suggestion that privacy policies should follow in the footsteps of Creative Commons, which has made media usage rights easy to understand.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-4807
Published: 2014-11-22
Sterling Order Management in IBM Sterling Selling and Fulfillment Suite 9.3.0 before FP8 allows remote authenticated users to cause a denial of service (CPU consumption) via a '\0' character.

CVE-2014-6183
Published: 2014-11-22
IBM Security Network Protection 5.1 before 5.1.0.0 FP13, 5.1.1 before 5.1.1.0 FP8, 5.1.2 before 5.1.2.0 FP9, 5.1.2.1 before FP5, 5.2 before 5.2.0.0 FP5, and 5.3 before 5.3.0.0 FP1 on XGS devices allows remote authenticated users to execute arbitrary commands via unspecified vectors.

CVE-2014-5395
Published: 2014-11-21
Multiple cross-site request forgery (CSRF) vulnerabilities in Huawei HiLink E3276 and E3236 TCPU before V200R002B470D13SP00C00 and WebUI before V100R007B100D03SP01C03, E5180s-22 before 21.270.21.00.00, and E586Bs-2 before 21.322.10.00.889 allow remote attackers to hijack the authentication of users ...

CVE-2014-7137
Published: 2014-11-21
Multiple SQL injection vulnerabilities in Dolibarr ERP/CRM before 3.6.1 allow remote authenticated users to execute arbitrary SQL commands via the (1) contactid parameter in an addcontact action, (2) ligne parameter in a swapstatut action, or (3) project_ref parameter to projet/tasks/contact.php; (4...

CVE-2014-7871
Published: 2014-11-21
SQL injection vulnerability in Open-Xchange (OX) AppSuite before 7.4.2-rev36 and 7.6.x before 7.6.0-rev23 allows remote authenticated users to execute arbitrary SQL commands via a crafted jslob API call.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?