Google Play Data Safety Auto-Detector (Gradle, Flutter & React Native)
Avoid "Invalid Data Safety Form" rejections in Google Play Console. Paste your dependency file below to see which data types and purposes your SDKs collect.
Paste package.json, pubspec.yaml, or build.gradle
Automatically detect which third-party SDKs require Google Play Console Data Safety disclosures.
Detected SDKs Requiring Play Console Declarations (6):
Firebase Analytics — App Activity & Device IDs
Tick in Play Console: App interactions, Installed apps, Advertising ID
Purpose: Analytics (Collected & Shared, Encrypted in transit)
Crashlytics / Sentry Crash Reporting — App Info & Performance
Tick in Play Console: Crash logs, Diagnostics, Device ID
Purpose: App functionality & Analytics
Google AdMob / Mobile Ads SDK — Location, Device IDs & App Activity
Tick in Play Console: Approximate location, Advertising ID, Ad interactions
Purpose: Advertising or marketing, Fraud prevention
OneSignal / FCM Push Notifications — Device or Other IDs
Tick in Play Console: Push token / Device ID
Purpose: Developer communications & App functionality
RevenueCat / Google Play Billing / Stripe — Financial Info
Tick in Play Console: Purchase history
Purpose: App functionality & Fraud prevention
Supabase / Firebase Authentication — Personal Info
Tick in Play Console: Name, Email address, User IDs (Requires Account Deletion URL!)
Purpose: Account management