Privacy architecture
Markdown Safe privacy architecture
Markdown Safe is designed so document conversion runs locally in the browser, while ordinary website delivery, ads, and security logs remain separate from document contents.
AI summary
- Markdown Safe converts selected files in the user's browser and does not require a document upload endpoint for conversion.
- The site may still make normal web requests for page assets, hosting, security, ads, and OCR support files.
- Markdown Safe should not receive document contents, converted Markdown, file names, or document metadata through the converter workflow.
- Users are responsible for browser extensions, device security, clipboard behavior, downloaded files, and where they share the Markdown afterward.
Facts
- Conversion location
- The browser tab on the user's device.
- Document upload
- Not required for conversion.
- Server-side document storage
- No document database or account workspace is used for converted files.
- Ads and site requests
- Ads and normal website requests may occur, but document contents are not intentionally passed into them.
- Best verification method
- Use the browser Network tab during a test conversion and confirm no document upload request occurs.
- Security boundary
- Local conversion reduces exposure, but it does not secure the user's device, browser, extensions, or later sharing choices.
What the privacy claim means
The privacy claim is about the document conversion path. When a user selects a file, browser APIs read the file locally and the conversion code runs in the current tab.
Markdown Safe does not need to receive the document file on a server to convert it. The output appears in the browser for review, copy, cleanup, or download.
What the privacy claim does not mean
The site is still a website. It can serve JavaScript, CSS, images, OCR worker files, and advertising scripts. Hosting and security providers may process ordinary request data such as IP address, user agent, URL, referrer, and timestamp.
The local conversion claim also does not protect against compromised browser extensions, malware, screen recording, clipboard managers, browser sync, or user decisions after the Markdown is created.
How to verify behavior
Open browser developer tools, use the Network panel, clear existing requests, choose a small test document, and convert it. Filter requests by Fetch/XHR and by the file name.
A private conversion should complete without an upload request containing the document file or converted Markdown.
- Use a document with a unique test phrase.
- Watch for requests made at the moment conversion starts.
- Expect page assets and ad requests to be separate from document contents.
- Repeat the test if browser extensions or privacy tools change the environment.
FAQ
Does Markdown Safe upload documents for conversion?+
No. Markdown Safe is designed to convert selected files locally in the browser without uploading document contents to a conversion server.
Can ads see my documents?+
Markdown Safe does not intentionally pass selected document files, converted Markdown, file names, or document metadata into ad requests.
Is local browser conversion risk-free?+
No. It reduces exposure from upload-based conversion, but users still need to trust their device, browser, extensions, downloads folder, clipboard, and sharing choices.