Google Play data safety policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Google Play apps completing or correcting the Data safety declarations in Play Console.
Selecting “no data collected” doesn’t make it true if a library sends information off the device. Google’s Data safety policy requires accurate, maintained answers describing the app’s collection, use, and sharing, including third-party code.
Build the answers from evidence
List data types, recipients, purposes, retention, and user choices for the submitted version. We’d compare actual requests with SDK settings, rather than copy another app’s form. Permissions and data collection are different questions.
Correct the behavior or the form
Remove unwanted collection or update the answers and privacy policy to describe the permitted behavior accurately. Use the Data safety guide for definitions and its noted ambiguity around ephemeral processing; don’t silently resolve contradictory official wording.
For a rejection, follow the invalid-form checks. Test the affected flow with fictional data and verify the saved console answers. Tell Google which data type or sharing answer changed and the evidence behind it.
Messages this guide can help with
Data safety; Data safety policy violation; Data safety rejection; Data safety denied
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Google Play: Data safety Checked 22 September 2026