Privacy Policy
Last updated: November 14, 2026 — effective November 2, 2026
mdai is a local-first desktop application. Your documents are plain Markdown files on your own disk. By default, they never leave your computer. They are sent elsewhere only if you choose to: when you use an AI feature with a cloud provider, or when you connect another AI tool. This page lists exactly what leaves your computer, and why.
Who is responsible
mdai is made and published by Goran Jovanović. Questions about this policy, or requests to delete data described below, go to support@mdai.me.
What mdai stores on your device
Your documents stay in folders you choose, as ordinary Markdown files. Application settings are stored in a local configuration file. AI provider API keys and cloud OAuth tokens are stored in your operating system's secure keychain, never in plain text and never on our servers.
What mdai sends to us — the complete list
There are exactly four things, and all of them are described in full here. They travel in five requests: the fourth — registering a device — is one request when you activate and another when you deactivate. The same four are listed, as those five requests, together with the address each one goes to and why mdai is not open source in the first place, on the openness page. The version from the Mac App Store makes none of them; what it sends instead is described under Mac App Store version below.
These four go to us. Publishing a document to your own site is not one of them — that traffic goes from your computer to the server you entered, and is described under Publishing to your own site.
1. Starting your trial
The first time you run mdai, it sends a single value to license.mdai.me: a salted SHA-256 hash of your operating system's machine identifier. That hash is the entire request — there is no name, no email address, no file name, and no document content in it. We store the hash together with the date we first saw it, so that reinstalling the application does not restart the free trial. The hash cannot be reversed back into your machine identifier, and it is not linked to any other information about you.
2. Checking for revoked license keys
mdai downloads a public list of hashed license keys that have been revoked after a refund or chargeback. This is a download: nothing about you is sent in it. Your key is checked against that list on your own device. The key's own validity is also proven offline, by checking its signature — that part never needs a server.
This download happens at most once every 30 days, and only on a copy that has been activated with a licence. It is not made while you are in the trial, and it is never made more often than that, whatever else you do in the application.
3. Checking whether a newer version exists
After the window opens, and at most once every 24 hours, mdai downloads a small file from dl.mdai.me that lists the current version. This is a plain download of a fixed address. The request carries nothing that identifies you or your machine: no account, no licence key, and not even the version of mdai you are running. Which version you have is compared with the list on your own device, not by us. The only thing the request states about the software is the name and version of the update component itself, in the ordinary browser-style user-agent header (tauri-plugin-updater/2.10.1).
If a newer version exists, mdai shows a bar offering it. Downloading and installing happen only when you click — never in the background, and never without telling you. If you are offline, or if the check fails for any reason, nothing appears and nothing is retried until the next day.
The version of mdai installed from the Microsoft Storedoes not include this update component at all — it is built without it, because the Store delivers updates itself. That version therefore never makes the request described in this section.
On Linux, only the AppImage makes this request. The Flatpak and the Arch Linux package (mdai-bin) never do — they are updated by your package manager instead.
As with any request over the internet, our provider (Cloudflare) briefly processes the connection itself, including your IP address, to deliver the response. We do not build profiles from it. This applies to every request to us described on this page.
4. Registering this device against your licence
A licence covers up to three devices, so we have to count them. When you press Activate, mdai sends three values to license.mdai.me: a SHA-256 hash of your licence key, the same salted machine hash described in point 1, and one word for the platform — macOS, Windows or Linux. That is the entire request.
Your licence key itself is never sent — only its hash, which cannot be reversed back into the key. There is no name, no email address, no computer name, no file name and no document content in the request, and none of those is stored.
We keep, per licence: the machine hash, the platform word, and the date each device was activated. That is all — it is what the device list inside mdai shows you, and there is nothing behind it that you cannot see there.
This request happens only when you press Activate, Deactivate, or Show my devices. It is not repeated, not scheduled, and never made in the background. Once a device is registered, mdai works offline indefinitely; it does not check in again. Pressing Deactivate sends the same two hashes once more, to free that device's slot.
Show my devices, in Settings → License, sends exactly the same three values as Activate and shows you what comes back: the device list for your licence. If your device is still on that list — the usual case — no new slot is taken. If its slot was freed in the meantime, by pressing Deactivate for it from another device, this registers the device again and takes a free slot, exactly as Activate would; if no slot is free, nothing is registered and you only see the list. Like the other two, it is sent only at the moment you press it.
What we run, and what it holds
We operate a small licensing service: a Cloudflare Worker with a key-value store. It holds hashed machine identifiers with their first-seen dates, license records, the device registrations described in point 4 (hashed key, hashed machine, platform, date), and hashes of revoked keys. It has never received and cannot receive your documents.
No analytics, no tracking, no crash reports
The application contains no analytics, no usage tracking, and no crash-reporting that sends data to us or to anyone else. Nothing about how you use mdai — which files you open, what you write, how long you work — is ever transmitted.
This website
The mdai application collects nothing about you. This website (mdai.me) uses Umami Cloud to count visits. It loads a small script from Umami, sets no cookies and does not track you across sites. We see which pages are visited, from which country, browser and device, which website referred you, and the campaign link you came through (UTM), so we know what is useful. It honours Do Not Track. Nothing from the website is connected to your notes or to the app.
AI features (bring your own key)
AI features are optional and work only if you supply your own API key for a provider you choose (Anthropic, Google Gemini, DeepSeek, or OpenAI). When you use an AI action, the selected text or document content is sent directly from your device to that provider, under your account and their privacy terms. mdai does not proxy, log, or store this traffic, and we never see your keys or your content.
The first time you use AI with a particular provider, mdai asks for your permission before it sends anything. The block names the provider and says what will be sent — your instruction with the whole document, the section you selected, or, for Ask vault, the passages found in your notes with their file names. Nothing goes to that provider until you press Allow and send. The permission is recorded on your own computer, in mdai's settings file, and is never sent to us. You can withdraw it at any time in Settings → AI; the next AI request then asks again. Ollama runs on your computer, so it is never asked.
Local AI (Ollama). If you choose Ollama as your provider, mdai talks only to Ollama running on your own computer (127.0.0.1). Nothing leaves your device through mdai.
Ask vault. To answer a question about your notes, mdai finds the most relevant passages using a local model on your computer (Ollama). Those passages, with their file names, are then sent to the AI provider you selected. With Ollama, they never leave your computer. With a cloud provider, they are sent to it exactly like any other AI action.
Connecting other AI tools (MCP)
Off by default. When you turn it on in Settings, mdai opens a connection point on your own computer only (127.0.0.1). It cannot be reached from the network. Tools you connect with your access token, such as Claude Code, can list and read the Markdown notes in your open vault and propose edits. mdai never applies a proposed edit without your Accept. What a connected tool does with what it reads is governed by that tool’s own terms.
Publishing to your own site
mdai can send a finished document to a site you run — WordPress or Ghost. The feature is optional, and it is added in version 1.3.6. When you open the publish dialog, mdai asks your site which categories and tags exist and what your account may do. Your document and images are sent only when you press the publish button. There is no background publishing, no scheduled publishing, and no retry you did not ask for.
Your content and images go directly from your computer to the server you entered — never through mdai.me. The post is built on your machine and sent straight to that address. We run no proxy for it, we log none of it, and we never see the address, the credentials or the post. The address you type in is stored in mdai's local settings file; the password or application token is stored in your operating system's system keychain, never in the settings file and never on our servers.
Images stored as files in your vault are uploaded to that same server at the moment you publish, and to nobody else — this applies to WordPress and Ghost. Images embedded directly in the document (data: images) are not uploaded separately; they go out inside the post's HTML. Images that are already web links (https://) stay links to wherever they are hosted; mdai does not download or re-upload them.
Links that point to files on your computer keep their text, but the link itself is removed before the post is sent.
mdai remembers which images it has already sent to each of your sites, so updating a post does not send them again. That list stays on your computer and holds a fingerprint of each image, its address on your site and which of your accounts it belongs to, never the image itself, your password or the text of your document.
If an upload fails, you are asked before the post is sent — skip that image and continue, or cancel the publish. When you cancel, no post is sent — but images that were already uploaded before you cancelled stay on your server.
mdai also keeps a small publishing log on your own disk. Each line records the time, the id of the account you used, the platform, the action (new post, update, or image upload), whether it succeeded, the server's status code when there was one, and the post id when the server returned one. It holds no document content, no path, no password, no token and no licence key. The post id and the address of the site you published to are also written into the document's own front matter, so that publishing the same document again updates that post instead of creating a second one.
Purchases
Purchases are processed by our merchant of record, Paddle, which handles payment and license key delivery under its own privacy policy. mdai never sees your card details. We receive the information Paddle passes on to issue your license, such as the email address you bought with.
Mac App Store version
The copy of mdai installed from the Mac App Store is built differently. It does not register a trial, does not download the list of revoked keys, does not check for a newer version (the App Store updates it), and does not register devices against a licence. None of the four things above is sent.
The free trial and the purchase are handled by Apple, under your Apple Account and Apple’s privacy policy. mdai checks them on your own device, through the App Store. mdai never sees your payment details, and Apple does not tell us your name or email address.
Using mdai on Windows or Linux. If you also want mdai on Windows or Linux, Settings → License has a button for that. Only when you press it, mdai sends two things to license.mdai.me: the email address you type in, and the record of your App Store purchase that Apple signs (it identifies the purchase, not you). We use them to issue a licence key and send it to that email address. We keep the email address, the purchase identifier, the key and the date — so that asking again gives you the same key.
Refunds. If Apple refunds your purchase, the App Store notifies our licensing service, and a key issued for that purchase is revoked.
When the trial ends
After the free trial expires, mdai locks editing only. Reading, copying, exporting, and opening your folders keep working, and your files remain ordinary Markdown that any text editor can open. We never hold your documents hostage.
Changes
If this policy changes, the updated version will be published at this address with a new date.