Last updated: July 27, 2026

Privacy Policy

Glimmd works locally inside Chrome. It does not sell, share, or transmit Markdown documents, browsing history, personal data, or preferences to the developer's servers.

Information handled

Glimmd handles the content and URL of the Markdown document the user opens solely to render it, create an outline, search it, refresh that exact document, and resolve local navigation. Processing happens on the device. Document content is not persistently stored and is not available to the developer.

Reader preferences are stored in the local Chrome profile using chrome.storage.local. To restore the reading point after reopening a document, Glimmd keeps a limited recent-reading record for up to 120 documents for no longer than one year. Each record contains an identifier derived from the normalized document URL, the selected view, an approximate numeric text offset, a scroll ratio, and an update time; it does not contain document text. Highlights and comments created by the user are stored separately in the extension's local IndexedDB and include the selected passage, short context, position, dates, and hashes used to match the file and version safely. Highlights also store the chosen color; comments store the text written by the user. They can be managed from the reader or deleted by document from Preferences. Preferences can also download a local JSON backup for one, several, or all documents. That backup contains selected passages and comments but no complete local paths; Glimmd does not upload it. A sibling-file list may be cached in session storage for 30 seconds. Uninstalling Glimmd removes its local data. None of this information is available to the developer or sent to developer servers.

The first-use notice stores only its version and acknowledgement date in the local Chrome profile. It contains no document or annotation content, is not included in preference exports, and is not sent to the developer. Local storage is not a backup and can be lost; see Important information and limitations.

Local files and network requests

File URL access must be enabled explicitly in Chrome. Folder navigation is limited to Markdown files in the exact parent folder of the open document. Remote images are blocked by default. When enabled by the user, HTTPS images are requested directly from their origin without a referrer. The origin may receive normal connection data such as the IP address.

External services

The optional support button opens Ko-fi only after a click. No document or preference is sent to Ko-fi by Glimmd. Ko-fi may process normal connection, cookie, and payment information under its own policy. Glimmd does not receive donation data.

The creator link opens Root Digital CR only after a click. It does not transmit documents or preferences.

If the user voluntarily opens a support request, GitHub processes the information the user submits under its own privacy terms. Support requests are public. Glimmd never attaches documents or preferences automatically.

Limited Use disclosure

The use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Information is used only to provide or improve Glimmd's visible Markdown reading features; it is not sold or transferred for advertising, profiling, or unrelated purposes, and it is not made available for human reading through developer systems.

Security and changes

Glimmd includes no analytics, advertising, remote executable code, or runtime CDN dependencies. Material changes to this policy will update the date on this page and the extension changelog.