• IP addresses

How it helps: Cloud Functions uses IP addresses to execute event-handling functions and HTTP functions based on end-user actions.

Retention: Cloud functions only saves IP addresses temporarily, to provide the service.

• Passwords
• Email addresses
• Phone numbers
• User agents
• IP addresses

How it helps: Firebase Authentication uses the data to enable end-user authentication, and facilitate end-user account management. It also uses user-agent strings and IP addresses to provide added security and prevent abuse during sign-up and authentication.

Retention: 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.

• Instance IDs

How it helps: Firebase Cloud Messaging uses Instance IDs to determine which devices to deliver messages to.

Retention: Firebase retains Instance IDs until the Firebase customer makes an API call to delete the ID. After the call, data is removed from live and backup systems within 180 days.

• Instance IDs
• Crash traces

How it helps: Crash Reporting uses crash stack traces to associate crashes with a project, send email alerts to project members and display them in the Firebase Console, and help Firebase customers debug crashes. It uses Instance IDs to measure number of users impacted by a crash.

Retention: Crash Reporting retains crash stack traces for 180 days. Firebase retains Instance IDs until the Firebase customer makes an API call to delete the ID. After the call, data is removed from live and backup systems within 180 days.

• Device specs (iOS)

How it helps: Dynamic Links uses device specs on iOS to open newly-installed apps to a specific page or context.

Retention: Dynamic Links only stores device specs temporarily, to provide the service.

• IP addresses

How it helps: Hosting uses IP addresses of incoming requests to detect abuse and provide customers with detailed analysis of usage data.

Retention: Hosting retains IP data for a few months.

• Device specs (iOS)
• Locally-stored contacts

How it helps: Invites allows users to send invitation links to their contacts. Those links are Firebase Dynamic Links, which use device specs on iOS to open newly-installed apps to a specific page or context.

Retention: App Invites only accesses locally-stored contacts from the device, and only stores device specs temporarily, via Firebase Dynamic Links, to provide the link service.

• Instance IDs
• IP addresses

How it helps: Performance Monitoring uses Instance IDs to calculate the number of unique app instances that access network resources, to ensure that access patterns are sufficiently anonymous. It also uses Instance IDs with Firebase Remote Config to manage the rate of performance event reporting. Additionally, it uses IP addresses to map performance events to the countries they originate from. For more information see Data collection.

Retention: Performance Monitoring keeps instance and IP-associated events for 30 days and de-identified performance data for 90 days. Firebase retains Instance IDs until the Firebase customer makes an API call to delete the ID. After the call, data is removed from live and backup systems within 90 days.

• Instance IDs

How it helps: Predictions uses Instance IDs to associate app instances with a project and to retrieve a time series of events. It uses those events to enable prediction of the likelihood of occurrence of customer-specified events, as well as spend and churn predictions by default.

Retention: Predictions stores instance-associated events for 60 days, and predictions made based on these events for a few weeks. Firebase retains Instance IDs until the Firebase customer makes an API call to delete the ID. After the call, data is removed from live and backup systems within 180 days.

• IP addresses
• User agents

How it helps: Realtime Database uses IP addresses and user agents to enable the profiler tool, which helps Firebase customers understand usage trends and platform breakdowns.

Retention: Realtime Database keeps IP addresses and user agent information for a few days, unless a customer chooses to save it for longer.

• Mobile ad IDs
• IDFVs/Android IDs
• Instance IDs
• Analytics App Instance IDs

How it helps: Google Analytics uses the data to provide analytics and attribution information. The precise information collected can vary by the device and environment. For more information see Data collection.

Retention: Google Analytics retains certain advertising identifier associated data (e.g., Apple’s Identifier for Advertisers and Identifier for Vendors, Android’s Advertising ID) for 60 days, and retains aggregate reporting and certain user-level campaign data without automatic expiration, unless the Firebase customer changes their retention preference in their Analytics settings or deletes their project.

• Instance IDs

How it helps: Remote Config uses Instance IDs to select configuration values to return to end-user devices.

Retention: Firebase retains Instance IDs until the Firebase customer makes an API call to delete the ID. After the call, data is removed from live and backup systems within 180 days.

• Uploaded Images
• Instance IDs

How it helps: The Cloud based APIs store uploaded images temporarily, to process and return the analysis to you. Stored images are typically deleted within a few hours. See the Cloud Vision Data Usage FAQ for more information.

Instance IDs are used by ML Kit when interacting with app instances, for example, to distribute developer models to app instances. Instance IDs also allow ML Kit to utilize Firebase Remote Config to ensure device-side APIs (e.g., topic lists and filters) are kept up to date.

Retention: Firebase retains Instance IDs until the Firebase customer makes an API call to delete the ID. After the call, data is removed from live and backup systems within 180 days.