Legal

Privacy

What data blabe handles when it turns your voice into text, who else handles it, and how long it’s kept.

Last updated: October 23, 2026. Effective date: October 23, 2026.

Who is responsible

blabe is made by its owner, a sole proprietor in California trading as blabe (“blabe”, “we”, “us”). We decide why and how the personal data described on this page is used, except where a company named below handles it under its own policy. Polar sells the subscription as the merchant of record. Contact: support@blabe.dev.

The short version

  • The app has no analytics or crash reporting, and no telemetry beyond the dictation times blabe for Mac sends from 1.0.25 and blabe for Windows from 1.0.9 (see What blabe’s transcription service keeps).
  • The app talks to blabe’s transcription service, which we run. It turns your speech into text and checks your trial or license; for a subscription, it checks the license with Polar. With Free with your key, the app also talks directly to your own xAI or Microsoft Azure account, which transcribes your audio (more). From version 1.0.23, the app asks blabe.dev whether a newer version exists on its own at most once a day, in the background while it runs, and whenever you choose Check for Updates… in the blabe menu; earlier versions ask at most once a day, and only right after you finish a dictation. If a check the app makes on its own finds one, Install updates automatically is on (it is by default), and the app and its folder are writable by your user, the app checks the update list once more, downloads the signed update through blabe.dev from Cloudflare R2, where blabe’s downloads are stored, and verifies it. Once it’s ready and blabe has been idle for five minutes, a five-second notice appears, then blabe installs it and restarts. Holding your hotkey postpones that, and installation also waits while a failed recording is kept for Retry, while dictation, pasting or sending is unfinished, while a modal dialog or attached sheet is open in blabe, or while your Mac is asleep. If automatic installation isn’t available, or the setting is off, the blabe menu offers the update, and nothing downloads until you click it and choose to install in the update window of Sparkle, the update library; installation can then finish when you next quit blabe. Check for Updates… opens that window directly, and nothing downloads until you choose to install there. Turning the setting off cancels an automatic update that hasn’t started installing, but can’t undo one that has, and an update already prepared may still install when you next quit blabe. These requests carry only what any web request does: your IP address, and a user agent naming the versions of blabe and of Sparkle. They send no license, account details, system profile or anything else about you or your Mac, and the website’s server logs the requests it receives like any other visit.
  • The service runs on Cloudflare Workers, with its records in a Cloudflare D1 database. With the trial or a subscription, for dictation that isn’t streamed to xAI (see below), it sends your audio directly to Microsoft’s MAI-Transcribe 2 model on Microsoft Azure, in the US West region (westus), and returns the text. Only after certain Azure errors, and never with Azure chosen in the Transcription setting, it may send the same audio once to xAI’s Grok Voice Transcribe 2.0 model instead; by default, xAI keeps API requests and responses for 30 days to check for abuse. The service doesn’t store your audio or your transcripts: it holds them in memory only while it passes them on. It deletes each request’s audio length and cost after 30 days.
  • With the trial or a subscription and the Transcription setting on xAI (live), the default, the service instead streams most dictation in English or with no pinned language to xAI’s Grok Voice Transcribe 2.0 model while you’re still recording, with your Words as hints, so the text is ready soon after you stop. If that stream can’t start, Azure transcribes the recording. Choose Azure in the setting and nothing goes to xAI (more).
  • AI cleanup is a setting: Aggressive, Standard or Off. Aggressive is the default for new installs. Updating keeps the setting you had. When it’s on, the service also sends each transcript, with your vocabulary words, directly to a third-party AI cleanup provider (or, as a backup when it’s slow or fails, to a second provider) that rewrites it for formatting and grammar (Standard) or into its shortest, clearest form (Aggressive), then returns both versions to your Mac. Neither is stored on the service, but if the backup handles the request, it may keep it, usually for up to 30 days, to check for abuse.
  • With Free with your key, you use blabe with your own xAI or Microsoft Azure key. The key is stored on your device. blabe’s service checks it once with your provider when you add it and never stores it, and your audio goes from the app straight to your provider. For the first 10 days after you add your key, AI cleanup is on by default (unless you had set it to Off) and your transcripts go through blabe’s service for it, as described above, at no charge. After that, AI cleanup turns off and your transcripts no longer go to blabe (more).
  • On your Mac, your audio is held in memory only. blabe never saves it to disk.
  • After a paste, blabe can offer to learn a word you fix. It reads that field on your computer only, never sends or logs the text, and you can turn it off in Settings → Words (more).
  • Your sign-in token and this Mac’s random IDs are stored in your Mac’s login Keychain.
  • blabe for Windows comes from the download page on blabe.dev, or from the Microsoft Store, which installs and updates the Store copy. The Store copy never checks for updates itself. The copy from the download page, from version 1.0.6 on, asks blabe.dev at most once a day whether a newer version exists and, if one does, downloads it from blabe.dev and verifies it, even with Install updates automatically off; these requests send the app’s version and no account or device ID. On a Windows PC, your sign-in token and the PC’s random IDs are stored in Windows Credential Manager. More about Windows.
  • We keep closed support emails and diagnostic attachments for 30 days after a case closes.
  • This website sets no cookies. It counts visits to its pages, and clicks on its Download, Microsoft Store and Subscribe buttons, with Umami, an analytics tool we run ourselves on the website’s server, so no analytics company receives the data. Its server keeps access logs for at most 30 days.
  • We never train AI models on your data, and we don’t build models from it. Microsoft and xAI each say they don’t train their models on the requests blabe sends them, and the AI cleanup providers don’t either (see Training, below). Some of them may still keep requests for a while, as described below.
  • We don’t sell or share your personal information.

