Catch up on everthing we announced at this year's Firebase Summit. Learn more

Prepare for Google Play's data disclosure requirements

In May 2021, Google Play announced the new Data safety section, which is a developer-provided disclosure for an app's data collection, sharing, and security practices.

This page can help you complete the requirements for this data disclosure in regards to your usage of Firebase Android SDKs. On this page, you can find information on whether and how our SDKs handle end-user data, including examples of applicable configurations or invocations you can control as the app developer.

We aim to be as transparent as possible in supporting you; however, as the app developer, you are solely responsible for deciding how to respond to Google Play's Data safety section form regarding your app's end-user data collection, sharing, and security practices.

How to use the information on this page

This page lists the end-user data collected by only the latest version of each Firebase Android SDK.

Each SDK has its own section later on this page where we provide information about data collected automatically versus data collected depending on your usage. Automatic collection means that the SDK collects specific data without you invoking any specific method or class in your app. However, in many cases, the data collected by the SDK depends on your app's specific usage of the product, meaning your app's configuration and how you invoke the SDK.

To complete your data disclosure, you can use Android's guide about data types to help you determine which data type best describes the collected data. In your data disclosure, make sure to also account for how your specific app shares and uses the collected data.

Overview of data encryption, data sharing, and data deletion for Firebase Android SDKs

Data encryption

For the collected end-user data listed on this page, Firebase encrypts the data in transit using HTTPS.

Data sharing

For the collected end-user data listed on this page, Firebase does not transfer this data to third-parties except:

  • To third-party subprocessors that assist us in providing Firebase services.
  • In accordance with your instructions (for example, if you choose to link Firebase to other non-Firebase services).
Data deletion

Firebase enables developers to delete end-user data in a manner consistent with the functionality of the Firebase services.



Firebase user agent

The Firebase user agent is not a Firebase Android SDK, but rather a bundle of information that's collected by several Firebase Android SDKs and includes the following:

  • Device metadata: OS version, name, model, brand, and form factor

  • App that was used to install your app (for example, the Play Store) (see documentation)

  • Which Firebase SDKs are used in your app, including their versions

The Firebase user agent is used internally by Google to determine platform and version adoption in order to provide, maintain, and improve Firebase services. It is never linked to a user or device identifier.

If a Firebase Android SDK collects the Firebase user agent, it will be listed in the SDK's section below.



A/B Testing

com.google.firebase:firebase-abt

Data collected automatically

The Firebase A/B Testing SDK does not automatically collect any end-user data.

Other considerations

The Firebase A/B Testing SDK uses data collected from Google Analytics to create and administer experiment groups.

Since the A/B Testing SDK is only used directly by Firebase Remote Config and Firebase In-App Messaging, refer to those specific sections on this page to learn more about any data collection and the purpose of collection.

Data collected depending on your usage

The Firebase A/B Testing SDK doesn't have optional features that the developer can configure or invoke to collect other end-user data.



App Check

com.google.firebase:firebase-appcheck
com.google.firebase:firebase-appcheck-debug
com.google.firebase:firebase-appcheck-safetynet

Data collected automatically

The Firebase App Check SDKs collect the following data automatically.

Data By default, the Firebase App Check SDKs...
Firebase user agent

For information, refer to the Firebase user agent section on this page.

Data collected depending on your usage

Depending on how you configure or invoke the Firebase App Check SDKs and the product's features, your app may collect end-user data that needs to be included in your data disclosure. The following table lists examples of end-user data that can be collected depending on your usage, but make sure to account for any data collected by your specific usage.

Data Depending on your app's configuration and invocation, the Firebase App Check SDKs...
Attestation token from SafetyNet

Collect this attestation token if your app uses SafetyNet as an attestation provider.

Additional information

Purpose for data collection

The Firebase user agent is used internally by Google to determine platform and version adoption in order to provide, maintain, and improve Firebase services. It is never linked to a user or device identifier.

Firebase App Check generally uses the other collected data listed in the sub-sections above to validate app attestations to help protect your Firebase resources from abuse. Also, review the sub-sections above for information about how specific data may be used. In your data disclosure, make sure to also account for how you specifically use the collected data.



Authentication

com.google.firebase:firebase-auth
com.google.firebase:firebase-auth-ktx

Data collected automatically

The Firebase Authentication SDK collects the following data automatically.

Data By default, the Firebase Authentication SDK...
IP address

