Google Play Data safety: the privacy policy link you need to finish the form
By Paul Cranmer, Founder · Last verified October 2026 · Google Play Console · App content → Data safety
Google's Data safety help page says it up front: before you start the form, make sure you have added a privacy policy, because one is required to complete the Data safety form and to have your data safety information shown to users. Developers of apps that collect no data must complete the form and provide the policy link too. This page shows the order to do things in so the form saves on the first pass, and how to keep the form and the policy saying the same thing.
Who this is for
- Developers whose Data safety section will not complete or publish
- Teams updating SDKs and re-answering collection and sharing questions
- First-time publishers who met the form before the policy
Not for
- The privacy policy warning on the Policy status page (see that how-to)
- Account deletion requirements (a separate App content item)
What the platform requires
- A privacy policy is required to complete the Data safety form and to have data safety information shown to users.
- Developers of apps that do not collect user data must complete the form and provide a link to their privacy policy.
- The Data safety answers (collected, shared, security practices) must be consistent with what the policy says.
- The policy itself is entered under App content → Privacy Policy, not inside the Data safety form.
Get a live URL first
Run the wizard as a Mobile App and tick the SDKs you ship; the page lists the same data types the Data safety form asks about, which makes the two consistent. Mobile apps are free.
Get the privacy policy URL for your Android app (free)Step-by-step: paste your privacy policy URL
- Add the privacy policy first. Play Console → Policy and programs → App content → Privacy Policy → Start or Manage → paste the live HTTPS URL → save. Without it the Data safety form cannot complete.
- Open Data safety. App content → Data safety → Start (or Manage). The overview explains the sections: data collection and security, data types, data usage and handling.
- Answer collection and sharing from the policy. For each data type your policy names, declare whether it is collected or shared and why. SDKs count: analytics, crash reporting and ads SDKs collect on your behalf.
- Declare security practices and deletion. Answer the encryption-in-transit and deletion-request questions truthfully; the policy should state the same retention and deletion path.
- Submit and check the store listing. Save and submit. After review the Data safety section and the privacy policy link appear on the store listing. If they disagree, Google can flag the listing later; fix the page first, then the form.
Field labels to look for
- App content → Privacy Policy
- Where the URL lives; required before Data safety completes.
- App content → Data safety
- The questionnaire; Start then Manage.
- Store listing
- Shows both the Data safety summary and the privacy policy link.
Common reasons the form fails
- Starting the Data safety form before adding the policy
- Declaring no collection while the policy lists analytics
- Forgetting SDK collection (crash logs, advertising ID)
- A policy URL that changed after the form was submitted
FAQ
Can I complete the Data safety form without a privacy policy?
No. Google's help page says a privacy policy is required to complete the Data safety form and to have the information shown to users.
My app collects nothing. Do I still fill the form?
Yes. Developers of apps that do not collect user data must complete the form and provide a link to their privacy policy.
Where is the privacy policy link entered?
Under App content → Privacy Policy, separate from the Data safety questionnaire.