What blabe handles

Your voice

This section and Live transcription with xAI describe the trial and a subscription. With Free with your key, your audio goes from the app straight to your own xAI or Azure account instead, as described in Free with your key.

While you hold the hotkey, blabe records from your microphone. If you chose “Press to start, press again to stop” in Settings, it records from one press of the hotkey to the next instead, for at most 5 minutes. blabe sends the audio over HTTPS to blabe’s transcription service, which we run on Cloudflare Workers, as you record, or all at once when the recording ends if it can’t stream. Without live transcription, the service sends the audio directly to Microsoft’s MAI-Transcribe 2 speech model, on blabe’s Microsoft Azure account in the US West region (westus), and returns the text to the app. Only after certain Azure errors, and never with Azure chosen in the Transcription setting, the service may send the same audio once, directly to xAI’s Grok Voice Transcribe 2.0 speech model on blabe’s xAI account, with your language if you pinned one and your Words, and returns that text instead (see xAI, below). The service processes your audio to transcribe it for you. The microphone is off at all other times. If you press Esc during a recording, it is discarded and nothing is pasted. The audio from before you pressed Esc has already reached blabe’s service, and with live transcription it has reached xAI too (see Live transcription with xAI).

On your Mac, blabe never writes the recording to disk. If a transcription fails, the recording stays in memory so that Retry Transcription can send it again. With the trial or a subscription, if live transcription had already sent it to xAI, Retry sends it to Microsoft Azure instead (see Live transcription with xAI). With Free with your key, Retry sends it to your own provider again. It is discarded after a successful transcription or when you quit blabe.

What blabe’s transcription service keeps: not your audio, and not your words. Your audio is passed on for transcription and isn’t stored on the service: the service holds it in memory only while passing it on. The text that comes back goes straight to your Mac and isn’t stored either. So if the text is lost on its way back, for example because your connection drops, the service has no copy to send again, and you record again. For each request, the service records a one-way fingerprint of the request, so that a retry isn’t counted twice, how much audio it was, when it happened, how it turned out, what it cost, which transcription provider handled it (Azure or xAI), and which license or trial it belongs to. A retry that goes to Azure after a live xAI failure counts as a new dictation. That also lets us see how much each license or trial is used. To prevent runaway use, it also counts each license’s or trial’s recent and simultaneous requests. After 30 days, the service deletes how much audio a request had and what it cost. It keeps the request’s fingerprint, time, outcome and transcription provider, and which license or trial it belongs to, for as long as the service keeps that license or trial, so that an old request can never be charged twice. With a subscription or a trial, each request also keeps how much of your allowance it used and which allowance period it counted against, because that’s how your remaining allowance is worked out. The counts of recent and simultaneous requests are deleted within a day. For troubleshooting, the service also keeps separate diagnostic records for accepted requests: the time, rounded down to the minute; the outcome; how many times it tried the transcription provider and how many of those tries were turned away as too busy; how long the request and the transcription took; the audio length, rounded to a tenth of a second; which transcription provider handled it; which blabe app sent it, blabe for Mac or blabe for Windows; that app’s build number (on a Mac) or version number (on Windows); and, from blabe for Mac 1.0.25 and blabe for Windows 1.0.9, how long your previous pasted dictation took on your Mac or PC: sending the audio, waiting for the text and pasting it. These records contain no audio, transcripts, IP addresses, or license, trial, Mac or request IDs.

Live transcription with xAI

The Transcription setting, under Settings → Dictation in the Mac and Windows apps, has two options: xAI (live), the default, and Azure. With xAI (live), most dictation in English or with no pinned language uses live transcription. The app sends your audio to blabe’s transcription service while you’re still recording. The service passes it on as it arrives, in small pieces, directly to xAI’s Grok Voice Transcribe 2.0 speech model on blabe’s xAI account. xAI transcribes while you speak, so the text is ready soon after you stop. With the audio, xAI gets your Words as hints, and your language if you pinned English, in the address of the connection. It gets no sign-in, license, device or request IDs. With the trial or a subscription, the app never connects to xAI itself; with Free with your key, it connects directly to your own xAI account (see Free with your key).

With Azure, the service sends your audio only to Microsoft Azure. Nothing from that dictation goes to xAI, even as a backup after an Azure error. A change to the setting applies from your next dictation. Older app versions don’t have the setting.

