Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.hyprcore.ai/llms.txt

Use this file to discover all available pages before exploring further.

Hyprcore collects a small amount of error and usage telemetry to help us spot bugs and prioritize fixes. You control how much.

​
Three modes

Settings → Advanced → Telemetry has three options:
ModeWhat’s sent
OffNothing. No errors, no logs, no usage events. Hyprcore never contacts our telemetry servers.
Errors only (default)Crashes and explicit error events with redacted context. No feature usage data.
FullEverything in Errors only, plus debug logs and feature usage events (e.g., “user started a meeting”, “model load took 2.3s”).
Default is Errors only.

​
What’s collected

In Errors-only and Full modes:
  • Crash stack traces. When Hyprcore crashes, we get a redacted stack trace via Sentry.
  • Explicit error events. Things like “model failed to load”, “audio device disconnected”, “sync request failed”.
  • Device shape. OS version, CPU architecture, GPU availability, app version. Used to spot platform-specific bugs.
In Full mode, additionally:
  • Feature usage events. Aggregate counts of dictation runs, meeting starts, sync syncs. No content.
  • Performance timings. Model load duration, transcription duration. Helps us spot regressions.
  • Logs. App-level debug logs, redacted of any user content.

​
What’s never collected

In any mode, including Full:
  • Audio. Hyprcore never sends a single byte of audio to telemetry.
  • Transcripts, notes, or any user content. Not the words you said, not the things you wrote.
  • API keys, passwords, credentials. Stored in macOS Keychain, never logged.
  • File paths to user content. Logged paths are redacted to filenames only.
  • Personal identifiers. No name, no email, no IP address (Sentry strips IPs).
If you sign in, your account email is associated with your Hyprcore Cloud usage—but that’s a separate system from telemetry, and it’s only there because we have to bill you.

​
How redaction works

Before any error event leaves your Mac, it passes through telemetry/redact.rs in the Rust backend. The redactor:
  • Replaces user-content paths with their filename.
  • Strips API keys matching common patterns.
  • Strips email addresses.
  • Strips home directory paths.
Redaction runs before any payload leaves your Mac.

​
Where it goes

  • Errors: Sentry (sentry.io). Encrypted in transit, retained 90 days.
  • Logs (Full mode only): Axiom (axiom.co). Encrypted in transit, retained 30 days.
Both services are GDPR-compliant. We don’t share telemetry data with third parties.

​
Turn it off

Settings → Advanced → Telemetry → Off. When set to Off, the telemetry code paths are skipped entirely—no network requests, no buffered events. You can verify this with Little Snitch or any network-monitoring tool.

​
Frontend errors

Errors that originate in Hyprcore’s React UI (rendering bugs, broken state) flow back to the Rust backend via the report_frontend_error Tauri command, then through the same redactor and the same telemetry path. They respect the same Off / Errors-only / Full setting.