Privacy

1. What runs locally

Microphone audio. Captured only while you hold the talk button, and torn down on release. It is transcribed on-device by a bundled Whisper base.en model. The raw audio is not stored and is not sent anywhere.

Speech synthesis. Spoken output is generated on-device by a bundled Kokoro 82M voice model. No cloud voice service is used.

Model weights. The voice and transcription models ship inside the app and load from disk. The app is explicitly forbidden from downloading models at runtime (allowRemoteModels = false), so voice works fully offline.

2. What is sent to Anthropic

Codeio does not run its own AI backend. It drives Claude Code through the Anthropic Claude Agent SDK, which runs the claude process using your existing Claude Code login. Codeio never asks for an API key and never handles model billing.

When you send a message or run a turn, these are transmitted to Anthropic:

• Your prompts and messages.
• The contents of files the agent reads, and the code it is asked to work with.
• Commands the agent runs and their output, and other tool inputs and results.
• Conversation and session identifiers used to resume context.

This data is handled by Anthropic under Anthropic’s own privacy policy and the terms of your Claude account. Codeio is not a party to, and does not control, that processing. If you do not want a piece of code or information sent to Anthropic, do not include it in a turn.

3. What is stored on your device

Codeio persists your work in a SQLite database in the operating system’s per-user application-data directory (userData/codeio.db). That includes projects, conversations, turns and messages — including your prompts and the full text transcripts of the agent’s responses — plus file paths and tool metadata, the speech timeline and cues, and your settings.

This database is stored unencrypted and is only as protected as your user account and your disk. Codeio does not copy it off the device. You can delete your data by removing conversations in the app, or by deleting codeio.db from the app’s data directory. Uninstalling does not delete it for you.

4. Network activity

• At build time, the model weights are downloaded once — by the packaging step, not by anyone running a packaged build.
• At runtime, the outbound activity started on your behalf is: the Agent SDK talking to Anthropic to run a turn; any network access the agent performs because you asked it to; and crash reports, if they are enabled.
• The app sends no usage analytics and no behavioural telemetry in this version. (The website is measured separately — §6.)

5. Crash and error reporting

To find and fix bugs during the beta, Codeio reports crashes and unhandled errors via Sentry. Reports are faults only: a stack trace, the app version, your operating system and architecture, and whether the fault was in the main or renderer process.

Never your prompts, code, file contents, conversation transcripts or microphone audio. Personally-identifying data is explicitly disabled (sendDefaultPii: false) and request and user fields are stripped before any report is sent.

It is on by default — a crash nobody hears about cannot be fixed — and one toggle away from off, in Settings → About → Crash & error reporting. With it off, or in a build with no reporting endpoint configured, errors are written only to a local log file (userData/logs/errors.log) and are never uploaded. Native crash minidumps are likewise collected locally and only uploaded when reporting is on.

6. Analytics

In the app, there is none in this beta. If analytics are ever added they will be opt-in — off by default, with a toggle in Settings — and content-free: event counts and error categories only, never your code, prompts or transcripts.

This website is a different thing, and it is measured. The pages on codeio.dev use Google Analytics 4 to count visits, so we know which parts of the site are worth keeping. It records the usual web measurements — pages viewed, approximate location derived from your IP address, referrer, device and browser — and sets cookies in your browser to recognise a repeat visit. That data is processed by Google under Google’s privacy policy.

It applies to the website only. Nothing about it reaches the app: the two share no identifier, and installing Codeio does not carry any of this with it. Browser tracking protection, an ad blocker, or a Do Not Track extension will all stop it, and the site works exactly the same with it blocked.

7. Children

Codeio is a developer tool and is not directed to children under 13, or the equivalent minimum age in your jurisdiction.

8. Changes

This policy will be updated as the product evolves. Material changes are reflected in the version and date at the top. Continued use after an update means you accept the revised policy.

9. Contact

Questions about privacy: privacy@codeio.dev