These dictations go to Microsoft Azure instead of xAI:

  • every dictation, when Azure is chosen in the Transcription setting
  • dictation in any other language you pinned
  • dictation with Clean up speech turned off in Settings → Dictation
  • dictation with a Word over 50 characters long, or a very long list of Words
  • dictation from older app versions that don’t support live transcription

Except when you chose Azure, xAI can still be the backup for these after certain Azure errors, as described under xAI, below.

When you haven’t pinned a language, xAI isn’t told one. If its text contains letters outside the Latin alphabet, the service also sends the kept copy to Azure once and uses Azure’s text if Azure returns any. For that dictation, both xAI and Azure receive your audio.

Because the audio goes out while you speak, xAI receives it even if you then press Esc or the recording turns out too short to transcribe. In that case the service closes the stream and nothing is pasted.

Your original recording is handled as before: the app keeps it in memory only, never on disk, and the service holds a copy in memory only while the dictation runs and stores none of it. If the connection to xAI can’t be opened, or fails before any audio reaches xAI, the service sends that copy to Microsoft Azure automatically, as it does for other dictation.

Once audio has reached xAI, a failure of the stream or of xAI doesn’t send the recording to Azure on its own. blabe shows an error, nothing is pasted, and the app keeps the recording in memory. If you choose Retry Transcription, the app sends the whole recording to Microsoft Azure as a new request, which counts as a new dictation. For that dictation, xAI has received some or all of the audio, and Azure receives all of it.

We may also turn live transcription off for everyone from the service. Dictation then goes to Azure. What xAI keeps, and what it says about training, is under xAI, below.

Your words

The text that comes back is pasted where your cursor is. To paste, blabe briefly replaces your clipboard with the text, presses ⌘V, and then puts your previous clipboard contents back. If pasting fails, the text stays on your clipboard so it isn’t lost. blabe keeps your last transcript in memory for Copy Last Transcript until you quit. It does not save transcripts to disk, and it does not keep a history. If you turn on sending to coding agents, blabe may also press Return after pasting. Before it pastes, blabe reads up to two characters just before your cursor to decide whether your words need a leading space; it uses them on your Mac only and never stores or sends them.

Learning from your edits

When you fix a word right after blabe pastes it, blabe can offer to learn the fix. For example, if blabe typed “super base” and you change it to “Supabase”, it asks whether to learn “Supabase”. Nothing is learned unless you click Learn. This is on by default on Mac and Windows, in the versions that include it. To turn it off, switch off Learn from my edits in Settings → Words.

To spot your fix, blabe reads the text of the field you pasted into, on your computer: when the paste lands, each time the field changes while it watches, and once more when 30 seconds have passed or you move to another field. If you send or clear the text before then, it uses the last version it read. It compares only the words it pasted and up to 64 characters on each side. It stops watching early if you start a new dictation or turn Learn from my edits off. It never reads password fields, blabe’s own windows or password manager apps, and on Windows it also skips Windows’ sign-in and permission prompts. The text it reads stays in memory on your computer and is dropped when it stops watching. It isn’t saved to disk or sent to blabe’s service or anyone else. blabe’s log notes only which app it was, why it stopped watching and whether it found a fix, never the text.

If you click Learn, the fix is saved with your other fixes on your computer. If the new word has a capital letter or isn’t a common word, it’s also added to your Words. Like any Word you add, a learned Word can travel with later dictations, as described under Hints that travel with your audio. If you click Not now or ignore the question, blabe saves a one-way hash of the pair, not the words themselves, so it doesn’t ask about that pair again.

AI cleanup

AI cleanup is a setting under Settings → Dictation: Aggressive, Standard or Off. Aggressive is the default for new installs. Updating keeps the setting you had. When it’s off, nothing below happens and your words are pasted as transcribed. When it’s on, after xAI or Microsoft returns the transcript, blabe’s transcription service sends the transcript and your vocabulary words directly to a third-party AI cleanup provider, on blabe’s account, which rewrites the text and sends it back. In the Standard style it edits for formatting, grammar and concision (lists, paragraphs, punctuation, filler words, repetition and self-corrections); in the Aggressive style it rewrites what you said into its shortest, clearest form and aims to keep your points and how strongly you meant them. If the provider fails, or hasn’t answered within about half a second, the service also sends the same request directly to a backup AI cleanup provider on blabe’s account. The service asks the backup not to store the request for later use. Neither provider uses it to train models, but the backup may keep it to check for abuse, usually for up to 30 days (see Backup AI cleanup provider, below); blabe’s account doesn’t have its zero data retention. The service uses whichever answer comes first and cancels the other. The service returns the rewritten text and the original transcript to your Mac and stores neither. blabe pastes the rewritten text, and Copy Last Transcript copies the original. If the rewrite fails or takes too long, blabe pastes the original transcript and says so. Your audio is never sent to the language model.

Free with your key

With Free with your key, you use blabe without a subscription by adding your own xAI or Microsoft Azure key in Settings → Account, in the Your API key field. The app stores the key on your device only: in your Mac’s login Keychain, for this Mac only and not synced, or in Windows Credential Manager. It’s never written to blabe’s settings files, logs or crash reports.

