What leaves your machine, and what does not.

The design premise

Creator is a desktop application. It opens a project that already exists on your disk, and the agents inside it read and write those files directly. There is no step where your repository is copied to a Radovar server in order for the product to work, because there is no Radovar server in the path.

That single decision removes a large part of the usual threat model. There is no shared bucket of customer source code to breach. There is no retention window to argue about. There is no internal team with a plausible reason to read your project. We cannot lose data we never receive.

Where the architecture stops

Being precise matters more than sounding safe, so: if you point Creator at a hosted model, the content of your prompts and the file context the agent needs are sent to that model provider. That is how hosted models work. Creator does not change it, and no amount of local-first design can.

What Creator does give you is the choice, made explicitly and visibly:

• Hosted model. Your prompt and the relevant file context go to the provider you selected, under that provider terms. Radovar is not in the middle of that exchange.
• Local model. The model runs on your own hardware. Nothing leaves the machine at all. This is the mode for work that genuinely cannot go anywhere.

Changes are proposed, not applied

An agent that can silently rewrite your working tree is a security problem regardless of where it runs. Creator treats every edit an agent wants to make as a proposal: it arrives as a diff, scoped to named files, and it does not land until you approve it.

This is the control that matters in practice. It means a mistaken instruction, a confused model, or text injected into a file the agent happened to read cannot turn into a committed change without a person seeing the diff first.

Credentials

Provider keys and sign-in sessions are stored on the machine that uses them, and are read only by the process that needs them to make a request. Radovar does not proxy provider traffic, so we never hold your provider credentials.

Reporting a vulnerability

If you believe you have found a security issue in Creator, write to security@radovar.com with enough detail to reproduce it. Please give us a reasonable window to investigate and ship a fix before disclosing publicly.

We will confirm receipt, tell you what we found, and tell you when a fix ships. If we disagree that something is a vulnerability, we will explain why rather than go quiet.

What we do not claim

Radovar is a small company and Creator is in early access. We hold no third-party security certification today, and we would rather say so plainly than imply otherwise. If a certification becomes relevant to how you would use Creator, tell us and we will tell you honestly where we stand.