We learned a lot last week at Facebook’s pseudo-annual developer conference, f8. Number one: we learned that Facebook knows how to put on a great event. We also learned that Facebook plans to basically provide the social plumbing for the entire Web through their what-is-sure-to-become ubiquitous “Like” buttons, open graph APIs and social plugins. And we learned that Facebook Credits, though it warranted little more than a footnote in Mark Zuckerberg’s keynote, is an important part of Facebook’s platform strategy going forward.
But perhaps one of the most important developments learned during f8 is in regards to the company’s new data policies, and how changes to the policies can go a long way towards helping game developers engage more deeply with their users. Here’s a quick recap of what these policies entail and what it means for you as an application developer.
New Data Policy
Effective immediately, Facebook is removing the 24 hour caching restrictions on developers. This means that developers don’t have to keep asking for data on their users and can simply store whatever data they collected the first time, which should help boost user engagement.
As a part of this new system Facebook has added several new rules to their existing policies requiring developers to:
- Post a privacy policy that explains what data you collect, and how you will use, store and/or transfer user data
- Keep your cached data up to date
- Get consent for data beyond the basic account info
- Delete data if the user requests it
Facebook may also require a developer to delete data if they violate terms.
New Data Permissions Dialog
We also learned that Facebook will be combining all of their permissions dialogs into one unified permissions box for the user to allow when they enter an app.
With this permissions box developers will be able to lump all of their basic requests into one place. It is unclear at this time how developers will need to ask for Extended Permissions.
Data Permission Display
Facebook is giving developers a few different ways to display to their users the authorization page for their app.
This request page will be shown to users with the list of permissions the developer is requesting. A description of each type of display is below:

Extended Permissions
By default, your application can access all public data in a user’s profile, including their name, profile picture, gender and friend list. In addition to the default information, a developer can choose to wrap additional extended permissions into that request flow, so that they gain access to information such as the user’s birthday, education history, hometown, etc.
With these new changes, it makes it possible for developers to get to know their users that much better and build deeper, more personal, and more lasting relationships. As Ethan Beard, director of the Facebook Developer Network team, put it on the Facebook blog:
These changes reflect two core beliefs: first, user data belongs to the user; they should have transparency and control over it. And second, you should be able to build relationships with your users; we should not be in the way. We hope these improvements will foster more trust and engagement for our platform and the applications and websites using it.
To learn more about the new data policies, read the Facebook Developer Principles and Policies or read about about authentication with the new permissions dialog.
director of the Facebook Developer Network team