When you add the key, the app sends it once, over HTTPS, to blabe’s transcription service. The service makes one request to your provider with it, to check that it works and to find which xAI team or Azure subscription it belongs to, then forgets it. The key is never stored or logged on the service. The service keeps only a one-way hash of that account’s ID, with when your 10 free days started and end. The 10 days belong to that account, so reinstalling blabe, a new computer or a new key on the same account doesn’t restart them, and everyone who shares one xAI team or Azure subscription shares one window.

Your audio goes from the app straight to your own provider account: xAI’s speech-to-text, or Microsoft’s MAI-Transcribe 2 on your own Azure resource, in the region you created it in, with your Words as hints. It doesn’t pass through blabe’s service, and it never switches to blabe’s transcription or to the other provider: if a transcription fails, the app keeps the recording in memory, and Retry Transcription sends it to the same provider again. That provider transcribes it under your agreement with it and its own privacy policy, and bills you for it; blabe doesn’t.

For the first 10 days after you add your key, AI cleanup (Standard or Aggressive) is on by default, unless you had set it to Off, and runs at no charge. During those days, with AI cleanup on, the app sends each transcript and your Words to blabe’s transcription service, which sends them to the AI cleanup provider, and to the backup provider when needed, exactly as described above, and stores neither. After 10 days, AI cleanup turns off, your transcripts no longer go to blabe and no language model sees your text; transcription keeps working with your key.

Hints that travel with your audio

Each request also carries your language setting (if you pinned one), the cleanup option (off, Standard or Aggressive), and the list of keywords blabe asks the model to favour: only the words you added in Settings, nothing added automatically. The list has at most 50 entries. The service passes them to the model with your audio. With live transcription, your Words, and your language if you pinned English, go to xAI in the address of the connection. With Free with your key, the app sends your audio and its transcription hints straight to your own provider, not to blabe. During the 10 free days with AI cleanup on, your transcripts, your Words, your cleanup style and your language still go to blabe’s service for AI cleanup (see Free with your key).

Your license

When you sign in with your license key, blabe sends it, with your Mac's model name (for example “Mac15,3”) and a random ID for this Mac, to blabe's transcription service. The service activates this Mac with Polar as one of your 3 devices and gives blabe a sign-in token. Your Mac keeps only that token and the random ID in your login Keychain, not the license key.

Each request to blabe’s transcription service carries that token. For a subscription, the service stores your license key, the activation ID, your Polar customer ID and the random ID for this Mac, so that it can check with Polar that your subscription is still active before it transcribes. It also stores your Polar subscription ID and when that subscription started, and, for each monthly allowance period, the period’s start and end dates and how much audio was transcribed in it. Each request record notes which period it counted against. Past periods are kept rather than overwritten, so your usage stays the same if you change devices or sign in again. None of these records contain audio or your words. The free trial needs no signup and no email address. When you start the free trial, blabe creates a random identifier and keeps it in your login Keychain on this Mac only; it doesn’t sync through iCloud, and it isn’t derived from your Mac’s hardware or from anything about you. blabe sends it, with your Mac’s model name (for example “Mac15,3”), to the transcription service, which stores only a one-way hash of the identifier, when the trial started and how much it has been used. That is how each Mac is limited to one trial, and why reinstalling blabe doesn’t restart it.

Your settings

Your hotkey, language, microphone, sound and sending choices, and your keyword list are stored on your Mac. Only the language, the cleanup option and the keyword list leave it, with your audio, as described above; from 1.0.25, so does how long your previous pasted dictation took on your Mac (sending the audio, waiting for the text and pasting it), numbers only.

What blabe looks at on your Mac

To decide whether it is safe to press Return after a paste, blabe checks which app is in front and, for terminals, which program is running in the tab. This happens on your Mac and none of it is sent anywhere. After a paste, blabe may also read that field for up to 30 seconds to learn from your edits (see Learning from your edits).

blabe for Windows

