Privacy notes

When you sign in, the app receives basic profile information from the provider you choose, such as your name, email, avatar, provider account id, and OAuth tokens needed to keep your session working.

When you connect GitHub, the app stores the account and installation information required to list repositories, create branches, push commits, and open pull requests you request through the agent.

When you create a session, the app stores session metadata, selected repository details, chat messages, sandbox state, and generated outputs needed to resume or review that work.

Authentication data is used to sign you in and maintain your account session.

GitHub and Vercel access is used to run the product workflow you initiate, including repository selection, sandbox creation, branch creation, commits, and pull requests.

Analytics may be used to understand whether the public landing page and product routes are working, but private repository content is not used for marketing analytics.

This deployment relies on providers such as Vercel, better-auth, GitHub, Neon Postgres, Upstash Redis, Vercel Sandbox, AI Gateway, and configured model providers.

Repository work runs in isolated sandbox infrastructure. Do not connect repositories that contain secrets, regulated data, or material you are not authorized to share with these services.

You control whether to sign in with Vercel or GitHub, whether to install or connect GitHub access, and which repository a session uses.

You can revoke provider access from your Vercel or GitHub account settings. You can also avoid connecting sensitive repositories and use a test repository for evaluation.