Last updated July 9, 2026
Privacy policy
Markdown Safe is built around a simple boundary: conversion happens locally in your browser, and your document files are not uploaded to Markdown Safe for processing.
The core privacy promise
Markdown Safe is designed so document conversion runs locally in your browser. When you choose a DOCX, PDF, TXT, HTML, or RTF file, the browser reads the file and conversion code runs in the current tab.
Markdown Safe does not require a document upload endpoint for conversion, does not store your documents in an account workspace, and does not use document contents for analytics, advertising, model training, or resale.
Files and document contents
Your selected files are processed by browser APIs on your device. We do not intentionally receive, inspect, copy, index, sell, or store the file contents you convert.
The converted Markdown is generated in the browser for you to review, copy, or download. You are responsible for deciding where you save or share the output after conversion.
Information we may receive
Like most websites, our hosting provider may process ordinary delivery data such as IP address, user agent, requested URL, timestamp, referrer, and basic security logs to deliver the site, prevent abuse, and operate the network.
If you contact us by email, we receive the information you choose to send. Do not send confidential documents, passwords, private keys, health records, legal files, financial records, or other sensitive materials through email.
Analytics, ads, affiliates, and payments
Markdown Safe may display Google AdSense ads or other sponsorships outside the local conversion workflow. Ad providers may process ad-request data such as page URL, IP address, browser/device information, cookies, identifiers, and ad interactions to deliver, measure, limit, or personalize ads.
Ad providers should not receive your document files or converted Markdown from the converter. We do not pass file contents, file names, converted text, or document metadata into ad requests.
If Markdown Safe later adds paid plans, affiliate links, sponsorships, or privacy-respecting ads, those features should stay separated from the local file-conversion path.
A payment provider, affiliate partner, sponsor, or ad provider may process limited information needed for that specific feature, such as billing details, click attribution, or ad delivery data. Those partners should not receive your document files from the converter.
Cookies and local storage
Markdown Safe may use local browser storage for convenience features such as interface preferences. Local storage stays in your browser unless you clear it or your browser syncs it through your own settings.
Google AdSense and other ad partners may use cookies or similar technologies for ad delivery, fraud prevention, frequency capping, measurement, and personalization where allowed. We do not need cookies to upload or store converted files because files are not uploaded for conversion.
Security model
Local browser conversion reduces exposure because files do not need to leave your device for processing. It does not make your device, browser, network, extensions, downloads folder, clipboard, or later sharing choices risk-free.
You are responsible for keeping your device, browser, extensions, operating system, and network secure, and for reviewing converted output before using it.
Children and restricted users
Markdown Safe is not intended for children under 13 or for anyone barred from using it by applicable law. If you use the site on behalf of an organization, you are responsible for having authority to do so.
Changes to this policy
We may update this policy as the product changes. The latest version posted on this page controls your use of Markdown Safe after it is posted.
Contact
Questions about this privacy policy can be sent to privacy@markdownsafe.com. Do not include document files or sensitive personal information in your message.