Privacy policy clauses for Firebase Crashlytics
Firebase Crashlytics is Google's crash reporting service that automatically captures diagnostic data when mobile apps experience errors or crashes. App developers use it to identify, prioritize, and resolve stability issues affecting user experience.
Free scan · No signup · Results in 60 seconds
What data Firebase Crashlytics collects
Your privacy policy must disclose each of the following data types when you use Firebase Crashlytics.
When does Firebase Crashlytics trigger privacy obligations?
Firebase Crashlytics begins collecting data the moment its SDK is initialized in your app or website. It immediately captures crash logs, stack traces, device identifiers (including IDFA on iOS, Android Advertising ID), OS version, app version, and RAM/storage state—without requiring user action or crash to occur.
GDPR (EU/UK/similar): If your app has even one user in the EU, GDPR Article 6 requires a lawful basis for processing this personal data. Device identifiers and crash metadata constitute personal data under GDPR Article 4(1). You must establish consent (Article 7) or another lawful basis *before* the SDK runs. GDPR Article 13/14 requires you disclose Firebase Crashlytics, Google LLC as processor, and data types in your privacy notice. If you process children's data (under 16, or under 13 in some countries), GDPR Article 8 mandates parental consent.
CCPA (California): If your app collects data from California residents, CCPA Section 1798.100 grants users the right to know what personal information is collected. Device identifiers and diagnostic data qualify. You must disclose Firebase Crashlytics in your privacy policy and honor opt-out rights under Section 1798.120.
