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

# Subprocessors

Review the third-party subprocessors Zenlytic uses to deliver and support the product.

**Last updated:** September 8, 2026

When we share your information with third party subprocessors, such as our vendors and service providers, we remain responsible for it. We work very hard to maintain your trust when we bring on new vendors, and we require all vendors to enter into data protection agreements with us that restrict their processing of Users' Personal Information (as defined in our [Privacy Policy](https://app.zenlytic.com/privacy-policy)).

For how customer data sent to our large language model providers is used and retained, see the [LLM Data Use and Retention Policy](/legal-and-support/legal/llm-data-use-and-retention.md).

<table data-full-width="false"><thead><tr><th width="229.17578125">Name of Subprocessor</th><th width="315.90234375">Description of Processing</th><th>Location of Processing</th></tr></thead><tbody><tr><td>Google Analytics</td><td>Website analytics and performance</td><td>United States</td></tr><tr><td>Segment</td><td>Customer analytics processor</td><td>United States</td></tr><tr><td>HubSpot</td><td>Email Marketing Service Provider</td><td>United States</td></tr><tr><td>LogRocket</td><td>Tracks user sessions for issue analysis</td><td>United States</td></tr><tr><td>Langfuse</td><td>Process developer logs</td><td>Global</td></tr><tr><td>Intercom</td><td>Support tool connecting our customers</td><td>United States</td></tr><tr><td>Snowflake</td><td>Internal analytics storage</td><td>United States</td></tr><tr><td>Airbyte</td><td>Data transport for internal analytics</td><td>United States</td></tr><tr><td>Google Cloud Platform</td><td>LLM Processing</td><td>Global</td></tr><tr><td>Amazon Web Services</td><td>Hosting and database infrastructure</td><td>Global</td></tr><tr><td>Azure</td><td>Database proxy infrastructure</td><td>United States</td></tr><tr><td>OpenAI</td><td>AI infrastructure</td><td>United States</td></tr><tr><td>Sentry</td><td>Error analytics processor</td><td>United States</td></tr><tr><td>Modal</td><td>Code sandbox infrastructure</td><td>United States</td></tr><tr><td>Auth0</td><td>Identity Provider</td><td>United States</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zenlytic.com/legal-and-support/legal/subprocessors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.