Pulse Insights & Service Diagnostics
Last updated · August 27, 2026
Pulse is local-first. This page explains the small, separate set of operational and optional product signals that may reach Pulse Cloud — and the content that never does.
01Current status
Pulse Insights is not enabled today. Before it is enabled, the desktop app will show this policy, ask for an explicit choice, and provide a way to change that choice in Settings.
02Two separate streams
| Stream | Purpose and choice |
|---|---|
| Required service diagnostics | Minimal reliability, security and capacity signals needed to operate Pulse Cloud. They are part of the service, not a market-research programme. |
| Pulse Insights | Optional, consent-based aggregate product research. Declining does not remove access to Pulse or its local workspace. |
03Required service diagnostics
Where you use Pulse Cloud, we may process the app version, operating-system version band, registered-device state, account-session and backup-operation result, and a predefined failure code. This helps us detect an outage, protect accounts, understand capacity, and fix a broken release.
We do not accept raw logs, exception text, stack traces, local paths, request bodies, authentication tokens, API keys, prompts or workspace content in this stream.
04Optional Pulse Insights
If you allow Pulse Insights, the app prepares a daily, privacy-minimised summary on your device. The initial catalogue is limited to counts and ranges for pull requests and reviews, review-time bands, AI provider family, rounded AI token totals, feature sessions, and local four-hour activity blocks.
We use these summaries to understand product adoption, reliability and broad workflow patterns, and to prepare aggregate benchmarks. We do not use them for advertising, individual profiling, credit decisions, or to sell personal data.
The app sends no repository name or identifier, organisation, URL, pull-request number, branch, code, diff, commit message, review text, prompt, completion, credential or API token to Pulse Insights.
05Aggregation, access and retention
- The Cloud records daily aggregate counters, not a stored event timeline for each person or repository.
- A short-lived delivery marker may be kept for up to 30 days to prevent duplicated or abusive submissions. It is separate from the aggregate dataset and is not used for reporting.
- Aggregate rollups are retained for up to 24 months.
- Reports suppress groups smaller than 100 accounts. They cannot drill down to a person, device, company or repository.
- Only narrowly scoped Pulse Cloud services may write these records. The desktop app has no database password and no direct access to analytics tables.
06Your choice
Pulse Insights starts off. You can allow or decline it from the in-app notice, and change the choice later in Settings > Privacy. Revoking it stops future optional submissions and clears any optional summary still waiting on your device. Required service diagnostics remain limited to the operational purpose described above.
Questions about this document
Write to mussicorp@gmail.com and you will get an answer from the person who wrote both the document and the app.