Privacy
Privacy & Database
Learn how CacheLane handles telemetry, config structures, and local databases.
Local-First Guarantee
CacheLane is designed to be fully local-first. We do not run hosted SaaS backend APIs, cloud databases, or external tracking servers. All telemetry, logs, and database metrics are kept entirely on your machine.
Data Paths
CacheLane stores its state and logs in the following directories on your system:
- Local Config:
~/.cachelane/config.json(pruning variables, ignore files, telemetry choices). - SQLite Log:
~/.cachelane/cachelane.db(turn cost statistics, block IDs, reference hashes, and stats). - Logs:
~/.cachelane/logs/*.log(daily rotated structured logs with a 7-day retention limit).
What is Stored in the SQLite Database?
To execute K-pruning and compile metrics for the stats panel, CacheLane stores block metadata. **It never stores the actual prompt text, file contents, assistant responses, or API keys.**
Stored columns include:
- Unique block IDs and content hashes.
- Block type classification (e.g. system, user query, tool schema).
- Billed token count estimates from Anthropic responses.
- Volatility designations and reference counts.
Telemetry Settings
Anonymous telemetry is **disabled by default**. Payloads only compile aggregated cache hits and baseline metrics. They never contain file names, content blocks, workspace keys, or session identifiers.