Your code stays yours.
Infersync watches your coding agents from a runner on your own machines, so your code never leaves them. Here is how we handle access and data, and an honest note on what we have not built yet.
Your code stays on your machines
Agents run there, in a git worktree, with their own accounts. Infersync receives the names of your repositories, the actions an agent takes, the pull request and the result of the check. Never your source files.
Encryption in transit and at rest
All traffic is encrypted in transit, data is encrypted at rest, and each machine's key is stored encrypted.
A person decides what can hurt
A change that touches auth, payments, secrets or a path you name goes to a person first. Merging the pull request is the approval, and every run, stop and approval is kept in the record.
Authentication
Sign in with GitHub. Each workspace sees only its own data, and each machine has its own key. SSO and SCIM are not built yet.
Your data, your call
An admin can delete the workspace with one command; after 30 days it is gone for good. Ask us to export or erase your data and we do it. We do not train models on your data.
Your agents, your accounts
Each agent runs with its own program and its own subscription or key, on a machine you control. Infersync never holds your agents' keys.
Where we are, honestly
No certifications we haven't earned.
We are an early company and we say so. Infersync has not completed a SOC 2 or ISO 27001 audit, and we will not claim a badge we do not hold. Any team can request our current security posture, a DPA, and a security review, and we are happy to walk through exactly what is and isn't in place today.