S4U Royale - hybrid watch face

"Firebase Authentication keeps logged IP addresses for a few weeks. It retains other authentication information until the Firebase customer initiates deletion of the associated user, after which data is removed from live and backup systems within 180 days."

Multiple Firebase services retain data indefinitely until the customer explicitly requests deletion, and even then impose a 180-day lag before data is purged from backup systems. Retention periods vary widely across services with vague timeframes like 'a few weeks' or 'a few months'.

"You can control whether your Firebase Service Data may be used by Google to provide more in depth analysis, insights, and recommendations about non-Firebase Google services and improve non-Firebase Google services. If this control is disabled, Firebase Service Data will continue to be used for other purposes, such as those mentioned above, in accordance with our privacy policy."

Firebase Service Data is shared across Google's broader ecosystem of services by default. Even when the opt-out control is enabled, data continues to flow for various other purposes including delivering 'other services you request.'

"Performance Monitoring uses IP addresses to map performance events to the countries they originate from. Country (based on IP address). Carrier (based on Mobile Country and Network Code). Radio/Network information (for example, WiFi, LTE, 3G)."

Firebase Performance Monitoring collects IP addresses to determine user location at the country level, along with carrier and network information, enabling geographic tracking of end users.

"Crashlytics collects the device's model name, CPU architecture, amount of RAM and disk space, a boolean indicating whether the device was jailbroken/rooted, the device's operating system name and version number, a boolean indicating whether the device's proximity sensor was triggered, and the contents of version-control-info.textproto."

Firebase Crashlytics and Performance Monitoring collect detailed device hardware and software information including CPU architecture, RAM, disk space, jailbreak/root status, proximity sensor state, and screen rotation—some of which goes beyond basic crash reporting needs.

"Firebase Service Data is used, for example, to understand your use of Firebase and other Google services. You can control whether your Firebase Service Data may be used by Google to provide more in depth analysis, insights, and recommendations about non-Firebase Google services and improve non-Firebase Google services."

Google uses Firebase Service Data to understand usage patterns across Firebase and other Google services, enabling cross-service profiling. The opt-out only covers some uses—basic cross-service understanding continues regardless.