Collects IP addresses to provide added security and prevent abuse during sign-up and authentication.

User agent strings:

  • whether the app uses FirebaseUI
  • version of Authentication SDK used by the app
  • platform of the device

Collects user agent strings to provide, maintain, and improve Firebase services.

Note that this user agent is not referring to the Firebase user agent.

Data collected depending on your usage

Depending on how you configure or invoke the Firebase Authentication SDK and the product's features, your app may collect end-user data that needs to be included in your data disclosure. The following table lists examples of end-user data that can be collected depending on your usage, but make sure to account for any data collected by your specific usage.

Data Depending on your app's configuration and invocation, the Firebase Authentication SDK...
Display name

Collects a user's display name if the developer provides it.

Email address

Collects a user's email address (as provided by the developer) if the app uses any of the following:

  • email password authentication
  • email link authentication
  • a federated identity as an authentication method and the federated provider's response contains the email address
Phone number

Collects a user's phone number (as provided by the developer) if the app uses any of the following:

  • phone authentication
  • phone number as an authentication method
  • SMS-as-second-factor authentication flows
Contact information

Collects a user's contact information related to third-party authentication providers if the app uses a third-party authentication provider with Firebase Authentication.

For example, a user's identifier may be linked to their Facebook profile if the app uses Facebook authentication, depending on the scopes granted.

Refer to the authentication provider's documentation for more information.

Game Center ID

Collects a user's Game Center ID if the app is linked to the Game Center.

User ID

Generates and stores a unique Firebase Authentication identifier.

Additional information

Purpose for data collection

Firebase Authentication generally uses the collected data listed in the sub-sections above to enable authentication and account management. User agent strings are used to provide, maintain, and improve Firebase services. Also, review the sub-sections above for information about how specific data may be used. In your data disclosure, make sure to also account for how you specifically use the collected data.



Cloud Firestore

com.google.firebase:firebase-firestore
com.google.firebase:firebase-firestore-ktx

Data collected automatically

The Cloud Firestore SDK collects the following data automatically.

Data By default, the Cloud Firestore SDK...
Firebase user agent

For information, refer to the Firebase user agent section on this page.

Data collected depending on your usage

Depending on how you configure or invoke the Cloud Firestore SDK and the product's features, your app may collect end-user data that needs to be included in your data disclosure. Make sure that you account for any developer-defined end-user data that's collected by your specific usage.

Other considerations

If you use Cloud Firestore with Firebase Authentication, and if an end-user is signed-in, then every request from Cloud Firestore automatically includes the applicable User ID from Firebase Authentication.

Additional information

Purpose for data collection

The Firebase user agent is used internally by Google to determine platform and version adoption in order to provide, maintain, and improve Firebase services. It is never linked to a user or device identifier.

Review the sub-sections above for information about how specific data may be used. In your data disclosure, make sure to also account for how you specifically use the collected data, in addition to how you use any developer-defined end-user data collected by the SDK.



Cloud Functions for Firebase

com.google.firebase:firebase-functions
com.google.firebase:firebase-functions-ktx

Data collected automatically

The Cloud Functions for Firebase Client SDK collects the following data automatically.

Data By default, the Cloud Functions for Firebase Client SDK...
Function name

Collects the function name at function invocation.

IP address

Collects the IP address of the function caller at function invocation in order to execute event-handling functions and HTTP functions based on end-user actions.

Firebase Cloud Messaging (FCM) token

Collects the FCM token to allow developers to use it in their functions to send notifications to the calling device at the time of call or to store it for later.

Note that this token is collected independently of whether the app includes or uses the FCM SDK.

Data collected depending on your usage

The Cloud Functions for Firebase Client SDK doesn't have optional features that the developer can configure or invoke to collect other end-user data.

Other considerations

If an end-user is signed-in via Firebase Authentication, every function request automatically includes the applicable User ID from Firebase Authentication.

Additional information

Purpose for data collection

Cloud Functions for Firebase generally uses the collected data listed in the sub-sections above to run backend code in response to events triggered by Firebase features and HTTPS requests from your app. Also, review the sub-sections above for information about how specific data may be used. In your data disclosure, make sure to also account for how you specifically use the collected data.



Cloud Messaging

com.google.firebase:firebase-messaging
com.google.firebase:firebase-messaging-ktx

Data collected automatically

The Firebase Cloud Messaging SDK collects the following data automatically.

