Service Specific Terms

The Firebase services listed below are "Services" and/or "Software" as defined in Google Cloud Platform License Agreement.

Capitalized terms not defined in these Firebase Service Specific Terms or the Google Cloud Platform Service Specific Terms have the meaning set forth in the Google Cloud Platform License Agreement between Customer and Google or the Google Cloud Platform Reseller Agreement between Reseller and Google or the Google for Work & Google for Education Commercial Partner Agreement between Google and Partner (as applicable, "Agreement"). For the purpose of these Firebase Service Specific Terms and the Google Cloud Platform Service Specific Terms, if the Agreement is the Google Cloud Platform Reseller Agreement, or the Google for Work & Google for Education Commercial Partner Agreement, then: (i) the term "Customer" as used herein means Customer and/or Reseller or Partner (as applicable) based on which entity is accessing the applicable Service, and (ii) the term "Customer" as used herein means "Reseller or Partner (as applicable)" for Sections 18.1, and 20.12-20.14.

1. Cloud Functions for Firebase

The following terms apply only to Cloud Functions for Firebase:

1.1. Documentation. Documentation for Cloud Functions for Firebase is set forth at: https://firebase.google.com/docs/functions/.

1.2. TSS. Notwithstanding anything to the contrary in the Agreement or the TSS Guidelines, Google does not offer TSS to Customer for Cloud Functions for Firebase, and will instead provide Customer with Firebase Support for Cloud Functions for Firebase.

2. Cloud Storage for Firebase

The following terms apply only to Cloud Storage for Firebase:

2.1. Data Storage. (1) If Customer chooses either the Flame payment plan or Blaze payment plan, for each additional bucket created after the initial bucket in Customer’s Project, Customer may select via the Service whether Core Firebase Storage Customer Data will be stored in: (a) either the United States or the European Union, and Google will store it accordingly; or (b) another location setting offered by the Service, and Google will not move it outside the location selected without notifying Customer, except to comply with laws (including government requests). For the initial bucket in Customer’s Project, Customer may not select via the Service where Core Firebase Storage Customer Data will be stored. (2) Customer may not select via the Service where Firebase Security Rules for Cloud Storage will be stored. ((1) and (2) together, "Firebase Storage Data Location Setting").

2.2. Transient Storage. Core Firebase Storage Customer Data and Firebase Security Rules for Cloud Storage may be stored transiently or cached in any country in which Google or its agents maintain facilities.

2.3. Limitations. No Firebase Storage Data Location Setting will apply to Core Firebase Storage Customer Data or Firebase Security Rules for Cloud Storage copied or moved by Customer or a Customer End User to another location or used with other Google products and services (including other Services, except to the extent Customer has selected the same data location setting for that other Service).

2.4. Documentation. Documentation for Cloud Storage for Firebase is set forth at: https://firebase.google.com/docs/storage.

2.5. SLA. The SLA for Cloud Storage for Firebase mirrors the SLA for Google Cloud Storage, set forth at: https://firebase.google.com/terms/sla/cloud-storage.

2.6. TSS. Notwithstanding anything to the contrary in the Agreement or the TSS Guidelines, Google does not offer TSS to Customer for Cloud Storage for Firebase, and will instead provide Customer with Firebase Support for Cloud Storage for Firebase.

3. Firebase Authentication

The following terms apply only to Firebase Authentication:

3.1. Phone Authentication. Phone numbers that each developer's end users provide for authentication will be sent and stored for a limited time by Google, together with phone numbers that other developers' end users provide for authentication, to improve our spam and abuse prevention across Google services, including but not limited to Firebase. Phone numbers are not logically isolated for a given developer's end users. Developers should ensure they have appropriate end-user consent prior to using the Firebase Authentication phone number sign-in service.

3.2. Documentation. Documentation for Firebase Test Lab for Android is set forth at: https://firebase.google.com/docs/auth/.

3.3. TSS. Notwithstanding anything to the contrary in the Agreement or the TSS Guidelines, Google does not offer TSS to Customer for Firebase Authentication, and will instead provide Customer with Firebase Support for Firebase Authentication.

4. Firebase Test Lab for Android

The following terms apply only to Firebase Test Lab for Android:

4.1. Documentation. Documentation for Firebase Test Lab for Android is set forth at: https://firebase.google.com/docs/test-lab/.

4.2. TSS. Notwithstanding anything to the contrary in the Agreement or the TSS Guidelines, Google does not offer TSS to Customer for Firebase Test Lab for Android, and will instead provide Customer with Firebase Support for Firebase Test Lab for Android.

5. Definitions

5.1. "Core Firebase Storage Customer Data" means only that Customer Data which is uploaded by Customer (or those authorized by Customer) or stored by an Application using the Cloud Storage for Firebase tools or API for storage by Cloud Storage for Firebase, excluding General Google Account Information and information about such Customer Data, such as Firebase Security Rules for Cloud Storage, access control lists (ACLs), bucket and object names, configuration data, and operational data such as logs, system events, and metrics.

Send feedback about...

Need help? Visit our support page.