What we store, and for how long.

Signing in stores your account identity and a session cookie. Creating a workspace stores its files. Nothing is sold, and there is no advertising or profiling. Deleting a workspace deletes its files; logging out expires the session.

With GitHub. The OAuth app requests the read:user and repo scopes — the second so a workspace can clone and push your repositories. We keep your numeric ID, login, display name, email address and avatar URL, plus the access token, inside a signed session cookie named oauth-session. It is HttpOnly, SameSite=Lax, and expires after seven days.

With an email link. We keep your address and a single-use token that expires fifteen minutes after it is issued. Requests are rate limited to three per address per minute. Magic-link accounts have no GitHub token, so the repository features are unavailable on that path.

Sign-in mail is delivered by Resend, which necessarily sees the recipient address and the message.

Each workspace has a record — owner, ID, name, template, and whether it is currently running — held in Redis, and a filesystem held in an S3-compatible bucket under a prefix derived from your account handle and the workspace ID. While a workspace is running, its container is a pod on the Kubernetes cluster; stopping it removes the pod and leaves the files.

Anything you put inside a workspace is stored: source files, installed dependencies, and anything a program running in it writes to disk. Treat the same way you would treat a shared machine — in particular, credentials written into a workspace are stored with it.

Deleting a workspace removes its object-storage prefix and its record in the same request. That is not recoverable; there is no trash and no backup to restore from.

Logging out expires the session cookie. To remove an account and everything attached to it, delete your workspaces and then open an issue or email — account deletion is not yet a button, which is worth saying plainly rather than implying otherwise.

Revoking the GitHub authorisation from your GitHub settings invalidates the stored token immediately, from GitHub’s side, without waiting for us.

This site loads Vercel Analytics, which records page views without cookies and without a cross-site identifier. The site itself is hosted on Vercel; the control plane, the cluster and the bucket are operated by the maintainer. Resend handles sign-in mail. There are no advertising, marketing or session-replay scripts, and no third-party cookies.

None of the above applies to a self-hosted deployment. It runs on your cluster, writes to your bucket, and sends mail through your own credentials — this project sees none of it.

Anything unclear or wrong here is a bug in this page. Raise it on the issue tracker or through the contact page.