Privacy Policy
Last updated: April 16, 2026
markdownalds is designed as a local-first macOS app for opening, reading, and editing Markdown files. Based on the current implementation, the app processes the Markdown documents you choose to open on your Mac and does not include its own account system, cloud sync service, advertising SDK, or analytics SDK.
The app reads Markdown files from your device and writes edits back to local files only when you choose to save.
The current app implementation does not include user accounts, ads, telemetry, or analytics services.
Remote image URLs are intentionally not fetched by the app. They are shown as privacy-preserving placeholders instead.
When you use markdownalds, the app may access the following information on your device:
This information is used to render the reading interface, support raw and structured views, and save your edits back to disk when requested.
http:// or https:// links in the current implementationThe app uses the macOS file importer to let you choose which Markdown file to open. It does not browse your files automatically without your action.
If you edit an opened file and choose Save, the app writes the updated text back to that local file on your device. The bundled sample document can be edited for preview but is not written back to disk.
Local image references may be loaded from disk to render image blocks. Remote image references are intentionally hidden for privacy and are not fetched in the current app behavior.
The app keeps the currently opened document, render mode, section selection, and any unsaved edits in local app memory while you use it.
Your document content remains in the original files you control. If you save edits, they stay in that file until you change or delete it. If you do not save, the unsaved in-memory draft is not intended as a long-term cloud-backed copy.
The current implementation does not provide its own hosted backend for Markdown documents, tags, or reader state.
Based on the current codebase, markdownalds does not bundle third-party analytics, advertising, or cloud-processing SDKs inside the app itself. If you distribute the app through a platform such as the Mac App Store, that platform may have its own independent data practices, which are governed by its own policies.
If the app later adds networked features such as sync, account services, remote image loading, telemetry, or external APIs, this privacy policy should be updated to describe those behaviors before release.
If you have questions about this privacy policy or want it updated for a production release, please reach out.
Email: crusade.ray@gmail.com