# Telemetry
Version: 1.1.1
Last Updated: January 23, 2026
Audience: Backend, app, extension engineers; governance reviewers
Scope
- What BranchPy collects (events, metrics, usage counts) and what it explicitly does not collect (no content, no auto-send without consent).
- Where telemetry is emitted (CLI, daemon, extension) and how it flows to storage.
- Control modes (Off, Manual, Auto) and export/upload behaviors.
- High-level privacy posture and links to governance/policy references.
Components
- Emitters: BranchPyApp CLI/daemon, VS Code extension, cache decorators.
- Local Storage: JSONL logs under user profile (
~/.branchpy/telemetry/, VS Code globalStorage). - Package Builder: Aggregates/sanitizes events (
TelemetryPackage, v1.0.0 schema). - Upload/Export: Manual and auto upload via CLI; RC export-first flow supported.
- Ingestion API: rc-backend
/api/telemetry/*endpoints (dashboard/API key auth). - Storage Sinks: SQLite (local), MySQL (production), Composite sink.
See Also
- architecture.md
- ingestion.md
- privacy.md
- configuration.md
- troubleshooting.md
- quick-reference.md
- api.md
- API index: Technical/api/api.md
- Event schemas: Technical/events/catalog.md
- Logging: Technical/logging/README.md