Everything above about your Mac applies to blabe for Windows on your PC in the same way, with these differences:

  • Getting and updating the app. You can download blabe for Windows from blabe.dev, which serves the installer from Cloudflare R2, or get it from the Microsoft Store. The Store copy makes no update requests of its own. The copy from the download page, from version 1.0.6 on, checks blabe.dev for a newer version at most once a day (and when you choose Check for Updates), and if one exists, downloads it from blabe.dev and verifies it, whether or not Install updates automatically is on. With that setting on (the default), it installs the update once blabe has been idle for five minutes, after a short notice, then restarts, or when blabe next starts; with it off, nothing installs until you choose the update in the tray menu. Earlier versions never check: to update one, you download the new version. For the Store copy, Microsoft handles the download, installation and updates under its privacy statement. Microsoft shows us, in its developer dashboard, statistics about installs and app health, such as crash counts. We don’t receive your name or contact details from the Store.
  • Your sign-in and IDs. Your sign-in token and the PC’s random device and trial IDs are stored in Windows Credential Manager on this PC, as generic credentials named blabe/session-v1, blabe/device-id-v1 and blabe/trial-id-v1. Windows encrypts them for your user account, and they don’t roam to other PCs. Uninstalling the Microsoft Store copy doesn’t remove them, and uninstalling the copy from the download page removes only your sign-in; the Windows uninstall guide shows how to remove the rest.
  • Your device’s name. Instead of a Mac model name, blabe for Windows tells the service only that the device is a Windows PC. Your Polar customer portal lists it as “blabe Windows · added” followed by the date you added it, for example “blabe Windows · added 2026-10-06”.
  • Your settings and logs. Your settings, Words, fixes and snippets are stored on your PC in %APPDATA%\blabe, and a diagnostic log in %LOCALAPPDATA%\blabe\logs; uninstalling doesn’t delete them. The Microsoft Store copy normally keeps them in %LOCALAPPDATA%\Packages\blabe.blabe_1wdw4w3fm6gqy\LocalCache\Roaming\blabe and %LOCALAPPDATA%\Packages\blabe.blabe_1wdw4w3fm6gqy\LocalCache\Local\blabe\logs: folders that belong to the Store app, which Windows normally deletes when you uninstall it. blabe never uploads these files or the log. As on a Mac, only your language, the cleanup options and your keyword list are sent when you dictate, with your audio, as described above; from 1.0.9, so are how long your previous pasted dictation took on your PC (sending the audio, waiting for the text and pasting it), numbers only.
  • What blabe looks at on your PC. On Windows, blabe presses Enter only in the Codex and Claude desktop apps’ message boxes, and only if you turn sending on (it’s off by default); never in a terminal, an editor or any other app. To decide, it checks on your PC which app and field are in front and whether you’ve typed or clicked since the paste. blabe may also read text just before the cursor in the field you’re pasting into, never in a password field: on every paste, up to two characters, to decide whether your words need a leading space; and, only if you turn sending on, a little more than the length of your transcript, before and after the paste, to confirm the whole transcript landed before it presses Enter. With sending on, that second read happens in whatever field you paste into, before blabe has ruled out apps it doesn’t send to, so it can include text you’d already typed there. This text is used on your PC only, and is never stored, logged or sent anywhere. Before it pastes, it asks Windows, through UI Automation, whether the field with your cursor is a password field; it compares the app in front with its own permission level, so that it doesn’t paste into apps run as administrator; and it checks whether an input method is still composing text. In any of those cases it copies your words instead of pasting them. This happens on your PC and none of it is sent anywhere. After a paste, blabe may also read that field for up to 30 seconds to learn from your edits (see Learning from your edits).
  • Your clipboard. To paste, blabe puts your words on the clipboard, presses Ctrl+V and then restores what you had copied. It marks its own copy so that Windows keeps it out of clipboard history and doesn’t sync it to your other devices.
  • Your microphone. blabe reads Windows’ microphone privacy settings to tell you when Windows is blocking it. It records only while you hold the hotkey, or between the two presses in toggle mode, for at most 5 minutes.

Support

If you write to us, we receive your email address and whatever you tell us, and the emails are stored with our email provider. Please don’t send recordings or passwords, or transcripts unless you’re reporting a problem with AI cleanup, and don’t send card details. For billing questions, we may ask for your Polar order reference. Apart from the dictation times in the service’s diagnostic records (see above), blabe never uploads logs or diagnostics by itself. In Help → Export Support Bundle…, you can save a file that summarizes blabe’s own logs from the last 24 hours and its recent crash reports, with message text and file paths left out and without audio, transcripts or keys, along with your blabe settings and permission states (not your vocabulary words), and choose whether to email it to us.

Purchases

Polar sells the subscription and is the merchant of record. That means Polar, not blabe, collects your payment details, billing address and email, and handles payment, tax and receipts. Polar is a controller of the payment data it processes and handles it under its privacy policy. We don’t receive your card details.

Polar shows us your customer record so we can provide blabe. According to Polar’s documentation, it includes your email address, name, billing name and address (including your country), any tax ID you enter, and your orders and subscriptions. We use it to run the subscription, to send you notices about it, such as a price change, and to answer support questions.

If you came to this website through a link we posted, for example on Hacker News or Product Hunt, that link carries tags after the “?” saying where it was posted (utm_source, utm_medium, utm_campaign and utm_content, such as “hn”). Product Hunt and BetaList add their own “ref” tag instead, which the website reads as the utm_source when the link has no utm_source. While you move around the website, the tags travel in the links you click, and the Subscribe button passes them to Polar’s checkout. Polar then stores them with your order and subscription, so we can see which post led to a subscription. The Microsoft Store button passes one campaign tag to the Microsoft Store (“cid”, made of the utm_source and utm_content when they are on our list of launch sites and subreddits or ad versions, such as “hn” or “reddit-r-windowsapps”; content that isn’t on the list is left out, so the tag is the source alone, and a source that isn’t on the list means no tag is passed at all), so Microsoft’s install reports to us can show which post led to an install. They say where the link was posted, not who you are. Nothing is stored in your browser for this. If your browser sends Do Not Track or Global Privacy Control, the tags aren’t passed on.

