Prepare for Google Play's data disclosure requirements
In May 2021, Google Playannounced 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 inregards to your usage of Firebase Android SDKs. On this page, you can findinformation on whether and how our SDKs handle end-user data, including examplesof applicable configurations or invocations you can control as the appdeveloper.
We aim to be as transparent as possible in supporting you; however, as the appdeveloper, you are solely responsible for deciding how to respond toGoogle Play's Data safety section form regarding your app's end-user datacollection, sharing, and security practices.
How to use the information on this page
This page lists the end-user data collected by only thelatest version ofeach Firebase Android SDK.
Each SDK has its own section later on this page where we provide informationabout datacollected automatically versus datacollected depending onyour usage. Automatic collection means that the SDK collects specific datawithout you invoking any specific method or class in your app. However, in manycases, the data collected by the SDK depends on your app's specific usage of theproduct, meaning your app's configuration and how you invoke the SDK.
To complete your data disclosure, you can use Android'sguide about data types to help you determine whichdata type best describes the collected data.In your data disclosure, make sure to also account for how your specific appshares and uses the collected data.
Important: To help you ensure that your app's disclosures are accurate, we recommend the following:- Always use the latest SDK versions in your app. This page lists the data collected by only thelatest version of each SDK.
- Review this page whenever you update your app's SDK versions. Check that your data disclosures are accurate and up-to-date.
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:
|
| Data deletion | Firebase enables developers to delete end-user data in a manner consistent with the functionality of the Firebase services. |
Firebase user agent
TheFirebase user agent is not a Firebase Android SDK, but rather a bundleof information that's collected by several Firebase Android SDKs and includesthe following:
Device metadata: OS version, name, model, brand, and form factor
App that was used to install your app (for example, the Play Store) (seedocumentation)
Which Firebase SDKs are used in your app, including their versions
The Firebase user agent is used internally by Google to determine platform andversion 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 inthe SDK's section below.
A/B Testing
com.google.firebase:firebase-abt
Data collected automatically
TheFirebase A/B Testing SDK does notautomatically collect any end-userdata.
Other considerations
TheFirebase A/B Testing SDK sets and usesGoogle Analytics userproperties in order to specify membership in experiment groups forFirebase Remote Config andFirebase In-App Messaging.
Since theA/B Testing SDK is only used directly byFirebase Remote Config andFirebase In-App Messaging, refer to those specific sectionson this page to learn more about any data collection and the purpose ofcollection.
Data collected depending on your usage
TheFirebase A/B Testing SDK doesn't have optional features that thedeveloper can configure or invoke to collect other end-user data.
Firebase AI Logic
com.google.firebase:firebase-ai
Firebase AI Logic was formerly called "Vertex AI in Firebase" with thepackagecom.google.firebase:firebase-vertexai.
Data collected automatically
TheFirebase AI Logic SDK collects the following dataautomatically.
| Data | By default, theFirebase AI Logic SDK... |
|---|---|
| Model name | Collects the model name at invocation. |
| Version of the SDK used by the app | Collects the version of theFirebase AI Logic SDK used by the app. This value is included in the header of each request. |
| Language version | Collects the version of the Kotlin runtime used by the app. This value is included in the header of each request. |
| Firebase App ID | If data collection is enabled, collects the Firebase App ID. This value is included in the header of each request. |
| App Version | If data collection is enabled, collects the app version. This value is included in the header of each request. |
Data collected depending on your usage
Depending on how you configure or invoke theFirebase AI Logic SDK andthe product's features, your app may collect end-user data that needs to beincluded in your data disclosure. Make sure that you account for anydeveloper-defined end-user data that's collected by your specific usage.
Other considerations
If you useFirebase AI Logic withFirebase Authentication, and if an end-user issigned-in, then every request fromFirebase AI Logic automatically includesthe applicable User ID fromFirebase Authentication.
If you enableAI monitoring in theFirebase consolefor theVertex AI Gemini API, then the prompts and generated output fromeach sampled request are collected along with performance and usage metrics.
Make sure to reviewData governance and Responsible AI in theFirebase AI Logic documentation to ensure that you're accounting for youruse of the underlying APIs(theVertex AI Gemini API or theGemini Developer API).
Additional information
Purpose for data collection
Firebase AI Logic generally uses the collected data listed in thesub-sections above to invoke the backend service in response to requests fromyour app. Also, review the sub-sections above for information about howspecific data may be used.In your data disclosure, make sure to also account for how you specifically usethe collected data, in addition to how you use any developer-defined end-userdata collected by the SDK.
App Check
com.google.firebase:firebase-appcheckcom.google.firebase:firebase-appcheck-ktxcom.google.firebase:firebase-appcheck-debugcom.google.firebase:firebase-appcheck-playintegrity
Data collected automatically
TheFirebase App Check SDKs collect the following dataautomatically.
| Data | By default, theFirebase App Check SDKs... |
|---|---|
| Firebase user agent | For information, refer to theFirebase user agent section on this page. |
Data collected depending on your usage
Depending on how you configure or invoke theFirebase App Check SDKs and theproduct's features, your app may collect end-user data that needs to be includedin your data disclosure. The following table lists examples of end-user datathat can be collected depending on your usage, but make sure to account for anydata collected by your specific usage.
| Data | Depending on your app's configuration and invocation, theFirebase App Check SDKs... |
|---|---|
| Integrity token fromPlay Integrity | Collect this integrity token if your app uses Play Integrity as an attestation provider. See additionaldata safety information for Play Integrity. |
Additional information
Purpose for data collection
The Firebase user agent is used internally by Google to determine platform andversion 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 listedin the sub-sections aboveto validate app attestations to help protect your backend resources from abuse.Also, review the sub-sections above for information about howspecific datamay be used.In your data disclosure, make sure to also account for how you specifically usethe collected data.
App Distribution
FullApp Distribution Android SDK implementation
com.google.firebase:firebase-appdistribution
The fullApp Distribution Android SDK implementation is intended for Betatesting usage only. Do not include the fullApp Distribution SDK implementationin your application when submitting toGoogle Play.
API-onlyApp Distribution Android SDK
com.google.firebase:firebase-appdistribution-apicom.google.firebase:firebase-appdistribution-api-ktx
Data collected automatically
The API-onlyApp Distribution Android SDK does notautomatically collect anyend-user data.
Data collected depending on your usage
The API-onlyApp Distribution Android SDK doesn't have optional features that thedeveloper can configure or invoke to collect other end-user data.
Authentication
com.google.firebase:firebase-authcom.google.firebase:firebase-auth-ktx
Data collected automatically
TheFirebase Authentication SDK collects the following dataautomatically.
| Data | By default, theFirebase Authentication SDK... |
|---|---|
| Firebase user agent | For information, refer to theFirebase user agent section on this page. |
| IP address | Collects IP addresses to provide added security and prevent abuse during sign-up and authentication. |
User agent strings:
| Collects user agent strings to provide, maintain, and improve Firebase services. Note that this user agent isnot referring to theFirebase user agent. |
| 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 theFirebase Authentication SDK and theproduct's features, your app may collect end-user data that needs to be includedin your data disclosure. The following table lists examples of end-user datathat can be collected depending on your usage, but make sure to account for anydata collected by your specific usage.
| Data | Depending on your app's configuration and invocation, theFirebase 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:
|
| Phone number | Collects a user's phone number (as provided by the developer) if the app uses any of the following:
|
| Integrity token fromPlay Integrity | Collects this integrity token if your app uses Phone Authentication. See additionaldata safety information for Play Integrity. |
| Token fromreCAPTCHA Enterprise | Collects this token if your app usesreCAPTCHA Enterprise to protectAuthentication flows. See additionaldata safety information for reCAPTCHA Enterprise. |
| 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 theGame Center. |
| User ID | Generates and stores a uniqueFirebase Authentication identifier. |
Additional information
Purpose for data collection
Firebase Authentication generally uses the collected data listedin the sub-sections aboveto 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 howspecific datamay be used.In your data disclosure, make sure to also account for how you specifically usethe collected data.
Cloud Firestore
com.google.firebase:firebase-firestorecom.google.firebase:firebase-firestore-ktx
Data collected automatically
TheCloud Firestore SDK collects the following dataautomatically.
| Data | By default, theCloud Firestore SDK... |
|---|---|
| Firebase user agent | For information, refer to theFirebase user agent section on this page. |
Data collected depending on your usage
Depending on how you configure or invoke theCloud Firestore SDK andthe product's features, your app may collect end-user data that needs to beincluded in your data disclosure. Make sure that you account for anydeveloper-defined end-user data that's collected by your specific usage.
Other considerations
If you useCloud Firestore withFirebase Authentication, and if an end-user issigned-in, then every request fromCloud Firestore automatically includesthe applicable User ID fromFirebase Authentication.
Additional information
Purpose for data collection
The Firebase user agent is used internally by Google to determine platform andversion 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 howspecific data may beused.In your data disclosure, make sure to also account for how you specifically usethe collected data, in addition to how you use any developer-defined end-userdata collected by the SDK.
Cloud Functions for Firebase
com.google.firebase:firebase-functionscom.google.firebase:firebase-functions-ktx
Data collected automatically
TheCloud Functions for Firebase Client SDK collects the following dataautomatically.
| Data | By default, theCloud 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 theFCM 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 theFCM SDK. |
Data collected depending on your usage
TheCloud Functions for Firebase Client SDK doesn't have optional features that the developer canconfigure or invoke to collect other end-user data.
Other considerations
If an end-user is signed-in viaFirebase Authentication, every function requestautomatically includes the applicable User ID fromFirebase Authentication.
Additional information
Purpose for data collection
Cloud Functions for Firebase generally uses the collected datalisted in the sub-sections aboveto run backend code in response to events triggered by Firebase features andHTTPS requests from your app.Also, review the sub-sections above for information about howspecific datamay be used.In your data disclosure, make sure to also account for how you specifically usethe collected data.
Cloud Messaging
com.google.firebase:firebase-messagingcom.google.firebase:firebase-messaging-ktx
Data collected automatically
TheFirebase Cloud Messaging SDK collects the following dataautomatically.
| Data | By default, theFirebase Cloud Messaging SDK... |
|---|---|
| Application version | Collects the app's version for topic subscription and unsubscription. |
| Firebase user agent | For information, refer to theFirebase user agent section on this page. |
Other considerations
Cloud Messaging has a dependency on theFirebase installations SDK.Since that SDK is transitively included in your app, make sure to account forthe end-user data collected automatically by that SDK (see theinstallations section on this page). To learn about the datathatCloud Messaging uses from that SDK's data collection, visit theManageFirebase installations documentation.
Data collected depending on your usage
Depending on how you configure or invoke theFirebase Cloud Messaging SDKand the product's features, your app may collect end-user data that needs to beincluded in your data disclosure. The following table lists examples of end-userdata that can be collected depending on your usage, but make sure to account forany data collected by your specific usage.
| Data | Depending on your app's configuration and invocation, theFirebase Cloud Messaging SDK... |
|---|---|
| Message delivery metrics | Collects and sendsmessage delivery metrics to BigQuery if the BigQuery integration is enabled and |
Other considerations
Some optional features ofCloud Messaging depend on the Firebase SDK forGoogle Analytics. If you include that SDK in your app, make sure to account forthe end-user data collected automatically by that SDK (see theGoogle Analytics documentation).The following table lists additional logged data:
| Data | If your app includes the Firebase SDK for Google Analytics, thenCloud 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 andversion 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 datalisted in the sub-sections aboveto send messages to the client app.Also, review the sub-sections above for information about howspecific datamay be used.In your data disclosure, make sure to also account for how you specifically usethe collected data.
Cloud Storage for Firebase
com.google.firebase:firebase-storagecom.google.firebase:firebase-storage-ktx
Data collected automatically
TheCloud Storage for Firebase SDK collects the following dataautomatically.
| Data | By default, theFirebase Cloud Messaging SDK... |
|---|---|
| Version of theCloud Storage SDK used by the app | Collects the version of theCloud 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 theCloud Storage for Firebase SDKand the product's features, your app may collect end-user data that needs to beincluded in your data disclosure. Make sure that you account for anydeveloper-defined end-user data that's collected by your specific usage.
Other considerations
If you useCloud Storage for Firebase withFirebase Authentication, and if an end-useris signed-in, then every request fromCloud Storage for Firebase automaticallyincludes the applicable User ID fromFirebase Authentication.
Additional information
Purpose for data collection
Cloud Storage for Firebase generally uses the collected data listedin the sub-sections above to provide, maintain, and improve Firebase services.Also, review the sub-sections above for information about howspecific datamay be used.In your data disclosure, make sure to also account for how you specifically usethe collected data, in addition to how you use any developer-defined end-userdata collected by the SDK.
Crashlytics
com.google.firebase:firebase-crashlyticscom.google.firebase:firebase-crashlytics-ktxcom.google.firebase:firebase-crashlytics-ndk
Data collected automatically
TheFirebase Crashlytics SDK collects the following dataautomatically.
| Data | By default, theFirebase Crashlytics SDK... |
|---|---|
| Stack traces | Collects stack traces when an application crashes. |
| Relevant application state | Collects relevant application state when an application crashes. |
| Relevantdevice metadata | Collects point-in-time metadata about the device when an application crashes. |
| Crashlytics installation UUID | Generates and stores theCrashlytics installation UUID to measure the number of users impacted by a crash. |
Other considerations
Crashlytics has a dependency on theFirebase installations SDK. Sincethat SDK is transitively included in your app, make sure to account for theend-user data collected automatically by that SDK (see theinstallations section on this page). Note thatCrashlyticsdoesn't use any of the data collected by theFirebase installations SDK,except to rotate theCrashlytics installation UUID based on changes to theapp instance'sFirebase installation ID.
Crashlytics also has a dependency on theFirebase sessions SDK to providequality metrics in theFirebase console. Since that SDK is transitivelyincluded in your app, make sure to account for the end-user data collectedautomatically by that SDK (see theFirebase sessions SDK section onthis page).
Data collected depending on your usage
Depending on how you configure or invoke theFirebase Crashlytics SDKand the product's features, your app may collect end-user data that needs to beincluded in your data disclosure. The following table lists examples of end-userdata that can be collected depending on your usage, but make sure to account forany data collected by your specific usage.
| Data | Depending on your app's configuration and invocation, theFirebase 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 ofCrashlytics depend on the Firebase SDK for GoogleAnalytics. If you include that SDK in your app, make sure to account for theend-user data collected automatically by that SDK (see theGoogle Analytics documentation).The following table lists the data thatCrashlytics uses from that datacollection:
| Data | If your app includes the Firebase SDK for Google Analytics, thenCrashlytics... |
|---|---|
| "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. |
If you also include theFirebase Remote Config SDK in your app, make sure toaccount for the developer-definedRemote Config data collected automaticallyby theCrashlytics SDK. The following table lists the data that theCrashlytics SDK collects:
| Data | If your app includes theFirebase Remote Config SDK, then theCrashlytics SDK... |
|---|---|
| Developer-definedRemote Config rollout metadata | Collects rollout metadata, which includesRemote Config template versions, rollout variant IDs, parameter keys, and parameter values affected by active rollouts. |
Additional information
Purpose for data collection
Firebase Crashlytics generally uses the collected datalisted in the sub-sections aboveto enable crash reporting and crash management services.Also, review the sub-sections above for information about howspecific datamay be used.In your data disclosure, make sure to also account for how you specifically usethe collected data, in addition to how you use any developer-defined end-userdata collected by the SDK.
Data Connect
com.google.firebase:firebase-dataconnect
Data collected automatically
TheFirebase Data Connect SDK collects the following dataautomatically.
| Data | By default, theData Connect SDK... |
|---|---|
| Whetherlocal code generation forData Connect is being used | Collects whether requests to theData Connect service are coming from code generated by theData Connect code generator, or, instead, from direct usage of theData Connect SDK. 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. |
| Firebase user agent | For information, refer to theFirebase user agent section on this page. |
Data collected depending on your usage
Depending on how you configure or invoke theData Connect SDK and theproduct's features, your app may collect end-user data that needs to be includedin your data disclosure. Make sure that you account for any developer-definedend-user data that's collected by your specific usage.
Other considerations
If you useData Connect withFirebase Authentication, and if an end-user issigned in, then every request fromData Connect automatically includesthe applicable User ID fromFirebase Authentication.
Additional information
Purpose for data collection
The Firebase user agent is used internally by Google to determine platform andversion 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 howspecific data may beused. In your data disclosure, make sure to also account for how youspecifically use the collected data, in addition to how you use anydeveloper-defined end-user data collected by the SDK.
Dynamic Links
com.google.firebase:firebase-dynamic-linkscom.google.firebase:firebase-dynamic-links-ktx
Data collected automatically
TheFirebase Dynamic Links SDK collects the following dataautomatically.
| Data | By default, theFirebase 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 theFirebase Dynamic Links SDK integrated, then Firebaselogs the app state and link interaction events.
Other considerations
If a user interacts with a Firebase dynamic link, the following data is loggedautomatically, 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
TheFirebase Dynamic Links SDK doesn't have optional features that the developer canconfigure or invoke to collect other end-user data.
Other considerations
Some optional features ofDynamic Links depend on the Firebase SDK for GoogleAnalytics. If you include that SDK in your app, make sure to account for theend-user data collected automatically by that SDK (see theGoogle Analytics documentation).The following table lists additional logged data:
| Data | If your app includes the Firebase SDK for Google Analytics, thenDynamic 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 datalisted in the sub-sections aboveto take end users directly to the linked content in your app.Also, review the sub-sections above for information about howspecific datamay be used.In your data disclosure, make sure to also account for how you specifically usethe collected data, in addition to how you use any developer-defined end-userdata collected by the SDK.
Google Analytics
com.google.firebase:firebase-analyticscom.google.firebase:firebase-analytics-ktx
Find Google Analytics data collection information in theGoogle Analytics documentation.
In-App Messaging
com.google.firebase:firebase-inappmessagingcom.google.firebase:firebase-inappmessaging-displaycom.google.firebase:firebase-inappmessaging-ktxcom.google.firebase:firebase-inappmessaging-display-ktx
Data collected automatically
TheFirebase In-App Messaging SDK collects the following dataautomatically.
| Data | By default, theFirebase 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 GoogleAnalytics. Since you must include that SDK in your app, make sure to account forthe end-user data collected automatically by that SDK (see theGoogle Analytics documentation).The following table lists examples of how theIn-App Messaging SDK interactswith data fromGoogle Analytics:
| Data | If your app includes the Firebase SDK for Google Analytics, thenFirebase 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 forGoogle Analytics in order to target messages that are based on user property conditions. |
In-App Messaging also has a dependency on theFirebase installations SDK.Since that SDK is transitively included in your app, make sure to account forthe end-user data collected automatically by that SDK (see theinstallations section on this page). To learn about the datathatIn-App Messaging uses from that SDK's data collection, visit theManageFirebase installations documentation.
Data collected depending on your usage
TheFirebase In-App Messaging SDKs don't have optional features that thedeveloper can configure or invoke to collect other end-user data.
Additional information
Purpose for data collection
Firebase In-App Messaging generally uses the collected datalisted in the sub-sections aboveto send messages to end users within the app itself.Also, review the sub-sections above for information about howspecific datamay be used.In your data disclosure, make sure to also account for how you specifically usethe collected data.
Installations
com.google.firebase:firebase-installationscom.google.firebase:firebase-installations-ktx
Data collected automatically
TheFirebase installations SDK collects the following dataautomatically.
| Data | By default, theFirebase installations SDK... |
|---|---|
| Firebase installation ID (FID) | Generates and collects a per-installation identifier (FID) that does not uniquely identify a user or physical device. |
| Firebase user agent | For information, refer to theFirebase user agent section on this page. |
Data collected depending on your usage
TheFirebase installations SDK doesn't have optional features that thedeveloper 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 andversion 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 datalisted in the sub-sections aboveto provide a unique identifier to identify app installations.Also, review the sub-sections above for information about howspecific datamay be used.In your data disclosure, make sure to also account for how you specifically usethe collected data.
Firebase ML model downloader
com.google.firebase:firebase-ml-modeldownloadercom.google.firebase:firebase-ml-modeldownloader-ktx
Data collected automatically
TheFirebase ML model downloader SDK collects the following dataautomatically.
| Data | By default, theFirebase 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 | Collectsinstallation 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 theFirebase installations SDK.Since that SDK is transitively included in your app, make sure to account forthe end-user data collected automatically by that SDK (see theinstallations section on this page). To learn about the datathatFirebase ML model downloader uses from that SDK's data collection,visit theManageFirebase installations documentation.
Data collected depending on your usage
TheFirebase ML model downloader SDK doesn't have optional features that thedeveloper 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-sectionsabove to download ML models.Firebase ML aggregates and uses the model download metadata to monitorproduct quality, understand usage, and inform product direction.Also, review the sub-sections above for information about howspecific datamay be used.In your data disclosure, make sure to also account for how you specifically usethe collected data.
Performance Monitoring
com.google.firebase:firebase-perfcom.google.firebase:firebase-perf-ktx
Data collected automatically
TheFirebase Performance Monitoring SDK collects the following dataautomatically.
| Data | By default, theFirebase 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. |
| Relevantdevice 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 theFirebase installations SDK.Since that SDK is transitively included in your app, make sure to account forthe end-user data collected automatically by that SDK (see theinstallations section on this page). To learn about the datathatPerformance Monitoring uses from that SDK's data collection, visit theManageFirebase installations documentation.
Performance Monitoring also has a dependency on theFirebase Remote Config SDK to helpcontrol the volume of events collected from an application. Since that SDK istransitively included in your app, make sure to account for the end-user datacollected automatically by that SDK (see theRemote Config section on this page).
Performance Monitoring also has a dependency on theFirebase sessions SDK to reporttimeline views of performance data in theFirebase console. Since that SDK istransitively included in your app, make sure to account for the end-user datacollected automatically by that SDK (see theFirebase sessions SDKsection on this page).
Data collected depending on your usage
Depending on how you configure or invoke theFirebase Performance Monitoring SDKand the product's features, your app may collect end-user data that needs to beincluded in your data disclosure. The following table lists examples of end-userdata that can be collected depending on your usage, but make sure to account forany data collected by your specific usage.
| Data | Depending on your app's configuration and invocation, theFirebase 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 datalisted in the sub-sections aboveto enable app performance reporting and monitoring.Also, review the sub-sections above for information about howspecific datamay be used.In your data disclosure, make sure to also account for how you specifically usethe collected data, in addition to how you use any developer-defined end-userdata collected by the SDK.
Firebase Phone Number Verification
com.google.firebase:firebase-pnv
Data collected automatically
TheFirebase PNV SDK collects the following dataautomatically.
| Data | By default, theFirebase Phone Number Verification SDK... |
|---|---|
| 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 theFirebase Phone Number Verification SDKand the product's features, your app may collect end-user data that needs to beincluded in your data disclosure. The following table lists examples of end-userdata that can be collected depending on your usage, but make sure to account forany data collected by your specific usage.
| Data | Depending on your app's configuration and invocation, theFirebase Phone Number Verification SDK... |
|---|---|
| Phone number | Retrieves the phone number of the device (with the user's consent). |
Additional information
Purpose for data collection
Firebase Phone Number Verification is a service intended to enable apps to obtain the phonenumber of a device directly from the mobile carrier. The SDK requires userconsent every time the app requests the device’s phone number. This capabilityis often, but not necessarily, used for app sign-in purposes.
In your data disclosure, make sure to also account for how you specifically usethe collected data, in addition to how you use any developer-defined end-userdata collected by the SDK.
Realtime Database
com.google.firebase:firebase-databasecom.google.firebase:firebase-database-ktx
Data collected automatically
TheFirebase Realtime Database SDK collects the following dataautomatically.
| Data | By default, theFirebase Realtime Database SDK... |
|---|---|
| IP address | Collects IP addresses to enable theprofiler tool, which helps developers understand usage trends and platform breakdowns |
| User agents | Collects user agent strings to enable theprofiler tool, which helps developers understand usage trends and platform breakdowns Note that this user agent isnot referring to theFirebase user agent. |
Data collected depending on your usage
Depending on how you configure or invoke theFirebase Realtime Database SDK andthe product's features, your app may collect end-user data that needs to beincluded in your data disclosure. Make sure that you account for anydeveloper-defined end-user data that's collected by your specific usage.
Other considerations
If you useRealtime Database withFirebase Authentication, and if an end-user issigned-in, then every request fromRealtime Database automatically includesthe applicable User ID fromFirebase Authentication.
Additional information
Purpose for data collection
Please review the sub-sections above for information about howspecific datamay be used. In your data disclosure, make sure to also account for how youspecifically use the collected data, in addition to how you use anydeveloper-defined end-user data collected by the SDK.
Remote Config
com.google.firebase:firebase-configcom.google.firebase:firebase-config-ktx
Data collected automatically
TheFirebase Remote Config SDK collects the following dataautomatically.
| Data | By default, theFirebase 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 theRemote 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 theFirebase installations SDK.Since that SDK is transitively included in your app, make sure to account forthe end-user data collected automatically by that SDK (see theinstallations section on this page). To learn about the datathatRemote Config uses from that SDK's data collection, visit theManageFirebase installations documentation.
Data collected depending on your usage
TheFirebase Remote Config SDK doesn't have optional features that thedeveloper can configure or invoke to collect other end-user data.
Other considerations
Some optional features ofRemote Config depend on the Firebase SDK forGoogle Analytics. If you include that SDK in your app, make sure to account forthe end-user data collected automatically by that SDK (see theGoogle Analytics documentation).The following table lists examples of how theRemote Config SDK interactswith data fromGoogle Analytics:
| Data | If your app includes the Firebase SDK for Google Analytics, thenRemote Config... |
|---|---|
| User properties | Collects user properties obtained by the Firebase SDK forGoogle Analytics in order to target parameters that are based on user property conditions. |
| First open time | Collects the |
IfRemote Config personalization is implemented, the data obtained by theFirebase Remote Config SDK and the events obtained by the Firebase SDK forGoogle Analytics can be used to construct predictive models and measurethe performance of those models.
Additional information
Purpose for data collection
Firebase Remote Config generally uses the collected datalisted in the sub-sections aboveto change the behavior and appearance of your app without publishing an appupdate.Aggregated data for OS version and SDK version is used by Firebase tounderstand usage trends and inform product direction.Also, review the sub-sections above for information about howspecific datamay be used.In your data disclosure, make sure to also account for howyou specifically use the collected data.
Transitively included Firebase libraries
The Firebase libraries listed in this section are transitively included in someof the other Firebase libraries. None of the following libraries have anaccessible surface for developers, but they might collect end-user data (seeeach library below for details).
Firebase sessions
com.google.firebase:firebase-sessions
Data collected automatically
TheFirebase sessions SDK collects the following dataautomatically.
| Data | By default, theFirebase sessions SDK... |
|---|---|
| App metadata | Collects metadata about the application, such as the package name, OS information, SDK version, and network connection type. |
| Device metadata | Collects metadata about the application, such as device manufacturer and model. |
| Application metrics | Collects usage data such as the time an app was foregrounded to start a new session. |
Data collected depending on your usage
TheFirebase sessions SDK doesn't have optional features that the developer canconfigure or invoke to collect other end-user data.
Additional Information
Purpose for data collection
TheFirebase sessions SDK uses the collected data listed in the sub-sectionsabove to provide crash and performance metrics for the application. Also, reviewthe sub-sections above for information about howspecific data may be used. Inyour data disclosure, make sure to also account for how you specifically use thecollected data, in addition to how you use any developer-defined end-user datacollected by the SDK.
Other helpful resources
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-18 UTC.