Pragma Privacy & Telemetry
This page explains what Pragma may collect when you use the desktop app, why that data exists, and what you can control in Settings → Privacy.
What This Page Covers
- Crash reports and diagnostics
- Product usage / telemetry signals
- AI-related context handling at a high level
- What stays local vs what may be sent to CredVault services
Crash Reports
Crash reports help CredVault find and fix desktop crashes. They typically include:
- App version and OS information
- Stack traces and error codes
- Limited environment details needed to reproduce the crash
Crash reports are meant for reliability, not for reading your project files.
Telemetry / Product Usage
Telemetry helps CredVault understand which features are used and where the product fails for users. Examples:
- Feature toggles and settings categories in use
- High-level performance or error counts
- Session health signals (not your source code by default)
Telemetry should never be treated as a license to browse private repositories. Sensitive content belongs in secrets, local files, and privacy controls you choose.
AI Features And Privacy
When you use Comp / the Pragma AI agent:
- The agent uses the workspace context you allow (open files, selected context, configured tools).
- You should review AI settings, rules, and codebase context controls before sharing sensitive repos.
- Secrets should be stored in Pragma Secrets / environment variables, not pasted into prompts when avoidable.
See also:
Controls In Settings
In Settings → Privacy you can typically:
- Review data-related preferences
- Manage crash reporting choices where available
- Open this documentation for a clearer explanation of data use
What CredVault Asks You To Know
- Privacy settings exist so you can make informed choices.
- Diagnostics exist to keep Pragma reliable.
- AI features only help when they have enough context — share only what you intend.
- Questions about privacy can go to support@credvault.net.