CapWrapp
Get started

Google Play · Data safety

Google Play Data safety section inaccurate

Data safety: the form doesn’t match the app

Data safety — Data safety: the form doesn’t match the app. What the app — or an SDK inside it — collects or shares doesn’t match your Data safety answers. Analytics, crash reporting, auth and ad SDKs collect data even when your own code doesn’t.

Updated

What this rejection means

What the app — or an SDK inside it — collects or shares doesn’t match your Data safety answers. Analytics, crash reporting, auth and ad SDKs collect data even when your own code doesn’t.

Why reviewers send it

Google scans the app and its SDKs for the data they collect. If analytics, crash reporting, ads or auth libraries collect something your Data safety answers don’t declare, the form is flagged as inaccurate.

The message Google Play sends

Issue found: Inaccurate Data safety section

The data your app collects or shares does not match what you declared in the Data safety form. For example, your app collects Device or other IDs, which is not disclosed.

The exact wording changes from one review to the next; the policy name is what to look for.

How to fix it

  1. List every SDK in the app and read its Data safety guidance — Firebase, Supabase, Sentry, RevenueCat and ad SDKs each publish one.
  2. Update Play Console → Policy → App content → Data safety so it covers every data type the email names.
  3. Remove SDKs and permissions you don’t use.
  4. Submit the form, and resubmit the release if it was rejected.

Fix it with Lovable, Bolt or Cursor

If the app was built with an AI builder, paste this into it, then check the result on a phone:

List every third-party SDK and Capacitor plugin in this project and, for each, the user data it collects or shares, so we can fill in Google Play’s Data safety form.

What to tell Google Play

Replace the [brackets] with what you actually changed:

We updated the Data safety form to declare [data types] collected by [SDK] for [purpose].

Got a different message?

Paste the whole rejection into the rejection explainer. It recognises this one and 26 others, in your browser — nothing is uploaded.

Other Google Play rejections

Fixed it? Ship the new build to Google Play

CapWrapp builds and signs the Android app from your GitHub repo, bumps the version code, and uploads it to Google Play — then promotes it to production when you are ready.

Get started free Paste a rejection in the explainer
  • Free to start
  • No credit card
  • Sign in with Google or GitHub