LoveMarkDown Privacy App privacy policy NgSense

Document / 01

Privacy policy for a local-first Markdown editor.

LoveMarkDown is designed around user-selected local files. It does not automatically upload Markdown content, file names, or full local paths.

Privacy highlights

The App Store privacy story in four points

These points summarize the privacy policy before the full legal text.

  1. 01

    No automatic document upload

    Markdown content, file names, and full local paths are not automatically uploaded.

  2. 02

    Limited anonymous analytics

    Matomo analytics uses predefined product events and coarse attributes, not document text or source URLs.

  3. 03

    User-initiated feedback

    Feedback is sent only when the user chooses Help -> Send Feedback. Contact information is optional.

  4. 04

    When network is used

    Remote images may load during preview or export. Web-to-Markdown fetches a page only when you start conversion for a URL you entered.

Policy

LoveMarkDown Privacy Policy

Summary

LoveMarkDown is a macOS Markdown editor built for local writing, live preview, local image references, and export. The app is designed so ordinary writing and preview work can happen with user-selected local files.

This policy explains LoveMarkDown’s privacy behavior in plain language.

Local Markdown documents

LoveMarkDown does not automatically upload Markdown document content.

LoveMarkDown does not automatically upload file names or full local file paths.

LoveMarkDown does not automatically attach Markdown content, file names, or full local file paths to analytics or feedback.

The app is intended to work with local files that the user opens, edits, saves, or exports.

Local images and relative paths

LoveMarkDown can preview relative local images referenced by the current Markdown document. This is part of the local document workflow. Referenced image files are not automatically uploaded by LoveMarkDown.

Local document archives and recovery

Direct 1.3.2 can open and create supported MDZ and Markdown ZIP archives containing documents and local image assets. Archive contents, passwords, filenames and full paths are not automatically sent to product analytics or NgSense.

Optional password protection is performed locally using standard archive encryption. The app does not automatically remember passwords or provide password recovery. Local recent-file identities and access bookmarks may be retained to reopen documents. Recovery checkpoints are stored locally; protected archive recovery retains encryption. Creating or converting a copy does not itself upload it anywhere.

Remote image references

A Markdown document can also reference images hosted on the internet. Previewing or exporting a document with remote image references may request those images from the referenced hosts. A separate Web-to-Markdown conversion is not required for these image requests.

The image host receives the image request. This is different from automatically uploading the Markdown document, its filename or its complete local path to NgSense. Use local image assets when you want the document’s images to be available without fetching them from a remote host.

In 1.3.2, HTTPS images are enabled unless remote images are turned off for that MDZ file; the off choice is remembered locally. Unencrypted HTTP images are blocked until you choose to load them from the document notice. Closing or keeping the notice blocked does not send those HTTP image requests. Reopening the archive requires a new HTTP choice.

Anonymous analytics

LoveMarkDown may use anonymous Matomo analytics for product usage measurement and release validation.

Analytics are limited to predefined product events and coarse-grained attributes, such as feature category, export format, theme, language, delivery mode, or source type.

Analytics do not include Markdown document content, file names, full local file paths, source URL text, clipboard content, or feedback message text.

User-initiated feedback

Feedback is sent only when the user chooses Help -> Send Feedback and submits the form.

Feedback message text is provided by the user. The app does not automatically attach Markdown document content, file names, full local paths, clipboard content, or screenshots.

Contact information is optional. If the user enables follow-up contact and enters contact text, that contact value is sent with the feedback message so NgSense can reply.

The shared feedback receiver distinguishes LoveMarkDown feedback from other NgSense products with app_name=LoveMarkDown.

Web-to-Markdown network access

LoveMarkDown may include a Web-to-Markdown feature. This feature requests network access only when the user enters a URL and asks the app to convert that web page into Markdown.

The network request is made for the URL entered by the user. Ordinary local Markdown editing, preview, saving, and export do not require Web-to-Markdown network fetching.

No account requirement

LoveMarkDown does not require an NgSense account for the core Markdown editing workflow.

Features not claimed by this policy

This policy does not describe cloud sync, AI writing, collaborative editing, account systems, or mobile apps because LoveMarkDown is not positioned around those features.

Contact

For privacy or support questions, use the NgSense contact page:

Contact NgSense