Privacy Policy

What Markside does

• Reads Markdown files from your local file system (file:// URLs) and renders them in the browser
• Stores your opened folder handle and recently accessed file handles in your browser's local IndexedDB so you don't have to re-authorize on every visit
• Stores aggregate action counts, active-day dates, and prompt state in local extension storage to schedule an optional Chrome Web Store review request
• Can create a Share Link whose complete Markdown content is compressed into the URL fragment after you confirm sharing

What Markside does not do

• Does not upload or store local file contents, paths, or Share Link contents on a Markside server
• Does not send usage analytics or telemetry to Markside or third parties
• Does not track browsing history
• Does not use cookies
• Does not use the Share Link fragment for analytics or server-side processing

Share Links

A Share Link places the Markdown and file basename after the # in the URL. Browsers do not send URL fragments in normal HTTP requests, so Markside's server receives the request for the viewer page but not the link content. Anyone who obtains the complete link can decode and read it; Share Links are not encrypted.

A Share Link is a frozen copy taken at creation time, not a live view — it does not update if the source file later changes.

The viewer does not use analytics. Markside's hosting provider may retain ordinary request logs for the /s page, such as IP address and user agent, according to its infrastructure policies. HTTPS images embedded in shared Markdown are requested directly from their original hosts, which can observe those image requests.

Share Link is an experimental Beta for successfully saved Markdown. Unsaved changes must be written to the local file before Markside creates a link. Local images, relative document links, and wikilinks remain Markdown text but are unavailable in the rendered viewer. Links work best under approximately 4,000 words; very long links may not paste cleanly into every chat, email, or browser address bar, and a document too large for a browser to decode cannot be shared as a link at all.

A Share Link has no encryption, password, access control, expiry, or revocation. Experimental links have no permanent compatibility promise. Complete URLs may remain in browser or synced history, chat or email history, clipboard managers, screenshots, and recipient-controlled systems.

Data stored locally

The following data is stored in your browser's IndexedDB or local extension storage, on your device only:

• The FileSystemDirectoryHandle of the last folder you opened (used to restore the file tree)
• FileSystemFileHandle references for recently accessed files (used to restore write access)
• Display and editing preferences
• Active Reviews that you have not cleared
• Aggregate action counts, action categories, active-day dates, first-use time, and prompt state used only to schedule the optional Store review request

This data never leaves your device.

Permissions

• file:// access — Required to read local Markdown files. Must be enabled manually via "Allow access to file URLs" in extension settings.

Contact

For feedback, questions, or concerns, email hello@zhuge.app.