Privacy Policy

Data We Collect

Hey Stentor collects account, update notification, billing entitlement, and support information needed to operate the beta. Update notification submissions may include email address, requested update interests, primary use case, optional notes, locale, source page, email-confirmation state, and bot-check verification metadata. Billing payments are processed by Paddle; Hey Stentor stores subscription identifiers and entitlement state, not raw payment card details.

Desktop and Local Data

Voice provider keys, local assistant settings, Hermes webhook subscription secrets, local logs, and local conversation data should remain on the user's device unless the user explicitly opts in to sharing diagnostics or support material.

When Hermes is installed locally, Hey Stentor may read the local Hermes webhook subscription file to sync the request secret and reply secret used for loopback HMAC verification. These secrets are used to sign requests sent to Hermes and verify replies sent back to the local callback server. They are not payment credentials and are not intended to be uploaded to Hey Stentor servers.

Voice Processing

Voice capture, transcription, text-to-speech, and assistant replies may involve the providers the user configures locally, such as OpenAI, Deepgram, Cartesia, ElevenLabs, or Hermes. Provider API keys and model choices are controlled by the user's local settings or Managed Plan configuration, and provider use is subject to the relevant provider terms and privacy practices.

Diagnostics

Diagnostic upload is intended to be opt-in. Redaction must remove API keys, auth tokens, webhook secrets, HMAC signatures, and raw payment identifiers before logs are used for support.

Optional Product Analytics

Desktop product analytics are planned as an opt-in setting only. If enabled, Hey Stentor may collect product-flow events such as app launch, permission state, provider selection, Speak start or failure, transcription completion without transcript text, Hermes connection tests, update checks, and update install outcomes.

Product analytics must not include raw audio, transcripts, assistant replies, Hermes payloads, provider API keys, auth tokens, HMAC signatures, webhook secrets, payment identifiers, or local file paths.

Your Choices

Users can request account, update notification, billing-support, and diagnostic data review or deletion by contacting support. Some billing records may be retained as required for accounting, fraud prevention, and legal obligations.