Your documents.
Your privacy, explained.

01 Scope

This policy applies to the Markdown Plus Chrome extension. It explains what information the extension handles, where that information is stored, and when a network request may occur.

02 Information processed on your device

When you choose to open or edit a supported local document, Markdown Plus processes its content, file name, and local file URL or path in Chrome to provide viewing, navigation, editing, saving, printing, and export features. This processing happens locally in the browser. Document content is not sent to a server operated by the Markdown Plus developer.

03 Information stored by the extension

• Reader, editor, explorer, theme, and plugin preferences are stored in chrome.storage.sync when available. Chrome may sync them through the Google account signed in to Chrome. If sync storage is unavailable, the extension uses chrome.storage.local. A failed sync write does not cause an automatic switch to local storage. The extension also keeps the last complete settings snapshot in chrome.storage.local, so it can display those settings while synchronized data is incomplete.
• Custom theme descriptions, colors, and background image references may sync with preferences. Background image files you choose remain on the current device in browser IndexedDB and are not uploaded to the developer. Image files do not sync; you may need to choose a local image again on another device.
• If recent-file history is enabled, local file URLs, file names, and last-opened times are stored only in chrome.storage.local on the current Chrome profile. Recent-file paths are not placed in sync storage.
• When supported and after you select a file for saving, Chrome may allow the extension to retain a file handle in browser IndexedDB. This lets later saves target the same file. Chrome remains responsible for file-system permission prompts and controls.

04 Network requests

Markdown Plus does not upload local document content to a developer-operated service. Some workflows can still make network requests:

• A document can reference remote images or other resources. Chrome may request those resources from the host named in the document, which can receive standard request information such as your IP address and browser headers.
• An exported HTML or Word-compatible document containing math may reference KaTeX CSS from cdn.jsdelivr.net. Opening that file while online may contact jsDelivr. The styles used to display math within the extension are bundled with it.
• External links are opened only when you choose to follow them.

Those third-party services process requests under their own privacy policies. Markdown Plus does not receive data from those requests.

05 Sharing and sale

Markdown Plus uses the information described in this policy only to provide its stated document-workspace features, in accordance with the Chrome Web Store User Data Policy, including its Limited Use requirements. The developer does not sell, rent, or use this information for advertising, credit decisions, or profiling, and does not receive document content, local history, file handles, or background images. Chrome may sync preferences through your Google account as described above.

06 Permissions

• file:///* lets the extension recognize, read, and display local files.
• storage stores preferences and recent-file history as described above.
• offscreen supports reading local documents and directory listings for the Files explorer.
• downloads saves HTML, Word-compatible documents, and Mermaid SVG/PNG exports. Editor Save writes only to the original file you explicitly connect; it does not download a fallback copy.

07 Your controls

You can disable recent-file history and clear its entries in Markdown Plus settings. In Settings → Themes, saving a replacement background image or changing to a non-image background removes the previous image from this device after the theme is saved successfully. Deleting a custom theme removes its local background image. Resetting extension settings also clears the local theme-image store. If image cleanup fails, an unused image may remain until you clear the extension's site data or uninstall it. You can revoke file access in Chrome, clear the extension's site data, or uninstall the extension. Uninstalling removes extension-managed browser storage according to Chrome's behavior; your original documents and exported files remain wherever you saved them.

08 This website

The developer does not add analytics, advertising, forms, or cookies to this website. The site saves only your light or dark theme choice in your browser’s local storage and does not send that choice to the developer. GitHub Pages hosts the site, so GitHub may process technical request data under the GitHub General Privacy Statement.

09 Changes to this policy

Material changes will be published on this page with an updated effective date. The repository history provides a public record of revisions.

10 Contact

For privacy questions or support, open an issue in the Markdown Plus GitHub repository.