Data By default, the Firebase Cloud Messaging SDK...
Application version

Collects the app's version for topic subscription and unsubscription.

Firebase user agent

For information, refer to the Firebase user agent section on this page.

Other considerations

Cloud Messaging has a dependency on the Firebase installations SDK. Since that SDK is transitively included in your app, make sure to account for the end-user data collected automatically by that SDK (see the installations section on this page). To learn about the data that Cloud Messaging uses from that SDK's data collection, visit the Manage Firebase installations documentation.

Data collected depending on your usage

Depending on how you configure or invoke the Firebase Cloud Messaging SDK and the product's features, your app may collect end-user data that needs to be included in your data disclosure. The following table lists examples of end-user data that can be collected depending on your usage, but make sure to account for any data collected by your specific usage.

Data Depending on your app's configuration and invocation, the Firebase Cloud Messaging SDK...
Message delivery metrics

Collects and sends message delivery metrics to BigQuery if the BigQuery integration is enabled and setDeliveryMetricsExportToBigQuery is set to true.

Other considerations

Some optional features of Cloud Messaging depend on the Firebase SDK for Google Analytics. If you include that SDK in your app, make sure to account for the end-user data collected automatically by that SDK (see the Google Analytics documentation). The following table lists additional logged data:

Data If your app includes the Firebase SDK for Google Analytics, then Cloud Messaging...
Notification interaction events

Sends message interaction events locally on-device for logging via the Firebase SDK for Google Analytics in order to provide analytics data for developers.

Additional information

Purpose for data collection

The Firebase user agent is used internally by Google to determine platform and version adoption in order to provide, maintain, and improve Firebase services. It is never linked to a user or device identifier.

Cloud Messaging generally uses the other collected data listed in the sub-sections above to send messages to the client app. Also, review the sub-sections above for information about how specific data may be used. In your data disclosure, make sure to also account for how you specifically use the collected data.



Cloud Storage for Firebase

com.google.firebase:firebase-storage
com.google.firebase:firebase-storage-ktx

Data collected automatically

The Cloud Storage for Firebase SDK collects the following data automatically.

Data By default, the Firebase Cloud Messaging SDK...
Version of the Cloud Storage SDK used by the app

Collects the version of the Cloud Storage for Firebase SDK used by the app.

This value is included in the header of each request.

Firebase Android App ID

