Processed in memory. Never stored.

What happens to your files

• Your file is uploaded over HTTPS to a serverless function, converted in that function’s memory, and the Markdown is returned in the same response.
• Nothing is written to disk, a database, object storage, logs, or a cache. When the response is sent, the memory is released.
• When you paste a URL, we fetch that page once from our servers, convert it, and discard it in the same way.
• Downloads and .zip bundles are assembled in your browser from the response. They never round-trip back to us.

What we do keep

• Rate-limit counters. A hashed count of requests per IP address for up to 24 hours, so the free plan’s limits can be enforced.
• Anonymous usage analytics. Which page was visited, which input formats and presets were used, and whether a conversion succeeded. No file names, contents, or personal identifiers. We use Vercel Analytics, which does not use cookies.
• Error reports. If a conversion crashes, we record the error type and stack trace so we can fix it. Request bodies are stripped before the report is sent, so your document never leaves with it.
• A counter in your browser. The “conversions left today” number is stored in your browser’s local storage and is never sent to us.

Who runs the servers

The service is hosted on Vercel. Conversions run in Vercel serverless functions, and Vercel’s own edge network terminates HTTPS. Vercel’s infrastructure logs may record request metadata such as timestamps, paths and IP addresses, as with any hosting provider. They never include your file contents.

Your choices

There is no account and no cookie banner because there is nothing to opt out of beyond your browser’s own settings. If you have a question about any of this, email hello@mdfileconvert.com.