Your privacy, plainly.

No vague reassurances — here's exactly what happens to your data, and when.

The short version

On the free plan, listening, recognizing your speech, and cleaning up the text all happen entirely on your own computer — Mac or PC — and nothing about your voice or your words is sent anywhere. Plus and Pro add two things that cannot 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. Meeting notes, on Pro, follow the same rule: offline they stay on your Mac, online the meeting audio goes to a transcription service. What follows says exactly what leaves, where it goes, and what happens to it.

Three things are true of Tiune on every plan, paid ones included: Tiune never stores your audio, Tiune never trains on your words, and no one at Tiune reads your words. The providers a paid plan sends work to are a different matter. Each one keeps and uses what it receives under its own policy, and those policies differ, so we set out below exactly what each provider does. Signing in with Google, Apple or Microsoft is required to use Tiune, but it's only for your account identity — it never touches your dictation.

What always stays on your computer

  • Your voice, from the moment you speak to the moment it becomes text. Tiune holds audio in memory and never writes it to disk as a sound file — there is no recording of you on your computer, at any point, on any plan, and that includes meeting notes. (Pro can send that audio to a transcription service; what happens to it there is set out below.)
  • Speech recognition itself, using Tiune's on-device engines — on every plan except Pro's cloud transcription, which is described below and is a choice you make in Settings.
  • Cleanup and transformations — punctuation, formatting, and removing filler words. The AI rewriting pass that Plus and Pro add is the exception, and it is described below.
  • Vocabulary learning — noticing and remembering your corrections.
  • Everything you see in the app — your past captures, vocabulary, and settings are stored in one file on your computer. Since 0.2.0 you can turn transcript saving off entirely, or erase what is saved, in Settings → Privacy.
  • Insights — the observations Tiune shares about how you speak, and about where your speaking time goes, are worked out purely from what is already saved on your computer.

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

On Android, Tiune is a keyboard

Everywhere above that says "your computer" means your phone too. This section is about 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 that it may be able to collect everything you type, including passwords. That warning is true of keyboards as a class, and it is the right thing to be cautious about. So here is exactly 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 keeps that in memory, in the same place the Mac and Windows versions keep what they read from the focused window, and uses it for the same two purposes: knowing where your dictated words should go, and letting the cleanup pass continue a list you already started instead of restarting it as a paragraph.
  • What is not kept. Tiune does not record what you type, does not keep a history of your keystrokes, and does not write them to its database. What is saved on the phone is what is saved on a Mac — your dictations, if you have transcript saving on, and your vocabulary and settings.
  • What leaves your phone. Exactly what leaves a Mac or a PC on the same plan, and no more: on Free, nothing; on Plus, the transcribed text plus the preceding-text described above; on Pro, the audio of a dictation. Being a keyboard does not add a category. In particular, nothing is sent because you typed it — the preceding-text rule above is the only thing Tiune ever sends that you typed rather than said, and its limits apply on the phone as well, including never reading a password field.
  • The microphone is asked for separately, by Android, the first time you dictate. Audio is handled exactly as it is on a computer: held in memory, never written to the phone as a sound file.

Tiune for Android is on Google Play. The data it declares there is the same list as this page. Meeting notes are not part of the Android app: a phone does not let an app hear the other side of a call.

Your account

Signing in with Google, Apple or Microsoft is required to start using Tiune — it's what lets your vocabulary and corrections follow you across every device you use. On a Mac or PC it opens your system browser to that provider directly; on Android it is Google only, using Android's own sign-in sheet inside the app. Either way Tiune never sees your password. Only your account's email and a session token come back; your 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.

Usage data

Tiune sends a small set of anonymous product-usage events (like "onboarding finished" or "a capture completed") to help us understand what's working — never transcript text, audio, or vocabulary content. If the app crashes, the crash location and a stack trace are sent the same way, to help us fix it; never anything you dictated. Neither is on until you say so: Tiune asks once, in plain words, the moment your first sign-in completes, and takes "Not now" for an answer. You can change your mind either way, any time, in Settings → Privacy → Share usage data.

One thing is sent even with that turned off: a single ping the first time Tiune runs on a machine, so we can count installs. It carries four things and nothing else — a number that stands for your device, the app version, which operating system it is, and whether the copy you are running is a public release or one of our own development builds. That number is worked out on your own machine by scrambling a hardware identifier beyond recovery: it always comes out the same on the same computer, so reinstalling Tiune counts once rather than twice, and neither we nor anyone else can turn it back into a serial number or match it against the separate device number your licence uses. It is never linked to your account or email, no other event is sent when the setting is off, and one device is only ever counted once.

Telling one machine from another

Free trials are one per machine, so there has to be some way to recognise a machine we have seen before. Tiune takes your machine's stable hardware id, adds a fixed salt and hashes it — on your machine, before anything is sent — and sends only the resulting hash. The underlying id never leaves your machine, the hash cannot be turned back into it, and it is used for exactly one thing: deciding whether this machine has already had a free trial. It is not used for analytics, not joined to your dictation, and not shared with anyone.

