> [!NOTE]
> **Note:** This is an archive. For the current version of this page, head to [Firebase Subprocessors](https://firebase.google.com/terms/subprocessors.md.txt).

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](https://firebase.google.com/terms)):

- **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](https://cloud.google.com/terms/subprocessors).

#### Previous versions

- [October 29, 2018](https://firebase.google.com/terms/subprocessors/20181029.md.txt)
- [June 28, 2018](https://firebase.google.com/terms/subprocessors/20180628.md.txt)
- [September 13, 2017](https://firebase.google.com/terms/subprocessors/20170913.md.txt)
- [March 9, 2017](https://firebase.google.com/terms/subprocessors/20170309.md.txt)