Privacy Policy

Data we collect

We collect only what we need to run the service:

• +

  Account details: your email address, and a password hash if you sign up with a password. If you sign in with GitHub, we store the GitHub OAuth access token issued to ronda so we can read and write the repositories you connect.

• +

  Connected repository data: metadata about the GitHub repositories you connect (such as repository name and structure) and the source files ronda reads and edits when you ask for a change.

• +

  Edit instructions and session data: the plain-language instructions you type, and the session state ronda keeps while a change is in progress.

• +

  Your model provider API key: ronda is bring-your-own-key. The key you provide for the model provider your workspace uses (Anthropic or an OpenAI-compatible endpoint) is encrypted at rest with AES-256-GCM, and only the last four characters are shown back to you in the interface.

• +

  Billing details: if you subscribe to a paid plan, payment is processed by Stripe. We do not store your full card number.

• +

  Usage and product analytics: we record events such as page views, key product actions, and the tool calls made by AI clients you connect (tool name, success, latency, and workspace and connection identifiers) to understand how ronda is used and to improve it.

How we use your data

We use your data to authenticate you, connect your GitHub repositories, apply the changes you request, generate pull requests, process billing on paid plans, and operate and improve the service. We do not sell your data.

Storage and security

Your data is stored in our PostgreSQL database hosted on our infrastructure. Sensitive values, including your model provider API key and other credentials, are encrypted at rest with AES-256-GCM. Access to production systems is restricted to ronda operators.

Third parties we share with

ronda relies on a small number of providers to deliver the service. Each receives only the data needed for its function:

• +

  Your model provider: when you ask ronda's own agent to make a change, your instructions and relevant source code are sent to the model provider your workspace configured (Anthropic, or an OpenAI-compatible endpoint), using your own API key. Your use of that provider is governed by its terms and privacy policy.

• +

  AI clients you connect, such as ChatGPT (OpenAI) or Claude (Anthropic): when you connect one, it receives the data described in the next section. That provider's terms and privacy policy govern what happens to it there.

• +

  GitHub: ronda reads and writes the repositories you connect through the GitHub OAuth access token you grant. Your use of GitHub is governed by GitHub's terms and privacy policy.

• +

  Stripe: handles payment and subscription processing for paid plans.

• +

  PostHog: provides product analytics for the events described above.

Connecting ronda to ChatGPT or another AI client

You can connect ronda to an AI client that supports MCP, such as ChatGPT or Claude, by signing in with OAuth. The client then acts on your workspace with the permissions you approve on the consent screen. This is what that involves:

• +

  What the client receives: results of the tool calls it makes. Depending on the tool, that includes repository file contents and search results, diffs, dev server and install logs, the output of commands it runs in the sandbox, preview URLs, project and session details, and, through the profile tool, your ronda account id, email address and workspace name.

• +

  What the client does with it: once data reaches the client, it is handled under that client provider's terms and privacy policy. For ChatGPT that provider is OpenAI. ronda does not control how a client stores or uses what it receives.

• +

  Which model does the work: when the client edits your code with its own tools, the model is the one the client runs and no ronda model key is used. When the client asks ronda's own agent to make an edit, your instructions and relevant code go to the model provider your workspace configured.

• +

  What ronda stores and logs: each edit the client makes is committed on the session's working branch in the sandbox and recorded as an edit with its instruction text, diff, commit hash and changed files. Commands the client runs are written to our server logs with the session and connection identifiers and the first 500 characters of the command text, but not the command output. Every tool call is also recorded as a usage event. Edits the client makes directly stay in the sandbox until a pull request is requested. Edits made by ronda's hosted agent are pushed to a working branch in your repository (its name starts with ronda/session-), never to the default branch.

• +

  Secrets in repositories: environment files such as .env are excluded from file reads and search results. Commands run in the sandbox can still read any file in the repository, and their output is returned to the client, so keep secrets out of repositories you connect.

• +

  Connection tokens: ronda issues the client an access token, valid for one hour, and a refresh token. We store only hashed copies, and access is limited to the permissions you approved.

• +

  Revoking access: open Connectors in your ronda settings and choose Revoke next to the client. It stops working immediately.

Data retention

We keep your account, project, and session data for as long as your account is active. Sandboxes that sit idle are archived rather than deleted, with your work saved in our database, so a session can be resumed. You can disconnect a repository, revoke a connected client, or delete your model API key at any time, which removes the stored value or access. When you ask us to delete your account, we remove your personal data, subject to any records we are required to keep for legal or accounting reasons.

Your rights

You can access, correct, or delete your personal data by contacting us at the address below. We will respond to verified requests within a reasonable time.

Contact

Questions about this policy or your data can be sent to the email address below. For general support, visit our support page.