Data privacy & safety when reading local sessions #62
-
|
Hi, I’m interested in using CodeBurn and had a question about data safety. Since the tool reads local session data from providers like Claude, Codex, Cursor, etc., I wanted to clarify a few things: Does CodeBurn send any data externally (e.g., telemetry, analytics, or API calls)? Some of my projects contain sensitive credentials, so I want to make sure I fully understand how data is handled before using the tool. Thanks in advance for the clarification! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
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:
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:
It does not touch 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! |
Beta Was this translation helpful? Give feedback.
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:
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: