What Orstrum stores
Two folders, two network calls, no telemetry. This page is the complete list.
In the project: .orstrum/
| File | What |
|---|---|
.gitignore | Contains *, so the folder stays out of your repository without touching your own .gitignore. |
events.db | SQLite. One row per hook event: tool names, file paths, exit codes, error strings, token counts, timestamps. Never file contents. |
spec.md, rules.md, policy.json | Written by /orstrum:orstrum start, with the agent's own file tools. Yours to edit. |
handoff.json, handoff.md | The latest handoff (Pro). |
shadow/ | A bare git repository holding checkpoints of your project files (Pro). Excludes .git, node_modules/ and whatever your .gitignore excludes. |
In your home folder: ~/.orstrum/
| File | What |
|---|---|
usage.db | Usage samples: the percentages the endpoint returned, with timestamps. |
license.json | Your Pro key, tier, and the time of the last successful check (Pro). |
statusline* | The status-line flag and scripts. |
hook.log | Errors swallowed by the fail-open hooks. |
Nothing is written anywhere else. If a feature ever needed to, it would be a bug.
Network
| Call | From | Carries |
|---|---|---|
Claude Code's usage endpoint at api.anthropic.com | The hook, at session start and at most once every two minutes at turn end | The OAuth token Claude Code already stores, read from its credentials file (or the macOS Keychain). Never refreshed, never written, never sent anywhere else. |
www.orstrum.com/api/license | The MCP server, once per session (Pro) | Your key. Nothing else. |
That is the whole list. There is no crash reporting, no usage analytics, no update check.
The account
The dashboard stores your email, your workspace, your subscription state from Stripe, and the hashes of your keys. It never receives anything from a session. See the privacy policy.