Firebase Analytics and Data Safety: The Row Developers Get Wrong Most
Firebase Analytics is in a huge share of Android apps, and it's also the single most mis-declared row in Data Safety forms. The typical mistake: developers mark "App interactions" as collected but forget "Device or other IDs," which Firebase also gathers by default for its analytics identifier.
Google's own SDK documentation lists what Firebase Analytics collects out of the box — but that list changes when you enable optional features like Google Analytics' advertising ID linking.
The fix
Fix: if you've enabled GoogleAnalytics.getInstance with ad ID collection, your Data Safety form needs a second row for identifiers, not just interactions.
The same check runs automatically when you upload your bundle to the AAB analyzer — permissions, SDK fingerprints, and version info in one pass, free.
Keep going
Run this check on your own AAB
Free analysis, exports when you need them.