Meta App Development

Data Deletion Request Callback

Apps that access user data must provide a way for users to request that their data be deleted. Your app can satisfy this requirement in one of two ways:

  • Implement a Data Deletion Request Callback.
  • Provide a URL with explicit instructions for app users on how to delete their data by way of a third-party website or tool. The third-party website may be the relevant section in the application's Privacy Policy.

The data deletion callback is called whenever an app user removes your app or removes access to their data that is being shared with your app, such as their email address, in Settings of their Facebook account.

This generates a POST with a signed request that is sent to your app. The signed request contains an app-scoped ID identifying the user making the request. For an example of how to parse the request and the structure of the parsed request, see the following section.

In response to the user request, you should acknowledge receiving a user data deletion request through the technical means we provide, and provide a link and a confirmation number. The link and confirmation number must give the user access to a human-readable explanation of the status of their request, including a legitimate justification for any refusal to delete (where legitimate will vary based on jurisdiction and our case-by-case interpretation of our policy as it relates to their stated reasons).

Implementing the Callback

To parse and respond to the request, you should implement a "data deletion request" callback. Your callback must use the secure HTTPS protocol and must be listed in the Data Deletion Request URL field in the Settings in the App Dashboard.

The Data Deletion Request callback that you implement must do the following:

  • Initiate the deletion of any data your app has from Facebook about the user.
  • Return a JSON response that contains a URL where the user can check the status of their deletion request and an alphanumeric confirmation code. The JSON response has the following form:
    { url: '<url>', confirmation_code: '<code>' }

Failure to comply with these requirements may result in your callback being removed or your app being disabled.

You can implement this callback in any language, but the following code is an example of the callback in PHP.

<?php
header('Content-Type: application/json');

$signed_request = $_POST['signed_request'];
$data = parse_signed_request($signed_request);
$user_id = $data['user_id'];

// Start data deletion

$status_url = 'https://www.<your_website>.com/deletion?id=abc123'; // URL to track the deletion
$confirmation_code = 'abc123'; // unique code for the deletion request

$data = array(
  'url' => $status_url,
  'confirmation_code' => $confirmation_code
);
echo json_encode($data);

function parse_signed_request($signed_request) {
  list($encoded_sig, $payload) = explode('.', $signed_request, 2);

  $secret = "appsecret"; // Use your app secret here

  // decode the data
  $sig = base64_url_decode($encoded_sig);
  $data = json_decode(base64_url_decode($payload), true);

  // confirm the signature
  $expected_sig = hash_hmac('sha256', $payload, $secret, $raw = true);
  if ($sig !== $expected_sig) {
    error_log('Bad Signed JSON signature!');
    return null;
  }

  return $data;
}

function base64_url_decode($input) {
  return base64_decode(strtr($input, '-_', '+/'));
}
?>

This produces a JSON object that looks like this, in which user_id is the relevant field for your callback.

{
   "algorithm": "HMAC-SHA256",
   "expires": 1291840400,
   "issued_at": 1291836800,
   "user_id": "218471"
}

For more information on signed requests, see Using a Signed Request in the Login for Games on Facebook topic.

Testing Your Callback

To test your callback:

  1. Log in to your app with Facebook Login.
  2. Go to your Facebook profile's Apps and Websites settings tab: https://www.facebook.com/settings?tab=applications
  3. Remove your app.
  4. Click the View Removed Apps and Websites link.
  5. In the popup, click the View button to the right of the application.
  6. In the window, appeared click Send Request to trigger your callback.

User Data Deletion Request FAQs

Q: Why did I receive this notice?

A: You received this notice because a user of the app for which you are an app admin requested that their data be deleted. Please take action by promptly deleting all associated user data in your records for the requested ID. User data deletion requests are captured under applicable privacy laws, so Meta expects that you will handle this matter promptly.

Q: How do I access the list of IDs that need to be deleted?

A: You can access these in the advanced settings page of your app dashboard, under “User Data Deletion Requests”.

Q: What is an app scoped user ID?

A: An app-scoped user ID (ASID) is a unique ID that Facebook creates for a user when they log into a Facebook app for the first time or with Limited Login. ASIDs are specific to the app and cannot be used by other apps.

Q: What is a page scoped user ID?

A: A Page-scoped User ID (PSID) is a unique ID that Facebook assigns to a user when they interact with a Facebook Page through Messenger.

Q: What is a instant game player ID?

A: ID issued by the Instant Game SDK for each user as the unique identifier. Note that Instant Game Player ID and ASID are different even for the same user of the same app.