Eidos

Security

Eidos is built so that there is little to attack from outside: a local project never leaves your computer, and Eidos online holds a project only once you turn on sync. Here is how both work, and how to tell us when something is wrong.

Last updated October 30, 2026

Report a vulnerability

If you find a security problem in the CLI, the desktop app, eidosmd.com, or Eidos online, send it with Send Feedback, under Help in the desktop app, or with eidos feedback --kind bug. Start the description with the word “Security”, say what you found and how to reproduce it, and include your email, since feedback has no reply channel. You can also write to The Virtual Panda at 800 N King Street, Suite 304 #2638, Wilmington, DE 19801, United States.

Please give us a chance to fix it before you tell anyone else, and do not test against other people’s computers or data.

Local first

A project you do not sync is a folder of markdown and YAML files on your disk, and that folder is the only place your work is kept: there is no copy of it anywhere of ours. The desktop app runs the same code as the CLI, and the page you see is served from your own computer, on an address only your computer can reach (127.0.0.1), not from the internet.

Nothing you write in it is uploaded. The only requests the software makes to eidosmd.com are the ones the Privacy page lists, and none of them carries your work.

Eidos online

A project you sync is also kept on Eidos online’s service, on Cloudflare, so its members can reach it. What the service keeps, and who else handles it, is on the Privacy page.

  • Signing in is an emailed code that works once, for ten minutes, or Apple, Google, or an optional password of at least 10 characters, refused when it is among known breached ones. Two-step sign-in, with an authenticator app and 10 backup codes, is asked after every way in once you turn it on.
  • Your sign-in on a device is a token kept in accounts.json in the app data folder, never in a project. Sign out removes it from that device.
  • Devices. An account is active on three devices at once, and Devices on the account site lists each one and signs it out.
  • Access. The service checks every change against its author’s access before anyone receives it, and a file in a part a member cannot read never reaches their disk.
  • Cards are taken by Stripe in its own fields. Eidos never sees a card number.
  • Eidos staff reach the service only through staff tools that need two-step sign-in and write every change to an audit log, and those tools never open a project’s files.

Keys you enter

Keys are kept in a file on your computer, readable only by your user account, never in a project, so they are never committed with your work:

  • An OpenAI key for hosted dictation is kept in transcription.yaml in the Eidos app data folder. It is used only to send a recording to OpenAI, and it is never sent back to the page, written into a project’s settings, or shown in an error or a log.
  • A Jira API token is kept by the Jira plugin in plugins/jira/credentials.json in the same app data folder.
  • Your AI agent’s sign-in belongs to the agent itself (Claude Code or Codex, for example). Eidos starts the agent you are already signed in to and does not handle the sign-in.
  • Git credentials stay with git on your machine. Eidos runs git, and git signs in to your remote the way it always does.

Where the app data folder is

On macOS, ~/Library/Application Support/eidosmd. On Windows, %APPDATA%\eidosmd. On Linux, ~/.config/eidosmd (or under $XDG_CONFIG_HOME when it is set). These files are not encrypted, so they are as safe as your user account: anyone who can sign in as you can read them.

Plugins

A community plugin from the Registry is installed with every file checked against the sha256 its listing gives, and a person reviews every version before it is listed. It runs only after a project switches it on and you allow it on your machine. Allow only plugins you trust: once allowed, a plugin runs as part of the CLI and the app, with the same access to your computer.

Signed builds

The macOS builds are signed with an Apple Developer ID and notarized by Apple. Windows builds are signed through Azure Artifact Signing. The release process refuses to build a macOS or Windows release without its signing credentials, so an unsigned one is never published. The Linux AppImage and deb are not code-signed. The app updates itself only in a packaged build, from dl.eidosmd.com.