1. Your documents never leave your browser

In short
  • Your writing is processed in your own browser tab and is never uploaded.
  • Drafts sit in localStorage on your device, not in a database of ours.
  • We keep plain server access logs. We run no analytics cookies and no ad trackers.
  • Google Fonts is the only third-party request any page makes.

Nothing you type is uploaded

Everything you type into the editor is handled by JavaScript inside your browser tab. That covers drafts, previews and exports alike. On our side there is no upload endpoint, no document database and no account system.

So we do not receive, store, read or transmit anything you write. This is not a promise we are asking you to trust. It is how the software is built.

Why your draft is still there tomorrow

The editor saves your draft to your browser's localStorage. That is a small storage area on your own device. Only this website, in this browser, is allowed to read it.

It is not a cookie. It is never sent along with network requests, and we have no way to reach it from outside your machine.

The one case to watch

Careful: localStorage belongs to the browser profile, not to you. On a shared or public computer, the next person to open mdeditor.tw in that profile can read your saved draft. Clear the site data when you finish, or write in a private window.

2. The little we do process

What the access log records

Like almost every website, our server writes a standard access log each time your browser asks for a page. A line in that log holds your IP address, the date and time, the URL requested, and your browser's user-agent string.

We use those logs for three narrow jobs: spotting abuse, diagnosing errors, and seeing how much load the site is under. They are rotated and deleted on a routine schedule. They are tied to no identity, because there are no accounts to tie them to, and they are never sold or shared for marketing.

What we do not collect

  • No analytics cookies. The site sets none at all.
  • No advertising trackers. No page carries a third-party ad or profiling script.
  • No account data. There is no sign-up, so there is no profile and no password to leak.

The only state the site keeps in your browser is functional. That means your saved draft and your interface preferences, such as language, both of which live in localStorage.

3. One third-party request: Google Fonts

Why the request happens

In the interest of full honesty, one request does leave your browser. The site loads its typefaces from the Google Fonts network, so your browser fetches the font files directly from Google's servers when a page loads.

What Google receives

Google receives your IP address and the standard technical details that come with any web request. Google states that Fonts requests are not used for advertising profiles. You can read Google's own privacy notes on Fonts and judge for yourself.

This is the only third-party request the site makes. Your document content is never part of it.

4. Your choices

Three switches you hold

Everything this site stores is under your control, and none of the switches are on our side:

  • Delete your drafts. Clear this site's data in your browser settings, usually under "Cookies and site data", or clear localStorage from the developer tools. This wipes saved drafts for good, so export anything important as a .md file first.
  • Block the font request. A content blocker or firewall rule on fonts.googleapis.com and fonts.gstatic.com stops your browser contacting Google. The site still works, and simply falls back to your system fonts.
  • Browse privately. In a private or incognito window, localStorage is thrown away when you close it. That is handy when the machine is not yours.

Tip: You can verify all of this yourself in about a minute. Open your browser's network panel, then type a few lines in the editor. Nothing goes out while you write. The only outbound call is the font fetch on page load.

5. Changes and contact

How we would announce a change

If we ever change how the site handles data, by adding a new third-party service for example, we will update this page before the change takes effect. The effective date at the top moves with it, and material changes are noted prominently on the site.

Where to ask a question

Questions about this policy, or about privacy on MD Editor generally, are welcome at [email protected]. The contact page covers what else that address is good for.

This page deals with privacy only. The terms of service set out the conditions the editor is offered under, and about MD Editor explains who runs the site and how it stays free.

Try the Editor

Try the Editor