Effective: August 4, 2026. This beta privacy notice describes the current Pulse Stack product.
Activity metadata we collect
We process account details, API-key identifiers, timestamps, duration signals, supported source/provider and session identifiers, projects, task/session labels, supported file paths, languages, editors, operating systems, machines, activity states, and diagnostic delivery metadata.
Content the tracker excludes
The collector does not upload user prompts, assistant replies, encrypted reasoning, source-code contents, transcripts, full command output, or patch contents. The ingest boundary uses allowlists and redacts sensitive or unknown fields before raw diagnostic metadata is stored.
Storage and access
Activity is private to the account by default. API keys are stored as hashes after creation. Transport uses HTTPS. Diagnostic raw metadata is restricted to staff audit tooling and remains subject to the same redaction boundary.
Public reports
Reports are opt-in and use revocable links. Project and date scope controls are available. Additional safe-by-default hiding for sensitive task and file names remains a beta launch gate; do not share a report containing names you consider confidential.
Compatibility configuration
The tracker prefers ~/.pulse-stack/config.toml. It can import or fall back to ~/.wakatime.cfg without modifying the Waka-compatible file.
Questions and deletion requests
Contact the Pulse Stack operator through the project repository while dedicated privacy support is being established. Account deletion and configurable retention are not yet self-service beta features.