Data safety form (Play Console)
This guide describes how to complete the Data safety form based only on how our SDK collects data.
If your application collects more data than this, or handles the data differently, then you need to ensure that this is reflected correctly in the answers that you provide.
About the Data safety form
Google outline that you must complete the Data safety form on the App content page in the Play Console so that you can inform Google about your app's privacy and security practices:
All developers must declare how they collect and handle user data for the apps they publish on Google Play, and provide details about how they protect this data through security practices like encryption. This includes data collected and handled through any third-party libraries or SDKs used in their apps.
You can read more about this in Google's developer documentation.
This information is displayed on you application's Play Store listing to help your end-user's understand how you collect and share data.
How to complete the Data safety form
- Open Play Console, then navigate to the App content page under the Policy section.
- Under Data safety, then click Start.
- Before you start the form, read the Overview section. This section provides information about the questions in the form and the information that you need to provide.
- Once you have read the overview, select Next to move on to the next section.
Data collection and security
In the Data collection and security section, you must review the list of required user data types that you need to disclose.
- For question Does your app collect or share any of the required user data types?, select Yes.
- For question Is all of the user data collected by your app encrypted in transit?, select Yes.
- For question Which of the following methods of account creation does your app support?, select No account creation.
If your application integrates other types of account creation alongside the Encap SDK, then you must check the relevant box for it here.
- For point Add a link that users can use to request that their account and associated data is deleted, you can provide a link if you selected an option in the previous question. If not, then you must select No.
Data types
In the Data types section, you must select all of the user data types that are collected or shared by your app. These data types are relevant to the risk parameters that are possible to enable in your application configuration.
- You must complete the Device or other IDs data type, as the
deviceHashis always collected. - The other data types are optional, as they have to be enabled in the application configuration that your app is configured to use.
- If none of the optional fields are enabled, then you can skip these sections.
- For all other data types not mentioned below, you must leave the fields empty if they do not apply to your application.
Location
You only need to complete this section if it is enabled in the application configuration that your app is configured to use.
The following points are applicable if you have the Location or Geofencing risk parameters enabled:
- If
android.permission.ACCESS_COARSE_LOCATIONexists inAndroidManifest.xml, then tick Approximate location. - If
android.permission.ACCESS_FINE_LOCATIONexists inAndroidManifest.xml, then tick Precise location. - If both permissions are present, then select both options.
App info and performance
You only need to complete this section if it is enabled in the application configuration that your app is configured to use.
If the batteryLevel risk parameter is enabled, then tick Diagnostics.
Device or other IDs
The deviceHash is always collected, therefore you must tick Device or other IDs. You can read more about the device hash in our Device hash appendix.
Data usage and handling
In the Data usage and handling section, you must answer questions about how the data is used and handled for each user data type that your app collects or shares.
You can do this by clicking Start next to each user data type.
Location
You only need to complete this section if it was applicable in the previous section.
- For question Is this data collected, shared, or both?, select Collected.
- For question Is this data processed ephemerally?, select No, this collected data is not processed ephemerally.
- For question Is this data required for your app, or can users choose whether it's collected?, select Users can choose whether this data is collected.
- For question Why is this user data required?, select App functionality.
Diagnostics
You only need to complete this section if it was applicable in the previous section.
- For question Is this data collected, shared, or both?, select Collected.
- For question Is this data processed ephemerally?, select No, this collected data is not processed ephemerally.
- For question Is this data required for your app, or can users choose whether it's collected?, select Data collection is required (users can't turn off this data collection)
- For question Why is this user data required?, select Fraud prevention, security, and compliance.
Device or other IDs
- For question Is this data collected, shared, or both?, select Collected. For question Is this data processed ephemerally?, select No, this collected data is not processed ephemerally.
- For question Is this data required for your app, or can users choose whether it's collected?, select Data collection is required (users can't turn off this data collection)
- For question Why is this user data required?, select App functionality.
How to submit the Data safety form
- Preview the information that will be shown to end-users on Google Play in the Store listing preview.
- Once you are ready to submit your completed form, select Submit.