Policy
Privacy policy
What Mermaid Live Editor keeps in your browser, what limited usage data may leave it, and which actions can contact third-party services.
By mermaid-live-editor.com maintainers · Updated
Scope and responsible site maintainers
This policy applies to mermaid-live-editor.com and is maintained by mermaid-live-editor.com maintainers. Questions and corrections can be submitted through the site-specific contact guidance. The upstream mermaid-js/mermaid-live-editor contributors do not operate this deployment and are not responsible for its data practices merely because their open-source work is used here.
Diagram content and local storage
Normal editing, rendering, history, preferences, and export happen in your browser. The app uses browser storage to remember editor state, history, theme, language-related choices, and interface preferences. This information remains on the device until you clear site data or replace it through the editor.
Share links encode diagram state in the URL fragment, the part after #. Browsers
do not send that fragment to the site in a normal page request. Anyone who receives the full
share URL can decode its diagram, so treat the link as containing the diagram itself.
Optional analytics
A deployment may enable privacy-focused Plausible analytics. When enabled, the app can send the page origin, path, search parameters, and coarse interaction events such as diagram type, export format, line-count range, or render-time range. Analytics code deliberately excludes the URL fragment and does not send Mermaid source text.
Analytics may be blocked by your browser or content blocker. The editor continues to work when analytics is unavailable.
User-initiated external requests
The editor can contact another service only when a feature or URL you choose requires it. For example, importing a GitHub Gist or a remote code/configuration URL sends a request to that host, and following an external product link opens that provider. Those providers receive the information ordinarily included in a web request and apply their own privacy terms.
Service worker and downloaded files
The progressive web app service worker may cache application assets on your device so the editor loads reliably. Exported PNG, SVG, PDF, and MMD files are created for download or copy through browser APIs and are not uploaded by the normal export flow.
Your choices
- Clear this site's storage in your browser to remove locally saved editor data.
- Use browser controls or a content blocker to limit optional analytics.
- Do not use remote imports or external links when you do not want those hosts contacted.
- Remove sensitive content before sharing a diagram URL or public issue.
Policy changes
Material changes are published on this page with a revised update date and remain reviewable through the public project history.