Add to Chrome
Privacy

Privacy Policy

Markside is a local Markdown viewer. Link Snapshot content is carried in the link fragment and rendered in your browser, not stored by Markside.

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
  • Can create a Link Snapshot 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 Link Snapshot contents on a Markside server
  • Does not collect usage analytics or telemetry
  • Does not track browsing history
  • Does not use cookies
  • Does not use the Link Snapshot fragment for analytics or server-side processing

Link Snapshots

A Link Snapshot 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 snapshot content. Anyone who obtains the complete link can decode and read it; Link Snapshots are not encrypted.

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.

Link Snapshot 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. The complete URL is limited to 16,000 characters.

A Link Snapshot 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, 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)

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 questions or concerns, email your@email.com.