This website

The website sets no cookies and has no third-party scripts, fonts or embeds. To count visits, it uses Umami, an analytics tool we run ourselves on the same server as the website, so no analytics company receives the data. When you open a page, your browser loads a small script from blabe.dev, which sends back the address of the page you opened, without anything after a “?” or “#”. When you click a Download, Microsoft Store or Subscribe button, it also sends which kind of button it was (the download itself, the download page, the Microsoft Store listing or the checkout), for the download and the Microsoft Store whether the button is for Mac or Windows, and, if you came through one of our tagged links, which site the link was posted on, for example Hacker News, and, when the tag names one, which subreddit or which version of an ad. A tag that isn’t on our list of launch sites is counted only as “other”. Each kind of click is counted at most once per page you open, and a download at most once per platform. It sends nothing else from the page: no page title and no referring site. If your browser sends Do Not Track or Global Privacy Control, the script doesn’t load and your visit isn’t counted. Like any request, the script’s request carries your IP address and your browser’s user agent. Umami uses them to work out your browser, operating system, device type and approximate location (country, region and city), and to recognize repeat visits: it combines them, with a secret value that changes every month, into a scrambled visitor ID. It stores that ID, the page, the time and those details, but not your IP address. Umami sets no cookies, stores nothing in your browser and doesn’t follow you to other sites. We use it only to see how many people visit which pages and which launch posts lead to downloads and subscriptions. It is served from a Hostinger VPS in Lithuania. The reverse proxy in front of it logs each request, with your IP address, the time, the page you asked for and your browser’s user agent, for security and troubleshooting. These logs are deleted after at most 30 days. Downloads are served from Cloudflare R2, under Cloudflare’s privacy policy and website terms.

Who else handles your data

We use these companies. Each has its own privacy policy, and we don’t control what they do with data they receive.

  • Microsoft (privacy statement) runs the MAI-Transcribe 2 model on Microsoft Azure and transcribes your audio in blabe’s Azure account. Its Azure Speech service receives your audio and the hints above directly from blabe’s transcription service, in Microsoft Azure’s US West region (westus), and returns the transcript. Azure handles every recording it gets in that region, wherever you are. Microsoft’s documentation, checked on October 3, 2026, says that Azure Speech doesn’t store or process data outside the speech resource’s region (Speech service regions), and that for fast transcription, which is how MAI-Transcribe 2 is used (MAI-Transcribe 2 guide), Microsoft does not retain or store the data it receives (data, privacy and security for speech to text). That last page doesn’t name MAI-Transcribe 2. On training, see Training, below.
  • xAI (SpaceXAI LLC, which its policies call “SpaceXSI”; API data and security FAQ) runs the Grok Voice Transcribe 2.0 speech model in blabe’s xAI account. With the Transcription setting on xAI (live), the default, it’s the main transcription provider for most dictation in English or with no pinned language: blabe’s transcription service streams your audio to it while you record, with your Words and any pinned language, and xAI returns the text (see Live transcription with xAI). It’s also the backup for Azure, except when you choose Azure in the Transcription setting. If Azure rejects a recording (HTTP 400, 401, 402, 403, 404 or 422) or stays too busy (HTTP 429) when no further Azure retry can be attempted, blabe’s transcription service may send that recording once, directly to xAI, with your language if you pinned one and your Words, and xAI returns the transcript. If blabe turns on a wider setting, it may also do this after an Azure server error, a dropped connection or an unreadable reply. Recordings over 5 minutes (300 seconds) never go to xAI as a backup. It receives no sign-in, license, device or request IDs. Its API security FAQ, checked on October 18, 2026, says: “SpaceXSI never trains on your API inputs or outputs without your explicit permission. By default, all API requests and responses are stored on our servers (encrypted at rest) for 30 days for auditing purposes in the event of suspected abuse or misuse.” It also says that its default API address, which blabe uses, “does not guarantee a processing region”.
  • AI cleanup provider: a third-party company runs the language model for AI cleanup, in blabe’s account. Only when AI cleanup is on, it receives your transcript and vocabulary words directly from blabe’s transcription service and returns the rewritten text. It doesn’t train models on them. It never receives your audio.
  • Backup AI cleanup provider: only when AI cleanup is on, and only when the main provider fails or is slow, a second third-party company receives your transcript and vocabulary words directly from blabe’s transcription service, in blabe’s account, and returns the rewritten text. It doesn’t train models on them, but it may keep abuse monitoring logs of them for up to 30 days, unless the law requires longer or longer is reasonably necessary to protect its services or anyone else from harm. blabe’s account doesn’t have its zero data retention, so that applies. It never receives your audio.
  • Cloudflare (privacy policy, website terms) hosts blabe’s transcription service on Cloudflare Workers, with its records in a Cloudflare D1 database, in blabe’s Cloudflare account. With the trial or a subscription, your audio and the returned text pass through the service on Cloudflare. With Free with your key, only the one key check when you add your key, and, during the 10 free days with AI cleanup on, your transcripts and Words pass through it. It also hosts the downloads on R2. It sees your IP address and request details when you use the service or download blabe. Where it processes and keeps data is covered by its own policy.
  • Polar (privacy policy, buyer terms) is the merchant of record. It processes your payment, tax and receipts, and issues and checks license keys. It uses Stripe to process card payments.
  • Hostinger (privacy policy) hosts the server in Lithuania that runs this website. It also hosts the support mailbox; where it keeps that mail is covered by its own policy.

