RubyWhisper

Privacy

RubyWhisper privacy.

RubyWhisper is built around transient dictation processing and metadata-only account records. This page describes the current beta product behavior, not a formal compliance certification.

Dictation content is not kept server-side.

RubyWhisper servers do not store audio, raw transcripts, cleaned text, clipboard content, app context, prompts, provider payloads, or local Recent Wisprs. The server contract is metadata-only for account, usage, request, billing, support, and admin operations.

Read beta terms

Transient processing

Audio and text pass through only to complete a request.

When you dictate, the Mac sends recorded audio to the RubyWhisper backend. The backend authenticates the account, checks Terms/Privacy acceptance, plan, quota, rate limits, and duration, then sends the needed request content to transcription and cleanup providers. The final text is returned to the Mac, and RubyWhisper does not persist the audio, transcript, cleanup prompt, provider payload, or final text as a server record.

Local Recent Wisprs

Recent Wisprs stay on your Mac.

Recent Wisprs are local recovery history for successful or failed insertions. They may include final cleaned text on the Mac, expire after 7 days by default, and can be disabled or cleared in local app settings. RubyWhisper web, support, and admin surfaces do not upload, display, or store local Recent Wisprs.

Persisted metadata

Account, usage, and billing records are metadata.

RubyWhisper stores only the metadata needed to run the beta: account identity, Terms/Privacy acceptance, plan state, aggregate usage counters, billing cache state, request IDs, timestamps, provider names, duration, word counts, latency, status, and safe error codes. Word counts are aggregate usage metadata and must not reveal the underlying dictation content.

Open account

Support and admin

Support should not need private dictation.

Beta support can help with account, billing, download, plan, request ID, and safe error-code questions. Support and admin operations should never see transcript, audio, clipboard, prompt, app context, dictionary, provider request, provider response, or Recent Wisprs content. Do not include private dictation content in support email.

Email support

What may be stored

Metadata that keeps the beta running.

  • Account profile metadata such as Clerk user ID, email, Terms/Privacy acceptance timestamp, and account status.
  • Aggregate usage counters such as trial words used, lifetime words used, monthly words used, monthly period start, and update timestamps.
  • Stripe billing metadata and cache state such as customer, subscription, plan, status, renewal, and webhook idempotency fields needed for account and billing decisions.
  • Request and error metadata such as request IDs, provider names, duration, word count, latency, app version, OS version, status, and safe error codes.

What is not stored

Private dictation content is excluded.

  • Audio payloads, audio files, or recording contents.
  • Raw transcripts, cleaned text, cleanup prompts, provider request bodies, or provider response bodies.
  • Clipboard content, surrounding app context, screenshots, personal dictionary terms, or local Recent Wisprs.
  • Private env values, auth tokens, magic links, card numbers, or secrets.