All posts

Google Play Data safety form for a small app

· 6 min read

You are close to your first Play release, and Play Console wants a Data safety form. It asks what your app collects, what it shares and whether you encrypt it. If you use Firebase, ads or crash reporting, it is easy to answer wrong without knowing it. This post covers what Google says, then a simple method for a small app. It is not legal advice.

Who has to fill it in

I read Google's page Provide information for Google Play's Data safety section on 10 November 2026. Google says all developers with an app published on Google Play must complete the form. That includes closed, open and production tracks. The same page says apps that are only active on internal testing tracks are exempt.

So you may not need it for an internal test, but you will need it before your closed test. If your app collects no user data, you still fill in the form and give a privacy policy link. In Play Console, open App content and select Start under "Data safety".

What "collected" and "shared" mean

Google defines both terms. They are narrower and more literal than you might expect.

  • Collect: "transmitting data from your app off a user's device."
  • Share: "transferring user data collected from your app to a third party." A third party is any organization other than you or your service providers.

Google lists cases that do not count as collection:

  • Data processed only on the device.
  • End-to-end encrypted data that nobody but the user can read.
  • Ephemeral processing: data kept only in memory, for no longer than needed to answer a real-time request. This does not cover data used to build ads or user profiles.

And cases that do not count as sharing:

  • Sending data to a service provider that processes it on your behalf.
  • Transfers for specific legal purposes.
  • Actions the user starts, or disclosures they consent to, that meet Google's User Data policy.
  • Fully anonymized data.

Read the exact wording on Google's page before you rely on any of these. A single exception can change an answer.

What the form asks

For each kind of data you collect or share, you pick a data type and a purpose. The types include location, personal info, financial info, messages, photos and videos, app activity, app info and performance, and device or other IDs. The purposes include app functionality, analytics, developer communications, advertising or marketing, fraud prevention and security, personalization and account management.

The form also asks whether all the user data your app collects is encrypted in transit. Google points to standard protocols such as TLS and HTTPS. And it asks whether users can request deletion of their data. Google doesn't prescribe how. Examples it gives are an in-app feature, a contact form or an email address.

If your app has accounts

Google has a separate rule in its account deletion help page. If your app lets users create an account, it must also let them ask for that account to be deleted. You need two things:

  • A prominent in-app path to delete the account and its data, for example in account settings.
  • A web link where users can request deletion. The page must work, name your app or you as the developer, and make the deletion path easy to find. Users shouldn't need to reinstall the app to use it.

You declare this in the Data safety form and enter the web link there. Accounts created and used only offline are outside the rule.

SDKs count too

This is where small apps go wrong. Google says collection and sharing include "user data transmitted off device from your app by libraries and/or SDKs used in your app." You must reflect that in your form, even though you didn't write the code.

Where to look for what an SDK sends:

  • Firebase's page on Google Play's data disclosure requirements has a section for each Firebase SDK. It separates data collected automatically from data collected depending on how you use it. For Crashlytics, for example, it lists stack traces, device metadata and an installation ID, plus any custom keys, logs or user IDs you attach. It says you are "solely responsible" for how you answer, and to review the page whenever you update SDK versions.
  • Google Play SDK Index links to each listed SDK's own guidance on what it collects and why. It covers popular commercial SDKs, not every library.
  • For any SDK not covered, read the provider's privacy docs. If you can't find an answer, don't guess. Ask the provider or drop the SDK.

The privacy policy

Google's privacy policy page sets these rules for the URL you enter under App content:

  • An active, public http or https URL with a valid SSL certificate.
  • Reachable worldwide, with no geofencing or login.
  • A normal web page, not a PDF or a downloadable file.
  • Specific to your app, and it must disclose how the app collects, uses and shares user data.

You must also link to it from your store listing and from inside the app. Google's page doesn't say the policy and the Data safety form must match word for word. My advice, not Google's: write them from the same notes, so they can't contradict each other.

What if you get it wrong

Google says its review "is not designed to verify the accuracy and completeness" of your answers, and you remain responsible for them. If Google finds a misrepresentation, it will "require you to fix it." Apps that don't become compliant are "subject to policy enforcement, like blocked updates or removal from Google Play." That is a good reason to be careful with the first answers, not a reason to panic.

A method that works for a small app

  1. List everything in your build. Open your build.gradle (or version catalog) and write down every dependency that touches the network: Firebase modules, ads, analytics, crash reporting, login, payments.
  2. Write what each one sends. Use the SDK's disclosure page. Note the data type, the purpose and whether it is on by default.
  3. Add what your own code sends. Sign-in details, user content, API calls to your server.
  4. Mark each item collected or shared using Google's definitions above, and whether it is encrypted in transit.
  5. Check deletion. Can users ask? Do you have an account deletion path and web link?
  6. Fill in the form and write the privacy policy from that one document.
  7. Keep the document. Update it, the form and the policy every time you add or upgrade an SDK.

Where TestSwap fits

TestSwap is a free site where app makers review each other's apps: you test someone's app, they test yours. Sign-in is with X, and new accounts start with 3 credits.

A reviewer can tell you which screens ask for data: a sign-up form, a permission prompt, an ad, a missing delete option. That helps you check your notes against what a real user sees. They can't tell you what an SDK sends in the background, and they aren't giving legal advice. TestSwap doesn't review your Data safety form or your privacy policy.

Ask for it in your test task, for example "list every screen that asks for personal data". If you are still planning your release, see internal, closed or open testing and the 12 testers for 14 days rule.

Try it

Post your app on TestSwap with a task that says what to look for. Reviewing someone else's app first is the quickest way to see how it works. Tell me what's missing or broken (@dizid on X). This post is not legal advice. Check Google's pages yourself, as they change.