Why Your Markdown Drafts Stay Private
Most online viewers upload your text to a server. This one renders in your browser — here is how to verify that, and why it matters.
Where the work happens
Rendering markdown is a self-contained job: take text, produce formatted HTML. There is no reason for a server to hold your text to do it, and every reason not to. This site reads the file locally, parses it with a JavaScript markdown engine, and draws the result in the page. Nothing is sent anywhere, because there is no upload step and no server copy to make.
Verify it in fifteen seconds
Press F12 to open Developer Tools, go to the Network tab, then use the tool normally. You will see the page's own files and, if advertising is live, an ad request — but never your document. Or simply turn off your Wi-Fi and keep using the site: it still works, because nothing has to cross the wire. A tool that uploads cannot do that.
Why "zero data retention" is not enough
You may have read the phrase "zero data retention". It only promises that a copy is deleted afterwards. The file still travelled across the network, and you have no idea who was listening on the way, whether the AI or hosting provider trained on it, or whether their systems were breached a month later. Deleting your copy does not un-send it. The only way to be certain text stays private is to never transmit it in the first place.
What this means in practice
Use the tool on a network you do not trust — a café, an airport, a hotel — and it genuinely does not matter, because there is nothing crossing the wire to intercept. Work on a confidential draft at your desk, on a plane, or behind a firewall, and the file stays on your machine the entire time. The convenience of a web page without the exposure of a web upload.
Who else could see an uploaded draft
When a document is uploaded to a converter, it passes through at least one server, and often more than one: a load balancer, an application server, maybe a queue and a log. Each is a place a copy could be retained, indexed or breached. Even a service that promises to delete the file immediately cannot promise that no copy was ever made, because it does not control every hop. The only copy you can be certain about is the one that never left your disk.
What "private" costs
Nothing. Rendering markdown in the browser is the same amount of work on your machine as on a server, and the page has already been downloaded. There is no trade-off to make between privacy and speed here, because the slow path — upload, render, download — is not the one being used. The local route is both more private and usually faster, which is why it is the default rather than a premium option.
What this site can and cannot promise
It can promise that the document you paste or open is parsed on your device and never sent to a server, because there is no code path that would do it. It cannot promise anything about the page you are reading it on if that page itself was tampered with, which is a general property of the web, not of this tool. For ordinary drafts, notes and internal docs, the local-only guarantee is the whole of what matters, and it is verifiable in fifteen seconds.