RubyWhisper

Beta support

RubyWhisper support.

Email beta support for account, billing, download, plan, and app workflow questions. Keep support requests metadata-only by default.

Email beta support without private content.

Use the support email path for beta help. Include metadata that lets RubyWhisper identify the account, plan state, request, app version, operating system, and rough step that failed without exposing what you dictated.

Email support

What helps

Metadata is usually enough.

Support can investigate many beta issues from account and request metadata. Useful details include account email, plan state, error code, request ID, app version, OS version, and rough workflow context.

What to keep out

Do not include private dictation by default.

Do not include dictation content, audio files, transcripts, clipboard contents, prompts, provider payloads, or screenshots with private text in support requests.

Account checks

Start with your account and plan state.

The account page shows signed-in account state, Terms/Privacy acceptance, trial and paid plan metadata, billing entry points, and download readiness without displaying dictation content.

Open account

Mac beta

Check the download and pricing pages.

Download and pricing routes describe current Mac beta artifact availability, trial words, paid beta plans, and launch limits before you write in.

Open download

Include

Safe troubleshooting details.

  • Account email or the email you used to sign in.
  • Plan state, such as trial, monthly, annual, paid active, or payment failed.
  • Safe error code and request ID shown by the app or account surface.
  • RubyWhisper app version and macOS version.
  • A rough workflow description, such as the app you were typing into and what step failed.

Do not include by default

Private content is not needed for most support.

  • Private dictation text, raw transcripts, cleaned text, or local Recent Wisprs.
  • Audio files, recording contents, or exported audio.
  • Clipboard contents, surrounding app context, prompts, or personal dictionary terms.
  • Provider request payloads, provider response payloads, auth tokens, or secrets.
  • Screenshots that show private text.