Can We Learn from Facebook’s Privacy Model?
Posted on December 1st, 2010 | Categories: privacy, social mediaIf you search online for “Facebook privacy policy” you will get endless links to articles criticizing Facebook’s light approach to privacy. You can even find a chart showing how default settings have grown since 2005 to reveal almost all your personal details to friends, friends of friends, all Facebook users and even to the public Internet.
But it seems that critics failed to identify Facebook’s innovative approach towards privacy transparency, at least when it comes to 3rd party applications. An approach, that I believe, should be adopted as the basis for a standard.
Get serious, we don’t read these
If you’ve installed programs on your computer, you probably clicked the accept checkbox many times without ever reading the End-User License Agreement (EULA). Well, at least if you are like me.

EULA screens, which usually appear as one of the first screens in the installation process, are the standard way of presenting users with programs’ terms and conditions. According to an online survey, published in 2009, only 2% (of 1987 participants) actually read EULAs. The rest 98% either “hit accept as fast as they could” or were unaware of EULAs all together.
In its revolutionary book “Privacy by Design”, Ann Cavoukian laid out the 7 principles for embedding privacy proactively into technology. The 6th one is:
Visibility / Transparency
Privacy by Design seeks to assure all stakeholders that whatever the business practice or technology involved, it is in fact, operating according to the stated promises and objectives, subject to independent verification. Its component parts and operations remain visible and transparent, to users and providers alike. Remember, trust but verify.
Put simply and in context, Privacy by Design requires applications to be transparent and communicate to consumers which data will be used, how and for what purpose.
The Facebook way
On June 2010, Facebook introduced a new way of granting user approval to applications.

Whenever you add a Facebook application, a dialog pops up with clear and discrete phrases stating what the application wants to do with your data. Among them are “Access my basic information”, “Access my photos and videos”, “Access my friends’ information”, “Send me email” and many more.
In fact, each Facebook application gets access to the user’s public information, including his name, profile picture, gender, and friends. If the application needs to access additional information, it has to request extended rights and these are propagated to users as the above dialog box. But Facebook do more than that. Their API actually allows applications access only to information approved by users.
Actually, Facebook were able to solve two critical problems that have never been resolved properly by the software industry:
- How to transparently notify users what the application is allowed to do with his information and get the user’s consent for that in a way that is understandable to common people.
- Enforce these permissions so that applications would not be able to gain access to unauthorized information.
I don’t claim that Facebook’s privacy policy is the best on the Web. I am aware of their permissive default settings, and even how difficult it is to find some settings, not to mention delete your own account. However my contention is that we can learn from their approach to application privacy and extend it for the benefit of other applications.
Privacy as a standard
In late October 2010, during the OECD Privacy Protection conference held in Jerusalem, a call was made to look for ways to standardize the way applications publish and enforce privacy policies.
Currently, most application developers choose to hide their terms of service and privacy policies in longish, legalistic, and un-readable documents (at least to normal people) that most people never open. Moreover, except on several mobile environments (for example, gaining access to location on iPhone or to specific JSRs in Java MIDP), no one took the responsibility for enforcing these terms, making sure they are not violated.
I believe that we need to completely change the paradigm and put more emphasis on transparency and enforcement. Although so far, we spoke only about Web applications, this approach can be easily extended to desktop applications as well.
In order to do that, we need to accept several new rules and guidelines:
- A standard set of access permissions should be defined (probably by one of the standard organizations handling privacy). These permissions, which will be clear to the common user, might include options like “Allow access to local disk”, “Store an identifier on this computer to identify you the next time you visit our site” and more.
- Each application or site should declare which of these access permissions is applicable to it
- Users will be presented with a clear list of permissions (in a simple language) the application had asked for. The permissions will be collected by the underlying operating system (or run-time environment or even browser) and not the application itself to ensure their credibility and prevent fraud.
- A simplified Terms of Use text will be provided with each application, in a non-legal language, describing the basic principles of the terms and conditions. A complete TOS can be provided as well.
- Operating systems, execution run-times and browsers will enforce the granted permissions
- If a breach attempt is detected (for example, an application was trying to access un authorized resources), this event should be published to a central website for everyone to see
This paradigm is not limited to software installations and should be used also in Web sites. Sites should provide a link to a page that states these terms and conditions for users to read, and also provide a machine-readable file (e.g., XML) that will ask the browser for permissions. Browsers could present these permissions to users or grant them automatically, depending on their settings. The most important thing is that browsers will be responsible also to enforcing these permissions.
It’s your turn
What do you think of the proposed scheme? Can it work? Can it be enforced?
Comments Off Permanent link







