HOME ›
Android›Google Play

How to Fill Out the Google Play Data Safety Form

Aug 5, 2026
4 min read
S
solodroid
Solodroid Developer

For Android developers, successfully navigating the Google Play Console Data Safety form is a mandatory and often confusing step before publishing a new app or submitting an update. Google requires developers to be fully transparent about how their apps collect, share, and handle user data.

If your application is built using a Solodroid template or SDK—which typically includes integrated modules for advertisements (Google AdMob) and push notifications (OneSignal)—your app automatically collects specific analytics identifiers and device data to function properly.

There is no need to guess or worry about app rejections. Below is a comprehensive, step-by-step cheat sheet to filling out the Data Safety form accurately, ensuring full compliance with Google Play’s privacy policies.

Crucial Note Regarding Local Storage: If your app features a “Save” or “Download” button (such as saving a wallpaper or image to the user’s gallery), this does NOT count as Data Collection. Because the file is saved directly to the device’s local storage and no personal user data is transmitted to an external server, you do not need to declare this action in the Data Safety form.

Step 1: Data Collection & Security overview

When you first open the Data Safety section in your Google Play Console, you will be asked a series of fundamental questions regarding your app’s security practices. Answer them exactly as follows:

  • Does your app collect or share any of the required user data types?
    • Select: Yes
  • Is all of the user data collected by your app encrypted in transit?
    • Select: Yes (Explanation: Both AdMob and OneSignal SDKs securely transmit data over HTTPS by default).
  • Do you provide a way for users to request that their data be deleted?
    • Select: No (Explanation: Unless your app has a custom built-in user account/login system where you manually store user profiles on your own server, you cannot delete individual user data from Google or OneSignal’s anonymized analytics servers).

Step 2: Data Types

Scroll down to the next page where you must declare the specific types of data your app processes. Expand the dropdown menus and check the following boxes:

1. Location

  • Check the box for Approximate location.

2. App Activity

  • Check the box for App interactions.

3. App info and performance

  • Check the box for Crash logs.
  • Check the box for Diagnostics.

4. Device or other IDs

  • Check the box for Device or other IDs.

Step 3: Data Usage & Handling Details

After selecting the data types above, click “Next”. You are now required to provide specific details on how and why each piece of data is handled. Click the arrow next to each data type and fill them out using this exact configuration:

1. Approximate Location

  • Is this data collected, shared, or both? Select Collected and shared.
  • Is this data processed ephemerally? Select No.
  • Is this data required or optional? Select Data collection is required (Users cannot opt-out within the basic app UI).
  • Why is this user data collected? Check the boxes for Analytics and Advertising or Marketing.

2. App interactions

  • Is this data collected, shared, or both? Select Collected and shared.
  • Is this data processed ephemerally? Select No.
  • Is this data required or optional? Select Data collection is required.
  • Why is this user data collected? Check the boxes for Analytics and Advertising or Marketing.

3. Crash logs & Diagnostics

(You will need to fill this out twice: once for Crash logs, and once for Diagnostics)

  • Is this data collected, shared, or both? Select Collected and shared.
  • Is this data processed ephemerally? Select No.
  • Is this data required or optional? Select Data collection is required.
  • Why is this user data collected? Check the box for Analytics.

4. Device or other IDs

  • Is this data collected, shared, or both? Select Collected and shared.
  • Is this data processed ephemerally? Select No.
  • Is this data required or optional? Select Data collection is required.
  • Why is this user data collected? Check the boxes for App Functionality (required for OneSignal to send push notifications to specific devices), Analytics, and Advertising or Marketing (required for AdMob’s Android Advertising ID tracking).

Important Warning: Target Audience & COPPA Compliance

The configuration provided above is strictly intended for apps targeting Teens and Adults (ages 13 and up).

If your application is specifically targeted at children (under the age of 13) or is enrolled in the Google Play Families program, you must exercise extreme caution. Google AdMob has strict privacy regulations (COPPA compliance) prohibiting the collection of Advertising IDs and Location data from minors. If your app targets children, you must ensure your AdMob account is configured for Child-directed treatment (Family-safe ads) and adjust the Data Safety form to reflect those restricted data collection practices.

By following this exact configuration for your general audience Solodroid app, your submission will successfully pass the Google Play Data Safety review process without any policy violation issues!

Best selling products