Privacy

Default data handling

TalkTalkType is designed around short desktop dictation, not transcript warehousing.

Last updated 2026-07-27 ・ 5 sections

At a glance

The service keeps what your account and your allowance need in order to work. The audio you speak, and the text it turns into, are not part of that.

Not stored

Audio: Sent to the configured speech provider, transcribed, and dropped. The service writes no audio file.
Transcript text: Comes back to your Mac as text. Neither the raw transcript nor the cleaned-up version is kept.
Clipboard: Pasting happens on your Mac. What sits in your clipboard never reaches the service.

Stored, and what for

Account: Google identity, sessions, plan and subscription state — what sign-in and billing run on.
Devices: One row per registered Mac, so the device limit works. Revoke any of them from Account.
Usage rows: Duration, status, preset, provider, latency. The numbers behind your allowance, with no content attached.
Support messages: Text you type into a support request is stored, because we have to read it to answer you.

Audio and transcript storage

Audio files and transcript text are not stored by default by the TalkTalkType Worker. The service records operational metadata such as device ID, plan, duration, status, provider, and latency so limits and reliability can be managed.

Cloud ASR data

When cloud transcription is used, the recorded audio is sent to the configured speech provider for transcription. Formatting requests may send transcript text to the configured formatter provider. Provider requests are made only to produce the returned text.

Account, device, and usage metadata

The service stores account identity, Better Auth sessions, registered devices, subscription state, referral state, license events, and monthly usage totals. Tokens are stored in the Mac Keychain on the device.

Subprocessors

The current service design uses Cloudflare for Worker, D1, and hosting; Google for OAuth; OpenAI or an equivalent configured provider for cloud transcription and formatting; and Stripe for billing once paid checkout is enabled.

What we are considering

We are exploring handling and processing data closer to each user's region, and broadening language support beyond the current set. These are directions under consideration, not features available today.