Hi @hardikaipm, quick answers:

1. Zero telemetry, zero analytics. No data about you or your sessions ever leaves your machine.

2. Processing is fully local. The only outbound network calls are downloads of public data:

• LiteLLM pricing JSON from the BerriAI public repo on GitHub (cached 24h locally)
• Currency exchange rates, only if you set a non-USD currency

Neither request includes any info about you or your usage. They are straight downloads.

3. Files read. CodeBurn reads session files in fixed provider paths: ~/.claude/projects/, ~/.codex/sessions/, Cursor's SQLite DB, ~/.copilot/session-state/, ~/.pi/agents/. The optimize command additionally peeks at:

• Your shell profile (for a single BASH_MAX_OUTPUT_LENGTH env check)
• CLAUDE.md files in detected project cwds
• MCP config files

It does not touch .env, credential stores, or arbitrary project source.

Honest caveat worth flagging: the session files themselves can contain whatever you pasted into Claude / Codex / Cursor, including secrets if they ended up in a prompt or tool output. CodeBurn only extracts aggregate metadata (model, token counts, tool names, bash command basenames) and never transmits content anywhere. The files stay untouched on disk.

Source is open if you want to audit: https://github.com/AgentSeal/codeburn/tree/main/src

Hope that helps!