By Will McCullough, DigiRune Studios ·
Who has to fill it in?
Google is explicit: even developers whose apps do not collect any user data must complete the form, and provide a privacy policy. The exceptions are narrow: apps active only on internal testing tracks, system services and private apps.
What do I declare?
- Whether the app collects or shares each data type Google lists, and for what purposes.
- Whether each type is optional or required for the app to work.
- Whether data is encrypted in transit.
- Whether users can request that their data be deleted.
- Optionally, an independent security review.
What counts as collecting?
Google defines collecting as sending data from your app off a user's device. Two cases do not count: data processed only on the device, and data protected by end-to-end encryption that you cannot read. Note one difference from what many people assume: Google says data sent off the device and only processed briefly still has to be included in your answers, though if it meets Google's standard for ephemeral processing it is not shown on your public listing.
What counts as sharing?
Sharing means passing data you collected to a third party, including other apps on the device. Some transfers are not counted as sharing, including:
- Sending data to a service provider that processes it only on your behalf.
- Transfers for legal reasons.
- Transfers the user starts, or that are covered by clear, prominent consent.
- Data that is fully anonymized.
Do my SDKs count?
Yes. Google says you must reflect data collected or shared by third-party code, such as SDKs and libraries, in your form. Analytics, crash reporting, ads and sign-in libraries often collect device or usage data on their own, so check each vendor's documentation before you answer.
What happens if the answers are wrong?
Google places the responsibility on you: you alone are responsible for complete and accurate declarations. Google reviews apps and may catch some mistakes, but only you know how your app handles data, and apps that misrepresent their data practices or do not become compliant face policy enforcement, which can include blocked updates or removal from Google Play.
How do I keep it accurate?
- Start from what your code really does, not from what you meant it to do. List every way data leaves the app: your server, analytics, crash reports, sign-in, email or feedback forms, file uploads and any AI service.
- Keep your privacy policy, which Google requires, consistent with the form.
- If your app has accounts, make sure the deletion answer matches a real way for users to ask for deletion.
- Revisit the form whenever you add a feature or an SDK.
Publishing on Apple too? Apple's version works differently; see our App Store privacy label guide.
Taking your app to the stores?
The DigiRune Studios Store Launch Kit is a step-by-step guide and checklist for getting through Apple App Store and Google Play review, built from the process we use for our own apps. Apple and Google make every approval decision; the kit helps you submit ready.
See the Store Launch KitSources
Store rules change. Check the official pages on the day you submit. Checked November 19, 2026.