Skip to content
OIOXO
Account

Privacy by design

Most AI IDEs upload your code to do their work. OIOXO doesn’t need to — the model runs in your browser. Here is exactly what stays on your device and what doesn’t.

Stays on your device — always

  • Your code and files. Projects live in your browser or your local folder. Opening a folder happens right in the browser; nothing is uploaded.
  • Your prompts. They go to the model running on your own computer.
  • Your API keys. Your keys and GitHub tokens are saved in your browser, on your machine. OIOXO’s servers never receive them.
  • Rules, memory, skills, settings, snapshots. All local.
  • Share codes. “Share” packs your whole project into the share code itself — it’s your files compressed and encoded in your browser. No upload, no server, no peer connection: the code is the project, so sharing one touches nothing of ours.

Goes directly to a third party — only when you use that feature

  • Your own key: your browser calls your chosen provider (OpenAI, Anthropic, …) directly. OIOXO does not route it through its own servers.
  • GitHub: opening a repo or pushing a commit talks to GitHub’s API from your browser, with your token.
  • Publish: publishing puts the site you chose to publish on GitHub Pages.

Touches OIOXO’s servers

  • Account: your email and login if you create an account.
  • Usage count: just numbers — how much the AI wrote — to keep the free allowance fair across your devices. Never the content of what it wrote.
  • Billing: handled by Stripe; OIOXO doesn’t store card numbers.
  • Getting the model: the one-time model download, and a quick version check so the “Refresh to update” banner can appear.
Check it yourself

Open OIOXO Doctor (tools menu → “Run health check”). The footer line is the policy in one sentence: “Everything runs on your device. Nothing here is uploaded.” And your browser’s network tab will confirm it.

The legal version of this page is the Privacy policy.