Privacy Policy
Last updated: November 11, 2026
This policy explains what Iron Spur Labs LLC ("we") collects when you use Trailboss and its website, why, and what you can do about it.
Two roles. For your account, billing and our website, we decide how data is used (we're the controller). For the content your organization brings to Trailboss (repositories, issues, documents, and anything personal inside them), your organization decides, and we process it on its behalf (we're a processor) under the Data Processing Addendum.
What we collect
| Data | Examples | Where it comes from |
|---|---|---|
| Account | Name, email, avatar, GitHub username | You, or GitHub when you sign in with it |
| Security | Passkeys (public keys only), authenticator-app secrets (encrypted), recovery codes (hashed), sign-in and step-up times | You |
| Organization | Name, members, roles, invitations, policies, settings | You and your teammates |
| Billing | Plan, credit, usage hours; Stripe holds your card, we keep only a reference to it | You, Stripe |
| Usage and audit | Jobs, who started them, approvals, the audit log of actions in your organization | Your use of Trailboss |
| Technical | IP address, browser, request logs, error reports | Your browser and devices |
| Content | Code, issues, documents, model API keys (encrypted, shown only as the last four characters) | You, and services you connect |
We don't use analytics or advertising trackers, and we don't buy data about you.
Why we use it
- To provide Trailboss: sign you in, run your jobs, bill you, send the emails you need (sign-in links, invitations, alerts you've turned on). Basis: contract.
- To keep it secure: rate limits, abuse prevention, fraud checks before granting free credit, audit logs, investigating incidents. Basis: legitimate interests.
- To improve it: aggregate operational metrics (never your content). Basis: legitimate interests.
- To meet legal duties: tax and accounting records, lawful requests. Basis: legal obligation.
We don't sell personal data, share it for cross-context advertising, or use your content to train AI models.
AI processing
Some features send content to AI models:
- Agents use the model access your organization connects, so your content goes to the provider you chose, under your agreement with them.
- Planning, triage and visual review run on Anthropic models through Amazon Bedrock in our AWS account (or Anthropic's API if we switch providers; see Subprocessors). Neither trains on that data.
- Customer-hosted mode with Bedrock: jobs run on a worker in your AWS account and call models through your Bedrock, so your code and data stay in your account. In other modes, content is processed by us and our subprocessors as described here.
Who we share it with
- Subprocessors that host and operate Trailboss for us, under contracts that protect it.
- Services you connect (GitHub, Slack, your AWS account, your model provider), when you ask us to act there.
- Your organization's owners and admins, who can see members, activity and the audit log.
- Authorities, when the law requires it, or to protect people from harm.
- A buyer, if we're acquired; this policy would continue to apply.
How long we keep it
We keep data for as long as your organization exists, with shorter limits where we don't need it. For example: sign-in links expire in minutes and are removed after a day; idempotency keys and event-stream records after 24 hours; finished background jobs after 7 days; read notifications after 30 days and all notifications after a year; expired invitations after 30 days; rate-limit records after an hour.
When an owner deletes an organization, deletion is scheduled with a 30-day grace period; after that its data, and people who belong to no other organization, are removed from our database. Two exceptions: the audit log is archived write-once and kept for 7 years for security and compliance; and backups expire on their own schedule within 35 days. Billing records are also kept by Stripe as the law requires.
Your rights
Depending on where you live, you can ask to access, correct, export or delete your personal data, object to or restrict some uses, and complain to your data-protection authority. Organization owners can export the organization's data (without secrets) and delete it from Settings. For anything else, email support@trailboss.dev; we'll answer within 30 days. If your data is in an organization's content, we'll pass your request to that organization.
Security
Data is encrypted in transit and at rest; organizations are isolated from each other in the database; secrets are encrypted and never shown again; access is logged. See our security page.
International transfers
We're based in the United States and our infrastructure is in the United States (AWS us-east-1). Where data leaves the EU, UK or Switzerland, we rely on the Standard Contractual Clauses.
Children
Trailboss isn't for children under 16, and we don't knowingly collect their data.
Changes and contact
We'll post changes here and email owners about material ones. Questions: support@trailboss.dev, Iron Spur Labs LLC, 30 N Gould St, Ste N, Sheridan, WY 82801, USA.