Implementation Summary

Ethyca uses the following endpoints in Firebase to retrieve and delete Personally Identifiable Information (PII) when a user submits a data subject request. See below for a summary of what Ethyca does with each endpoint:

EndpointUser Can DownloadUser Can Delete
UsersYesNo

Because Firebase is a mobile application development platform, it stores PII about your customers. Keep this in mind when you are setting the DSR Customization as it will impact what is returned in your subject's DSR package.

If this aligns with your use of Firebase, please proceed to the next section to begin setting up your integration in the Control Panel.

For any questions, please reach out to your dedicated Customer Success Manager.

Connection Settings

To connect your instance of Firebase to Ethyca, you will need to enter your API Key, Type, Project ID, Private Key ID, Private Key, Client Email, Client ID, Auth URI, Token URI, Auth Provider X.509 Cert URL, Client X. 509 Cert URL, and Atlas location of UID.

To locate your API Key and Project ID, follow the steps below:

1. Open your Firebase console at console.firebase.google.com. Select your project.

2. Click the gear icon. Select "Project settings" from the popup menu. If you are prompted to choose a project, select your Firebase project from the menu.

13741374

3. Your API Key is listed in the Web API Key field. Copy and paste your API Key into Ethyca.

13741374

4. Your Project ID is listed in the Project ID field. Copy and paste your Project ID into Ethyca.

916916

To locate your Type, Private Key ID, Private Key, Client Email, Client ID, Auth URI, Token URI, Auth Provider X.509 Cert URL, Client X.509 Cert URL , follow the steps below:

  1. Open your Firebase console at console.firebase.google.com. Select your project.

  2. Click the gear icon. Select "Project settings" from the popup menu. If you are prompted to choose a project, select your Firebase project from the menu.

  3. Select "Service Accounts" from the menu bar.

916916
  1. Underneath the "Admin SDK configuration snippet" click on the "Generate new private key" button
916916
  1. A popup will appear with a warning. Click on the "Generate Key" button. This will automatically generate a JSON file that will be downloaded to your computer.
28942894
  1. Open the JSON file with any text editor. It should look something like this:
{
  "type": "Your_type_appears_here",
  "project_id": "Your_project_id_appears_here",
  "private_key_id": "Your_private_key_id_appears_herd",
  "private_key": "Your_private_key_appears_here",
  "client_email": "Your_client_email_appears_here",
  "client_id": "Your_client_id_appears_here",
  "auth_uri": "Your_auth_ur_appears_here",
  "token_uri": "Your_token_uri_appears_here",
  "auth_provider_x509_cert_url": "Your_auth_provider_x509_cert_url_appears_here",
  "client_x509_cert_url": "Your_client_x509_cert_url_appears_here"
}
  1. Copy and paste your Type, Private Key ID, Private Key, Client Email, Client ID, Auth URI, Token URI, Auth Provider X.509 Cert URL, Client X.509 Cert URL into Ethyca.

The Finishing Touches

If you are using Ethyca’s Atlas, please identify what column mapped to Atlas contains customers and orders. Once identified, please notify your Ethyca Customer Success Manager, who will then complete the last step in identity propagation mapping.

When you have finished adding your connection details, move on to the next two tabs to configure your DSR Customization settings and complete your Data Mapping.