Privacy

The short version

The same is true of the text Blurt produces. Transcripts are written to a file on your machine and stay there. We hold no copy. We cannot read your transcripts, and we cannot recover them for you if you delete them.

Polish, which cleans up your dictated text, also runs locally using a model on your machine. It makes no API call and sends nothing anywhere. Meeting mode captures system audio on your machine and follows exactly the same rules as normal dictation.

What does leave your Mac

We would rather state this plainly than bury it. Once you have activated a licence, Blurt makes these network requests and no others on your behalf:

• Licence checks to evolveratechnologies.com. When you first enter a key on a Mac, Blurt activates it by sending the key, your operating system name, the Blurt version you are running, and a device label taken from your computer's hostname so you can tell your own devices apart. After that, about once a week, it sends only the key and that Mac's activation ID to confirm the subscription is still valid. Nothing else.
• Activation, to the same endpoint. When you first enter a licence key on a device, Blurt sends the same information to claim that device's slot against your licence.
• Update checks to downloads.theblurt.app, which serves a signed version manifest and the update itself. You can switch this off in Settings. Copies of Blurt installed before this moved to our own domain still check downloads.evolveratechnologies.com, which keeps serving the same files.
• Model downloads from huggingface.co, once, when you choose an engine. The models are public builds of Whisper and Parakeet fetched straight from the model host, so that request goes to them and not to us. After it, dictation works with the wifi off.
• Feedback to feedback.evolveratechnologies.com, and only when you press Send feedback. It carries what you typed and the email address you chose to give, and it is never opened on its own.
• Optional usage sharing to analytics.theblurt.app, from Blurt 1.2.3, and only if you switch it on. It is off when you install Blurt and off after an update. Turned on, it sends counts and timings so we can see how often Blurt is used and how transcription performs — never your words. The next section is the full account of it.

Optional usage sharing, from Blurt 1.2.3

When it is on, the app sends app-open events, transcription outcomes — completed, empty or failed — and meeting-completion events. Each event can carry the audio duration in whole seconds, a word count, the processing time, the app version, the operating system, a time-based session identifier, and a randomly generated installation identifier. These are measurements of usage, not recordings and not the words you spoke.

The installation identifier represents an installation, not a named account. We do not connect it to your email, your licence key or your purchase. It is pseudonymous rather than anonymous, and we would rather use the accurate word: an identifier that is stable for one install is not the same thing as a guarantee that nothing can ever be linked.

Events go to our own relay at analytics.theblurt.app, hosted on Cloudflare, which forwards the permitted fields to Google Analytics 4. The relay accepts a fixed list of fields and rejects anything else outright, so a field we never intended to collect cannot arrive by accident. It does not forward your IP address or your User-Agent to Google. Cloudflare does necessarily process the IP address of the incoming request in order to answer it — we have turned off the Worker's own application logging, and that is not the same as claiming a hosting provider handles no network metadata at all. Advertising data use and advertising personalisation are explicitly denied on every event we send.

Sharing uses that local installation identifier rather than any browser cookie. Turning it off stops new collection, discards events still queued when they are next checked for dispatch, and removes the local identifier. A request already in flight may still complete. Turning it back on creates a new identifier, unconnected to the old one. Turning it off, or resetting your settings, does not delete events Google has already received. Activity from before you opted in is never backfilled. Delivery is best effort: time spent offline and deliveries that fail are simply missing from the reports.

• Never included in usage sharing: your audio, your transcripts, what you dictated about, window titles, the contents of your screen, your licence details, your email address, or raw error messages.

What we never collect

Stated explicitly, because privacy policies usually only tell you what is taken. We do not collect, receive, or store:

• Your audio, or any recording of it
• Your transcripts, or any text you dictate
• The content or topics of your dictation. Optional usage sharing sends numerical word counts and duration, never the words or audio.
• Your keystrokes
• The contents of your screen, or the apps you dictate into
• Your files or documents

What the app reads on your Mac, and never sends

Two optional features read things outside the microphone to get your spelling right. Both are switches in Settings, both are off unless you turn them on, and neither sends anything anywhere.