The companies that carry or transcribe your audio (Cloudflare, Microsoft and xAI), and, for your transcript, the AI cleanup providers with AI cleanup on, decide how long they keep it and where they process it, under their own policies, and we don’t promise that they keep nothing. These companies may process data in the United States and other countries. With Free with your key, Microsoft or xAI transcribes your audio on your own account instead of blabe’s, under your agreement with it.

Training

We never train AI models on your audio, your transcripts or your words, and we don’t build models from them. blabe has no model of its own to train. Here is where each company that receives your audio or text stands on training, checked on October 16, 2026:

  • Microsoft (transcription): its Speech service documentation says, “Microsoft does not use customer data to improve its Speech models” (Speech service encryption of data at rest). MAI-Transcribe 2 runs through that service’s fast transcription (MAI-Transcribe 2 guide), though the statement doesn’t name the model.
  • xAI (live transcription, and backup transcription): its API data and security FAQ says it “never trains on your API inputs or outputs without your explicit permission,” and it says it doesn’t train on the requests it keeps for 30 days. blabe hasn’t given that permission.
  • AI cleanup provider: it doesn’t train models on the requests blabe sends it.
  • Backup AI cleanup provider: it doesn’t train models on the requests blabe sends it.

Not training is a separate question from keeping data. xAI keeps API requests for 30 days by default, and the backup AI cleanup provider may keep abuse monitoring logs for up to 30 days, as described above.

How long data is kept

  • Audio on your Mac: in memory only, until it is transcribed successfully or you quit blabe. Never on disk.
  • Transcripts on your Mac: the last one in memory until you quit. Never on disk. Whatever you paste stays in the app you pasted it into.
  • Text read to learn from your edits: in memory only, until blabe stops watching, at most about 30 seconds after the paste. Never on disk. Learned fixes and Words stay with your other Words until you delete them. Declined suggestions are kept as one-way hashes, up to the 500 most recent.
  • Audio, transcripts and request records on blabe’s transcription service: audio and transcript text are not stored; the service holds them in memory only while passing them on. The device, request and usage records described above are kept on the service, as are any license, subscription, allowance-period and trial records. Device records stay while the service keeps the license or trial they belong to; when a device’s place is freed, its record is deleted. Each request’s audio length and cost are deleted after 30 days; its fingerprint, time and outcome stay while the service keeps the license or trial it belongs to, so that a retry is never charged twice. A retry that goes to Azure after a live xAI failure counts as a new dictation. With a subscription, the allowance each request used and the period it counted against are deleted 400 days after the request, long enough to cover a yearly billing period. For a trial or a subscription, some of these records can’t be deleted early without letting a Mac start a second trial, or a license be charged twice or get a fresh allowance. Those stay for the periods above, even if you ask us to delete them. A daily job deletes the diagnostic records once they are seven days old. Deleted records can remain in Cloudflare’s automatic database recovery history for up to 30 days. License and subscription records (the license and customer IDs from Polar and the devices activated on them) stay while the license is in use and are deleted 12 months after it was last used, with these exceptions. They stay longer while a device’s activation or a request’s outcome is unconfirmed, for example when the service never learned whether a dictation went through, so that nothing is charged twice. The service doesn’t settle an unconfirmed outcome on its own, so those records have no automatic deletion date. After they’re deleted, a minimal record of the license, holding only a one-way hash of it and no license ID, customer ID or sign-in token, stays with its request records until every one of those requests is confirmed and 400 days old; a request that’s never confirmed keeps it with no end date. If we have turned a license off, that minimal record and its request records stay while it remains off, so that signing in again can’t turn it back on. For a license already in use before this schedule began, the 12 months count from no earlier than the day it began, because earlier use wasn’t recorded, so its records can stay up to a year longer. Sign-in sessions are deleted 30 days after they expire or are signed out. A trial’s start and end, with a scrambled form of the Mac’s trial ID, stay for as long as we offer trials, so each Mac gets one trial; the allowance a trial used is deleted 30 days after it ends. With Free with your key, the one-way hash of your xAI team or Azure subscription ID, with when its 10 free days started and end, stays for as long as we offer Free with your key, so each provider account gets one free window.
  • Audio sent to xAI: blabe’s service keeps none of it. xAI keeps API requests and responses for 30 days by default to check for abuse, then deletes them, according to its API data and security FAQ.
  • Support emails: 30 days after the case is closed.
  • Diagnostic attachments: 30 days after the case is closed.
  • Website server logs: deleted after at most 30 days.
  • Website visit statistics: kept for 12 months, then deleted. They don’t include your IP address.
  • Payment and tax records: kept, by Polar and in our own records, for as long as tax law requires, generally up to seven years. The 30-day period does not apply to these.
  • Sign-in and IDs on your Mac: your sign-in token and this Mac’s random IDs stay in your Keychain until you delete them. Freeing a device's place in your Polar customer portal releases its seat. The trial identifier stays in your Keychain, and the service keeps its hashed trial record, so that each Mac is limited to one trial. See the uninstall guide.
  • Sign-in and IDs on a Windows PC: the device and trial IDs stay in Windows Credential Manager until you delete them, even after you uninstall either copy of blabe. Uninstalling the copy from the download page deletes the sign-in token; uninstalling the Microsoft Store copy keeps it. Signing out deletes the sign-in token too. The trial identifier stays, and the service keeps its hashed trial record, so that each PC is limited to one trial. See the Windows uninstall guide.
  • Data held by the other companies named above: under their own policies.

