Subprocessors
We use the following subprocessors to help us provide, secure, and support the Services. We require appropriate data protection commitments and rely on SCCs where applicable for international transfers. We will update this page before materially adding or replacing a subprocessor.
| Name | Service | Purpose | Data categories | Location | Transfer mechanism | DPA/Policy |
|---|---|---|---|---|---|---|
| Sentry | Error monitoring & performance | Collect and analyze errors and performance telemetry to maintain reliability and debug issues. | Diagnostics, Error traces/stack data, Service usage metadata | US/EU | SCCs where applicable | Policy |
| Logto | Authentication & identity (OIDC/SSO) | Authenticate users, manage sessions, and support SSO flows. | Identifiers (email, user ID), Auth events | Varies (self-hosted or cloud) | N/A if self-hosted; SCCs if cloud | Policy |
| OpenAI | LLM provider | Process prompts and generate model outputs as part of the Services. | Customer content (prompts/outputs), Usage metadata | US | SCCs for EEA/UK transfers | Policy |
| Anthropic | LLM provider | Process prompts and generate model outputs as part of the Services. | Customer content (prompts/outputs), Usage metadata | US | SCCs for EEA/UK transfers | Policy |
| Deepseek | LLM provider | Process prompts and generate model outputs as part of the Services. | Customer content (prompts/outputs), Usage metadata | Outside EEA (see vendor regions) | SCCs where applicable | — |
| DigitalOcean (Spaces) | Object storage & backups | Store artifacts and data necessary to provide the Services (e.g., execution artifacts, backups). | Customer content, Execution artifacts, Metadata | US/EU regions (per account configuration) | SCCs where applicable | Policy |