• Context awareness reads the title of the window you are dictating into and the text field you are focused on, so names and jargon already on screen are spelled the way they appear.
• Learn your project names reads the names of git repositories and branches under your development folders, and the names of your installed apps, and uses them to spot words it would otherwise mangle. It reads names, not file contents.

What we hold about you

If you buy Blurt, we hold your email address, which plan you bought, whether your subscription is active, your licence key, and which devices that key is activated on.

If you turned on usage sharing in the app, there is also a second, separate set of records: pseudonymous usage events held in Google Analytics under a random installation identifier. They are not joined to your purchase, and nothing in them identifies you by name or email. We are listing them here because a policy that says the purchase record is everything would now be wrong.

We run no database of our own. Our licensing server is a stateless proxy: it passes your licence key to Polar, returns the answer to your app, and keeps nothing. The record of your purchase lives with Polar.

We process your licence and subscription data to give you the software you paid for, which is performance of our contract with you. We check for updates on the basis of our legitimate interest in keeping installed software working and secure. Usage sharing is processed on the basis of your consent, given in the app, and you can withdraw it there at any time.

Cookies

If you accept, Google Analytics 4 sets two cookies in your browser: `_ga`, which lasts two years, and `_ga_` followed by our measurement ID, which also lasts two years. Both hold a randomly generated identifier that lets Google count you as one returning visitor rather than several new ones. Neither carries your name, your email, or anything you have dictated.

Your choice is remembered in local storage under `blurt-analytics-consent`, not in a cookie, so declining leaves you with an empty cookie jar. That single entry is the only thing this site stores on a declining visitor's device, and it exists so we do not ask you again on every page.

You can change your mind at any time. `Cookie settings` at the bottom of any page reopens the question, and choosing Decline stops any further collection. Clearing your browser's site data for theblurt.app removes everything described here.

There are no advertising cookies, no remarketing tags, no session recording and no A/B testing tool. Google's advertising and personalisation signals are switched off explicitly in our configuration rather than merely left unused.

This choice covers this website only. It does not switch anything on or off inside the desktop app, which has its own separate control described under Optional usage sharing. Accepting here leaves the app exactly as it was.

This website

With your consent, this website uses Google Analytics 4 to count visits, see which pages people read and which searches bring them here. That is the whole purpose. There is no tag manager, no advertising tag, no remarketing, no session recording and no A/B testing tool.

The website and the desktop app each have their own opt-in, and neither answer carries over to the other. Decline here and nothing about your visit reaches Google, whatever you chose in the app. Accept here and the app still shares nothing unless you separately turned that on in Settings. Both start off.

There are no third-party embeds. The fonts are served from this site rather than from a font CDN, so loading a page does not tell a font host your IP address, whatever you answered. The only other outbound links are the ones you click: the checkout at Polar, the download, and our company site.

• What Google receives if you accept: the pages you view on this site, roughly where you are from your IP address, your browser and device type, and how you arrived — a search, a link, or directly. IP anonymisation is on.
• What it never receives: anything you dictate. Audio and transcripts stay on your Mac and are not part of any website measurement, because the website never has them in the first place.
• Our hosting provider and our CDN keep their own short-term request logs, as every web host does, in order to serve pages and absorb attacks. Those logs contain IP addresses. We do not build profiles from them and we do not join them to anything else, but we do not control their retention and would rather say so than pretend the internet works without them.
• Legal basis: your consent, under the ePrivacy rules and Article 6(1)(a) of the GDPR. You can withdraw it as easily as you gave it, from `Cookie settings` at the bottom of any page.

Where your data is

Evolvera Technologies is based in Pakistan, so the little we hold — your email, your plan, your licence key and its activations — is handled from there.

Polar, our payment processor and merchant of record, operates from the United States and holds the record of your purchase. If you accepted analytics, Google also processes your visit data in the United States. If you are in the European Union or the United Kingdom, both therefore involve your data leaving your country, under the safeguards set out in their own terms — and the analytics half of that happens only because you agreed to it, and stops the moment you withdraw.