This website

Separately from the app, tiune.app itself (the site you're reading right now) uses Google Analytics and Microsoft Clarity to understand traffic and how the site is used — standard web analytics, including anonymized session replay of on-page behavior like scrolling and clicks. This is about the marketing site only; it has no connection to the app, your dictation, or your account.

The hold-to-talk bar at the top of the home page is the one thing on this site that listens, and only while you hold it. It runs on your browser’s own speech recognition, not on Tiune: your browser asks for the microphone, and the company behind it hears the audio and returns the words, under its own terms (Google for Chrome, Microsoft for Edge, Apple for Safari). Tiune receives neither the audio nor the words. They stay on the page until you leave it, and they are masked from the session replay described above. The app does not work this way, and the rest of this page is about the app.

If someone sends you a referral or affiliate link — a tiune.app/r/ address ending in a short code — opening it adds 1 to a count of how many times that code’s link was opened that day. That count is the whole record: there is nowhere in it for an address, a device, a browser or an account, nothing is stored in your browser to carry that code or to recognise you when you come back, and the person who shared the link sees a number and never anything about who opened it. (The site analytics in the paragraph above run on that page as they do on every other page here.) If you later subscribe using their code, our record of it links the subscription to their code so we can pay them — what they can be shown from it is a count and an amount, never your name, your address, or anything you dictate.

If you join the waitlist for Android (or, before 0.2.0, for Windows), we store the email address you type, along with your browser's user-agent string and the date — nothing else, and only because you asked us to tell you when those versions land. We use it for that one announcement and nothing more, we never sell or share it, and you can have it deleted at any time by emailing support@tiune.app.

Meeting notes

Meeting notes are a Pro feature on macOS 14.4 or later and Windows 10 version 2004 or later. They are the one part of Tiune that hears people other than you, so they get their own section.

  • Nothing is recorded until you say yes. When a call app (Zoom, Teams, Slack, WhatsApp, FaceTime, Skype, or a call in your browser) opens your microphone, Tiune offers to take notes. Opening a microphone never starts a recording by itself. While notes are being taken the pill shows a red recording state, and you can stop it from the pill, or the menu bar on a Mac and the tray on Windows.
  • What is recorded. Your microphone, and the call's sound: on a Mac through macOS's System Audio Recording permission — the audio-only permission, not screen recording — and on Windows from the sound the call app plays, with no extra permission. Tiune holds that audio in memory and never writes it to disk as a sound file.
  • Where it goes. It follows your transcription setting. Offline, the meeting is transcribed on your computer and no audio leaves it. Online, on Pro, the meeting audio is sent through Tiune's server to Deepgram to be transcribed, and the text comes back; Tiune's server stores none of it on the way through. Meetings deliberately do not use the speech provider dictation uses.
  • Summaries and translations. When a meeting ends, its transcript is sent to the same AI cleanup providers named below to write the notes — the summary, key points, decisions, action items and open questions — and, if you press Translate, the translation. Like a dictation, the text is held only for the seconds the request takes.
  • What is kept. The transcript, the speaker names you confirm, and the summary are saved on your computer, in the same file as your dictation history, and never uploaded unless you share that meeting. Turn transcript saving off and meetings are not saved either; “Delete what’s saved” erases them with everything else, and you can delete one meeting at a time.
  • Sharing a meeting. If you press Share, Tiune makes a link on tiune.app for that one meeting’s notes — and its transcript, only if you tick that. The notes are encrypted on your computer before they are uploaded, with a key made for that one link, and the key is the part of the link after the #, which browsers never send to any server. So Tiune’s server stores something it cannot read, and the page on tiune.app unlocks it in the reader’s own browser. The flip side is plain: anyone who has the link can read what you shared, so send it only to people who should. A link lasts 7, 30 or 90 days, or until you stop it; stopping it, or deleting the meeting, deletes the stored copy at once, and expired copies are deleted within the hour. The page that shows shared notes runs no analytics. Names Tiune only guessed for other speakers are never included, and you choose the name that replaces “You”.
  • Other people. Recording a conversation may need the consent of the people in it where you are. That decision is yours: Tiune cannot know the law where you are, so it does not guess.

Plus and Pro: what leaves your computer

Both paid plans are upgrades you choose. Nothing below happens on the free plan, and nothing below happens until you turn the feature on.

  • Plus — the AI cleanup pass. After your own machine has already turned your speech into text, that text is sent to Tiune's server, which passes it to a language-model provider to be rewritten, and hands the result straight back. Your audio never leaves your machine on Plus — transcription is still local. The text is held only for the seconds the request takes; Tiune's server writes none of it to a database, a file, or a log.
  • Plus — and, since 0.3.0, the words already in the box. Dictate into a field that already has something in it and Tiune sends up to 256 characters from immediately before your cursor along with the dictation. It is there so that a list you started in one breath carries on as a list in the next instead of 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 without a setting — it is never read from a password field or any other secure input, it is never read at all on the free plan, and it is never sent with a transformation. Where a field will not expose its contents — many chat composers do not — nothing is sent, and Tiune falls back to a single word for how your own last dictation into that same app ended: "bullets", "numbered", "lead-in" or "paragraph". Like the dictation, it is held only for the seconds the request takes and written to no database, file, or log. This is the one thing Tiune sends that you typed rather than said, so it is set out here in full rather than folded into the line above.
  • Plus and Pro — sync. Your vocabulary and your custom transformations are stored on Tiune's server so they reach your other signed-in devices. That is the whole list: not your dictations, not your history, not your meetings — apart from a meeting you choose to share, which is uploaded encrypted, as described under Meeting notes.
  • Pro — cloud transcription. Your audio streams through Tiune's server to our speech provider, which sends the words back as you speak. Tiune's server is a relay in both directions and stores nothing on the way through. The provider does keep what it receives, though, so read the next section before you turn this on.

Who we send it to, and what they may do with it

We name our sub-processors rather than describing them, because "a trusted third party" tells you nothing you could check. Tiune itself stores none of what passes through to them and trains on none of it. What each provider does is set by its own policy, and they differ. What follows is what each one says, as we read their own pages on 2026-11-06. If a provider changes its terms, its own page wins over our summary.

  • AI cleanup runs on Groq, and on Cerebras when Groq is unavailable. This covers Plus and Pro dictation, and meeting summaries and translations. Under Groq's services agreement, Groq may not use inputs or outputs to train or fine-tune any model. GroqCloud does not retain inference requests by default. Inputs and outputs may be logged for up to 30 days, but only to troubleshoot reliability problems or investigate abuse. Cerebras receives the same text only when the request to Groq fails. Its terms give it no right to use that text to train or fine-tune models, and its privacy policy says it does not retain inference inputs or outputs.
  • Cloud transcription of dictation runs on ElevenLabs, only on Pro, and only when you choose cloud transcription. This is the provider that keeps the most:
    • Retention. By default, ElevenLabs keeps the audio and the transcript of each request for as long as it needs them to provide its service, and stores them in the United States. Its staff can reach that data where their work requires it, including support and safety teams.
    • The no-logging flag. We send ElevenLabs' no-logging flag on every request, but ElevenLabs offers Zero Retention Mode only to enterprise customers. Tiune isn't one today, so the flag doesn't stop it keeping your audio.
    • Training. ElevenLabs' terms let it use what it receives to improve its services unless the account opts out. Tiune's account is opted out, which covers audio sent from 7 November 2026 on.
    If you need audio that no provider keeps, use Plus, where your audio never leaves your machine. For an organisation, it's an Enterprise conversation, priced to include the provider plan that requires.
  • Meeting transcription runs on Deepgram, only for meeting notes, only on Pro, and only when your transcription setting is online. Dictation never goes to Deepgram. By default, Deepgram keeps audio and transcripts to improve its models. Every request from Tiune opts out of that, and with the opt-out, Deepgram does not store the audio or the transcript once it has returned the response. It does keep request metadata and usage logs, which contain no audio and no text.
  • Where a provider gives us a choice, we take the private one. We opt out of training wherever a provider lets us. A provider whose policy said it trains on what it receives, with no opt-out available to most of our users, was removed from Tiune in August 2026. It was deleted from the source code, not switched off, so no setting can bring it back.

What that adds up to

Tiune never stores your audio, whether it's a dictation or a meeting. It is processed as it streams and never written down: not on your computer, not on our server, not in a log. There is no recording of you anywhere in Tiune's systems to lose, subpoena or leak. On Pro with cloud transcription, the provider receiving the audio does keep it, as set out above.

Tiune never trains on your words. We have nothing to train on, because we keep nothing, and Tiune has no training programme. No setting anywhere in Tiune opts you into one. The providers' own training rules are set out above: the cleanup providers may not train on what we send, and we opt out with the two transcription providers that would otherwise use it.

No one at Tiune reads your words. There is no human review queue, no quality-sampling process, and no support tool that can pull up something you dictated. The only words of yours on Tiune's server are your vocabulary and custom transformations, kept so they sync, and nobody reviews them. Whether a provider's staff can see what it keeps is set by that provider's policy, linked above.

What stays on your computer either way is your history: every capture Tiune shows you lives in a single file on your machine and is never uploaded. You can stop Tiune saving it at all, or erase what's already there, in Settings → Privacy.

Payment

Subscriptions are billed through Stripe, which collects your card details directly — Tiune never sees, handles, or stores a card number. We keep only the identifiers needed to know which plan you are on and to let you manage or cancel it.

What "Accessibility access" actually means

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. It does not read your screen generally, and it doesn't see anything in apps you're not actively dictating into.

Questions

Reach us any time at support@tiune.app.

Last updated 2026-11-06.