Your ideas belong
to you.

Preview policy · October 17, 2026

Freecoda is built around local execution, clear permissions, and straightforward data use. We do not sell your source code or conversations, train models on your content, or share it with advertisers.

What stays on your machine

When you use the local CLI, your repository, tool execution, and conversation history stay on your machine. When you use your own API key, the key is stored locally with restrictive file permissions. Direct provider requests bypass Freecoda.

Cloud workspaces

Cloud workspaces are optional and require explicit consent before creating a project or starting an agent run. Project files, chat prompts and responses, diffs, and command output are stored in encrypted cloud records for up to seven days after last activity. Code executes in an isolated cloud sandbox. This content leaves your machine and is sent to the model provider when needed to complete your task.

Do not put secrets or private customer data in a cloud project. Only GitHub repositories you select for the Freecoda GitHub App can be imported. GitHub credentials stay on the server and are not provided to the sandbox or agent. A private preview uses short-lived access. Publishing requires reviewing the diff and explicitly confirming a branch and draft pull request; the agent cannot merge or deploy it.

Cloud workspaces share the free service’s capacity and may suspend when idle or when limits are reached. Suspending stops compute; it does not immediately delete saved project content. You can delete a cloud project to remove its content and stop its preview. Existing GitHub repositories and pull requests are unaffected.

What leaves your machine

AI inference requires sending your prompt and the relevant source excerpts, repository instructions, and tool output to a model provider. Hosted requests pass through Freecoda and Vercel AI Gateway to OpenAI using our provider credentials. This is not an offline product. Review your repository trust and tool approval prompts before sharing context.

No training on hosted prompts

OpenAI API requests use response storage disabled. OpenAI does not train on API inputs or outputs by default; operational and abuse-monitoring retention may still apply. Gateway routes must disallow prompt training. This is different from zero data retention. Review the provider’s data controls before sharing sensitive material.

Ads and sponsorship

Sponsor cards are separate from agent responses. When no sponsor campaign is active, we show a labeled Freecoda announcement without counting a paid impression. Advertisers do not receive source code, prompts, or conversations. Sponsor measurement is described below.

Website analytics

Vercel Web Analytics measures page views and traffic using cookie-free analytics. Vercel Speed Insights measures page loading, responsiveness, and visual stability. This is separate from sponsor measurement and does not include prompts, source code, or conversation content.

Accounts and usage

We retain your GitHub identity and email, authorized device records, invitation status, and usage metadata to operate the service. The free hosted beta does not collect payment cards or sell credits. For local CLI inference, we do not persist prompts, responses, source code, or tool output in our application database or application logs. Optional cloud workspaces retain the project content described above for up to seven days after last activity.

Sponsor placements

Direct sponsors appear in labeled placements, separate from model output. Ads are selected by placement and active campaign, not your prompts, code, identity, or repository. We count aggregate deliveries and clicks using short-lived random ad tokens. These tokens identify an ad delivery, not a person. No advertising cookies or third-party tracking pixels are used. Freecoda announcements are not billed as sponsor impressions.

Your choices

You can revoke CLI devices in your workspace and clear local history with the CLI. Deleting your account removes active sessions and access; records required for fraud prevention or legal obligations may be retained. BYOK use is governed by your provider’s agreement and settings.

Preview status

Hosted access is limited to invited beta accounts and available daily capacity. The model and provider shown in the CLI are the ones configured for your session. Privacy changes will be reflected here before new data uses begin.