Privacy

Here's a plain, specific answer to "what happens to my data" — no vague reassurances, just what actually happens. The paid plans change the answer, so this page is organized around that.

The short version

On the free plan, Tiune does everything — listening, recognizing your speech, and cleaning up the text — entirely on your own device, Mac, PC or Android phone. Nothing about your voice or your words is sent anywhere; there is no network path in the dictation pipeline at all.

Plus and Pro add two things that can't run locally — an AI cleanup pass, and cloud transcription — so on those plans some of your words, and on Pro your audio, do leave your machine. What follows says exactly what leaves, where it goes, and what happens to it.

What leaves your machine, by plan

Free — nothing. No audio, no text.
Plus — the transcribed text, at the end of a dictation. Your own machine has already turned your speech into text; that text is sent to be rewritten and the result comes straight back. Your audio never leaves your machine on Plus — transcription is still local.
Plus — and, since 0.3.0, the words already in the box. Up to 256 characters from immediately before your cursor, so a list you started in one breath carries on as a list in the next. Never from a password field or any other secure input, never on the free plan, and never with a transformation. Set out in full under What we send about where you're writing, below.
Pro — audio, but only when you've turned cloud transcription on. The live preview you see while speaking is always produced locally, either way. In Online, offline backup, dictation Tiune hears as English stays on your computer, and only other languages go to the cloud.
Plus and above — your vocabulary and your own transformations, for sync. They're kept with your account so they can reach your other devices. No audio and no transcripts. See Sync.
Meeting notes (Pro, macOS) — the transcript text, and on an online mode the audio. Set out in full under Meeting notes, below.

Audio is held only for the length of the request. Nothing is written to disk and no transcript is logged.

Who receives it. Cloud transcription of dictation runs on ElevenLabs; the AI cleanup pass, and the summaries and translations in meeting notes, run on Groq, and on Cerebras when the request to Groq fails. Both cleanup providers receive the same text on the same terms, and neither may train on it. They are named rather than described, because "a trusted third party" is not a sentence anyone can check — and Cerebras is named for exactly that reason even though it only ever sees a request Groq could not take.

Meeting transcription runs on Deepgram, only for meeting notes, only on Pro, and only when your transcription setting is online. Every request opts out of Deepgram's model-improvement programme, which under their documentation means the audio is kept only for as long as it takes to process. Dictation never goes to Deepgram.

What always stays on your machine

Your voice, from the moment you speak to the moment it becomes text. Audio is processed in memory and is never saved as a sound file, anywhere, at any point.
Speech recognition itself, on all three of Tiune's local engines. On Pro you can opt into cloud transcription, for dictation and for meeting notes; that's the one exception, and it's yours to turn on.
Basic cleanup — punctuation, formatting, removing filler words.
Vocabulary learning — noticing and remembering your corrections.
Everything you see in the app — your past captures, meetings, vocabulary, transformations, and settings are stored in one file on your own machine. Your captures, meetings and settings are never uploaded — a meeting you choose to share is the one exception, and it is uploaded encrypted (below). On Plus and above, your vocabulary and your own transformations are also kept with your account so they can sync to your other devices.

You can also keep no history at all. Turn off Save transcripts on this device in Settings → Privacy and nothing is written down — not a blanked row, not a redacted one, nothing. Today stays empty as a result, which is the honest consequence of the setting rather than a bug, and meeting notes aren't saved either. Delete what's saved erases everything already stored, meetings included, leaving your vocabulary and settings intact.
Insights — the observations Tiune shares about how you speak are generated purely from rows already saved on your machine.

Downloading a speech engine, and Tiune's background check for app updates, also involve normal internet requests — no personal data is included in either.

Meeting notes

Meeting notes is on Pro, on a Mac with macOS 14.4 or later. It records other people, so it's set out separately.

It never starts on its own. Tiune offers when a call app opens your microphone, and nothing is recorded until you say yes. A red dot shows on the bar the whole time notes are being taken.
It hears both sides. Your microphone, and the call's audio through macOS's System Audio Recording permission. That permission is for sound only; it is not Screen Recording, and Tiune never sees your screen.
Where the audio is transcribed depends on your mode. In Offline, on your Mac. On Pro in either online mode, the audio is sent to Deepgram to be transcribed — not to ElevenLabs. Tiune's server relays it and stores none of it.

Meeting transcription runs on Deepgram only for meeting notes, only on Pro, and only when your transcription setting is online. Every request opts out of Deepgram's model-improvement programme, which under their documentation means the audio is kept only for as long as it takes to process. Dictation never goes to Deepgram.
The notes are written in the cloud, in every mode. The summary, key points, decisions, action items, open questions and translations are written by Groq (or Cerebras) from the transcript text. They receive text, not audio.
Audio is never saved. Not as a sound file on your Mac, not on our server.
The transcript is kept on your Mac, with your other history, and nowhere else. Delete one meeting or all of them in the Meetings view. With Save transcripts on this device off, meetings aren't saved at all.
Sharing is encrypted, and the link is the key. Share makes a link on tiune.app for one meeting's notes (and its transcript, only if you include it). The notes are encrypted on your Mac first, with a key made for that link, and the key is the part after the # — which browsers never send to a server. Tiune stores what it cannot read; the page unlocks it in the reader's browser, and runs no analytics. Anyone with the link can read it. A link lasts 7, 30 or 90 days or until you stop it, and stopping it or deleting the meeting deletes the stored copy.
Consent is yours to handle. Recording a conversation can require the consent of the people in it, depending on where you and they are.

