Data Processing Addendum
How Trailboss processes personal data in your organization's content on your behalf: instructions, security, subprocessors, breaches, deletion and international transfers.
Last updated: November 13, 2026
This addendum forms part of the Terms of Service (or the customer's signed agreement) between the customer ("Customer", the controller) and Iron Spur Labs LLC, a Wyoming limited liability company ("Trailboss", the processor). It applies when Trailboss processes personal data in Customer's content on Customer's behalf, under the GDPR, UK GDPR, Swiss FADP, the CCPA/CPRA or similar laws ("Data Protection Law").
1. Roles and instructions
1.1 Trailboss processes Customer personal data only on Customer's documented instructions: the agreement, this addendum, and Customer's configuration of the service (policies, approvals, connected services, execution mode). Trailboss tells Customer if it believes an instruction breaks Data Protection Law.
1.2 Trailboss doesn't sell or share Customer personal data, use it for its own purposes (including training AI models), or combine it with other data, except as Data Protection Law allows a service provider to.
1.3 In customer-hosted mode, jobs run on a worker in Customer's AWS account. Data that stays in that account is processed by Customer's own infrastructure, not by Trailboss; Trailboss processes only what the worker reports back (job status, logs Customer chooses to send, usage).
2. Personnel
Trailboss staff with access are bound by confidentiality and get access only when needed. Support access to an organization is read-only, time-limited (up to 8 hours) and recorded in that organization's audit log.
3. Security
Trailboss maintains the measures in Annex II and reviews them at least yearly. It may update them as long as protection doesn't decrease.
4. Subprocessors
4.1 Customer authorizes the subprocessors at /legal/subprocessors. Trailboss binds each to data-protection terms at least as protective as this addendum and stays responsible for them.
4.2 Trailboss gives at least 30 days' notice before a new subprocessor. Customer may object on reasonable data-protection grounds; if the parties can't resolve it, Customer may terminate the affected service and get a refund of prepaid fees for the remaining term.
5. Data subject requests
Trailboss helps Customer answer requests, mainly through the product: owners can export the organization's data and delete it. Requests Trailboss receives directly about Customer data are passed to Customer.
6. Personal data breaches
Trailboss notifies Customer without undue delay, and within 72 hours of becoming aware, of a personal data breach affecting Customer personal data, with what it knows and the steps taken, and updates Customer as it learns more.
7. Assistance
Trailboss gives reasonable help with data protection impact assessments and consultations with authorities, to the extent they concern the service.
8. Deletion and return
During the agreement, owners can export Customer data (without secrets) at any time. When an owner deletes the organization, or the agreement ends, Trailboss deletes Customer data from its database after a 30-day grace period, except: (a) the write-once audit archive, kept for seven years for security and compliance; (b) backups, which expire within 35 days; (c) data the law requires Trailboss to keep. Retained data stays protected by this addendum.
9. Audits
Trailboss makes available information needed to show compliance: this addendum, its security documentation and, once available, independent reports (a penetration test summary, and a SOC 2 report if we obtain one). If that's not enough, Customer may audit once a year on 30 days' notice, at its own cost, during business hours, under confidentiality, without access to other customers' data.
10. International transfers
Where Customer personal data is transferred from the EEA, UK or Switzerland to a country without an adequacy decision, the European Commission's Standard Contractual Clauses (Module Two, controller to processor, or Module Three where Customer is itself a processor) are incorporated by reference, with the UK International Data Transfer Addendum and the Swiss amendments where they apply. Annexes I–III below complete them. For the Clauses: the docking clause applies; the Clauses are governed by the law of Ireland and disputes go to the courts of Ireland; and the competent supervisory authority is the one for Customer's establishment in the EEA.
11. General
If this addendum conflicts with the agreement, this addendum wins for data protection. Liability under it is subject to the agreement's limits, where the law allows.
Annex I: Processing details
- Parties: Customer (controller, or processor on its own clients' behalf); Trailboss (processor or sub-processor).
- Data subjects: Customer's members; people whose data appears in repositories, issues, documents and connected services; visitors to and users of apps Customer publishes through Trailboss.
- Categories: names, emails, usernames, IP addresses, commit metadata, and any personal data in Customer content. Customer should not send special-category data; previews run on generated fixtures, never production data.
- Nature and purpose: hosting, indexing, AI-assisted planning, code generation, testing, review and deployment of Customer software; notifications; support.
- Duration: the term of the agreement plus §8.
- Frequency: continuous.
Annex II: Security measures
In place in the product today:
- Isolation: each organization's data is separated by Postgres row-level security on every request; jobs run with per-job limits and, when hosted, behind an egress allowlist.
- Access control: sign-in with email links, GitHub, Google, Microsoft or single sign-on; passkeys and authenticator apps as second factors, which an owner can require at every sign-in, with step-up for sensitive actions; roles and permissions per organization; scoped, revocable API tokens.
- Encryption: TLS in transit; the database, backups and audit archive encrypted at rest with AWS KMS; secrets (authenticator secrets, API keys) sealed with application keys, write-only and shown only as the last four characters.
- Governance: every job passes execution authorization before it's queued and carries a signature the worker checks; high-risk work needs approvals bound to the plan; budget ceilings; a suspension kill switch that cancels all jobs.
- Logging: an append-only, hash-chained audit log per organization, archived write-once with a verify command; structured logs with credential redaction.
- Application security: security headers and CSP, outbound request guard against SSRF, rate limits, same-origin checks; secret scanning, dependency, vulnerability and container scanning in CI.
- Resilience: backups with a tested restore; health checks; alarms with runbooks.
- Secrets rotation: keys rotate with an overlap window, without downtime.
Planned: an external penetration test before general availability.
Annex III: Subprocessors
As listed at /legal/subprocessors on the date Customer accepts the agreement, and as updated under §4.