Privacy Policy
SpeakWith is built around a simple principle: your words are yours. This policy explains what SpeakWith does and does not do with the recordings, transcripts, and documents you create. November 2026 change: a new section describes the AI service included with a monthly membership, which sends transcript text to IKI Systems and then to OpenAI.
Your recordings are processed on your device
SpeakWith records, transcribes, organises, and searches entirely on your own device, whether that is your Mac or your iOS device. Turning speech into text, shaping it into your daily document, and answering your searches all happen locally. SpeakWith does not need an internet connection to do its core work, and it does not send your recordings to a server to be processed.
Three optional features can send transcript text, never audio, to a language model: generating a session title, polishing a take, and checking corrections. All of them are off until you turn them on. Session titles and polish can run through the AI service included with a monthly membership, described in the next section, or through your own OpenAI API key. On the Mac they can also use a local Ollama model, so nothing leaves your machine when you choose Ollama. On iPhone and iPad, session titles and polish use the AI service included with SpeakWith Pro. An OpenAI API key you provide is an alternative. Without Pro and without a key, nothing leaves the device. Correction checks, if you enable them, use your OpenAI key.
One more feature can send transcript text off your device, and it works differently: Send to agent, on the Mac only. When you use it, the topics you have ticked in the Outline are handed to a coding agent already installed on your Mac, such as Claude Code, Cursor, Codex, or Gemini. SpeakWith hands that text to the program on your machine; the program is what contacts a provider, under your own account with whichever service it uses, and that provider then sees the topics you sent. What happens to the text from there is covered by that agent's own terms and privacy policy, not by this one. Nothing is sent until you press Send to agent, and nothing is sent if you never use the feature.
The AI service included with a monthly membership
A monthly membership includes an AI service for session titles and polish, so you do not need to supply your own API key. When you use it, SpeakWith sends the transcript text for that step to a service run by IKI Systems, which forwards it to OpenAI to produce the title or the polished text. Audio never leaves your device, and transcription still happens locally. If you turn on automatic polish, text is sent each time a take settles, not only when you press a button.
To confirm that your membership is current, the app sends a hashed form of your purchase credential. The service stores that hash, a hashed short-lived session token, your membership tier, and the time of first and most recent use. It does not store the credential itself, your name, or your email address. It keeps a monthly total of the tokens each membership has used, so it can apply the allowance. That ledger holds counts, not your words. These records live in Amazon Web Services, in the US West (Oregon) region.
SpeakWith can reach a language model three ways, and your text only passes through us on one of them: a local Ollama model on the Mac, where nothing leaves your device; an OpenAI API key you provide, where the text goes from the app straight to OpenAI and never through us; and the included service. For that third path our role is transit and nothing else. Our AI service never writes the text you send, or the text that comes back, to a log or to a database - not when a request succeeds, and not when it fails. Whatever we record about a failure describes the failure, never the text that was in flight. What OpenAI does with the text on its side is governed by OpenAI's terms and policies.
The allowance is a monthly ceiling on how much text the service will process for one membership. If it runs out, or the service is unavailable, the app offers to use an OpenAI API key you provide instead, and nothing is sent until you choose. A one-time purchase and the 14-day free trial do not include the service; they use your own key or, on the Mac, a local Ollama model. Correction checks are not part of the included service and always use your own key.
No telemetry, analytics, or tracking in the app
The SpeakWith application does not include usage analytics, advertising, or behavioural tracking. We do not collect a record of how you use the app, what you record, or what you search for. There are no third-party trackers in the application.
This is a statement about the app itself. This website, which is separate software running in your browser, measures anonymous visitor counts; that is described under “The support website” below. Nothing measured on the website is connected to the app, and the app never reports usage to us. The one exception is the included AI service: when a monthly membership uses it, the service records the token totals needed to apply the allowance, as described above. That is billing bookkeeping for a feature you chose to use, not product analytics, and it records amounts, not content.
Your files belong to you
Everything SpeakWith produces (your recordings, transcripts, and daily documents) is stored as ordinary files on your device. Open, copy, move, back up, or delete them with any tool you like.
Crash reporting is opt-in only
If something in SpeakWith goes wrong, a diagnostic report can help us fix it. SpeakWith never sends such a report automatically. Crash and diagnostic reporting is strictly opt-in: nothing leaves your device unless you explicitly choose to send it, and you can decline or turn it off at any time.
The support website
This website uses TelemetryDeck, a privacy-focused analytics service, to count page views and how often the download and pricing links are used. It tells us which pages people find useful. It is not used to profile you.
No cookies are set for analytics and no advertising or cross-site tracking identifiers are used. Visits are identified only by a random value that lives in your browser tab and is discarded when you close it, and TelemetryDeck anonymises that value before storing it. We see aggregate counts - pages, referrers, campaign links, browser and country - never individual visitors, and never anything you type.
Standard server request logs may exist at the hosting provider, as they do for any website.
Changes to this policy
If this policy changes, the updated version will be posted here with a new date. Material changes will be summarised at the top of the page.
Contact
Questions about privacy? Email [email protected].