Where your data lives

State is local

Runs, per-case scores and traces, assets, portfolios, and gaps live in a single SQLite file: kno.db in the working directory (--db to override). There is no hosted service, no ~/.kno global state, no account.

Traces are customer data

Stored traces include the agent’s output, which is conversation content if your evals come from production logs. Kno treats that with the same discipline as any customer data:

• No trace content in log lines above DEBUG; none ever goes into telemetry.
• Nothing expires on its own, and nothing is deleted without you.
• kno purge removes trace content, keeps scores and costs, and never deletes a row, a purged run stays resumable.

What leaves your machine

Your cases go to the provider you point Kno at, and that provider’s retention is theirs. Kno itself sends nothing anywhere, there is no telemetry of content, ever. OTel span export is planned for a later version; today --trace-spans writes content-free spans to stderr only.

Why the design is what it is

An eval tool that phones home would be unusable on real agent data, so “nothing leaves” is a hard requirement, not a feature flag. The full retention semantics: the retention recipe.