Clair Flow processes your audio in the cloud, so trust has to be explicit. This page describes what the product does with your data in plain language.
What Clair Flow stores
- account data such as your email address
- browser sessions, device approvals, and device records
- hashed device API keys
- subscription and billing identifiers
- usage counters and dictation session metadata
- transcript text associated with completed dictation sessions
What stays local to the Mac app
- microphone capture
- hotkeys and shortcut preferences
- local permission state
- text insertion into the focused app
What the cloud service processes
During dictation, Clair Flow sends audio to the cloud so it can:
- authenticate the connected device
- perform speech recognition
- clean and normalize the transcript
- apply glossary-aware terminology guidance
- record usage and account state
Transcript text and session metadata are stored. Raw audio is processed during your dictation session but is not saved afterward.
What this means in practice
Clair Flow requires a cloud connection for speech processing and transcript cleanup. All dictation sessions are processed through the cloud pipeline described above.
Device security model
Clair Flow uses device-specific API keys for the native app:
- each connected device gets its own credential
- keys are shown once and stored hashed on the server
- keys can be revoked from the account dashboard
How the boundary works
The product is designed around a clean boundary:
- local app for capture and insertion
- cloud service for processing, billing, and account state
That boundary is central to how Clair Flow works today.