Privacy Policy

Effective date: 27 September 2026 · Applies to the Markdown Browser Tools browser extension and this website.

The short version

The extension collects no data. Not usage analytics, not crash reports, not file contents, not file names, not anything. There is no account, and the extension initiates no network traffic on your behalf.

The website counts visits in two ways. Cloudflare, which serves the site, counts without cookies. Google Analytics counts with them, and where the law requires it asks you first; both are set out under This website below. Otherwise the site keeps nothing of yours until you deliberately send it something. The feedback form stores the message you write and any images you attach, so that a person can read them; using it is optional.

What the extension does with your files

The extension renders Markdown documents — local .md files, local folders, and Markdown served by websites you have allowed — inside your own browser, on your own machine. Reading, rendering, search and folder listings all happen locally. Nothing you open, and nothing about what you open, is transmitted anywhere.

What the extension stores

Your settings (theme, layout, language), your list of recent and pinned files, and your chosen folder are stored using the browser's extension storage, on your device only. Uninstalling the extension removes them. We cannot see them; they never leave your machine.

Permissions, and why they are asked for

  • Access to file URLs — lets the extension render local .md files and folder listings. It is a browser-level switch you control, and the extension works only with what you open.
  • Access to websites — lets the extension render a Markdown document a website serves you. It checks the page's content type and leaves every ordinary web page untouched. You can narrow site access at any time in your browser's extension settings.
  • Storage — the local settings described above.
  • Scripting — used to load the bundled diagram (Mermaid) and math (KaTeX) renderers into a page only when a document actually needs them. All code ships inside the extension package; nothing is fetched from a server.

This website

markdown-browser-tools.com is a static informational site. Two things count visits.

Cloudflare, which serves the site, counts requests at its edge and, through a small script of its own, page views. Neither uses cookies or identifies you: Cloudflare's Web Analytics is built not to.

Google Analytics counts with cookies. It sets Google's _ga cookies in your browser and receives the address of each page you read, a random visitor identifier, and the usual browser and device details; Google Analytics 4 does not log or store IP addresses. Whether it runs depends on where you are. In the European Economic Area (including the EU's overseas regions), the United Kingdom and Switzerland, where the law asks for consent first, a banner asks and nothing is sent to Google unless you accept. Elsewhere it runs unless you decline, which Cookie settings in the footer lets you do at any time, or unless your browser sends a Global Privacy Control signal, which counts as declining for as long as it is on. Declining after it has run removes the _ga cookies and stops it in every tab of this site you have open. Where you are is read from your connection by Cloudflare as it serves the page and kept for a day in one cookie of the site's own, mbt-consent-region, which records only whether your region asks, never the country. Your answer is kept in a second, mbt-consent-choice, with a copy of the same name in your browser's local storage; it records which answer you gave and when, and nothing that identifies you. An acceptance lasts six months, after which you are asked again where the law asks first; a decline lasts until you change it. Both last only as long as your browser keeps this site's storage — some browsers, Safari among them, clear it after about a week without a visit, and the site then treats you as a new visitor. The site's earlier cookie for the answer, mbt-consent, is read once — a decline in it is carried over — and then removed.

The site sets no advertising cookies, and nothing it collects is used for advertising. How Google handles this data is described in How Google uses information from sites or apps that use its services.

The feedback form

Sending feedback is optional, and it is the one place where something you provide is stored on a server. When you submit the form we keep:

  • the message you wrote, and any images you attached;
  • the email address you gave, if you chose to give one — used only to write back to you;
  • the interface language you were reading in, and which page you came from;
  • your browser's user-agent string, which usually names the browser and its version, because a bug report is far easier to act on with it;
  • a salted, one-way hash of your IP address — never the address itself. It exists so that one sender cannot flood the form, and it cannot be turned back into an address.

This is stored on Cloudflare, in the same account that serves this site. It is not shared, not used for marketing, and not used to build a profile of you. Ask through the form and we will delete a submission.

The form is protected by Cloudflare Turnstile, which checks that a person rather than a script is submitting; Turnstile processes data as described in Cloudflare's privacy policy.

Changes

If any of the above ever changes — for example, if an optional licensing check is added for paid features — this policy will be updated first, with the change described plainly, and the extension's store listing will disclose it.

Contact

Use the feedback form. It reaches a person, and it is the only contact channel we publish — an address on a public page collects far more junk than mail from readers.