Do I need to fill out the Data safety form if my app collects no data at all?

Yes. Google's documentation says developers of apps that don't collect any user data still need to complete the form and provide a privacy policy link. You simply answer that you don't collect data.

Do apps in closed testing need to complete it too?

Yes. Apps on closed, open, and production tracks are all included. Only apps that are active solely on the internal testing track don't need to complete it.

Do I need to declare data that Firebase or ad SDKs collect?

Yes. Data collected or shared through libraries and SDKs in your app must also be reflected in the form. Check the data safety guidance published by each SDK provider, or the Google Play SDK Index.

Is sending data to an analytics tool considered 'sharing'?

Google's documentation says transfers to a service provider that processes data on your behalf don't need to be disclosed as sharing. That data may still count as 'collected,' though, so declare it as collected.

What happens if I get it wrong?

You're responsible for making accurate declarations, and Google can take action if it finds discrepancies. The documentation says apps that don't comply may face enforcement such as blocked updates or removal from Google Play.

← Blog

Requirements

How to fill out the Data safety form in Google Play Console: what 'collection' and 'sharing' mean, including SDKs

You have to complete the Data safety form even if your app doesn't collect any data, and apps on closed testing tracks are included. Based on Google's Help Center documentation, we cover the definitions of 'collection' and 'sharing', the steps to fill it out, data taken by third-party SDKs, and what happens if you get it wrong.

Last checked Oct 14, 2026.

1. Who has to fill it out — even apps that collect nothing

The Data safety form is where you declare what user data your app collects and shares. Your answers are shown on your store listing, so users see them before downloading your app. According to the Play Console Help Center, it applies as follows.

All apps on closed, open, and production tracks must complete it. Apps in closed testing are included.
Apps that collect no data must still complete it and provide a privacy policy link.
Apps that are active only on the internal testing track don't need to complete it.

2. What 'collection' and 'sharing' mean

The form's questions are built around these two words. Knowing the documentation's definitions first makes the answers easier.

Collection — transmitting data from your app off the user's device. Data that is processed only on the device and never sent, or data that is end-to-end encrypted so that even you can't read it, doesn't need to be disclosed.
Sharing — transferring user data your app collected to a third party. However, transfers to service providers that process data on your behalf, for legal purposes, as part of an action the user initiated, or of fully anonymized data don't need to be disclosed as sharing.

3. How to fill it out

On the App content page in Play Console, click Start under Data safety.
Read the overview, then answer the data collection and security questions. They ask whether you collect or share any of the required user data types, whether data is encrypted in transit, and whether users can request that their data be deleted.
Select the data types you collect or share.
For each data type, answer what it's used for and how it's handled.
Preview how it will appear on your store listing, then submit.

If you don't know an answer right away, you can save a draft and come back later. You can also export and import the form as a CSV, but importing overwrites your existing answers.

4. Looking only at your own code gets it wrong

The thing people miss most is third-party SDKs. The documentation says data collected or shared through libraries and SDKs in your app must also be reflected in the form.

Check each SDK provider's data safety guidance to see what your analytics, crash reporting, ads, sign-in, and payment SDKs send.
You can look up data safety information for each SDK in the Google Play SDK Index.
Whenever you add or remove an SDK, update the form as well.

5. Keep it consistent with your privacy policy

You need a privacy policy to complete the Data safety form, and the data your policy says you collect has to match your answers in the form. You're responsible for making accurate declarations, and the documentation says apps that don't comply may face enforcement such as blocked updates or removal from Google Play.

For how to publish a policy and add it in Play Console, see How to add a privacy policy; for what apps that require sign-in also need to fill out, see App access.

Frequently asked questions

Do I need to fill out the Data safety form if my app collects no data at all?: Yes. Google's documentation says developers of apps that don't collect any user data still need to complete the form and provide a privacy policy link. You simply answer that you don't collect data.
Do apps in closed testing need to complete it too?: Yes. Apps on closed, open, and production tracks are all included. Only apps that are active solely on the internal testing track don't need to complete it.
Do I need to declare data that Firebase or ad SDKs collect?: Yes. Data collected or shared through libraries and SDKs in your app must also be reflected in the form. Check the data safety guidance published by each SDK provider, or the Google Play SDK Index.
Is sending data to an analytics tool considered 'sharing'?: Google's documentation says transfers to a service provider that processes data on your behalf don't need to be disclosed as sharing. That data may still count as 'collected,' though, so declare it as collected.
What happens if I get it wrong?: You're responsible for making accurate declarations, and Google can take action if it finds discrepancies. The documentation says apps that don't comply may face enforcement such as blocked updates or removal from Google Play.

Meet the requirement without recruiting testers

DUIRE joins your closed test with real Android devices and opens your app every day for 14 days. Registering your app and checking installability are free.

Check installability See how it works