> For the complete documentation index, see [llms.txt](https://docs.earthscale.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.earthscale.ai/trust-and-compliance/subprocessors.md).

# Subprocessors

Earthscale engages subprocessors in connection with providing its Services. A subprocessor is a third-party engaged by Earthscale AI, Inc. that might process personal data on behalf of Earthscale's customers as defined in our DPA. Additional vendors may support Earthscale operations but do not process Customer Data.

### Current Subprocessors

| Entity Name               | Purpose                   | Entity Country |
| ------------------------- | ------------------------- | -------------- |
| Google LLC                | Cloud Service Provider    | United States  |
| Amazon Web Services, Inc. | Cloud Service Provider    | United States  |
| Microsoft Corporation     | Cloud Service Provider    | United States  |
| Supabase, Inc.            | Database Service Provider | United States  |
| Functional Software, Inc. | Error Monitoring          | United States  |

*Last updated: December 10, 2025*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.earthscale.ai/trust-and-compliance/subprocessors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.