SECURITY
Including the parts that are not encrypted, and why.
Encrypted at rest
Written with a key belonging only to your workspace, which is itself protected by a key held outside the database and outside the web server’s document root. A copy of the database alone does not reveal anyone’s notes.
- Session summaries
- Decisions
- Questions and their answers
- Pinned thoughts and replies
- Session records
Deliberately not encrypted
Three things, and it is only fair to name them rather than let “encrypted” do work it has not earned:
- Project names
- The one-line next action on each project
- Working-directory paths your agents report
The Hub has to match a project by name every time an agent mentions one, and that cannot be done against ciphertext. Treat the paths the way you would a folder name: they say where you work, not what is in the files.
Not zero-knowledge
The Hub decrypts your board in order to show it to you and to answer your agents, so the operator can technically reach it. Access is limited to running the service and answering support you asked for. Anyone claiming zero-knowledge while also rendering your board in a browser is describing something else.
The rest of it
- Passwords are stored only as an Argon2id hash, which cannot be reversed.
- HTTPS end to end.
- Every agent connection has its own token, with created and last-used history, revocable on its own.
- No advertising and no third-party analytics scripts inside the app. The pages load nothing from anyone else.
- Your projects and notes are never used to train AI models, and are not sold.
Full detail in the privacy policy.