Data Safety Form Declarations for AdMob, Firebase & Google Analytics in 2026

Google Play's Data Safety form is audited against the actual SDK binaries compiled in your APK or AAB. Even if you personally collect no user data, third-party libraries like AdMob and Firebase collect diagnostic identifiers that you must declare.

What Google AdMob SDK Collects

• Device or other IDs (Advertising ID / AAID): Collected for Advertising or marketing purposes. Must declare as 'Collected' and shared with third parties.
• Approximate Location: If ad requests use network-derived coarse location.
• App Interactions: Ad impressions, clicks, and user engagement metrics.
• Diagnostic Information: Crash logs and ad performance data.

What Firebase Crashlytics & Analytics Collect

• Crash Logs & Diagnostics: Stack traces and device state at crash time for App functionality & Analytics.
• Performance Data: App startup latency and HTTP network request timings.
• User IDs: If you use Firebase Auth or set custom user identifiers.

Always declare data collection as 'Encrypted in transit' when using Google Play services and Firebase libraries, as all communications use HTTPS/TLS.