A sub-processor is a third-party service that processes data on our behalf in
order to run Tracore. We keep this list short and choose providers that meet our
security and data-protection expectations. This page lists every sub-processor we
use, where it is located, and what it does.
Core infrastructure
| Provider | Location | Purpose | Privacy policy |
|---|
| Railway Corp. | United States | Application and Postgres hosting | Privacy policy |
| Cloudflare, Inc. | EU jurisdiction | DNS, R2 object storage, SSL proxy | Privacy policy |
Communications
| Provider | Location | Purpose | Privacy policy |
|---|
| Resend | United States | Transactional email delivery | Privacy policy |
| Stripe, Inc. | United States | Payment processing | Privacy policy |
Observability
| Provider | Location | Purpose | Privacy policy |
|---|
| Axiom | United States | Structured logs | Privacy policy |
These providers are only involved when you choose them. Mistral is the default
provider. The others are used only if you connect your own provider key for them
(bring-your-own-key). See Data Residency for what this means
for where your data is processed.
| Provider | Location | Purpose | Privacy policy |
|---|
| Mistral AI | France | Default AI provider | Privacy policy |
| Anthropic | United States | Optional — used only if you provide an Anthropic key | Privacy policy |
| OpenAI | United States | Optional — used only if you provide an OpenAI key | Privacy policy |
| Google LLC | United States | Optional — used only if you provide a Google key | Privacy policy |
Development
| Provider | Location | Purpose | Privacy policy |
|---|
| GitHub, Inc. | United States | Source code and CI | Privacy policy |
Changes to this list
We update this list at least 30 days before adding a new sub-processor that
processes user data, so you have time to review the change.