Marker Privacy Policy

Overview

Marker ("the Application") is a markdown viewer and editor available as a desktop app (via Tauri, for Windows, macOS and Linux) and as a browser app. This policy applies to both, and explains exactly what data the Application handles, where it lives, and what happens to it.

What data is processed

Marker processes only the file content you explicitly open:

• Markdown file content — the file(s) you open via Open File or Open Folder are read into memory to render and edit them, and written back to disk when you save.
• Folder listings — when you open a folder, Marker lists that folder's top-level .md filenames to populate the sidebar. It does not read subfolders, and does not read the content of files you haven't opened.

Marker does not collect your name, account information, usage analytics, or any data about you as a person.

Where data is stored

Nowhere but the file itself. Marker holds the open file's content in memory while you view or edit it, and writes it back to the same path on save. There is no separate local cache, no application database, and nothing synced to the cloud.

Desktop app: filesystem access

On desktop, Marker's Rust backend exposes file list/read/write as direct commands rather than restricting itself to a pre-declared folder allowlist — the standard approach for a local editor that needs to open whatever file or folder you point it at through the native OS dialog. In practice this means Marker only ever touches files and folders you explicitly select yourself; it never scans your filesystem on its own, and has no command that lists or reads a path you haven't chosen through Open File or Open Folder.

Browser version: File System Access API

The browser build at markdw.netlify.app uses the browser's own File System Access API in Chrome and Edge, which is permissioned per-site and requires a user gesture (you clicking Open File / Open Folder) before Marker can see anything — Marker adds no access on top of what that browser API already grants. In browsers without that API (Firefox, Safari), Marker falls back to a standard file picker for opening, and saves by triggering a normal file download rather than writing back to the original file.

What Marker accesses, and why

Rendering and sanitization

Every markdown file you open is converted to HTML with marked and then passed through DOMPurify.sanitize() before it's displayed — with no exception for any file, since the whole point of Marker is opening files from disk that could contain anything. This protects you from a malicious or malformed markdown file executing script content when rendered.

Third parties and analytics

Marker does not use analytics, telemetry, crash reporting, advertising, or any third-party service that receives your data. The browser build is hosted on Netlify, which serves the static application files; it does not see the content of the files you open, since nothing about your file content is ever sent to it.

Authentication and payments

Marker has no accounts, sign-in, or payment functionality. It is free and open source.

Data retention and deletion

Marker itself retains nothing beyond the open file's content in memory during your session, which is cleared when you close the file or the app. Deleting or editing the file through Marker (or any other program) is the only way its content changes; uninstalling the desktop app removes the application itself and nothing else, since it kept no separate storage.

Your rights

Because all data stays on your device — or, in the browser, in memory and wherever you choose to save a download — and Ziduri never receives or stores it, there is no remote copy of your data for us to access, export, or delete.

Changes to this policy

If a future version of Marker changes what it accesses or stores — for example, adding an optional update checker or cloud sync — this policy will be updated first, and the version and effective date above will change accordingly.

Contact

Questions about this policy can be sent through the contact page or by opening an issue on the GitHub repository.