Security
What lands on your disk, and what leaves it.
ClawMetry runs as a daemon on your own machine. This is the full account: what it writes, what it scrubs before writing, what crosses the network, and what we can reach. Measured on one reference install, not estimated.
Your session data stays on your machine unless you turn cloud on.
Cloud sync is off by default and the daemon opens no inbound ports. A default install still sends an install ping and checks PyPI for updates: DO_NOT_TRACK=1 stops the ping and CLAWMETRY_OFFLINE=1 stops both. With cloud on, session content reaches us as ciphertext we cannot open, alongside operational metadata we can read.
What the daemon puts on your disk
One reference install: 165 sessions, 19,977 events. Measured on that machine, not estimated.
Footprint
CLAWMETRY_OFFLINE=1noneclawmetry uninstallThe query server binds to loopback only, with a one-time 32-hex token and a discovery file at mode 0600. It is why the dashboard can read the store without holding the writer lock.
Cloud sync off is not offline. A default install still sends an install ping (a random install id, version, OS, Python version, detected agent and CI flag) and checks PyPI for updates. DO_NOT_TRACK=1 stops the ping; CLAWMETRY_OFFLINE=1 stops every discretionary request. The full list is the network egress inventory.
What leaves, exactly
With cloud sync off, these stay in the local file.
The key is created on the node and our servers keep no copy. Your browser and any paired device receive it so they can decrypt; if you rotate a key from the web dashboard, the new key passes through our servers to reach the node. Compelled by a subpoena, we hand over sealed blobs we cannot open, plus the readable metadata: hostname, session ids, runtime and model names, token and cost totals, tool names.
Three things we would rather you heard from us
Every product has edges. These are ours, written out before you install anything.
The local file is not encrypted
Session content is sealed in transit and at rest in our cloud. On your own disk the store is a plain DuckDB file with your normal permissions, so anything already running as you can read it, the same as your shell history.
We scrub credentials, not personal data
API keys, tokens, passwords and private keys are replaced with a fingerprint before anything is written to disk. It matches credential shapes, so it will not catch names or customer records. If the scrubber itself hits a bug we keep the event rather than lose it. With cloud sync off, none of it is uploaded.
Cloud on means your nodes are reachable
Turn cloud on and Stop, Pause and Resume reach any node on the account, from the dashboard or the desk device. That is the feature. Stay local-only and that channel does not exist.
You do not have to take our word for any of it
The daemon, the scrubber and the enforcement path are open source. The redaction rules are one readable file, clawmetry/redaction.py, and you can switch them off with CLAWMETRY_REDACT=0 if you would rather capture raw. Run clawmetry uninstall and the store and the daemon are gone.
For a security review, start at the trust hub: data flow for each deployment mode, the egress inventory, how to verify a release, how to report a vulnerability, live status, and the compliance status, which says plainly that we hold no certification yet. Our disclosure policy is in SECURITY.md, and the contact is also published as security.txt. Which OWASP, MITRE ATLAS and NIST AI RMF items our controls map to, with their limits and the gaps, is on the framework coverage page.