Privacy Policy

The short version

Your files never leave your device. MarkdownForge performs all file conversions locally in your web browser using client-side JavaScript and WebAssembly. We operate on a strict Zero Data Retention basis — we do not receive, store, log, or have any access to the contents of the documents you convert.

Client-side processing mechanics

When you drop a file onto the converter, it is read directly in memory by the browser’s FileReader API. The conversion libraries (such as Mammoth.js, SheetJS, PapaParse, pdf.js and Turndown.js) then run entirely within your browser tab. The resulting Markdown is rendered in the on-page editor. At no point is the file, or its converted output, transmitted to our servers — because for these formats, there is no server involved at all.

The one exception: URL to Markdown

The URL-to-Markdown feature is the only function that makes a network request. Because browsers block cross-origin requests (CORS), fetching a third-party web page requires a proxy. We use a stateless Cloudflare Edge Worker that:

• Receives the URL you asked to convert;
• Fetches that page’s HTML and returns it with CORS headers;
• Stores nothing — no logs of the URLs you submit, no copies of page content, and no association with you.

The actual Readability extraction and Markdown conversion still happen in your browser after the HTML is returned.

What we don’t collect

• No accounts, names, or email addresses are required to use the tool.
• No copies of your files or converted Markdown.
• No selling or sharing of personal data — we don’t have any.

Analytics & cookies

We may use privacy-respecting, cookieless analytics to understand aggregate traffic (for example, page views per converter). These analytics never capture the contents of your files. Your theme preference (dark/light) is stored in your browser’s LocalStorage on your device only.

Contact

Questions about this policy? Reach us at hello@markdownforge.app or via our contact page.