How to correctly map your app's permissions to Google's Data Safety form — and avoid the "Misleading Declaration" suspensions that catch so many developers off guard.
The Most Common Ban Reason
Inconsistencies between your AndroidManifest.xml and your Data Safety Form are the #1 cause of
suspensions in 2025. If you request ACCESS_FINE_LOCATION but claim you don't collect location
data, you will be flagged.
How to Fill It Correctly
- Audit Your Libraries: AdMob, Firebase, and Unity all collect data. You must declare this.
- Encryption: Always mark "Data is encrypted in transit" if you use HTTPS (which you should).
- Account Deletion: If you allow account creation, you must provide a way to delete the account both in-app and via a web link.
Using Policy Audit
Our Policy Audit tool scans your manifest and auto-generates a report telling you exactly what to declare in the Data Safety form, eliminating the guesswork.
Get your Data Safety form right the first time
Run an AI Policy Audit to cross-check your permissions against your declarations before you submit.
Run Policy Audit