Skip to data controls
ReadySaid
SupportTermsPrivacy
Data Controls

Know what goes where.

ReadySaid separates local speech recognition, local cleanup, optional cloud text refinement, and account synchronization. This page maps those paths and the controls attached to them.

Last updated: August 10, 2026Applies to: current Mac architecture and shared account services
On this page At a glance Dictation modes Personalization Accounts and billing Cloud refinement Your controls

This is a product transparency page, not a replacement for the Privacy Policy. Actual options can vary by platform, app edition, account entitlement, and release status.

1. At a glance

Audio stays local

Current Mac speech recognition processes microphone audio on the device. ReadySaid does not send microphone audio to its account backend or text-refinement provider.

Clean is local

Exact normalization and deterministic Clean rules run on the device without a language-model rewrite.

Cloud text is optional

Eligible Natural and Professional wording may send only protected, completed text after a separate consent and activation check.

No training by ReadySaid

ReadySaid does not use your dictation to train a ReadySaid model. OpenAI states API data is not used for model training by default.

2. Dictation and output modes

ReadySaid dictation features, information, processing location, and controls
FeatureInformationWhere it runsDefault and control
Microphone captureLive audio while you deliberately dictate; a bounded recent-audio buffer may exist temporarily in memoryYour Mac using Apple speech technologyStarts only when triggered; stops on release, stop, cancel, timeout, or failure
Exact outputRecognized textOn deviceSelected by you; applies local normalization without model-assisted rewriting
Clean outputRecognized textOn deviceSelected by you; local grammar and punctuation evidence, filler, repetition, and supported self-correction rules
Natural or Professional wordingCompleted, locally cleaned text; protected values replaced with placeholders before an eligible cloud requestLocal safeguards, then ReadySaid gateway and OpenAI when cloud refinement is enabled and availableCloud processing is separately controlled; a failed or unsafe result falls back to local text
Text deliveryCompleted transcript, bounded clipboard items, destination metadata, selection information, and the focused field’s before-and-after value for insertion verificationOn device and in the destination app you chooseUsed only for the insertion you request; not used to learn from other apps; ReadySaid refuses known secure fields and clipboard restoration is best-effort

3. Personalization and Insights

ReadySaid personalization features, contents, storage, and controls
FeatureWhat it can containStorageControl
Speech ProfileLanguage, recognition mode, vocabulary, corrections, shortcuts, output choices, and approved calibration resultsLocal Application Support storage with restrictive file permissions and backup exclusion; the profile file is not separately encrypted by ReadySaid; approved fields may sync to your accountReview, remove, disable, or reset profile entries
Voice checkShort live audio and aggregate accuracy resultAudio is processed in memory and not intentionally saved; approved result may be stored in the profileYou choose when to run it
Private InsightsDaily aggregate dictation counts, word totals, durations, delivery outcomes, and an optional typing-baseline valueLocal application storage for up to 366 daysPause future collection or delete Insights using available controls
Application preferencesAppearance, activation, language, output, privacy, and related settingsLocal preferences; selected settings may sync to the accountChange in ReadySaid settings or sign out to stop future synchronization on that installation

4. Account, sign-in, and billing services

  • ReadySaid accountSupabase processes authentication, the account identifier, email, synchronized preferences and profile, device records, consent, and feature entitlements.
  • Google, Apple, or Microsoft sign-inThe chosen provider authenticates you and may share basic identity information. ReadySaid does not receive the provider password or use sign-in to access mail, files, contacts, or calendars.
  • Company SSOThe company domain you enter may be sent to Supabase for SSO-provider discovery. A configured identity provider may then return account claims used for authentication.
  • Direct subscriptionStripe hosts payment entry and subscription management. ReadySaid receives identifiers, status, dates, plan, and entitlement information—not complete card details or security codes.
  • Apple subscriptionApple handles App Store payment information and subscription management. ReadySaid receives verified transaction and entitlement information needed to provide access.
  • Early-access websiteVercel and Neon process the email address and plan interest submitted through readysaid.com, along with normal hosting and security data.
  • Direct-app update checkWhen you deliberately choose Check for Updates, ReadySaid requests its update feed from readysaid.com. Hosting systems receive ordinary network-request metadata such as IP address and request time.

5. What an eligible cloud-refinement request excludes

ReadySaid’s refinement contract is designed to exclude:

  • microphone audio and audio recordings;
  • partial hypotheses, raw speech segments, alternatives, confidence values, and audio timing;
  • clipboard contents and surrounding document text;
  • application, window, document, field, and website names;
  • original values identified by local safeguards, such as email addresses, URLs, names, numbers, dates, and approved shortcut values (detection is heuristic and may not identify every sensitive value); and
  • your raw ReadySaid account identifier in the provider safety identifier.

An eligible request also carries operational metadata needed to validate and route it: random request and turn identifiers, platform, app version and build, locale, Natural or Professional selection, punctuation settings, personalization revision, and completion metadata. The ReadySaid gateway sees the authenticated Supabase session; OpenAI receives a keyed pseudonymous safety identifier instead of the raw ReadySaid account identifier.

The request uses store: false, but that flag alone is not a Zero Data Retention promise. Under OpenAI’s default API controls, content may remain in abuse-monitoring logs for up to 30 days. ReadySaid will describe a shorter period only after the applicable provider control is approved and verified.

6. Controls available to you

  • Select the output mode appropriate for the text you are creating.
  • Keep cloud-assisted refinement off, or turn it off to stop future cloud text requests.
  • Review and reset Speech Profile information and local Insights using available app controls.
  • Review microphone, Accessibility, Input Monitoring, and login-item permissions in system settings.
  • Replace or clear clipboard content when a transcript remains copied.
  • Sign out to stop future account synchronization on that installation.
  • Revoke social-provider access in the provider account. Contact ReadySaid separately if you also want the ReadySaid account deleted.
  • Use supported account-deletion controls or email support@readysaid.com from the account address to begin a verified deletion request. An emailed request is not complete until ReadySaid confirms the required identity and billing steps.

Questions about a specific path can be sent through ReadySaid Support.

ReadySaid

Voice to text designed around intentional control, local processing, and clear choices.

HelpSupportData ControlsContact
LegalPrivacyTerms
© 2026 ReadySaid. All rights reserved.