Collects the Firebase Android App ID of the app (this is not the app's package name).

This value is included in the header of each request.

Data collected depending on your usage

Depending on how you configure or invoke the Cloud Storage for Firebase SDK and the product's features, your app may collect end-user data that needs to be included in your data disclosure. Make sure that you account for any developer-defined end-user data that's collected by your specific usage.

Other considerations

If you use Cloud Storage for Firebase with Firebase Authentication, and if an end-user is signed-in, then every request from Cloud Storage for Firebase automatically includes the applicable User ID from Firebase Authentication.

Additional information

Purpose for data collection

Cloud Storage for Firebase generally uses the collected data listed in the sub-sections above to provide, maintain, and improve Firebase services. Also, review the sub-sections above for information about how specific data may be used. In your data disclosure, make sure to also account for how you specifically use the collected data, in addition to how you use any developer-defined end-user data collected by the SDK.



Crashlytics

com.google.firebase:firebase-crashlytics
com.google.firebase:firebase-crashlytics-ktx
com.google.firebase:firebase-crashlytics-ndk

Data collected automatically

The Firebase Crashlytics SDK collects the following data automatically.

Data By default, the Firebase Crashlytics SDK...
Stack traces

Collects stack traces when an application crashes.

Relevant application state

Collects relevant application state when an application crashes.

Relevant device metadata

Collects point-in-time metadata about the device when an application crashes.

Crashlytics installation UUID

Generates and stores the Crashlytics installation UUID to measure the number of users impacted by a crash.

Other considerations

Crashlytics has a dependency on the Firebase installations SDK. Since that SDK is transitively included in your app, make sure to account for the end-user data collected automatically by that SDK (see the installations section on this page). Note that Crashlytics doesn't use any of the data collected by the Firebase installations SDK, except to rotate the Crashlytics installation UUID based on changes to the app instance's Firebase installation ID.

Data collected depending on your usage

Depending on how you configure or invoke the Firebase Crashlytics SDK and the product's features, your app may collect end-user data that needs to be included in your data disclosure. The following table lists examples of end-user data that can be collected depending on your usage, but make sure to account for any data collected by your specific usage.

Data Depending on your app's configuration and invocation, the Firebase Crashlytics SDK...
Developer-defined data

Collects any custom keys, logs, and free-text user IDs that a developer attaches to crash reports.

Developer-defined data

Collects any developer-defined non-fatal events with custom stack traces.

Other considerations

Some optional features of Crashlytics depend on the Firebase SDK for Google Analytics. If you include that SDK in your app, make sure to account for the end-user data collected automatically by that SDK (see the Google Analytics documentation). The following table lists the data that Crashlytics uses from that data collection:

Data If your app includes the Firebase SDK for Google Analytics, then Crashlytics...
"breadcrumb" logs

Uses the "breadcrumb" logs collected by the Firebase SDK for Google Analytics. These logs identify user actions immediately before a crash along with crash counts.

Additional information

Purpose for data collection

Firebase Crashlytics generally uses the collected data listed in the sub-sections above to enable crash reporting and crash management services. Also, review the sub-sections above for information about how specific data may be used. In your data disclosure, make sure to also account for how you specifically use the collected data, in addition to how you use any developer-defined end-user data collected by the SDK.



com.google.firebase:firebase-dynamic-links
com.google.firebase:firebase-dynamic-links-ktx

Data collected automatically

The Firebase Dynamic Links SDK collects the following data automatically.

Data By default, the Firebase Dynamic Links SDK...
Dynamic link URL

Collects the dynamic link URL when the URL is interacted with, including the developer-defined metadata that the developer sets in the link when the link was created.

If the app is installed with the Firebase Dynamic Links SDK integrated, then Firebase logs the app state and link interaction events.

Other considerations

If a user interacts with a Firebase dynamic link, the following data is logged automatically, regardless if the app is installed on the user's device:

Data By default, Firebase...
Dynamic link URL

Logs the dynamic link URL when the URL is interacted with, including the developer-defined metadata that the developer sets in the link when the link was created.

Package name of the app

Logs the app's package name for deferred-deep linking (deep-link post app install).

App state

Logs information relating to the state of the app on the user's device, including install state and if the app has been opened before.

Link interaction events

Logs link interaction events.

Data collected depending on your usage

The Firebase Dynamic Links SDK doesn't have optional features that the developer can configure or invoke to collect other end-user data.

Other considerations

Some optional features of Dynamic Links depend on the Firebase SDK for Google Analytics. If you include that SDK in your app, make sure to account for the end-user data collected automatically by that SDK (see the Google Analytics documentation). The following table lists additional logged data:

Data If your app includes the Firebase SDK for Google Analytics, then Dynamic Links...
Link interaction events

Sends link interaction events locally on-device for logging via the Firebase SDK for Google Analytics in order to provide analytics data for developers.

Additional information

Purpose for data collection

Firebase Dynamic Links generally uses the collected data listed in the sub-sections above to take end users directly to the linked content in your app. Also, review the sub-sections above for information about how specific data may be used. In your data disclosure, make sure to also account for how you specifically use the collected data, in addition to how you use any developer-defined end-user data collected by the SDK.



Google Analytics

com.google.firebase:firebase-analytics
com.google.firebase:firebase-analytics-ktx

Google Analytics is preparing documentation about its product's behaviors for publication. We will update this section with more information in the coming weeks.



In-App Messaging

com.google.firebase:firebase-inappmessaging
com.google.firebase:firebase-inappmessaging-display
com.google.firebase:firebase-inappmessaging-ktx
com.google.firebase:firebase-inappmessaging-display-ktx

Data collected automatically

The Firebase In-App Messaging SDK collects the following data automatically.

Data By default, the Firebase In-App Messaging SDK...
Message interaction events, including impressions, clicks, and dismissals

Sends message interaction events in order to provide analytics data for developers.

Other considerations

In-App Messaging has a required dependency on the Firebase SDK for Google Analytics. Since you must include that SDK in your app, make sure to account for the end-user data collected automatically by that SDK (see the Google Analytics documentation). The following table lists examples of how the In-App Messaging SDK interacts with data from Google Analytics:

Data If your app includes the Firebase SDK for Google Analytics, then Firebase In-App Messaging...
Message interaction events, including impressions, clicks, and dismissals

Sends message interaction events locally on-device for logging via the Firebase SDK for Google Analytics in order to provide analytics data for developers.

User properties

Sets and uses user properties collected by the Firebase SDK for Google Analytics in order to target messages that are based on user property conditions.

In-App Messaging also has a dependency on the Firebase installations SDK. Since that SDK is transitively included in your app, make sure to account for the end-user data collected automatically by that SDK (see the installations section on this page). To learn about the data that In-App Messaging uses from that SDK's data collection, visit the Manage Firebase installations documentation.

Data collected depending on your usage

The Firebase In-App Messaging SDKs don't have optional features that the developer can configure or invoke to collect other end-user data.

Additional information

Purpose for data collection

Firebase In-App Messaging generally uses the collected data listed in the sub-sections above to send messages to end users within the app itself. Also, review the sub-sections above for information about how specific data may be used. In your data disclosure, make sure to also account for how you specifically use the collected data.



Installations

com.google.firebase:firebase-installations
com.google.firebase:firebase-installations-ktx

Data collected automatically

The Firebase installations SDK collects the following data automatically.

Data By default, the Firebase installations SDK...
Firebase installation ID (FID)

Generates and collects a per-installation identifier (FID) that does not uniquely identify a user or physical device.

IP address

Collects network request sender IP addresses, which may be used for debugging purposes.

Firebase user agent

For information, refer to the Firebase user agent section on this page.

Data collected depending on your usage

The Firebase installations SDK doesn't have optional features that the developer can configure or invoke to collect other end-user data.

Additional information

Purpose for data collection

The Firebase user agent is used internally by Google to determine platform and version adoption in order to provide, maintain, and improve Firebase services. It is never linked to a user or device identifier.

Firebase installations generally uses the other collected data listed in the sub-sections above to provide a unique identifier to identify app installations. Also, review the sub-sections above for information about how specific data may be used. In your data disclosure, make sure to also account for how you specifically use the collected data.



Firebase ML model downloader

com.google.firebase:firebase-ml-modeldownloader
com.google.firebase:firebase-ml-modeldownloader-ktx

Data collected automatically

The Firebase ML model downloader SDK collects the following data automatically.

Data By default, the Firebase ML model downloader SDK...
ML model download metadata, including download events, deletion events, and errors

Collects model download event metadata to monitor for stability and latency issues.

installation auth token

Collects installation auth tokens for device authentication when interacting with app instances (for example, to distribute developer models to app instances).

Other considerations

Firebase ML model downloader has a dependency on the Firebase installations SDK. Since that SDK is transitively included in your app, make sure to account for the end-user data collected automatically by that SDK (see the installations section on this page). To learn about the data that Firebase ML model downloader uses from that SDK's data collection, visit the Manage Firebase installations documentation.

Data collected depending on your usage

The Firebase ML model downloader SDK doesn't have optional features that the developer can configure or invoke to collect other end-user data.

Additional information

Purpose for data collection

Firebase ML generally uses the collected data listed in the sub-sections above to download ML models. Firebase ML aggregates and uses the model download metadata to monitor product quality, understand usage, and inform product direction. Also, review the sub-sections above for information about how specific data may be used. In your data disclosure, make sure to also account for how you specifically use the collected data.



Performance Monitoring

com.google.firebase:firebase-perf
com.google.firebase:firebase-perf-ktx

Data collected automatically

The Firebase Performance Monitoring SDK collects the following data automatically.

Data By default, the Firebase Performance Monitoring SDK...
App performance metrics, including app start time and network request latency

Collects app performance metrics during the lifecycle and end-user usage of the app.

CPU/memory usage

Collects CPU/memory usage of the application to provide a timeline view of the app’s performance.

Relevant device metadata

Collects relevant device metadata to filter the performance data against different segments of devices.

IP address

Collects the IP address to map performance events to the countries they originate from.

Other considerations

Performance Monitoring has a dependency on the Firebase installations SDK. Since that SDK is transitively included in your app, make sure to account for the end-user data collected automatically by that SDK (see the installations section on this page). To learn about the data that Performance Monitoring uses from that SDK's data collection, visit the Manage Firebase installations documentation.

Performance Monitoring also has a dependency on the Firebase Remote Config SDK to help control the volume of events collected from an application. Since that SDK is transitively included in your app, make sure to account for the end-user data collected automatically by that SDK (see the Remote Config section on this page).

Data collected depending on your usage

Depending on how you configure or invoke the Firebase Performance Monitoring SDK and the product's features, your app may collect end-user data that needs to be included in your data disclosure. The following table lists examples of end-user data that can be collected depending on your usage, but make sure to account for any data collected by your specific usage.

Data Depending on your app's configuration and invocation, the Firebase Performance Monitoring SDK...
Developer-defined custom traces

Collects app performance metrics for any custom traces that a developer instruments in their app.

Custom performance metrics
(developer-defined data)

Collects any custom performance metrics that a developer attaches to custom traces.

Custom attributes
(developer-defined data)

Collects any custom attributes that a developer attaches to custom traces.

Additional information

Purpose for data collection

Firebase Performance Monitoring generally uses the collected data listed in the sub-sections above to enable app performance reporting and monitoring. Also, review the sub-sections above for information about how specific data may be used. In your data disclosure, make sure to also account for how you specifically use the collected data, in addition to how you use any developer-defined end-user data collected by the SDK.



Realtime Database

com.google.firebase:firebase-database
com.google.firebase:firebase-database-ktx

Data collected automatically

The Firebase Realtime Database SDK collects the following data automatically.

Data By default, the Firebase Realtime Database SDK...
IP address

Collects IP addresses to enable the profiler tool, which helps developers understand usage trends and platform breakdowns

User agents

Collects user agent strings to enable the profiler tool, which helps developers understand usage trends and platform breakdowns

Note that this user agent is not referring to the Firebase user agent.

Data collected depending on your usage

Depending on how you configure or invoke the Firebase Realtime Database SDK and the product's features, your app may collect end-user data that needs to be included in your data disclosure. Make sure that you account for any developer-defined end-user data that's collected by your specific usage.

Other considerations

If you use Realtime Database with Firebase Authentication, and if an end-user is signed-in, then every request from Realtime Database automatically includes the applicable User ID from Firebase Authentication.

Additional information

Purpose for data collection

Please review the sub-sections above for information about how specific data may be used. In your data disclosure, make sure to also account for how you specifically use the collected data, in addition to how you use any developer-defined end-user data collected by the SDK.



Remote Config

com.google.firebase:firebase-config
com.google.firebase:firebase-config-ktx

Data collected automatically

The Firebase Remote Config SDK collects the following data automatically.

Data By default, the Firebase Remote Config SDK...
Country code

Collects country code in order to target parameters that are based on this data.

Language code

Collects language code in order to target parameters that are based on this data.

Time zone

Collects time zone in order to target parameters that are based on this data.

Platform version

Collects platform version in order to target parameters that are based on this data.

OS version

Collects OS version in order to target parameters that are based on this data.

Firebase Android App ID

Collects the Firebase Android App ID of the app (this is not the app's package name) in order to target parameters that are based on this data.

Package name of the app

Collects the package name in order to target parameters that are based on this data.

Version of the Remote Config SDK used by the app

Collects the version of the SDK to provide, maintain, and improve Firebase services.

Other considerations

Remote Config has a dependency on the Firebase installations SDK. Since that SDK is transitively included in your app, make sure to account for the end-user data collected automatically by that SDK (see the installations section on this page). To learn about the data that Remote Config uses from that SDK's data collection, visit the Manage Firebase installations documentation.

Data collected depending on your usage

The Firebase Remote Config SDK doesn't have optional features that the developer can configure or invoke to collect other end-user data.

Other considerations

Some optional features of Remote Config depend on the Firebase SDK for Google Analytics. If you include that SDK in your app, make sure to account for the end-user data collected automatically by that SDK (see the Google Analytics documentation). The following table lists examples of how the Remote Config SDK interacts with data from Google Analytics:

Data If your app includes the Firebase SDK for Google Analytics, then Remote Config...
User properties

Sets and uses user properties collected by the Firebase SDK for Google Analytics in order to target parameters that are based on user property conditions.

Note that we're preparing documentation about Personalization. We will update this section with more information in the coming weeks.

Additional information

Purpose for data collection

Firebase Remote Config generally uses the collected data listed in the sub-sections above to change the behavior and appearance of your app without publishing an app update. Aggregated data for OS version and SDK version is used by Firebase to understand usage trends and inform product direction. Also, review the sub-sections above for information about how specific data may be used. In your data disclosure, make sure to also account for how you specifically use the collected data.



Other helpful resources