Subprocessors
The third parties that process customer data for Tracix, what each one does and where it does it.
Last updated [Date].
Current list
Who processes customer data for us
| Subprocessor | What it does | Data it processes | Location |
|---|---|---|---|
| Amazon Web Services | Hosts every workspace and the console: compute on Amazon EKS, storage on Amazon S3, EBS and EFS, the console database on Amazon RDS, DNS on Route 53 and email through Amazon SES. | Telemetry and everything else stored in your workspaces, and your console account details | United States: us-east-1 (N. Virginia) |
| Amazon Web Services (Amazon Bedrock) | Runs the model behind the assistant in the console. | What you ask the console assistant, and the console details it reads to answer | United States |
| Stripe | Subscriptions, invoices and payments for paid plans. | Billing contacts and payment details | [Location] |
[Legal to confirm the subprocessor list]
Services you connect
Providers you bring are not our subprocessors
AI in your workspace, including Brain and Auto-Fix, uses the model provider you connect with your own key: Anthropic, OpenAI or a compatible endpoint. Auto-Fix works in the code host you connect, and alerts go to the notification channels you set up.
Those providers act for you, under your own agreement with them, so they are not Tracix subprocessors. An admin can turn AI off for a workspace entirely.
[How and when we tell customers before a new subprocessor starts]
Ask about subprocessors