How to fill the Google Play Data Safety in the Play Console?

Here is all the information needed to fill the Google Play Data Safety section in the Play Console.

About Google Play's Data Safety section

In May 2021, Google rolled out a new Data Safety Section in the Play Console, where developers must declare their apps' privacy and security practices such as:

• Collected data: type of data collected and purposes of the data collection.

• Data shared: data collected and communicated with third parties.

• Security practices and data handling.

Google Play Store - Data safety

Information provided by developers is shown in your app listing on the PlayStore, allowing final users to know the kind of data your app collects before installing your app.

User-side Data safety sharing

Completing the Data Safety form

Important note

Before filling in the questionnaire, please take some time to:

• 📚 Read the documentation: Make sure you read Batch documentation on the data you are collecting by default via the SDK.

• ⚙️ Check your integration: Developers can disable part of the data collection or collect additional data if needed. Review your current integration of Batch SDK to be sure you provide the correct information in the Data Safety form.

• 🔒 Consult your data privacy / legal team: As a data controller, you are responsible for defining the data collected via Batch and the purposes of the data collection. This article only provides basic information on the Data Safety form and must not be considered legal advice.

Starting the questionnaire

CommentShare feedback on the editorFirst of all, go to the Play Console. Select your project, then scroll down and click "App content" in the left panel. Locate the "Data safety" section and click "Start". The questionnaire is divided into three parts:CommentShare feedback on the editor

1. CommentShare feedback on the editorData collection and security

2. CommentShare feedback on the editorData types

3. CommentShare feedback on the editorData usage and handling

CommentShare feedback on the editorThe information provided will be reviewed by Google teams as part of the app review process.CommentShare feedback on the editor

Data collection and security

Quesitons	Answers related to Batch SDK
Does your app collect or share any of the required user data types? (see more here on data types)	Yes, data is collected via Batch SDK based on choices made by the developer.
Is all of the user data collected by your app encrypted in transit?	Yes, data collected via Batch SDK and sent to Batch servers is encrypted in transit.
Do you provide a way for users to request that their data be deleted?	Yes, data collected via Batch SDK can be deleted. You will find more details on that point in the "Actionable features for GDPR compliance" part of our GDPR compliance article.

Data types

To help you fill the Data Safety form required by Google, we sorted the data collected by default by Batch using categories provided by Google in their documentation.

Category	Answers related to Batch SDK
Location	Approximate location: By default, Batch uses IP geolocation to determine approximately the city where users are located. Precise location: Not collected by default. Only collected if the app uses Batch SDK methods to share precise locations with Batch (see documentation).
Personal info	Not collected by default. Only collected if the app uses Batch SDK methods to send user IDs, email addresses, phone numbers, attributes, etc (see documentation).
Financial info	Not collected by default. Only collected if the app uses Batch SDK methods to send data on purchase history (see documentation).
Health and Fitness	Not collected by default. Only collected if the app uses Batch SDK methods to send data on fitness habits via attributes or events (see documentation).
Messages	Other in-app messages: By default, Batch SDK will track user activity related to push notifications and In-App messages for analytics and segmentation purposes: Push notifications: push received/opened. In-App messages: displays, clicks on In-App buttons and on the close button.
Photo and videos	Not collected.
Audio files	Not collected.
Files and docs	Not collected.
Calendar	Not collected.
Contacts	Not collected.
App activity	App interactions: Batch SDK collects some app activity data like lifecycle events, In-App messages interactions, Inbox messages interactions or push opt-in status. Other data subcategories: Not collected by default. Only collected if the app uses Batch SDK methods to track user interactions (see documentation).
Web browsing	Not collected.
App info and performance	Diagnostics: Batch SDK tracks internal metrics on the performance of Batch web services.
Device or other IDs	Batch SDK generates an anonymous ID the first it starts, the "installation id" (see more here). Other IDs, attached to the installation, can be collected: A push token is required to send push notifications to the device. Advertising ID : SDK < v2.0 : if the app can share it with Batch SDK. The collection of this data can be deactivated (see documentation). SDK > v2.0 : Advertising IDs are no longer collected by Batch.