braids collects nothing, sends nothing, and stores nothing anywhere but your own machine. What follows is that, said precisely.
braids reads the transcripts Claude Code has already written under
~/.claude, and writes an index of them to
~/.braids. Both stay on your computer. Nothing is uploaded,
and there is nobody to upload it to: braids has no account, no server and no
backend.
It makes no network calls. The binary contains no HTTP client and opens no connections. You do not have to take that on trust:
go list -deps ./cmd/braids | grep net/http # no output
It never talks to a language model. braids arranges conversations you have with one; it does not have one of its own, and it needs no API key.
Two things do use the network, both started by you and neither by braids.
The installer at braids.chat/install.sh downloads a release from
GitHub when you run it. And the map can offer to run that installer again
when a build is old, which it decides by reading the binary's own
modification time rather than by asking anything.
braids.chat is static files on GitHub Pages. There is no analytics script, no tag manager, no cookie, no font fetched from anywhere else and no content delivery network. Nothing on these pages tries to identify you.
GitHub serves the files and keeps its own server logs, which is outside our control and covered by GitHub's privacy statement.
The plugin carries a skill and a set of hooks. The hooks run
braids hook on your machine, which appends a line to
~/.braids/events.jsonl recording that a session stopped or asked
you something: the event name, the session id, the tool name and the working
directory. No prompt, no response, no code and no tool output is recorded.
The file never leaves your computer, and braids hooks --remove
stops it being written.
Nothing. There is no telemetry, no crash reporting, no usage counting and no opt-out to offer, because there is nothing to opt out of. If that ever changes it will be opt-in, announced in the release notes, and this page will say so before it ships.
braids hooks --remove # stop sessions reporting braids skill --remove # take the skill back out rm -rf ~/.braids # the index and its sidecar files rm "$(command -v braids)" # the binary
Your transcripts under ~/.claude are Claude Code's, not braids',
and removing braids leaves them exactly as they were. braids has only ever
read them.
ashes4799@gmail.com, or open an issue. For anything security related, see SECURITY.md.
Last updated 11 September 2026.