There is nothing to opt out of
FigyTerm has no analytics pipeline, no crash reporter, no account system and no server of its own. This page exists to say exactly that, and to be specific about where each thing you make actually lives.
No telemetry, no analytics
Nothing measures you. There is no event pipeline to opt out of, because there is no event pipeline.
No account, ever
Nothing to sign up for and nothing to sign in to. The app has no concept of a user.
Offline by design
Completions, indexes, history and collections are computed and stored locally. The one request the app makes on its own is an update check.
Auditable
MIT licensed, with the design notes for every major panel committed alongside the code.
The one request the app makes
FigyTerm checks GitHub Releases for a new version. That is a request to GitHub for a public file, carrying nothing about you beyond what any HTTP request carries — and it is the only network call the app initiates on its own. Everything else that leaves your machine leaves because you asked it to: a URL you opened in the browser panel, a request you fired from the API client, a git push you ran.
| What | Where it lives |
|---|---|
| Commands and shell history | Your shell's own history file, read by FigyTerm and never copied elsewhere. |
| Autocomplete matching | Computed in the Rust backend against specs shipped with the app. |
| Files you edit | Written straight back to your disk. Unsaved drafts are journalled locally so a crash cannot lose them. |
| API collections and request history | A SQLite file on your machine. Postgres sync is opt-in and points at a server you choose. |
| Drawings and their notes | Local storage on your machine. There is no cloud and no share link. |
| Browser panel | Its own webview storage, separate from your main browser. The sites you open are between you and them. |
| Claude Code conversations | Handled by the Claude Code CLI itself, under its own terms. FigyTerm draws the window and stores nothing. |
This website
The site you are reading is static and carries no analytics script, no advertising tag and no third-party embed. Fonts are served with the page. If that ever changes, it will change here first.
Questions about any of this belong in an issue, in public, where the answer is useful to everyone else too.