privacy

Privacy Policy

The short version. We do not collect your personal data. There is no server to collect it, no account to make, and no telemetry to send. Below is exactly what that means, and where the exceptions are.

Effective 2026-09-04 · last revised 2026-09-04

1. At a glance

Whatcodeme
Accounts · sign-inno
Usage statistics · telemetry · analyticsno
Automatic crash reportsno
Uploading code or files to a serverno
Advertising · tracking cookiesno
Sharing personal data with third partiesno
Calls to the repository and issue-tracker APIs you gave a token foryes — only when you turn it on

2. What is not collected

The codeme desktop app collects and transmits no personal data — no name, email, device identifier, IP address or usage pattern. There is no analytics SDK inside it, no crash reporter, and no "send anonymous usage statistics" option. That option is missing not because it defaults to off, but because there is nowhere for it to send anything.

3. What stays on the machine

For the app to work it has to remember state, and all of that state lives only on your disk.

  • The settings file — theme, sidebar layout, key scheme, and the addresses of the repositories and issue trackers you registered
  • The paths of the projects and worktrees you have open, and the recent list
  • Session state such as tabs, layout and window size
  • The agent sessions' local records (whatever the agent CLI leaves on that machine)

Delete these files and that is the end of them. There is no copy anywhere.

4. Repository and issue-tracker tokens

To use the My work panel you paste a personal access token for GitHub, Forgejo or Jira once. That token is handled like this.

  • It is kept in the OS credential store — the keychain, on macOS.
  • The settings file keeps only the address. The token value is never written to it.
  • No IPC command hands a token back to the window (the webview). The token stays on the shell side.
  • The token is sent only to the repository or issue-tracker API you pointed at. It is never sent to us — there is no server to receive it.
  • Disconnect in the panel and it is deleted from the credential store.

5. Where anything goes out

The app uses the network on its own only in these cases.

  • The repository and issue-tracker APIs you registered — to read tickets and pull requests. If you enter no token, the call is never made at all.
  • Reading AI usage — your agent's plan limit is not written down on this machine, so the app asks somewhere that knows it. If that fails it falls back to a local estimate, and says so.
  • git remote operations — fetch, pull and push go out when you ask for them, to whatever remote your git configuration points at.

Beyond that, there is no network call on the app's critical path. With the internet unplugged, editing files, the terminal, worktrees and commits all keep working.

6. AI agents

This is the most important item here. The AI agent CLIs codeme runs are third-party software. The prompts you give an agent, and the code that agent reads, may be transmitted to that provider's servers. That transmission and its handling are decided entirely by that provider's policy; codeme neither takes part in that flow nor can see or stop it.

When you work on sensitive code, read the privacy policy and data-retention policy of the agent provider you use for yourself. That codeme is "local-first" does not make that agent local.

7. This website

  • This site has no analytics script and no advertising or tracking cookies.
  • Nothing is stored in your browser. No cookie and no localStorage value — the site's appearance is fixed, so there is no setting to remember.
  • No external font and no external script is loaded.
  • The server this site is hosted on (a static hosting provider) may keep ordinary access logs. We do not analyse those logs or combine them with anything else.

8. Your rights

Under the Personal Information Protection Act you have the right to access, correct and delete your personal data, and to have its processing suspended. But we hold no personal data of yours, so in practice there is nothing to make that request against. The settings and tokens left on your machine you can delete yourself, and the guide says how.

Rights over information held by a repository, an issue tracker or an agent provider have to be exercised against that provider.

9. Children's personal data

This Service is aimed at developers and is not directed at children under 14. Since no personal data is collected, none is collected from children either.

10. Revisions

When this policy is revised, the revision date on this page is updated. A change that adds anything to what is collected is announced in the release notes as well.

11. Contact

For questions about the handling of personal data, tell the distributor through wherever you got the build. Anything you would rather not make public, such as a security vulnerability, can go the same route separately.