for agents: this page is markdown at https://switchyard.so/docs/security.md; every page is listed in llms.txt.
Security and trust
This page explains where Switchyard stores code and accounts, who can reach them, what leaves Switchyard and to whom, and how to report a problem.
You will have: the facts about storage, access, sign-in, AI suggestions and the companies that process your data. Works with: the board, yard, MCP, REST, and plain Git. The same rules apply on every surface.
Where things live
- Code is in Switchyard's own Git store on Cloudflare R2. Each project has its own store, apart from the store of every other project.
- Saved check disks, for a project where Switchyard turned them on, hold a copy of main's checkout with our hosting provider. A saved disk is one project's. After the project is deleted it is never used again, and it can take up to 30 days to expire. Its storage region cannot be chosen.
- Accounts are in a Cloudflare D1 database: your GitHub login, name, picture and email, your organizations and teams, and your sessions with the address and browser they came from. Passkeys and two-factor data are kept there too. GitHub access tokens are encrypted before they are stored, and only the server reads them.
- An organization's own Anthropic key, when an owner saves one, is sealed before it is stored.
- History, merge records and audit events are kept for each project and for each organization.
Who can reach what
- Projects belong to organizations. Owners and admins run an organization. Developers and members see the projects that their teams give them. A billing member reads billing only. The teams, roles and keys guide has the roles and the keys, how long each key lasts and what is logged.
- Keys have a scope. An admin key acts for one project. A task key writes only its own task. An agent group key gives each agent its own task. Give agents a task key or an agent group key, never the admin key.
- Checks never hold a credential from Switchyard. A GitHub Actions job sent to a Switchyard machine gets only the secrets that GitHub gives any runner for that job.
- Only a person who is signed in approves a review. The project admin key, an organization API key and agents approve nothing.
- A signed-in session works only from Switchyard's own pages. Switchyard refuses a request that carries a session from another site.
- A session that is signed out, or an organization key that is revoked, stops within 30 seconds on every project. A request already in flight finishes. A Git key that a revoked organization key started runs to its own end.
Sign-in
- People sign in with GitHub, with a link emailed to their address, with Google where the sign-in page offers it, or with single sign-on where their organization set it up. During the private beta, only accounts on the list can sign up.
- An organization on Scale or Enterprise can require single sign-on. Its members then sign in only through the organization's identity provider. A connection signs nobody in until a DNS record proves each of its email domains.
- An organization can require two factors: an authenticator app or a passkey, GitHub's own two-factor for a GitHub sign-in, or single sign-on. Every organization recommends two factors by default and refuses nobody for them.
- One email address gets at most 10 sign-in links and welcomes from Switchyard in a day. Invitations and billing emails do not count toward it. Where the sign-in page shows a Cloudflare Turnstile check, Switchyard verifies it before it sends a sign-in link.
- An agent can sign in with AgentID as an agent account. An agent account joins only the organizations that invited it, as a developer or a member. It approves no review, and its session lasts 1 hour.
- Sessions last 30 days and renew while you use them. They are signed with a secret that the database does not hold, so a copy of the database alone signs nobody in. Session cookies are Secure, HttpOnly and SameSite=Lax.
- Your account page lists where you are signed in. You can sign out one place, or every place,
yardin terminals included. - You can delete your account from the account page. You leave every organization. If you are the only owner of an organization that has other people or owns projects, first make someone else an owner, or remove the others and delete the projects.
AI suggestions
AI suggestions run only for an organization that turned them on in its settings. An owner or an admin turns them on or off, and the audit log records each change. Saving the organization's own Anthropic key does not turn them on: it decides which key a suggestion uses once they are on.
When the file rules cannot merge a code conflict, Anthropic receives these items for that one file, and nothing else from the repository:
- the file's path;
- the file as the task has it, when the file has 60,000 characters or less;
- each conflicting part, with its earlier text, both sides and the 6 lines before and after it;
- what each side was doing: the description of its task, its plan and its commit messages.
Switchyard does not remove secrets from the file's text, so do not keep secrets in files that agents change.
- Suggestions go to Anthropic's API, model
claude-opus-5-5. They use the organization's own Anthropic key when it saved one, and Switchyard's key otherwise. - A suggestion changes nothing until the task's agent or a person accepts it. The history records which model answered and how much text it read and wrote.
- A suggestion on Switchyard's key costs $0.50. Switchyard does not bill a suggestion on the organization's own key. The limits page says how many suggestions an organization can have, and the conflicts guide says where the step is.
Evidence
- Every sensitive action is in your organization's audit log for at least 400 days, and you can export it.
- Every merge has a signed merge record of what merged, why it was allowed and which checks passed. The guarantees page says what it holds and how
yard verifychecks it.
Who processes your data
| Company | For |
|---|---|
| Cloudflare | Hosting, code storage, databases and email |
| GitHub | Sign-in, and the repositories that you connect |
| Sign-in, for people who sign in with Google | |
| AgentID (AgentMail) | Sign-in, for agents that sign in with AgentID |
| Anthropic | AI suggestions, only for organizations that turn them on |
| TypeSafe | Whether two tasks' plans describe the same work, and the questions that a project's rules file asks about a change |
| Stripe | Cards and invoices, for organizations that pay by card |
Reporting a problem
If you find a security problem, tell us privately before you tell anyone else, and give us a reasonable time to fix it. Write to security@switchyard.so. The same address is in /.well-known/security.txt.