Firebase Subprocessors
Stay organized with collections
Save and categorize content based on your preferences.
Last modified: September 23, 2021 | Previous versions
Google and its affiliates use the following third party subprocessors to assist them in
providing Firebase Services (as described in the relevant Firebase Terms of
Service):
- Accenture, LLP, headquartered in the United States, to provide customer and technical support, which may
include phone and email support, response, diagnosis and resolution services,
incident tracking, and responding to customer queries.
- EPAM Systems, Inc, headquartered in the United States, to provide customer and technical support, which may
include phone and email support, response, diagnosis and resolution services,
incident tracking, and responding to customer queries.
- Fastly, Inc., headquartered in the United States, to deliver content and managed services on Firebase Hosting to end-users, via the Fastly content delivery network.
- Firebase, Inc., a Google Group affiliate used to engage personnel
and vendors to provide infrastructure, service support, and IT-facility
management in connection with Firebase Crashlytics and Firebase
App Distribution. This includes data center and processing services, and
managing the availability, latency, scalability and efficiency of Firebase
Crashlytics and Firebase App Distribution.
Many Firebase features integrate closely with Google Cloud Platform, whose
subprocessors are identified here. The Google Cloud
Platform subprocessors identified as Google Group Subprocessors may be used as
subprocessors to perform limited activities in connection with the Firebase
Services.
Previous versions
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
[null,null,[],[],[],null,["**Last modified: September 23, 2021** \\| [Previous versions](#previous_versions)\n\nGoogle and its affiliates use the following third party subprocessors to assist them in\nproviding Firebase Services (as described in the relevant Firebase [Terms of\nService](/terms)):\n\n- **Accenture, LLP**, headquartered in the United States, to provide customer and technical support, which may include phone and email support, response, diagnosis and resolution services, incident tracking, and responding to customer queries.\n- **EPAM Systems, Inc**, headquartered in the United States, to provide customer and technical support, which may include phone and email support, response, diagnosis and resolution services, incident tracking, and responding to customer queries.\n- **Fastly, Inc.** , headquartered in the United States, to deliver content and managed services on **Firebase Hosting** to end-users, via the Fastly content delivery network.\n- **Firebase, Inc.** , a Google Group affiliate used to engage personnel and vendors to provide infrastructure, service support, and IT-facility management in connection with **Firebase Crashlytics** and **Firebase\n App Distribution** . This includes data center and processing services, and managing the availability, latency, scalability and efficiency of **Firebase\n Crashlytics** and **Firebase App Distribution**.\n\nMany Firebase features integrate closely with Google Cloud Platform, whose\nsubprocessors are identified [here](//cloud.google.com/terms/subprocessors). The Google Cloud\nPlatform subprocessors identified as Google Group Subprocessors may be used as\nsubprocessors to perform limited activities in connection with the Firebase\nServices.\n\nPrevious versions\n\n- [September 23, 2019](/terms/subprocessors/20190923)\n- [October 29, 2018](/terms/subprocessors/20181029)\n- [June 28, 2018](/terms/subprocessors/20180628)\n- [September 13, 2017](/terms/subprocessors/20170913)\n- [March 9, 2017](/terms/subprocessors/20170309)"]]