If a dispute or a legal obligation needs a support case kept longer, we keep only what is needed until it is resolved. Copies of deleted email may remain in our email provider’s backups for a while after we delete them.

Security

blabe sends your audio and license details only over HTTPS, and it keeps your license record in the Keychain on a Mac, or in Credential Manager on Windows. No system is completely secure, and we can’t promise that nothing will go wrong.

Your choices

  • Press Esc during a recording to cancel the dictation, and nothing is pasted. With live transcription, the audio from before you pressed Esc has already gone to blabe’s service and xAI (with Free with your key, to your own xAI account).
  • In Settings → Dictation, set Transcription to Azure, and your audio goes only to Microsoft Azure, never to xAI. The default is xAI (live). The change applies from your next dictation (more).
  • Turn AI cleanup off in Settings → Dictation, and no language model sees your text.
  • With Free with your key, click Remove key in Settings → Account to delete your key from this device.
  • Turn off Learn from my edits in Settings → Words, and blabe stops reading the field after a paste to learn your fixes.
  • Free a device's place and cancel your subscription in your Polar customer portal.
  • Delete blabe and its Keychain entries by following the uninstall guide.
  • On Windows, sign out, uninstall blabe and delete its Credential Manager entries by following the Windows uninstall guide.
  • Choose whether to send us a support bundle.
  • Turn on Global Privacy Control or Do Not Track in your browser, and this website won’t count your visits.

Your rights

To use any of the rights below, email support@blabe.dev. We will reply within the time the law requires. To find your data, we may ask for your Polar order reference or the email address you used at checkout. We never need your full license key, so don’t send it. If you only used the free trial, its records on the service aren’t linked to your name or email, so we can’t match them to you; they’re kept only for the periods under How long data is kept. We will handle your request for any personal data we hold, including any that blabe’s transcription service keeps. What the service keeps is described above. For data the other companies named above hold under their own policies, you may need to ask them too.

California

We don’t sell or share your personal information. If you live in California, the California Consumer Privacy Act gives you these rights:

  • to know what personal information we collect, use and disclose about you;
  • to delete the personal information we hold about you;
  • to correct inaccurate personal information;
  • not to be treated differently for using these rights.

EU and UK

If you are in the EU or UK, the GDPR or UK GDPR gives you the right to access your data, to have it erased or rectified, to object to how we use it, and to complain to your supervisory authority. We handle these requests the same way, by email. If you ask us to delete your data, we delete what we can. We keep only the records described under How long data is kept that stop a Mac from starting a second trial, a payment from being counted twice or a license we turned off from being turned back on, and anything the law requires us to keep.

Legal bases

Where the GDPR applies, we rely on these legal bases: contract (transcribing your audio through blabe’s transcription service when you use a trial or a subscription, and rewriting the transcript when AI cleanup is on, the license and your subscription, and answering your support emails), legitimate interests (security logs on this website, keeping the transcription service secure and preventing its abuse, and troubleshooting it with the diagnostic records described above), and legal obligation (payment and tax records). The service’s device, request, license, trial and usage records rely on contract (checking your access and applying any limit) and legitimate interests (preventing abuse and counting a retry only once). With Free with your key, checking your key, rewriting your transcripts during the 10 free days and keeping the hashed account record that counts them rely on contract (providing Free with your key) and legitimate interests (preventing a second free window on the same account). Cloudflare’s built-in request logging is turned off; the diagnostic records described above are stored separately. Cloudflare processes connection data, such as your IP address, to deliver and protect the service under its own privacy policy; that relies on our legitimate interest in running the service securely. Counting visits and button clicks on this website with Umami, and passing a launch link’s tags to Polar’s checkout and the Microsoft Store, rely on our legitimate interest in knowing which pages people use and which launch posts lead to downloads and subscriptions.

Children

blabe is not meant for children under 16, and we don’t knowingly collect data from them. If you think a child has sent us data, email us and we will delete it.

Changes to this policy

If we change this policy, we will post the new version here with a new date. For a significant change, we will say so at the top of this page.

Contact

blabe, support@blabe.dev. We aim to reply within two business days. This is a goal, not a guarantee.