> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usetero.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Subprocessors and Third Parties

> Third-party services used in hosted deployments and their processing roles.

export const securityEmail = "security@usetero.com";

<Badge>Last reviewed: March 5, 2026</Badge>
<Badge>Owner: Security + Engineering</Badge>
<Badge>Review cadence: Quarterly</Badge>
<Badge color="green">Status: Implemented</Badge>

This page lists the core third-party services Tero uses in hosted deployments and the role each one plays.

## Reviewer focus

* Which third parties are involved in hosted delivery
* What data category each subprocessor handles
* How subprocessor scope changes in self-hosted deployments

## Current subprocessors (hosted)

| Service                                    | Purpose                                  | Data category                        | Location |
| ------------------------------------------ | ---------------------------------------- | ------------------------------------ | -------- |
| Google Cloud Platform                      | Infrastructure runtime, storage, backups | Control-plane operational data       | US       |
| WorkOS                                     | Authentication and identity workflows    | Identity and authentication metadata | US       |
| Anthropic or OpenAI (deployment-dependent) | AI-assisted classification workflows     | AI workflow input scope              | US       |
| Stripe (self-service only)                 | Billing operations                       | Billing metadata                     | US       |

## Self-hosted model boundary

In self-hosted deployments, you choose and operate your own infrastructure and provider stack. You define subprocessor scope for the components you host.

## Change management baseline

* Subprocessor changes follow internal review before customer use.
* Tero communicates material changes that could affect security, availability, or data handling in advance where required by contract or plan terms.
* Tero communicates emergency changes, with impact context, as soon as it understands the impact.

## Evidence you can request

| Topic                             | Primary evidence                                                                                 |
| --------------------------------- | ------------------------------------------------------------------------------------------------ |
| Ownership split                   | [Shared Responsibility](/trust/shared-responsibility)                                            |
| Data scope and retention baseline | [Data Handling](/trust/controls/data-handling), [Data Retention](/trust/policies/data-retention) |
| Compliance context                | [Compliance and Assurance](/trust/assurance/compliance-and-assurance)                            |

## Questions

For subprocessor detail requests, email [{securityEmail}](mailto:\{securityEmail}).