On Android, Tiune is a keyboard

Everywhere above that says "your machine" means your phone too. This section covers the one thing a phone genuinely changes.

A phone gives an app no way to type into another app from outside it, so Tiune for Android is an input method — a keyboard you turn on in Android's settings. When you enable any keyboard, Android warns you it may be able to collect everything you type, including passwords. That warning is true of keyboards as a class and is worth taking seriously, so here is what this one does.

What the keyboard receives. Android hands an input method the text around your cursor and tells it when the cursor moves. Tiune holds that in memory — the same place the Mac and Windows versions hold what they read from the focused window — and uses it for the same two purposes: knowing where your dictated words go, and letting cleanup continue a list you already started.
What is not kept. Tiune does not record what you type, keeps no history of your keystrokes, and writes none of them to its database. What is saved on the phone is what is saved on a Mac: your dictations if transcript saving is on, plus vocabulary and settings.
What leaves your phone. Exactly what leaves a Mac or PC on the same plan and no more — on Free nothing, on Plus the transcribed text and the preceding text described below, on Pro the audio of a dictation. Being a keyboard adds no category. Nothing is sent because you typed it; the preceding-text rule is the only thing Tiune ever sends that you typed rather than said, and its limits hold on the phone too, including never reading a password field.
The microphone is requested separately by Android the first time you dictate. Audio is handled as it is on a computer: held in memory, never written to the phone as a sound file.

Tiune for Android is coming to Google Play and isn't listed there yet. When it is, what it declares on its Play listing will be the same list as this page. Meeting notes isn't on Android: a phone can't hear another app's call.

What we send about where you're writing

The AI cleanup pass writes differently depending on the destination — an email and a Slack reply want different sentences out of the same speech. Tiune works this out on your own machine, from the shape of the fields around your cursor.

Nothing that identifies the app ever leaves your machine — never the window title, never the app name. Only a single one-word category goes with the request.

Since 0.3.0 one more thing does go with it, and it is the only thing Tiune sends that you typed rather than said, so here it is in full.

Up to 256 characters from immediately before your cursor. Dictate into a field that already has something in it and that text goes with the dictation. It exists so a list you started in one breath carries on as a list in the next rather than restarting as a paragraph — and it is used for that and nothing else. The instruction sent with it forbids repeating, correcting, summarising or returning any of it.

Three limits hold on their own, with no setting to find:

Never from a password field, or any other secure input. Tiune does not read those at all, for this or anything else.
Never on the free plan. There is no cleanup request to put it in, so the field is not read — not read and discarded, not read.
Never with a transformation. You asked for something specific to be done to text you can see; the surrounding formatting has no say in that.

You can turn all of this off with Send where you're writing in Settings → Privacy. Off, none of it is read: not the category, not the field, not the words before your cursor. Your dictation is still cleaned up; it just arrives without knowing where it's going.

Where a field will not expose its contents — many chat composers do not — nothing is sent. Instead Tiune falls back to a single word for how your own last dictation into that same app ended: bullets, numbered, lead-in or paragraph. It is never sent for a different app than the one it came from, never once five minutes have passed, and it is held in memory only — quitting Tiune ends it.

Like the dictation itself, none of it is written to a database, a file, or a log. It is held for the seconds the request takes and then it is gone.

Your account

Signing in with Google, Apple or Microsoft identifies your account so your vocabulary and corrections can follow you across devices. On a Mac or PC it opens your system browser to that provider directly; on Android, sign-in is Google only and uses the phone's own Google account picker. Either way, Tiune never sees your password. Only your account's email and a session token come back, and the session token is stored in the operating system's own credential store — Keychain on macOS, Credential Manager on Windows — never on disk in the clear. Android has no equivalent store available to Tiune, so on a phone the session is a file in the app's own private storage, which the operating system keeps other apps out of.

No dictation content, audio, or transcript is ever part of this — account sign-in and speech processing are entirely separate systems.

If you used an earlier build that asked you to paste in your own ElevenLabs or DeepSeek API keys, those keys are deleted from your Keychain or Credential Manager the first time 0.2.0 starts. They were live provider credentials that nothing would ever read again. If you use those keys elsewhere they still work — this only removes Tiune's copy.

Three things that never happen

These aren't settings, because they were never choices. They hold on every plan, Plus and Pro included:

Tiune never stores your audio. Your voice is processed as it streams and never written down — not to a file, not to a database, not to a log, and that includes meeting audio. Online transcription is relayed to the provider — ElevenLabs for dictation, with its no-logging flag set, and Deepgram for meeting notes; what each provider itself keeps is spelled out on the privacy page.
Your words never train an AI model. We keep nothing to train on, and the AI cleanup runs on a provider contractually barred from training on what it receives.
No one at Tiune reads your words. No human review, no quality sampling, no support access to your transcripts. There is nothing stored for anyone to read.

What "Accessibility access" actually means for your privacy

On macOS, Accessibility sounds like a broad permission, so it's worth being precise: Tiune uses it for exactly two things — typing your dictated text into whatever app you're using, and briefly checking the text field you just typed into, only to notice if you corrected a word (see Vocabulary Learning). It does not read your screen generally, and it doesn't see anything in apps you're not actively dictating into. The equivalent access on Windows is used the same way and for the same two things.

On this page