Privacy policy

What this covers

CodeInOven is free, open source software published by Pillardash. It reaches you in three ways, and each one handles your information differently:

• This website is a public site that measures visits and nothing else.
• The desktop app works without an account. Your work stays in its own folder on your computer.
• The account and the mobile app are optional. You need an account only to sign in on a phone and read your projects there.

Your work stays on your computer

The desktop app keeps your projects, threads, chats, plans, checkpoints, speech recordings and settings in its own folder on your machine. It opens a folder to work in rather than storing itself inside your repository, and it does not change your files unless you or an agent asks it to.

Your API keys, GitHub access and the passwords for your machines are kept in your operating system's secure vault, encrypted on your computer. An agent can ask to use a key, but it is shown a placeholder instead of the value, so the secret never appears in a conversation, a plan or a file.

Dictation and cleanup run on a local model while one is installed, so the audio stays on your machine. If you never sign in, none of this reaches a CodeInOven server.

If you create an account

You can sign up with an email address and a password, with Google, or with GitHub. Any of the three gives you the same account. We keep your email address, your display name if you give us one, your profile picture, and which of the three you used to sign in.

When you choose Google or GitHub, you sign in on their page, not ours, and we never see your password for either service. They tell us your name, email address and profile picture, and nothing else.

The GitHub sign-in is limited to reading your basic profile and your email addresses. It asks for no access to your repositories, organizations, workflows or notifications, so approving it gives away nothing in your GitHub account. Google shares your name, address and picture only.

If you sign up more than once, we connect the accounts only when the provider confirms the same verified email address.

Using the phone app

The phone app is a reader for your account, not a second workstation. You connect it by signing in with Google, GitHub or your email and password. Your phone keeps the sign-in securely, and you stay signed in until you sign out or remove the phone from your account.

On the phone you can see your projects, their threads and the conversations in them, and you can send a prompt. The work itself still runs on the machine that owns the project. The phone cannot open a terminal, browse your files, review a change or start an agent, and it never receives your API keys, your vault or the passwords for your machines.

What the account keeps

An account keeps what it needs to sign you in and to show your projects on a phone:

• Who you are: your email address, whether it is confirmed, your name and your picture.
• How you signed in: whether it was Google, GitHub or a password.
• Your devices: the name you gave each one, what kind of device it is, and when it was last used.
• Your projects: the projects, threads, conversation messages, queued prompts and assistants you create in a thread.
• Your machines: the name of any computer you added as an Oven, so the account can list it.

An account does not keep your API keys, your vault, your repository, your terminal output or anything else from the desktop app that you did not send to a thread.

Where your prompts go

When you send a message, the agent and the model you chose receive what that turn needs: your message, the parts of the project the agent reads, the results of the commands it runs, and its reply. That traffic goes straight to the account or API key you connected, under that provider's own privacy terms. We do not sit between your machine and your model provider, and we do not use your prompts to train a model.

A model you run yourself, through Ollama, LM Studio or your own server, keeps the prompt on your network.

This website

We measure visits so we know which pages are worth keeping: page visits, the site you arrived from, campaign tags, what kind of device you used, how far you scrolled and which downloads you clicked. That measurement service is PostHog, in the United States.

We do not use analytics cookies, we do not record your session, we do not read form contents, and we do not collect your location, your IP address or the full web addresses you open. A notice on your first visit says so, and dismissing it only hides the notice.

If your browser sends Do Not Track or Global Privacy Control, we collect nothing at all. The desktop and phone apps do not use this measurement; what you do there stays yours.

Who else is involved

We rely on a small number of services to run the parts that do not run on your computer:

• Hosting and a database for this website and for accounts, which hold the information listed above.
• PostHog, for the website measurement described above.
• Google and GitHub, only when you choose to sign in with them, under their own privacy policies.
• An email service, once one is in place, to send confirmation and password reset links.

We do not sell your information, we do not give it to advertising networks or data brokers, and we disclose it beyond that only when the law requires, and then only what the request covers.

How long it is kept

Confirmation links last a day and password reset links last 30 minutes. A sign-in lasts 30 days and renews while you use it, and it ends the moment you sign out or remove the device from your account list.

Your projects and conversations stay in your account until you delete them or close the account. Closing the account removes everything the service holds for you. Deleting a thread removes it on the next sync. Removing the desktop app's folder deletes the work that never left your computer.

What you can ask for

You can ask for a copy of what your account holds, have a mistake corrected, have everything deleted, or object to a particular use. You can also close the account yourself in the app, and that takes effect immediately.

If you live in the European Economic Area, the United Kingdom or Switzerland, those are your rights under the GDPR and its UK equivalent. If you live in California, you have the rights the CCPA gives you, and since we do not sell or share personal information for advertising, there is nothing to opt out of.

Write to [email protected] from the address on the account, and we answer within 30 days.

How we protect it

Passwords are stored scrambled, so nobody, including us, can read them back, and we encourage a long one. A sign-in can be revoked from any other device, which takes effect at once. Traffic to the account service is encrypted, and on your computer your keys live in the operating system's secure vault rather than in a project file.

Children

CodeInOven is a tool for professional work and is not meant for children. An account may not be created by anyone under 16, and we delete an account we learn was created below that age.

Changes to this policy

This policy changes as the product does, and the date at the top changes with it. If a change affects what your account keeps or who receives it, we tell you in the app before it takes effect.