If you turned on usage sharing in the app, those events are handled by Cloudflare, which runs the relay and processes the request from wherever its network answers you, and then by Google, which processes them in the United States. Both handle that data under their own published terms, which is the honest limit of what we can tell you: we have not negotiated a region guarantee, and we are not going to invent one here.

Nothing you dictate is involved in any of this. Your audio and transcripts never leave your Mac, so they never cross a border at all.

Payments

We never see your card details. Not the number, not the expiry, not the security code. Payments are processed by Polar, which acts as our merchant of record, meaning Polar is the seller of record for your purchase and handles payment processing and sales tax.

From Polar we receive your email address, the plan you bought, your subscription status, and your licence key. Cancellations, invoices and card changes all happen in Polar's customer portal, not with us.

Who else is involved

• Polar processes payments and issues licence keys, and holds your customer record as described above.
• Google Analytics measures traffic on this website if you accepted the cookie banner, and separately receives desktop usage events if you turned on usage sharing in the app. These are two different Google Analytics properties, and each is fed only by the switch you actually agreed to. Google acts as our processor for both and holds the data under its own terms.
• Cloudflare hosts the relay at analytics.theblurt.app that carries desktop usage events, and processes the IP address of each request in order to answer it. If you never turn usage sharing on, your app never contacts it.
• Our hosting provider serves this website and the licensing endpoint your app talks to. Like any web host, it processes the IP addresses of incoming requests in order to answer them.
• The release manifest and the installer are served from downloads.theblurt.app, and from downloads.evolveratechnologies.com for copies installed before the move. Both are the same storage behind two names. Fetching a file tells that host your IP address, as fetching any file from any host does.

How long things are kept

Licence and subscription data is kept for as long as your licence is active, and afterwards for as long as Polar needs it to meet tax and accounting obligations.

Website analytics, if you accepted them, are held by Google with event-level and user-level data both set to 14 months, counted from your last visit. The two cookies in your browser expire after two years, or immediately if you clear site data or press Decline in Cookie settings.

Desktop usage events, if you turned sharing on, are held in a separate Google Analytics property with event-level data set to 2 months and user-level data set to 14 months. Both settings were checked on 9 September 2026. Those limits govern the detailed records; the aggregate reports Google builds from them are not deleted on the same clock, so totals can outlive the individual events behind them. Turning sharing off in the app stops anything new arriving — it does not erase what has already been received.

Everything Blurt creates on your Mac stays on your Mac, and you can delete it yourself at any time. Your transcript history lives in history.jsonl inside Blurt's folder under ~/Library/Application Support/. Use the app's own History controls to delete entries rather than removing files by hand — older builds wrote a history.json, and a file by that name on your disk may be a leftover rather than your current history. Because we never had a copy, we cannot restore what you delete.

Your rights

You can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete it. For your purchase and licence data — your email, plan, subscription status, licence key and its activations — your email address is enough for us to find the record, and these requests are quick to answer.

Usage-sharing records are different, and we would rather be straight about it than promise a button that does not exist. They are stored under a random installation identifier with nothing linking them to your email, so an email address alone does not let us find them. If you want them dealt with, turn sharing off in the app first, which stops collection and removes the local identifier, then email us; if you can still supply the installation identifier, we can ask Google to delete the matching records, and if you cannot, we will tell you so rather than claim we have.

Email us and we will respond within 30 days. Deleting your licence data ends your ability to activate Blurt on new devices, so we will confirm before doing it.

Depending on where you live, you may also have the right to object to processing, to restrict it, or to complain to your local data protection authority.

Children

Blurt is not directed at children. We do not knowingly collect information from anyone under 13, or under 16 in the European Union. If you believe a child has provided us with information, email us and we will delete it.

Changes to this policy

If we change what Blurt sends or what we hold, we will update this page and change the date at the top before the change ships. For anything that meaningfully affects your privacy, we will also say so in the app's release notes.

Updated on 9 September 2026 for Blurt 1.2.3, which introduces optional desktop usage sharing. It is off unless you turn it on, and the change is called out in that version's release notes as well as here. This page was updated before the release, not after it.

Contact

Evolvera Technologies, contact@evolveratechnologies.com.