Privacy policy
What stays on your Mac, what leaves it, and what happens to the little that reaches a server. Written against the code rather than from a template.
This policy covers the Speaklively app for macOS and the website at www.speaklively.com. It is written by the person who builds both, and it describes what the software actually does today — 1 November 2026.
1The short version
- Your voice never leaves your Mac. There is no recording and no upload. Listening and transcription happen on the machine, on Apple’s on-device models.
- Your words leave only when you press a button that sends them — the AI Rewrites (Polish and Structure), and two optional features described in section 3.
- A message you write in “Tell the Maker” reaches us — only when you press Send, and it is emailed to the maker rather than stored on a server. See the end of section 3.
- Nothing you dictate is stored on any server. The proxy that meters those requests keeps counts and costs. It does not keep the text going through it, and it does not keep the reply.
- Your dictation history stays on your disk, as plain files. It is never uploaded.
- Nothing is sold, ever, to anybody, for any purpose. There are no advertising networks and no third-party tracking SDK inside the Mac app.
2What never leaves your Mac
These are not settings you have to find and switch off. There is nothing to send in the first place.
- Microphone audio. Heard on the machine and gone when the dictation ends. It is never written to disk as a recording and never transmitted.
- Live transcription. Apple’s on-device speech models, which is why dictation works with no network at all.
- Original and Tidy. Both are produced on the Mac. Nothing you dictated — no transcript, no fragment of one — reaches any server, including ours. The anonymous counts in section 5 and the app events in section 6 still happen, and section 7 is the switch for both.
- Your history. Plain files on your own disk, under your own user account.
- What was on screen when you pressed. The app reads the focused window’s title and the text already in the field, to bias the recogniser toward names it can see you are working with. Those terms live for the length of one dictation and are then discarded. They are not stored, and they are never sent anywhere.
If you never turn on an AI Rewrite and never make an account, no text you dictated ever leaves your Mac. What still leaves is described in sections 5 and 6: counts of words and seconds, and a short list of named events about whether the app worked. Neither carries anything you said. Section 7 is the switch that stops both.
3What leaves, and only when you ask
Three features send text to Anthropic’s Claude models. The app’s Privacy pane shows them under SENT TO AI, alongside two things that are kept rather than sent, and carries a switch for three of the five.
- Polish and Structure — the one transcript you are looking at, sent when you press the button — or each time the panel opens, if it opens on Polish or Structure — so it can be rewritten. Each is switchable. The request carries a short context block with it, because that context is what makes the rewrite good rather than generic: the name of the app you are dictating into (“Mail”, “Slack”), a one-line note on how people write there, your vocabulary terms for that app, and your voice profile if you have built one. That is the one place an app’s name leaves your Mac — it never reaches our own servers, which see only a category.
- Vocabulary suggestions — a batch of your recent corrections (what the recogniser heard, and what you changed it to) used to propose words it should have known, each tagged with the bundle identifier of the app it came from so a term can be scoped to where you actually use it. Switchable, in Settings → Privacy or Settings → Vocabulary.
- Writing style — the samples you record for the Voice feature, sent when you build or rebuild a style. There is no switch because the feature is the sending: if you never record a sample, nothing goes.
Two routes, and the difference matters
Which one you are on depends on how you set up access, and it changes who can see the request:
| If you are using | The text goes | We can see |
|---|---|---|
| Your own Anthropic API key | Straight from your Mac to api.anthropic.com | Nothing. It never touches our server, and neither does your key — that is held in your Mac’s Keychain |
| The free allowance, or a paid plan | Through our proxy, then on to Anthropic | That a request happened, and what it cost — never what it said. See section 4 |
In both cases Anthropic processes the text under its own terms and privacy policy. Anthropic states that it does not train its models on API inputs or outputs; the current statement is the authority, not this sentence.
A message you send us
The app’s menu has Tell the Maker…, a box for telling the person who builds Speaklively that something is broken, confusing or missing. Nothing goes until you press Send. Then it sends:
- what you wrote, and nothing else from the box;
- your email address, only if you type one — used to reply to you, and for nothing else;
- the app version and build, and your macOS version;
- your country, as Cloudflare’s network determined it from the connection;
- the install identifier from section 5, only while usage data is on, so the message can be read next to what that install reported. The window says so before you send.
It is emailed to the maker through Resend and is not stored on our server. What the server keeps is that a message was sent, with a country, a time and whether it came from the app or the website, so that it can refuse more than fifty in a day from the app or twenty from the website. The email is kept in the maker’s mailbox, and deleted if you ask.
The same box is on the website, at speaklively.com/tell-the-maker, for anyone without the app. From there it sends what you wrote, the topic you tapped if you tapped one, your email address only if you type one, and your country as above. There is no app version and no install identifier to send. If you then say you are happy to be quoted on the website, that answer and the first name you give go as a second short message, with your email if you gave it. Both are handled exactly as above, and the website’s analytics are not told that you sent anything.
4What the server records when it does
When a request goes through our proxy, one row is written per call. Successful or not, it holds:
- the time, the model name, and the HTTP status;
- token counts and the cost in millionths of a dollar — this is what the allowance is measured against;
- which feature made the call (cleanup, vocabulary or voice), so background work is not charged against a free allowance somebody wanted for dictating;
- a one-off identifier for the dictation, so pressing both Polish and Structure on the same sentence counts once rather than twice. It is generated per dictation, kept nowhere on your Mac, and means nothing once that dictation is over;
- a hash of the access token the call was made with.
No prompt, no reply, no transcript. The proxy is built to meter without reading, and the storage has nowhere to put the text even if it wanted one.
5Anonymous usage counts
The app sends a small report on its own schedule — every few hours for the first days after installing, then daily. That is how many installs are actually running is known at all, and it is the only way to see whether the parts that never touch a server are working. It carries:
- An install identifier — a hash of a random identifier the app generated on first launch. It is not derived from your hardware, your name, or anything about the machine, so it dies with the install rather than following you to your next Mac. If you make an account, we link that install to it, so that a support request can be answered and so we can see whether the app is actually working for people. The link is recorded with a date and is deleted along with everything else if you ask. Neither is ever joined to what you dictate, because what you dictate never reaches us at all.
- the app version and build number;
- four totals describing what the app changed about your words — how many words you said, how many were inserted, how many filler words were removed, and how many words were corrected. Four numbers, added up across a day; never the words themselves, and nothing that could be used to reconstruct them.
- your country, as Cloudflare’s network already determined it from the connection. Not a city, not a region, and not from anything the app knows;
- counts — words dictated, number of dictations, seconds spoken. Never the words themselves;
- a category of app and which engine produced the text. The category is one of five fixed buckets — technical, correspondence, short informal, notes, general — and is never an app name or a bundle identifier. Anything the app does not recognise falls into “general” by construction, so unusual and personal apps collapse into one bucket automatically rather than because somebody remembered to strip them.
And a short note each time the app starts, sent before anything else in the launch: the same install identifier, the app version and build, your macOS version, and one word for how the app’s previous run ended — it was quit, it stopped while still starting, or it stopped while running (a crash, a force quit, or the power going). That last word is how a version that crashes is told apart from a Mac where the app was simply not opened. It goes to our server only, not to the analytics provider in section 6.
These reports are also how we notice somebody being let down. When an install that was used on two or more days sends nothing for two days, or stops reporting dictations for five, our server emails the maker a short note: that install’s random label, its country, its app version and the counts above. Nothing in it names you, and nothing is sent to you. It is how a broken update gets found and fixed rather than discovered weeks later.
There is a switch for all of this, in Settings → Privacy, on by default. Turning it off stops the counts report, the start-up note and the events in section 6, throws away anything already queued rather than holding it, and stops the app saying which install it is when it checks for updates — you keep receiving updates, that is a separate switch. One thing it does not stop: dictation counts already recorded but not yet reported stay on your Mac, and are simply never sent.
No IP address is stored with any of this. Exact mode runs entirely on your Mac and no text from it reaches any server; these counts, and the engine named on a first dictation in section 6, are the only way it is visible at all. They exist so that “is anybody using this” has an answer that does not require reading anything anybody wrote.
6Your account, if you make one
You can use Speaklively without an account. Dictation, live transcription, Tidy and history never ask for one, and the first fifteen AI Rewrites do not either. Verifying an email address gets you a further hundred. If you make an account, this is what exists:
- Your email address, stored in readable form — not hashed, unlike everything else here. That is deliberate: an address nobody can read is one you cannot be sent a receipt at, answered from, or refunded to. Gmail addresses are normalised (dots and +suffixes removed) so that one person cannot be two accounts by punctuation.
- Your address on the first-week email list. Verifying an address starts a few emails from the person who builds Speaklively, about getting started: up to five — a welcome, then one on each of the first, second, fourth and seventh days — and then they stop. Each one says why it came. Reply stop and they stop: the reply reaches a person, who adds your address to a do-not-send list. A record of which of these emails went to your address is kept, so that none is sent twice.
- Your plan and, if you are paying, when it renews.
- A six-digit verification code, while you are signing in. Stored as a hash, expiring shortly, with a limited number of attempts, and deleted as soon as it is used or finally fails.
- An access token, stored only as a hash — the token itself exists on your Mac, in the Keychain, and nowhere else. This is why a lost token can be reissued but never recovered.
- A hashed device identifier, so the free allowance cannot be reset by removing the app and adding it again.
- One row per dictation spent from an allowance, holding the account or device it belonged to and the time — never the dictation.
- A record of a few moments, sent to our analytics provider. Thirty-three named events, and they come from two places.
Five are made by our server as it answers a request: a sign-in code being asked for, a code being checked, a token being issued, an allowance running out, and somebody joining the waitlist for the paid plan, and whether they joined in the panel or in Settings.
Twenty-eight are made by the app, on your Mac, and sent from it. They are the switch in section 5’s subject, and they are how a solo developer learns that something is broken on a machine he has never touched. Named individually, because a list you can count is worth more than an adjective:
- install_created and app_launched — that this copy of the app exists, and then once per launch. Between them they carry your macOS version, whether Apple Intelligence is available and — when it is not — which of Apple’s three reasons applies, your Mac’s model name (Mac14,2 and the like: the same string on every unit of that model, so it names the product and not your machine — never the serial number, never the hardware id), which of the four permissions are granted, whether the fn key is free, and which key you hold to dictate.
- engine_ready — that dictation became usable, how long that took from launch, whether a speech model had to be downloaded first and how long that took, and for which language.
- window_opened and pane_opened — that the window came up and why, and which of the app’s seven screens you moved between. The name of the screen, never anything on it.
- permission_requested, permission_granted and permission_denied — which of the four gates you were asked for, whether it was a dialog or a trip to System Settings, how many times it has been asked this launch, how long after installing, and what you answered.
- setup_completed — that setup finished, how long it took, and how many gates were outstanding when you started.
- onboarding_step — what happened on each screen of the setup window: that it came up, was finished, skipped, gone back to or closed, how long you spent on it and how many tries it took, and if it put up help — no sound, the wrong microphone, the fn key still opening emoji — which help it was and what fixed it. A random number ties one run through the setup together. Fixed labels, never a microphone’s name and never anything you said.
- try_it_focused — that you put the cursor in the practice box on the setup window’s “Let’s try it” screen, how long after it appeared, and whether setup was finished by then. Not what you then typed or said into it.
- first_dictation — once ever, on the first dictation that lands. How long after installing, how many words, the app category, which engine, and whether it was the practice box rather than a real app.
- dictation_empty, dictation_failed and event_tap_dead — that a dictation produced nothing, or that the key stopped being heard, with the reason and enough shape to diagnose it: how long you held, whether any audio arrived, whether it was silent, whether any of it was loud enough to be speech, and which language was selected. If another key stopped it, which kind of key: ⌘, ⌃, ⌥, Escape, or just “another key”. How much sound, never any of it.
- dictation_inserted — once for every dictation that ends with words: whether they were pasted, or kept on the clipboard because there was nowhere to paste or you had switched apps; whether they went straight in or through the panel first, and how the panel was closed; the app category from section 5; and whether macOS’s secure input was switched on at the time.
- language_offered and language_changed — that the language picker was offered while you practised in setup and which language was selected at the time, and if you changed it, which language you moved from and to.
- offer_shown — that the offer of free AI rewrites was on screen.
- nudge_shown, nudge_taken and nudge_dismissed — that the panel offered one of its one-line suggestions (try hands-free, try Tidy, switch on Apple Intelligence and the like), which one, how many times it had been offered, and whether you pressed its button or closed it. For the hands-free offer, also how many presses in a row had missed.
- keychain_prompted — that macOS asked you for your password to unlock a stored credential, how many seconds it waited, and whether you allowed it. The name of the item, never its contents. It exists because that prompt can hang the app silently, and until it was counted nobody could see it happening.
- tidy_ready — that Apple Intelligence became available after having been unavailable, and how long that took.
- first_cleanup — once ever, the first time a rewrite succeeded. Which one, how many dictations you had done first, which plan paid for it, and whether it ran on your own Anthropic key or through us.
- rewrite_failed — that a rewrite you asked for did not come back: which one, a fixed label for why (timed out, offline, refused and the like), the error number if there was one, and how many dictations you had done by then. Never the server’s own message.
- voice_profiled — that you asked the app to describe how you write, and how many samples you had given it. Never the samples.
- dictation_chord_set — that you chose a shortcut of your own to dictate with: how many modifier keys it uses, whether its key is a function key, and whether the confirming press arrived. Never which keys.
What one press carries. The three events a press can end in — dictation_inserted, dictation_empty and dictation_failed — share a few more lines, because “it did nothing” has a dozen causes and these are how they are told apart:
- Timing and gesture — how long you held the key; how many milliseconds the microphone took to open and the first sound took to arrive; whether you were already talking when it opened, or still talking when you let go; how you pressed (held, hands-free, sent to the panel, or a shortcut of your own); whether the panel lit up to say it was listening, and which tip it showed for this press and for the one before; a running count of your presses, the seconds since the last one, and how many presses in between did nothing of their own; and a random number made up for this one press, so its events can be matched. Timings and labels — no sound, no words.
- focus_role — on dictation_inserted, the kind of thing that had the cursor when the words arrived: a text field, a search field, a text area, part of a web page, some other control, or one of our own windows. The kind of element, never what was in it and never its title.
- mic_route — whether the microphone was a Bluetooth one or not, because Bluetooth headsets drop to phone quality while they listen and the words get worse. Never the microphone’s name.
None of them can carry text. The app can only put a string, a number or a true/false into an event, and our server accepts nothing else — no nested object, no list — so there is no shape a transcript could travel in even by accident. Every event also carries the app version, the build, the country our server infers from the connection, and which kind of build sent it — a release, a test build or a developer build — so that testing is never counted as somebody using the app.
How they identify you. Three kinds of identifier, never your address itself. Events about an account use a one-way scramble of your email; events about a device that has no account use a scramble of a random identifier the app made up and kept; and the app’s own events use a scramble of a second random identifier, made on first launch, that is derived from nothing about your Mac — no serial number, no hardware id. None of the three can be turned back into an address or a machine.
7The website
When you download
Downloading asks you for nothing: no name, no email address, no form. The download is counted: the time, which file and version, your country from Cloudflare’s network, and where the link said it came from — either a campaign tag written into the link, or the hostname the visit arrived from. Only ever the hostname: the rest of a referring URL is discarded in the browser before any request is made, because that is where a search phrase or a private thread would be. There is no identifier attached, so this is a count of downloads and is honest about not being a count of people.
If you ask for the gift
The page after the download offers a gift: one email with the download link and the steps that switch on a hundred free AI Rewrites in the app (this site calls them AI cleanups). It asks for an email address and nothing else, and sends nothing until you press the button. On a phone, or on a computer that is not a Mac, the same box sends the same email, so you can open the link on your Mac.
Each email that actually goes is recorded as one row: your address, normalised as in section 6; the time; which version of the page asked for it — the one for Macs, or the one for phones and other computers; the campaign tag in the link you arrived by, if it had one; your country, from Cloudflare’s network; whether the address already had an account, because then the email explains how to sign in rather than promising a second free hundred, which nobody gets; and the email service’s id for the message. Nothing else is recorded alongside it — no IP address, no browser string, no referrer. If the email fails to send, nothing is recorded.
Those rows are what let the box refuse to email one address more than three times in a day, and pause all sending if somebody tries to use it to fill other people’s inboxes. The address gets the email you asked for and nothing else: no reminder, and it is not put on the first-week email list. It is never sold. The only companies that handle it are the two in section 9 that run our server and deliver the email: Cloudflare and Resend. If you have already asked us to stop emailing you, the box sends nothing at all. Verifying the same address in the app later is a separate step, and section 6 says what that starts.
Your address is never sent to website analytics. Google Analytics is told that a download started, that the gift box was used, and where the visit came from. It is not told who you are, and your address is never put into a link or the address bar, where analytics would pick it up.
If you used the old download form
The download button used to open a form asking for a name and an email address. What it collected is still kept: the address, the name, and the date, with nothing else alongside — no IP address, no browser string, no referrer. The address is on the same first-week email list as section 6, and some of those emails greet you by the name you gave; reply stop and they stop. The site no longer asks for either.
Analytics and storage in your browser
- Google Analytics 4 runs on the production site only. It sets cookies and receives your IP address, as any web request does, and uses it to derive a coarse location; Google’s own privacy policy governs what it does with that. Blocking it costs you nothing on this site. It does not load at all if your browser sends Global Privacy Control or Do Not Track. In the EU, the EEA, the UK and Switzerland it does not load until you press OK on the question at the bottom of the page; anywhere else it loads unless you say no. “Privacy choices” at the foot of every page changes your answer.
- One localStorage entry and one cookie hold your answer to that question and whether to ask it. The cookie says only “Europe” or “elsewhere”, never your country.
- Vercel Speed Insights collects anonymous page performance measurements. No cookies.
- Three sessionStorage entries. Two, speaklively:src and speaklively:ref, remember where your visit came from, between arriving and clicking download. The third, speaklively:welcome, remembers whether that click came from a Mac, which download button it was and when, so the page after it knows whether to say your download is under way. None of them holds your email address. Deliberately sessionStorage and not localStorage: it dies with the tab, so it describes one visit rather than leaving a mark that follows you between them.
8What is never collected
Stated as a list because a policy that only describes what it takes leaves the interesting question unanswered:
- Audio. There is no recording, on your machine or anywhere else.
- The contents of your dictations, on any server — including the text sent for an AI Rewrite, which is passed through and not retained.
- The names of the apps you dictate into, or their bundle identifiers. Our servers are told a category — one of five buckets — and never the app. The one exception is described in section 3: a cloud rewrite tells Anthropic which app the text is going into, and a vocabulary suggestion tells it which app a correction came from.
- What is on your screen. It is read locally and discarded locally.
- Your IP address, in our own storage.
- Keystrokes: what you type, and which keys you press. Three things come close, so they are named here rather than left out, and section 6 has each one. A count of presses of your dictation key that did nothing of their own, such as a macOS shortcut on fn. When another key stops a dictation, which kind of key it was: ⌘, ⌃, ⌥, Escape, or just “another key”. And if you set a shortcut of your own, how many modifier keys it uses. Never a letter, never a key code, never which keys.
- Browsing history, files, or contacts.
- Your own Anthropic API key, if you use one.
- Anything at all through a third-party analytics or advertising SDK inside the Mac app. There is none, and there is no advertising or tracking code of any kind. The app does contain one piece of third-party code — Sparkle, which downloads and installs updates. It talks only to our own update feed. The events in section 6 are named individually and go only to our analytics provider; twenty-eight of them are made by the app on your Mac, and five by our server.
9Who else is involved
Running the service means other companies handle parts of it. These are all of them:
| Who | What for | What they get |
|---|---|---|
| Anthropic | The AI Rewrites, vocabulary suggestions and writing style | The text you sent for that one request, and its reply |
| Cloudflare | The proxy, its database, and hosting the app download | Requests in transit, including IP addresses at the edge; the stored rows described above |
| Vercel | Hosting this website and its performance measurements | Web requests to the site |
| Google Analytics | Counting visits to the website | Visit data and IP address. Never your name or email address |
| Resend | Delivering sign-in codes, the gift email in section 7 and the first-week emails in section 6, and delivering Tell the Maker messages and the notes in section 5 to the maker | Your email address and the code. For the gift and first-week emails, your address and the email itself, which uses your name only if you gave one on the old download form. A Tell the Maker message, with your address if you typed one. For the notes, an install’s random label, country, version and counts — never your email address |
| PostHog | Understanding whether the app works for people | The events in section 6. A one-way scramble of your email address, of a device identifier, or of an install identifier — never the address itself; never anything you dictated, and never your IP address |
When paid plans open, a payment provider will be added to this list. It will be a merchant of record, which means it — not this project — takes your payment details. Card numbers will never reach us. This section will name it before it is switched on.
10How long any of it is kept
- Sign-in codes — minutes. Deleted when used, when the attempts run out, and dead on expiry regardless.
- Account, token and allowance rows — until you ask for them to be deleted, or the account is closed.
- Gift requests, the first-week email list, and the record of which of those emails went to each address — until you ask for them to be deleted. Nothing removes them automatically today. If you reply stop, your address goes on a short do-not-send list and stays there, because that list is what keeps it from being emailed again.
- Per-call metering rows, usage counts, start-up notes, download counts — kept while the project runs. They contain no text and no address, and nothing automatically removes them today.
- Tell the Maker messages — not kept on our server at all. Each one is an email in the maker’s mailbox, deleted when you ask.
- The analytics events in section 6 — kept for twelve months by our analytics provider, then deleted.
- Website visit data — kept for fourteen months by Google Analytics, then deleted.
- Your dictations and history — for as long as you keep them, on your own disk. Deleting them in the app deletes them; there is no copy elsewhere to catch up with.
11Getting a copy, or getting it deleted
Write to hello@takeoffdigilabs.com and ask. You can have a copy of everything associated with your address, have it corrected, or have it deleted. Deleting removes your account, your tokens, your allowance rows, any link recorded between your address and an install, your gift requests, and your place on the first-week email list — with the name, if you gave one — along with the record of which emails went to you. The usage counts themselves stay, and once that link is gone there is nothing in them that identifies you — they are counts of words and seconds, with no address and no text. If you once replied stop, your address stays on the do-not-send list, since that is what stops it being emailed again; say so if you want that gone too.
Depending on where you live, the India Digital Personal Data Protection Act, the UK and EU GDPR, or your local equivalent may give you these rights formally. You do not need to cite one. Asking is enough, and a reply should take days rather than weeks — this is a project run by one person, so it is answered by a person.
12Children
Speaklively is not directed at children, and an account should not be made by anyone under 16. Nothing here is knowingly collected from them; if you believe an account belongs to a child, write and it will be removed.
13Changes to this policy
The date at the top says when this text took effect. If something changes that widens what is collected or what it is used for, the date moves and anyone with an account is told by email before it applies — not afterwards, and not by quietly editing this page. Corrections and clarifications that do not change what happens to your data are made without notice.
14Contact
Takeoff Digi Labs (OPC) Private Limited is the data controller for everything described above. No. 5/1, Soodamanipuram, Karaikudi, Sivaganga District, Tamil Nadu 630003, India.
Questions, objections and requests: hello@takeoffdigilabs.com. It reaches the person who builds Speaklively.
The companion document is the terms of service.