Subprocessors
Last updated: November 11, 2026
These are the companies that process customer data for us to run Trailboss. We give owners at least 30 days' notice by email before adding or replacing one; subscribe at support@trailboss.dev to get notices if you aren't an owner.
| Subprocessor | What for | Data | Location |
|---|---|---|---|
| Amazon Web Services, Inc. | Hosting the app, database, job queue, backups, audit archive and hosted execution; sending email (SES) | All data in hosted mode | United States (us-east-1) |
| Amazon Web Services, Inc. (Amazon Bedrock) | Trailboss's own AI features: planning, triage, visual review. Anthropic models served by AWS; prompts and outputs aren't used for training | Content those features read | United States (us-east-1) |
| Stripe, Inc. | Payments, subscriptions, invoices, tax | Billing contact, payment details (held by Stripe, not us), plan and usage totals | United States |
| Anthropic, PBC | Standby only: used for Trailboss's own AI features if we switch from Bedrock to Anthropic's API. We'll give notice before switching | Content those features read | United States |
Not our subprocessors
These process your data under your relationship with them, when you connect them:
- Your model provider (your Anthropic or OpenAI-compatible key, your Bedrock account, or a local model): agents call it with your access.
- GitHub (sign-in, repositories, pull requests), Slack (notifications and approvals): we act there with the permissions you grant.
- Your AWS account in customer-hosted mode: the worker, its logs and its data are in your account, and Trailboss holds no credentials for it. With Bedrock as the model provider, your code and data stay in your account.
Changes
| Date | Change |
|---|---|
| November 11, 2026 | First list. |