sub-processors · 19 November 2026
Who handles data for us
These are the companies that handle data for Switchyard. Each row says what the company is for, what it receives and when. The privacy policy says what we collect and how long we keep it. If anything here is unclear, write to hello@switchyard.so.
Companies that handle what is in your projects
| Company | What for | What it receives | When |
|---|---|---|---|
| Cloudflare | Hosting, Git storage, databases, running checks, and the email the product sends | Everything Switchyard stores and serves: your Git data, accounts, tasks, plans, check logs, merge records and audit logs | Always |
| GitHub | The repositories you connect | What the Switchyard GitHub app is allowed on those repositories: contents, metadata, workflows, pull requests and checks. Merges that pass are written there | When you connect a repository on GitHub |
| Anthropic | AI suggestions for a conflict | For one conflicting file: its 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; and what each side was doing: the description of its task, its plan and its commit messages | Only after an owner or admin turns AI suggestions on, and then when the file rules cannot merge a conflict. When your organization has saved its own Anthropic key, the request is made with that key |
| TypeSafe | Whether two tasks' plans describe the same work, and the questions a project's rules file asks about a change | For two plans: each task's number and description and its plan (the summary, the approach and the paths, symbols and interfaces it says it will touch). For a rule's question: the question, the paths the change touches and the lines it adds. An input that looks as if it holds a secret is answered by our own code and is not sent | When a task's plan is compared with another task's plan; when a rule that asks a question meets a change |
Companies used for sign-in, forms and payment
| Company | What for | What it receives | When |
|---|---|---|---|
| GitHub | Sign-in with GitHub | Your sign-in, on GitHub's own page. We read your profile and email | When you choose it |
| Sign-in with Google | Your sign-in, on Google's own page. We read your name, email and picture | When you choose it, where the sign-in page offers it | |
| AgentID (AgentMail) | Sign-in for agents | The agent's sign-in, on AgentID's own page. We read the agent's name and email, and its owner's identifier, name, email and whether AgentID verified them | When an agent signs in with AgentID |
| Cloudflare | The check that a form is not sent by a bot (Turnstile), and the contact form's email | The check's answer and your IP address; what you write in the contact form | For the check: on the sign-in, waitlist and contact forms, where the check is shown. For the email: when you send the contact form |
| Stripe | Cards, invoices and tax | From us: the organization's name, its identifier and short name in Switchyard, and a billing email. From you, on Stripe's own page: card, billing address, tax id | For organizations that pay |
What is not on this list, and why
- Your own Anthropic key. When your organization has saved its own key, AI suggestions are asked for with that key, on your organization's own Anthropic account.
- GitHub profile pictures in the app. Your browser loads them from GitHub.
- Fonts. Our pages and the app serve their fonts from our own domains.
Changes to this list
When this list changes, the date at the top changes and we say what moved.
- sign-up is open to everyone. The bot check is on the sign-in and contact forms.
- 19 November 2026: Google is no longer used for fonts: our pages and the app serve their own. Google stays for sign-in with Google.
- 17 November 2026: first version of this page. Against the list on the privacy page of 21 October 2026 it adds Google, AgentID, TypeSafe and Cloudflare's bot check, and shows Stripe as in use.