Skip to content
DownloadLog inSign up

Privacy and security

Your chats

  • No account needed. The apps have no account or password. Your phone or computer makes its own key the first time it runs and signs every message with it. On the website, the site signs your messages for you.
  • In the web chat on openagents.com, we save your chats on our servers. Our team can read them.
    • Logged in (with GitHub), your chats belong to your account: you see them in any browser where you log in, and after you log out, someone else using that browser doesn't. Chats you started in that browser before logging in move to your account when you log in.
    • Not logged in, a random cookie tells this browser's chats apart. Only this browser opens them, and anyone using it can. If you clear your cookies, you can't open them again.
    • Deleting. To delete a chat, open it and choose Delete chat. To delete every chat, choose Delete all chats: in Settings when signed in, or on a chat's delete step when not. Chats are removed from our servers right away, though our storage provider may keep a copy we can recover for up to 7 days. Chats you don't delete stay; there's no time limit yet.
    • Exporting. Logged in, open Settings and choose Download under Your data (or go straight to openagents.com/settings/export). You get one file with every chat (each with a Markdown copy to read), your projects, your uploaded traces, your logged-in computers, and your settings. It opens in any text editor, without OpenAgents. It holds only your own account's things, and never a key, token, or password: an API key shows by name only, and a saved Claude credential by its kind only. From a terminal logged in with coder login, coder export --account saves the same file (--output FILE to choose where).
  • In the Mac app, Terminal, and phone app, your chats are saved on your device, encrypted with its key (on a computer, by its host). Your messages are encrypted before they leave your device, and the OpenAgents relay that carries them to our chat service sees only the encrypted form and keeps nothing. When your phone reaches your computer through the relay, the relay holds those messages, encrypted, for that phone and computer only.
  • Our chat service doesn't keep your message text. It records each request's time, key, surface, route, model, token counts, and timings for usage statistics, and deletes those records after 30 days.
  • Training. We may use your chats to train and improve our models. On a paid plan you can ask us to opt you out; we set that up with you.
  • Reports. If you send a problem report and choose to share the chat, that chat goes to our team with it.

Who sees what

To answer, our chat service sends your messages to these services:

  • Google's Gemini 3.8 Flash, on Google's Vertex AI, through OpenRouter, or through the Vercel AI Gateway (and Gemini 2.5 Flash, through the same gateway, for some Gym news replies).
  • GLM, through OpenRouter or the Vercel AI Gateway, as a backup when Gemini doesn't answer.
  • TypeSafe's Jev, which decides how we reply. Jev is reached through the Vercel AI Gateway first, then OpenRouter, then TypeSafe directly.
  • OpenRouter, for a short personalized line in some replies that hand work to Coder.
  • OpenAI embeddings, through the Vercel AI Gateway, when a question is answered from our product notes, our code, or the Gym's records.

When we send your messages to Gemini, GLM, or the OpenRouter model that writes personalized lines, we ask the model provider not to keep them or train on them. If a model's provider can't agree, we don't use that model. We don't ask this of Jev or the embeddings yet.

When you chat on a computer, or from a phone connected to one, each message also names that computer and the chat's project folder; after Coder runs in a chat, the next messages carry what it reported, the files it changed, and its commands. Only our chat service and the chat model read those.

Ask the chat "What happens to my messages?" and it answers with the services it uses right now.

What we count on the website

We count how openagents.com is used ourselves. There's no outside analytics service, no tracking script from another company, and no cookie for it.

  • What we count: which page was opened (the kind of page, not its full address: every chat counts as "a chat"), the name of the site that sent you (like ycombinator.com), whether you're on a phone, tablet, or computer, whether the visit came from a person, an AI agent, or a crawler, how fast the page loaded, and a few actions: sending a chat, getting an answer, clicking a suggestion or a card, clicking a download, copying the install command, and logging in.
  • What we don't: your IP address, cookies, your account, what you write, or anything that tells one visitor from another. We keep hourly totals, so we can't tell whether two visits came from one person.
  • Do Not Track and Global Privacy Control: with either one on in your browser, we count only that the page was opened, and nothing else.
  • How long: the hourly totals are kept for 13 months.

Our hosting provider's request logs, which keep the site running and secure, do see IP addresses; they're deleted after 30 days.

Links that credit who sent you

Our own campaign links start with openagents.com/go/ (like openagents.com/go/yt-cost), and links shared by people who recommend us start with openagents.com/r/. Unlike the counting above, following one of these keeps a cookie in your browser, so we can credit who sent you.

  • What's kept in your browser: one cookie, oa_ref, that only our site can read. It holds the link you followed, its series, a random click number, and the time. It lasts 30 days; a newer link replaces it, and it's deleted when you log in or sign up.
  • What we keep: for each click, the random click number, the link's code (a short code for a referral link, never the link itself), the series, the time, the page it led to, and whether a person, an agent, or a crawler clicked, for up to 13 months. Not your IP address, device, browser, or account. If you sign up while the cookie is set, your account keeps which link brought you. A later paid plan is counted for that link too.
  • Asking first: in the European Economic Area, the UK, and Switzerland, or when we can't tell where you are, we ask before setting the cookie, and set nothing if you say no.
  • Do Not Track and Global Privacy Control: no cookie, and we only count that a link was followed. Agents and crawlers never get the cookie.
  • Who sees it: we do. Someone who shares a referral link may see totals for their own link, never who you are. What we pay them is in our affiliate terms.

Your computer

  • A phone can reach your computer only after you scanned that computer's QR code (or pasted its code, or approved it on the computer's screen).
  • Every connected phone gets full access to that computer, a terminal included. The computer checks each message against that access. Remove in the Mac app cuts a phone off at once.
  • The Mac app keeps its keys in the Mac's keychain.
  • Coder works on your computer, in your projects. Like Codex or Claude Code on their own, the coding agent it runs sends what it reads to that agent's model provider, under your login there.
  • By default Coder approves its own steps, including a push, so it can finish without stopping to ask. To run it inside a stricter boundary, see coder.access in the settings reference. In the coder terminal app, production deploys, merges, secrets, payments, and DNS changes always wait for you; see Safety.

Your phone's keys

  • Device key: made on your phone, kept in its Keychain on this device only, and never synced. It holds access to your computers.
  • World key: a separate key for the Verse and your XP, so other players can't link you to your device key.
  • Wallet: its own recovery words, separate from both.

The full details are in the Privacy Policy and the Terms of Service.

Next: Coder.