Six Degrees: come in, your time is up

From Facebook today:

We’re writing to inform you of a Facebook Platform policy violation within your application, Six Degrees.

Our terms and policies are in place to ensure that Facebook Platform serves users well, allows applications to thrive, and provides a great experience for all involved. Unfortunately, we have determined that your application does not meet our terms and policies.

Specifically, your application contains “Store my friend list” and “Keep up-to-date” functionalities that imply storing data in violation of our policies on this behavior. Whether you obtain user permission or not, applications may not store data obtained from Facebook for longer than 24 hours per section I.6.1 of our Platform Guidelines ( This includes friend connections between two users, as mentioned on .

We request that you stop storing this data. As friend connections are crucial to your application’s functionality, we recommend that you prompt users to grant the offline_access permission and then query their friend list dynamically as required. For more information, please see .

Additionally, it appears that your application pre-fills text fields in the Settings section with user data, including but not limited to first name, last name, and gender. Data obtained and stored through these means of pre-filling is still in violation of our data policies, as explained in section I.14.2 of our Platform Guidelines. We request that you stop pre-filling these fields with user data.

Finally, your application publishes a one-line Feed story when users authorize it. These stories read ” has logged into the Six Degrees application” and are in violation of section II.5.1 of our Platform Guidelines. We request that you remove them from your application.

We trust and expect that all applications managed by you and your team meet our terms and policies, so we appreciate in advance that you proactively ensure that this is the case in the future.

Please make these requested changes by 1:00pm Pacific Time Thursday, 25 June 2009. When you have done so, please let us know by replying to this email.

We realize that this is a short timeframe, but it is important for the sake of our users and other developers that this issue is resolved quickly. If you cannot resolve this by the above deadline, your application may be subject to additional enforcement actions, including but not limited to being disabled.