Google Play rejects an update because the Data safety form is invalid
Issue found: Invalid Data safety sectionShort answer
Play checks that your Data safety answers match what the app does. It is usually wrong because the form is incomplete, no privacy policy is linked, or SDKs collect or share data you did not declare. Review permissions and SDK guidance, update App content, Data safety, and send the update again.
Fix it fast
1Find out which cause you have
Open Policy status in Play Console and read the exact issue text. It names whether the form is incomplete, or whether the app's behaviour differs from it.
# Play Console > Policy and programs > App content > Data safety, and Policy status2Match what you see, then jump to its fix
- 1
The Data safety status is not a green check markThe form is incomplete or has no privacy policyFix - 2
The app uses ads, analytics, crash or login SDKsThird-party SDKs collect or share data you did not declareFix - 3
Location, contacts or identifiers are used but not declaredAnswers disagree with permissions and APIs the app usesFix
- 1
What does the error look like?
Issue found: Invalid Data safety sectionData safety section is not a green check mark in Policy status
Cause 1 of 3
The form is incomplete or has no privacy policy
1Check
Every app must complete the form even if it collects no data, and must link a privacy policy.
# App content > Privacy policy and Data safety show Completed2Fix
Finish every question, add the privacy policy link, and save.
# App content > Data safety > Start/Manage > answer all sections > Save3Verify
The section shows a green check mark.
# Policy status shows no Data safety issueConfirmed by support.google.com
Cause 2 of 3
Third-party SDKs collect or share data you did not declare
1Check
Data collected or shared by libraries must be in your form. Check each SDK provider's Data safety guidance; the Google Play SDK Index helps find it.
./gradlew :app:dependencies --configuration releaseRuntimeClasspath2Fix
Update the answers to include what each SDK collects and shares.
# App content > Data safety > Manage > edit data types > Save3Verify
The updated form passes the next review.
# Publishing overview shows no pending issueConfirmed by support.google.com
Cause 3 of 3
Answers disagree with permissions and APIs the app uses
1Check
Compare the permissions and APIs in the final manifest with the data types you declared.
./gradlew :app:processReleaseManifest
grep -n "uses-permission" app/build/intermediates/merged_manifest/release/*/AndroidManifest.xml2Fix
Declare every data type the app handles, or remove the permission or API that you do not need.
# Edit the Data safety form, or remove the permission from the manifest3Verify
Submit the update and check Policy status for results.
# Policy > Policy statusConfirmed by support.google.com
How do I stop it coming back?
- Review the Data safety form on every release that adds an SDK or permission.
- Keep a short list of what each SDK collects, from its provider's guidance.
- Check Publishing overview after each submission; reviews can take up to 7 days in exceptional cases.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Mobile apps
adb cannot start because something already holds its port
adb start-server failed
The adb server must bind local TCP port 5037, and every adb client talks to it there.
2 causes, each with a fixMobile apps
The phone shows as unauthorized and Android Studio will not run the app
adb devices lists the phone but Android Studio cannot deploy to it
An unauthorized phone means it has not trusted this computer's RSA key.
3 causes, each with a fixMobile apps
Android Studio cannot pair the phone over Wi-Fi
The Pair devices over Wi-Fi dialog lists no device
Wireless pairing needs the phone on Android 11 or higher and on the same Wi-Fi network as the computer, with current Platform-Tools.
4 causes, each with a fixMobile apps
adb cannot connect to its daemon or start the server
* daemon started successfully *
The adb server is a background process on your computer that listens on TCP port 5037.
2 causes, each with a fixMobile apps
adb prints 'server version doesn't match this client; killing...'
adb server version doesn't match this client; killing...
adb runs a background server, and every adb command is a client.
3 causes, each with a fixMobile apps
adb tcpip 5555 fails because no device is found
adb: more than one device/emulator
adb tcpip only works while the device is attached and listed by adb, because it tells the phone to start listening on port 5555.
4 causes, each with a fix