Help › Google Play – Invalid Data safety form
Google Play 'Invalid Data safety form': how to fix it
Updated [DATE] · Plain-English guide, not official Apple or Google text.
What the rejection looks like
“We detected user data transmitted off device that you have not disclosed in your app's Data safety form as user data collected.”
Real example shared publicly: source. Exact wording varies.
Common causes
- An SDK (analytics, ads, payments) sends data you didn't declare
- Declared 'no data collected' but the app sends device IDs
- Form not updated after adding a new library
How to fix it
- Open the rejection's 'Issue details' and note the data types and version code Google listed
- List every SDK in your app (analytics, ads, crash reporting, payments, maps) and read each SDK's Play data disclosure page
- Update the Data safety form so it declares everything the app and its SDKs collect or share (including device IDs)
- If the app no longer needs an SDK that sends data, remove or update it
- Make sure the privacy policy matches the Data safety answers
- Submit the updated form (and a new release if you changed code)
Decode your exact message
Paste your full rejection into the free decoder to confirm the guideline and see the likely causes. It runs in your browser; nothing is uploaded.
Want the reply written for you?
The $9 Fix Pack (coming soon) adds a reviewer reply template, a resubmission checklist and ready prompts for your coding tool for this guideline.
See the Fix PackFAQ
I don't collect any data. Why was I flagged?
SDKs for ads, analytics, crash reporting or payments often send device or usage data. Those count as your app's collection.
Do I need a new release?
Only if you change code (e.g. remove an SDK). If you only fix the form, update it and send it for review.
Official source: https://support.google.com/googleplay/android-developer/answer/10787469