what we keep, and why

who is responsible

switchyard is made by one founder in the united kingdom and is being set up as a company. until registration completes, the founder is the controller of the personal data described here, trading as switchyard. this page will name the company, its registered number and its address as soon as they exist. contact for anything about your data: hello@switchyard.so.

what we collect

the waitlist

your email, your two optional answers (how many agents you run, your company), your browser's user agent string and the time you joined. we do not store your ip address. we send one email to say you are on the list and one when there is room for you.

your account

sign-in is with github. we keep what github gives us: your github login, name, picture and email, plus the teams you belong to in switchyard and your sign-in sessions (when and from what kind of device, so you can see where you are signed in and sign out anywhere). the github access token github issues us is encrypted before it is stored and is read only to act on github for you.

your repositories and your agents' work

when you connect a repository, switchyard installs a github app on it with these permissions: repository contents (read and write), metadata (read), workflows (read and write), pull requests (read and write) and checks (read and write). we then hold a copy of the repository's git data in switchyard's own git storage, and everything the product records about work on it: tasks, the agents' plans, pushes and commits, warnings about overlapping work, conflicts and how they were fixed, merge records with the checks that passed, and an audit log of sensitive actions with who did them and when. commit messages and commits carry the names and emails your agents and people put on them.

setting up your agent

the setup command on the set-up page sends us three things: the one-time code, your computer's name and the address of your clone. the entry for your coding tool is added on your computer by the script, never by us, and your tool's other settings are never sent. the key it writes is yours; we never print it.

checks

when switchyard runs your checks, your code runs in a fresh container that is destroyed afterwards. we keep the check's output log with the merge record. containers hold no credential of yours unless your team has set a test secret for them, which only an owner or admin can do.

AI suggestions

off until an owner or admin turns them on for the team. when they are on and the file rules cannot merge a conflict, anthropic receives, for that one file: its path, the file as the task has it when it is under 60 KB, each conflicting part with its earlier text, and the one-line description of each task. the answer is a suggestion and changes nothing until a person or the task's agent accepts it. we record which model answered and what it cost. we send nothing to anthropic for training; it is processed under anthropic's commercial api terms.

email we send

the product sends email about your projects: a task that needs you, a digest, an alert. each one says why you got it. the sending address and your reply go through cloudflare's email service.

support

if you write to us, we keep the correspondence to answer you and to fix what you reported.

billing, when it starts

switchyard is in private beta and takes no payment yet. when billing starts, card details will go to stripe, our payment processor, and never to us; we will hold your billing name, address, tax id if you give one, invoices and usage records. this page will be updated before the first charge.

what we do not do

• no analytics trackers, advertising pixels or third-party scripts on this site or in the product. the only script on these pages is our own.
• no selling or renting of personal data, and no sharing except with the processors named below.
• no training of models on your code or your conflicts. if we ever ask for that, it will be opt-in, in writing, and off by default.
• no reading of your repositories by people, except with your request to fix a problem, which is written in your audit log.

cookies

the product sets one session cookie when you sign in. it is secure, httponly and samesite=lax, and it is removed when you sign out. this website sets no cookies.

who processes your data

a data processing agreement is available to teams on the scale and enterprise plans, and on request to any paying team.

how long we keep things

• your account: until you delete it from your account page. deleting it signs you out everywhere and removes you from every team; a team only you are in, with no projects, goes with you.
• a project: until it is deleted. a deleted project's record and git data are kept 30 days so a mistake can be undone, then purged.
• the audit log: 400 days per team.
• the waitlist: until you are invited or ask to be removed.
• support mail: as long as the matter is open and for a year after.
• backups and logs: operational logs are kept for up to 30 days to run and secure the service.

your rights

you can ask what we hold about you, have it corrected or deleted, take it with you, or object to how we use it. your code is already portable: a plain git clone takes all of it. your project's history and audit log can be exported from the product. write to hello@switchyard.so; we answer within 30 days. if you are in the uk or the eu and are not satisfied, you can complain to your data protection authority; in the uk that is the information commissioner's office.

security

how code and accounts are protected is on the security page. to report a problem, write to security@switchyard.so; see also security.txt. if a breach affects your data, we will tell you without undue delay and say what happened and what we did.

children

switchyard is for teams at work and is not for anyone under 16.

changes

when this page changes, the date at the top changes and we say what moved. for a change that matters to you, such as a new processor, we email the owners of each team before it takes effect.