Data and network

spekterm has no account, no telemetry, and no update check. This page lists every connection it makes itself, and the programs it starts that make connections of their own.

What spekterm itself connects to

Slack — only after you save Slack credentials in the inbox, and only to Slack’s API (or the endpoint you set there; the dialog warns that your credentials are sent to it). Without credentials, the Slack part of spekterm does nothing. See Inbox and Slack.
Remote images in rendered markdown — markdown that spekterm renders (files you open, OpenSpec artifacts in the side panel, the conversation view) may contain https: images, and they are loaded from where they point. Plain http: images are not loaded.
Links you open — a link you click is handed to your web browser; spekterm does not load it.

Nothing else. In particular, spekterm turns off the spell checker built into its browser engine, which would otherwise download a dictionary from a third-party server at startup.

Programs spekterm starts, which connect on their own

spekterm runs programs you installed. What they send is up to them, and spekterm’s own checks cannot observe what these programs do:

claude (Claude Code) — every agent session runs the real claude CLI with your own login, and it talks to Anthropic’s service. The conversation report (“Reading”) also runs your claude, and only when you ask for one; it shows exactly what will be sent and asks you first.
openspec — the side panel runs the OpenSpec CLI to read your changes. The OpenSpec CLI sends anonymous usage statistics unless you turn them off. To turn them off in a way that works however spekterm is started, run:
Terminal window
```
openspec config set telemetry.enabled false
```
The environment variables OPENSPEC_TELEMETRY=0 and DO_NOT_TRACK=1 also work, but only if they are in the environment spekterm itself was started with. A value set in .zshrc does not reach openspec when you start spekterm from the desktop menu: spekterm reads your login shell’s environment once at startup, gives it to the terminals it opens, and takes only PATH from it for its own process.
Your login shell — runs once when spekterm starts, to read your environment (for example PATH). Whatever your shell configuration does at login happens then.

Where your data is stored

Everything spekterm keeps is on your machine, under ~/.config/Spekterm:

your workspace (the folder list, the order, what is pinned) and the side panel’s position per folder;
your sessions, and the last screen of each shell session so it can be replayed after a restart;
your preferences;
the inbox and handoff files;
a copy of your Claude Code conversations for the conversation numbers and readings, and the readings you generated;
your Slack credentials, in their own file that only your user account can read or write. The file is not encrypted; anyone who can read your files as you can read it.

spekterm also reads Claude Code’s own transcripts under ~/.claude/projects to show the conversation view. It never writes there.