Google Play safety section
Daria Mamchenkova avatar
Written by Daria Mamchenkova
Updated over a week ago

From April 2022, app developers have to complete the Google Play Data safety section form and publish a link to a privacy policy, even if they don’t collect any of the data types specified by Google.

This article helps you complete the form in the Google Play safety section correctly.

⚠️ The information described in the article is general and basic. Each application has its own settings, so the details of filling out the form may differ.

🔎 You can read more about the Data security form on Google Play here. We also recommend watching the video, which shows how to fill the form.

Google safety form

To find the Google safety form, go to Google Play Console > Policy > App content > Data safety. Click Start.

The Google safety form includes the following sections:

You need to assess your data collection and handling practices before responding to the form. You should fill the form in accordance with your specific use cases, configurations, and partner integrations.

🔎 Affise works with the following data types:

  • Operator, network status (Wi-Fi, mobile operator), IP address

  • Device data

  • Advertiser ID (GAID - IDFA)


This section contains information about the questions you need to answer on the questionnaire, and the information you need to provide. You can also learn the definitions, which you will see in the questionnaire.

Data collection and security

In this section, you should answer the following questions:

  • Does your app collect or share any of the required data types?

  • Is all the user data collected by your app encrypted in transit?

  • Do you provide a way for users to request deletion of their data?

Data types

In this section, you should select all the user data types collected or shared by your app.

You are to answer the following questions:

  • Is the data shared?

  • Is the data processed ephemerally?

  • Is the data required?

  • What is the purpose?

You can view the table with categories, data types, and its description here.

The following table assumes Affise software default configurations:

Data type

Affise default data collection


Location Info

  • Approximate Location

  • Precise Location

See notes

  • Approximate Location: Yes, the IP address is received and mapped to a region/city level.

  • Precise Location: No.

Personal Info

  • Name

  • Email Address

  • Personal identifiers (account ID, number, or name)

  • Address

  • Phone Number

  • Race and ethnicity

  • Political or religious beliefs

  • Sexual orientation or gender identity

  • Other personal info

See notes

Personal info should not be collected. Affise restricts the collection of such personal data as name and address. However, if you configured to transmit hashed emails or hashed phone numbers or a customer user account ID (CUID), respond accordingly.

Financial Info

  • Credit card, debit card, or bank account number

  • Purchase history

  • Credit info

  • Other financial info




Financial information, such as credit cards and credit information, should not be collected.

If you measure in-app purchases (purchase history), respond Yes.

Health and Fitness

  • Health information

  • Fitness information


Should not be collected.


  • Emails

  • SMS or MMS messages

  • Other in-app messages


Should not be collected.

Photos or Videos

  • Photos

  • Videos


Should not be collected.

Audio Files

  • Voice or sound recordings

  • Music files

  • Other audio files


Should not be collected.


  • Calendar events


Should not be collected.

App activity

  • Pageviews and taps in-app

  • In-app search history

  • Installed apps

  • Other user-generated content

  • Other actions

See notes

Affise by default measures app launches, which may be deemed page views or other actions.

Furthermore, if you configure your app to measure specific in-app events, respond Yes in accordance with your configurations.

Web browsing


Should not be collected.

App info and performance

  • Crash logs

  • Diagnostics

  • Other app performance data




Launch time or battery levels may be received for fraud detection purposes.

Device or other identifiers

  • Device or other identifiers (for example, IMEI, MAC, and Ad ID)


Ad ID is collected when accessible.

Data usage and handling

You need to answer the questions about the data usage.

🔎 "Collected" means the transmitted data from your app off a user’s device by any means (for example, webview, or SDK). "Shared" means the transfer of data to a third party (whether off or on the device).

Exceptions include the following:

  • Transfers to service providers that process the data on your behalf and per your instructions.

  • Transfers required for legal purposes (for example, in response to a government request).

  • End-user action or based on a prominent in-app disclosure and consent.

  • Anonymous data.

Read more about data sharing and handling here.


In this section, you can view what information will be shown to users on Google Play in accordance with your answers.

Please contact the Affise Customer Support team regarding all raised questions via the e-mail: [email protected].

Did this answer your question?