Your document content stays private by default.
Last updated: August 27, 2026
The interactive editor processes documents on your device by default. This policy explains the limited cases where data is sent to a service and describes the analytics and advertising technologies that help operate the site.
The interactive editor renders and stores documents locally in your browser.
No sign-up, so we hold no names, emails, or profiles.
Analytics and advertising services are disclosed below and operate separately from document processing.
Your documents stay on your device
The core interactive editor processes the markdown you write or paste in your browser. Normal editing, preview, local saving, export, and share-link creation do not upload the document body to our servers.
- Local storage — documents are auto-saved to your browser's
localStorageso your work survives a reload. This data lives only on your device; clearing browser storage removes it. - Share links — when you create a share URL, your document is compressed and encoded into the link itself. We do not store a copy; recipients decode it locally. Shared sessions disable analytics, but advertising may still load. Browsers do not include the
#share=document fragment in HTTP requests. Read the technical explanation of how private share links work. - Rendering & export — the editor's preview, copy, and export controls run entirely in your browser. Your markdown is not transmitted to our servers.
Analytics
We do not require accounts or build user profiles from document content. To understand aggregate usage, the site may load:
- Google Analytics — usage information such as pages visited, approximate location, device and browser type. Google may receive IP addresses and use cookies or other identifiers to provide and secure this service. See Google's Privacy Policy or opt out with the GA Opt-out Add-on.
- Plausible Analytics — aggregate page-view measurement configured without cross-site advertising profiles.
We do not intentionally send markdown document bodies to either analytics service.
Advertising
Google AdSense is the only advertising programme we have applied to, and that application is still under review. No ads are being served on the site today. The AdSense script loads on every page except embedded tool frames, because Google needs it in place to review the site; if the application is approved, ads may begin to appear without further notice here.
Google and its advertising partners may place and read cookies in your browser and may use web beacons, IP addresses, device information, or other identifiers. They may collect, share, and use this information to serve personalized or non-personalized ads, limit ad frequency, measure performance, and prevent fraud.
Learn how Google uses information from sites that use its services, change your Google ad settings.
Cookies
Browser storage keeps your local documents and theme preferences. Analytics and advertising providers may set their own cookies or use other identifiers when their services load.
You can block or delete cookies through your browser settings. Blocking third-party cookies does not prevent the core editor from working.
Your privacy controls
You can use browser privacy settings, content blockers, and the provider opt-out links above to limit third-party analytics and advertising. Before serving Google personalized advertising in a region where Google requires it, we will configure a Google-certified consent management platform.
Children’s privacy
The site is a general-audience developer tool and is not directed at children under 13. We do not knowingly collect personal information from children.
Data security
Because normal editor use keeps documents on your device, the primary security boundary is your own browser. The site is served over HTTPS, and rendered output is sanitized with DOMPurify to protect against cross-site scripting.
Changes to this policy
We may update this policy from time to time. Changes will be posted on this page with an updated date; continued use of the site constitutes acceptance of the revised policy.
Questions? Write to us at contact@markdownviewer.org.