Google Play Data Safety Generator

Google Play has required the Data Safety form since July 2022, and tightened Android ID disclosure in April 2025. About 40% of Play rejections trace to a mismatch between this form and actual SDK behavior. Paste your build.gradle dependencies or list your SDKs, answer a few questions, get a checklist you can keep open beside Play Console. Pairs with the iOS App Privacy Label tool and the Privacy Manifest generator.

1. Your Android SDKs

Paste your build.gradle dependencies block (recommended)Or list SDK names manually (Android artifact IDs or iOS canonical names — we accept both)

2. What does your app's own code collect?

Don't include data your SDKs collect — those are auto-detected. Only tick what your code directly handles.

Collect email addresses?Collect names?Collect phone numbers?Collect precise location (GPS)?Collect coarse location (city/region)?Collect photos or videos?Collect health data?Collect contacts?Collect crash logs / diagnostics?Track product interactions for analytics?

My app shares any of the above with third partiesTracking SDKs (AppsFlyer, AdMob, Adjust, etc.) auto-flag as shared regardless of this answer.

3. Security questions (Google asks these at the top of the form)

Data is encrypted in transitAlmost always Yes if you use HTTPS — most SDKs default to it.Users can request data deletion (account deletion / data wipe flow)Google strongly recommends declaring Yes — implementing a delete-account flow is required for GDPR + CCPA + PDPL anyway.

For guidance, not legal advice. Google's Data Safety form documentation is the source of truth. Built by Arqam360.