Google Play Data safety form: how to fill it in correctly
Last reviewed 21 November 2026
Every app on Google Play has a Data safety section, and you write it. It looks like a quick questionnaire, but Google holds you responsible for every answer, including what the libraries inside your app do. Here’s how to get it right the first time.
Every app published on Google Play needs the form, even one that collects nothing. Declare all data that leaves the device, including data sent by analytics, advertising and other libraries in your app, and say whether each item is shared, why, and whether it’s required. Keep it consistent with your privacy policy, and update it whenever the app’s data use changes.
Who has to fill it in
According to Google’s guide, every app published on Google Play must complete the form, including apps on closed, open and production tracks. Only apps that live solely on the internal testing track are exempt. Apps that collect no data at all still fill it in, and still need a privacy policy link.
You’ll find it in Play Console under App content → Data safety.
Collected or shared?
- Collected means data that leaves the device, whether it goes to your server or to someone else’s, including data sent by libraries in your app. Two exceptions: end-to-end encrypted data that only the sender and recipient can read isn’t collected, and data processed only briefly in memory still goes in the form but isn’t shown on your listing.
- Shared means passing data to a third party. Google doesn’t count sending it to your own service providers, transfers for legal reasons, transfers the user starts with consent, or fully anonymised data.
- Advertising libraries are a trap. Google says an SDK that builds ad profiles across many apps isn’t acting as your service provider, so its data use counts.
The libraries in your app count
This is the part most teams get wrong. Analytics, crash reporting, advertising, chat and sign-in libraries all send data, and Google says it’s your responsibility to declare it. Many providers publish their own disclosure guidance, as Firebase does, and Firebase advises checking it again whenever you update the library. Ask your developer for a list of every library that sends data, and what it sends.
Details that catch people out
- Location from an IP address counts as approximate location.
- The advertising ID goes under device or other IDs.
- Required or optional: data the app needs to work must be marked required, not optional.
- Encryption in transit: you can only answer yes if it covers all data, including what libraries send.
- Deletion: if people can create an account, you need a way to delete it inside the app and a web link for deletion requests. Google rejects submissions when these answers have problems.
- One form for everything: it must cover every version, country and age group the app is available to.
- Don’t copy Apple’s answers. Google says its definitions may differ materially from other app stores’, so Apple’s privacy labels won’t map across directly.
- Payments: card details collected directly by a payment service such as Google Play billing don’t need declaring, but purchase history may.
It must match your privacy policy
Google’s User Data policy says the Data safety section and your privacy policy must be consistent. The policy can say more than the form, but not less. It has to be at a public web address, not behind a login and not a PDF.
Keep it up to date
Update the form whenever your data use changes: a new library or a library upgrade, a new feature that collects something, a new purpose, or a new partner you share data with. Google’s review doesn’t check your answers for accuracy, but it does act on mismatches it finds later, from blocked updates to removing the app. See what to do if Google Play rejects your app.
Questions founders ask
My app doesn’t collect any data. Do I still need the form?
Yes. Google requires it from every published app, and you still need to link a privacy policy.
Do I have to declare what Firebase or other libraries collect?
Yes. Data sent by libraries and SDKs inside your app counts as your app’s collection, and Google holds you responsible for declaring it.
Can I reuse my Apple privacy label answers?
Not directly. Google says its data types and definitions may differ from other app stores’, so go through Google’s form question by question.