How to Fill the Google Play Data Safety Form (Step by Step, 2026)

The Data safety section on your Google Play page tells users what data your app collects and shares. Google requires every app to complete the form in Play Console, and a wrong answer can lead to a rejected update or a policy warning. This guide walks you through each step in plain English.

Free tool
Need a privacy policy first?
The Data safety form asks for your privacy policy link. Create one for free in two minutes, with AdMob and Firebase included.
Open Privacy Policy Generator →

Before you start: make a data list

Write down every type of data your app – and every SDK inside it – collects. Check:

  • Your own features: sign-up, profile, contact forms, uploads, location, payments
  • Ads SDKs such as Google AdMob, Meta Audience Network, Unity Ads or AppLovin
  • Analytics and crash tools such as Firebase Analytics and Crashlytics
  • Login, push notification and payment SDKs

Most SDK providers publish a “Data safety” or “data disclosure” page that tells you exactly what to declare. Open each one before you start.

Step 1: Open the form

In Google Play Console, open your app and go to Policy and programs › App content › Data safety (the menu name can change slightly over time – search for “Data safety” in Play Console if you cannot find it).

Step 2: Data collection and security

You answer three main questions:

  • Does your app collect or share any of the required user data types? If you use ads or analytics, the answer is almost always Yes.
  • Is all user data encrypted in transit? Answer Yes only if every connection uses HTTPS/TLS.
  • Do you provide a way for users to request that their data is deleted? If your app lets people create an account, Google also requires an account deletion option inside the app and a web link where users can ask for deletion.

Step 3: Choose the data types

Tick every type that your app or its SDKs collect. The main categories are:

CategoryExamples
LocationApproximate or precise location
Personal infoName, email address, user IDs, phone number
Financial infoPurchase history, payment info
Photos, videos and audioImages or recordings users upload
App activityScreens viewed, taps, search history in the app
App info and performanceCrash logs, diagnostics
Device or other IDsAdvertising ID, Firebase installation ID

Step 4: Explain how each data type is used

For every data type you ticked, Google asks:

  • Is it collected, shared with third parties, or both?
  • Is it processed ephemerally (only in memory, never stored)?
  • Is collection required or can users choose (optional)?
  • Why do you collect it? Options include app functionality, analytics, developer communications, advertising or marketing, fraud prevention and security, personalisation and account management.

For example, an app with AdMob usually declares Device or other IDs as collected and shared for advertising and analytics.

Step 5: Preview and submit

Check the preview of how your Data safety section will look on Google Play, then save and submit. Make sure the answers match your privacy policy – Google compares them.

Common mistakes

  • Saying “no data collected” while using AdMob or Firebase. SDKs collect data even if your own code does not.
  • Forgetting the account deletion link when your app has sign-up.
  • Not updating the form after adding a new SDK or feature.
  • A privacy policy that says something different from your Data safety answers.

FAQ

Is the Data safety form required for all apps?

Yes. Every app on Google Play must complete it, including apps that collect no data – they still submit the form and declare that no data is collected.

What is the difference between “collected” and “shared”?

“Collected” means data leaves the user’s device and is sent to you or your service provider. “Shared” means it is transferred to a third party, such as an ad network, for its own purposes.

How do I declare AdMob in the Data safety form?

Check Google’s AdMob data disclosure guide. Most apps declare device or other IDs (and often approximate location, app interactions and diagnostics) as collected and shared for advertising, analytics and fraud prevention.

Free tool
Try the free Privacy Policy Generator
No signup and nothing uploaded – it runs right in your browser. See all our free tools for app makers on the Free Tools page.
Open Privacy Policy Generator →

Need help building or publishing your app? Talk to Techpass Master – we design, build and publish Android apps for clients worldwide.

WhatsApp us📞 Call now