DEV Community

Cover image for Google Play data safety form: 5 fixes to pass review
ExtensionBooster
ExtensionBooster

Posted on Originally published at appranker.net

Google Play data safety form: 5 fixes to pass review

Originally published on AppRanker.

You submit a routine update and Google Play replies with "Issue found: Invalid Data safety form." The Google Play data safety form is easy to put off and expensive to get wrong: get it wrong and Google can block your updates or remove the app entirely. This article covers the two definitions that decide most answers, what Firebase and AdMob actually declare, and the five fixes that get the form past review.

"Collected" means the data left the phone

Google has required an accurate form from every app since July 20, 2022. Every app on a closed, open or production track must complete it, even an app that collects nothing; only apps that live exclusively on the internal testing track are exempt. A privacy policy is required even when you answer "No data collected."

Two definitions decide most answers:

  • Collected means data transmitted off the user's device: your own API calls, any SDK in the binary, and webviews your app controls.
  • Shared means transferring collected data to a third party, from your server or from the device to another app.

Three cases don't have to be declared as collection: on-device processing (data never leaves the phone), end-to-end encryption, and ephemeral processing (data handled only in memory, kept no longer than needed — it stays in your answers but is not shown on the listing, and Google says data used for advertising or user profiles can never be ephemeral). Pseudonymous data like an analytics ID still counts.

Transfers that don't count as sharing: service providers processing on your behalf (hosting, crash reporting — unless they build ad profiles across customers), legal transfers, user-initiated transfers, and fully anonymized data.

One more rule that causes errors: a data type is optional only if every user on every device in every region can decline it and still use the app's core features.

Build the data inventory before you open Play Console

The form is fast when you know the answers and painful when you don't. List every SDK first — one Gradle line covers it:

./gradlew :app:dependencies --configuration releaseRuntimeClasspath | grep -E "firebase|gms|ads|analytics|crash|facebook|appsflyer|adjust|onesignal|sentry"
Enter fullscreen mode Exit fullscreen mode

Then write one row per data type:

Data type Sent off device by Purpose Shared? Optional?
Email address Your sign-up API Account management No No
Crash logs, Diagnostics Crashlytics App functionality, Analytics No (service provider) No
Device or other IDs Firebase Analytics, AdMob Analytics, Advertising Yes, for ads No

For each SDK, read its data disclosure page (the Google Play SDK Index links to many of them), then audit your own API fields — every field in sign-up, profile, upload, search and support requests — and check the merged manifest for location, contacts, camera and microphone permissions.

What common SDKs actually send off the device

SDK What the vendor documents
Firebase Crashlytics Crash logs (stack traces), diagnostics (app state, device metadata), a Crashlytics installation UUID, plus any custom keys or user IDs you attach
Firebase Cloud Messaging A per-installation identifier, app version, and notification interaction events when paired with Analytics
Google Mobile Ads (AdMob) IP address (approximate location), user product interactions, diagnostics, and device identifiers including the advertising ID and app set ID — collected and shared for advertising, analytics and fraud prevention

Two details that catch people out: what you attach is yours to declare (send a user's email as a Crashlytics user ID and you're collecting Personal info), and ads flip the sharing answer (ad networks are sharing under Google's definition, not service providers). On encryption: Firebase documents HTTPS in transit and AdMob documents TLS — answer Yes to the encryption question only if every endpoint, yours included, is covered.

The five fixes for "Invalid Data safety form"

The typical rejection names the data type (usually Device or other IDs) and sometimes the SDK — often the Play services measurement library that Firebase Analytics depends on. The fix path:

  1. Read the full notice in Play Console or email: it names the version code, the data type, and usually the SDK.
  2. Trace where the SDK comes from: rejection causes are often transitive dependencies — an ads mediation adapter, analytics pulled in by a game engine, or a billing library. The Gradle command above shows you.
  3. Choose one of the two fixes Google offers: declare the data type with the right purposes, or remove or reconfigure the SDK (AdMob documents a manifest setting that stops advertising ID collection).
  4. Update the form and submit a new release if you changed code: the old version code stays flagged until it's replaced.
  5. Make the privacy policy match the form: a form that declares location while the policy never mentions it is an inconsistency reviewers notice.

Google is explicit that its review doesn't verify the accuracy of your declarations — you're responsible, and apps that stay non-compliant can have updates blocked or be removed.

Key takeaways

  • Collected = data sent off the device, by your code or any SDK. Shared = sent to a third party.
  • You're responsible for your SDKs; most rejections are undeclared Device or other IDs.
  • Keep a written inventory and re-check it whenever you add an SDK, permission, or feature.
  • Answer the encryption question Yes only if your endpoints and every SDK use HTTPS or TLS.
  • The form changes alongside your app, not once at launch.

For the full walkthrough in Play Console order — the 14 data categories, the CSV import for managing several apps, and the account deletion rules — see the complete Google Play data safety form guide. Once the form is clean, the next job is sending installs to that listing: AppRanker's pay-to-rank leaderboard shows every rank's price before you pay and links straight to your store page.

Which SDK has caused a data safety rejection in your app — and did you declare it or strip it out?

Top comments (0)