We constantly publish updates to our documentation, which may not yet be available in your language. For the most current information, use the English version.

for Marketers

Google Play Data Safety

Google Play wants to inform users about how an app collects and shares user data before they download it. To achieve this, each app listing on the store shows information about its privacy and security practices. This information is gathered using the Data safety form in Play Console.

All developers that have an app published on Google Play need to complete the Data safety form. This includes apps on internal, closed, open, or production testing tracks.

Important:

Google states that from April 2022, Play Store users can see the Data safety section. From July 20th 2022, privacy policies and approved Data safety forms are required for all app updates and new app submissions.

We recommend that you review the Google Play guidelines and submit your Data safety form as soon as possible. This ensures you can receive feedback and make necessary changes before rejected forms prevent you from publishing new app updates.

To learn more about Adjust’s privacy practices and end-user options, please see Adjust’s Privacy Policy.

Before you begin

Here's what you need to know before getting started.

Requirements

Your answers should follow the Google Play User Data policy and any applicable laws.
You are solely responsible for keeping your responses accurate and up to date. If your practices change, make sure to update your responses in Google Play.

Data collection by Adjust’s SDK

To complete the Data safety form, you need to know the types of data that you and/or your third-party partners, including Adjust, collect from your app.

Adjust’s SDK is configurable both in what data we collect on your behalf and how you use that data. This means you are mostly choosing the data Adjust can access in your app based on how you configure and implement Adjust’s SDK code.

While there is some data that the SDK collects by default, you always have the flexibility to block or limit sending that data to Adjust. Therefore, you need to identify all possible data types and purposes applicable to your setup, even if not outlined here or even if the data is collected and used in limited situations.

Collection by data type

The following table lists different data types and notes what Adjust collects by default. However, make sure to compare this to your custom configuration of Adjust’s SDK and the data collection practices in your app to confirm that your answers are accurate.

For example: Adjust’s SDK does NOT collect “Personal Info” by default. However, if your app collects user email addresses (or any other type of Personal Info) and then sends that data to Adjust using custom parameters, then you should answer Yes to this field on the form. This is because the Adjust SDK is collecting “Personal Info” you pass to it for your specific app. This includes if the email address is hashed.

In the table below, you can see what data the Adjust SDK does and does not collect by default. In instances where a data type is marked "Yes" or "Optional", you can find out precisely how the SDK handles this data in the dropdowns beneath.

Data types	Data collected by Adjust SDK?
Location Approximate location Precise location	No
Personal information Name Email address User IDs Address Phone number Race and ethnicity Political or religious beliefs Sexual orientation Other info	No
Financial information User payment info Purchase history Credit score Other financial info	No Optional: Adjust can read the details for in-app purchase verification receipt validation, only if you choose to integrate purchase verification SDK and send data to Adjust via custom parameters. Learn more. No No
Health and Fitness Health info Fitness info	No
Messages Emails SMS or MMS Other in-app messages	No
Photos or Videos Photos Videos	No
Audio Files Voice or sound recordings Music files Other audio files	No
Files and Docs	No
Calendar	No
Contacts	No
App activity	Yes, Adjust collects this data on your behalf (Adjust collects sessions/app launches by default. Other types of “Usage Data” is optional and Adjust can collect them on your behalf if you configure it). Learn more.
Web browsing	No
App info and performance Crash logs Diagnostics Other app performance data	No
Device or other identifiers	Yes, Adjust collects the Device ID data on your behalf (e.g. device metadata such as operating system version, Adjust SDK version, etc.). Learn more.

How the SDK handles collected data

Purchase history

App activity

Device or other identifiers

Data use by Adjust

To complete the Data safety form, you need to have a clear understanding of how each data type is being used by you and your third-party partners, including Adjust.

The following table lists the purposes for which Adjust uses data.

	Data used by Adjust?
App functionality	Yes
Analytics	Yes
Developer communications	Optional: Adjust can share the data with you, if you configure the integration.
Advertising or marketing	Optional: Adjust can share the data with you or other entities who display first-party ads in your app if you configure the integration.
Fraud prevention, security, and compliance	Yes
Personalization	Optional: Adjust can share the data with you, which you can use for product personalization, if you choose to export the relevant data.
Account management	No

Data linked to the user

You need to identify whether each data type is linked to a user’s account, device, or identity by you and/or your third-party partners, including Adjust.

Adjust may provide the ability for you to associate the data it collects on your behalf with the Advertising ID or other device identifiers, when allowed by Google’s policies. Any associations you might be capable of making with Adjust’s data (e.g. associations to a user’s account or an individual identity) is unique to your app and at its own discretion.