Privacy Policy

Last updated July 27, 2026 · Beta policy

What we store

  • Account data — your email, password hash (email sign-ins), and the identity your OAuth provider shares (GitHub, Google, or Linear login and email).
  • Beta access requests — if you ask for private-beta access before you have an account, we keep what that form collects: your email, plus any name, company, role or note you add, until the request is decided.
  • Organization data — members, roles, invites, projects, and the configuration of everything your org connects. Every credential in that list — the access tokens a connector's OAuth flow returns, git push tokens, model-provider keys, and anything you save under Settings → Secrets — is encrypted at rest, and decrypted only when a run needs it.
  • Run data — tasks, runs, phase transcripts, events, check output, and published artifacts, so you can review them later.
  • Devices — if you use the phone app, one push token per phone per organization, so a gate can reach you. It is removed when you sign out of that phone, and when the token stops delivering.
  • Your session — kept differently on each surface: the website uses one HttpOnly cookie (plus a ten-minute state cookie while a "sign in with" round-trip is in flight), the desktop app uses your OS keychain, and the phone app uses the device's secure storage. No advertising trackers, no third-party analytics scripts.

Your code

A run needs your code, so it clones your repository into a sandboxed container on our infrastructure, works there, and pushes to a branch in your repository. The container and its workspace cache are destroyed when the run ends — we keep no copy of your codebase, and the diffs you review are read back from your repository on demand.

What does persist is the run's record, and that is worth being exact about: transcripts, events and check output quote whatever the agent printed, which routinely includes file contents and diffs. If a workflow uses a preview step, the build it serves is reachable at an unlisted URL for as long as that preview is held open — it isn't behind your session, so treat the URL as the only thing guarding it.

What we don't do

  • We don't sell your data or share it with advertisers.
  • We don't train models on your code or transcripts.
  • We don't read your repositories beyond what a run you started needs.

Third parties

Runs call the model provider you configured (Anthropic, OpenAI) with the prompts your workflow builds — your code travels inside those prompts, and their terms govern that traffic. Tracker and notifier connectors exchange data with the services you connect (GitHub, Linear, Jira, GitLab, Notion, Slack, Discord, …) on your org's behalf.

Three more sit on our side of the line: Expo delivers push notifications, so a device token and each notification's title and body pass through it; Resend sends account and invite email; and Peractor Cloud runs on DigitalOcean.

Deletion

Ask and your account, its organizations, and their runs, tasks, connections and stored credentials are deleted. Contact us via GitHub while in-product deletion is being built.