Google Play Data Safety Form: Complete Guide for Developers

The Data safety form is mandatory for every app on Google Play. Incomplete or inaccurate declarations are one of the top reasons production access gets delayed after closed testing. This guide walks through what to declare and how to avoid common errors.

What the Data safety form covers

Google asks what data your app collects, whether it is shared with third parties, whether collection is optional, and your security practices. The answers appear publicly on your Play Store listing — users see them before installing.

Data you must declare

• Personal info: name, email, phone, address, user IDs
• Financial info if you process payments
• Location — coarse or precise — if any SDK accesses it
• Photos, files, or contacts if your app reads them
• App activity: analytics events, crash logs, diagnostics
• Device IDs and advertising IDs from analytics or ad SDKs

Check every SDK in your project

Firebase Analytics, Crashlytics, AdMob, Facebook SDK, Amplitude, Sentry — third-party libraries often collect data your app code never touches directly. Read each SDK's documentation and declare what they collect. Google compares your form against automated scans of your APK.

Permissions must match declarations

If you request CAMERA or READ_CONTACTS in AndroidManifest.xml, your Data safety form should explain why. Remove permissions you do not use — undeclared permission usage is a red flag during review.

Common Data safety mistakes

1. Selecting 'No data collected' when analytics SDKs are present
2. Forgetting account email collection in login flows
3. Not updating the form after adding a new SDK
4. Declaring data as not shared when ad networks receive device IDs
5. Skipping encryption or deletion policy questions

Data safety and closed testing

You can run closed testing before the form is perfect, but production access requires it to be complete and accurate. Fix Data safety while testers are active so you are ready to apply the day eligibility unlocks. PlayStorePass handles the tester side so you can focus on compliance and polish.