Privacy policy

Marknote is designed to keep your data on your machine. This policy explains what data the app does and does not handle.

What we don't do

• We do not collect, transmit, or analyse your notes or your usage automatically.
• We do not have telemetry, analytics, or automatic crash reporting. There is no account unless you join the Marknote Sync beta.
• We do not embed third-party trackers, ad networks, or analytics SDKs.

Network requests the app makes

Marknote works offline. These are the only times it talks to the network, and what each request carries:

• At launch — one request to our sync service asking whether the Sync beta is open to new sign-ups. It carries no identifier and nothing about you or your notes; the answer is kept in your settings file so the app is stable offline.
• When you open the theme marketplace — the app fetches the listing from marknote.md, and a theme file from marknote.md when you install one. The same as visiting marknote.md/themes in a browser; nothing about you is sent. See Themes and the theme marketplace below.
• When you use git — with the remote you configured. See Git integration below.
• When you turn on Marknote Sync — your encrypted notes travel to and from our sync service. See Marknote Sync below.
• The Microsoft Store checks for updates on its own schedule; that is Windows, not Marknote.

What is stored locally

The following data is stored on your computer only. Nothing is transmitted to us or to third parties.

• Application settings — at %LocalAppData%\Marknote\settings.json. Includes your theme choices, window size and position, editor font size, recent files list, list of currently open tabs, custom keybinding overrides, journal folder path, your custom CSS (if any), and the cached answer to the launch-time beta check.
• Workspace configuration — at <your-folder>\.marknote.json for any folder you open as a workspace. Contains pinned files and other per-workspace overrides. A folder you have bound to Marknote Sync also carries <your-folder>\.marknote\sync-state.json: which vault it belongs to and what has been synced, no note content.
• Installed themes — at %LocalAppData%\Marknote\themes\, one folder per theme, plus a cached copy of the marketplace listing so the gallery opens offline.
• Installed plugins — at %LocalAppData%\Marknote\plugins\. See Plugins below.
• Crash log — at %LocalAppData%\Marknote\crash.log. Appended only when an unhandled exception fires inside the app. Never transmitted; used by the in-app crash-recovery dialog and optionally attached to a Send Feedback issue if you choose to include it.
• Auto-save backup files — alongside your documents as *.marknote-backup. Removed automatically after a successful save.

Send feedback (opt-in)

The in-app About → Report a bug / Request a feature dialog opens a pre-filled GitHub issue in your browser. It is opt-in and visible: you see exactly what gets attached before you submit.

• What is attached when "Include diagnostics" is ticked — Marknote version, OS edition, .NET runtime version, your settings-file path, your active vault path, and the tail of crash.log (if present). All of this is pre-rendered into the GitHub issue body so you can review and edit it before posting.
• What is never attached — your notes, file contents, file names other than the active vault path, GitHub credentials, or anything outside the diagnostics block.
• Submission opens a GitHub issue at github.com/wearemarknote/issues. The issue itself is public; do not include sensitive information in your description.

Marknote Sync beta list (opt-in)

If you choose to join the beta list at marknote.md/beta, we store what you type into that form — nothing else. The desktop app never submits anything itself; the in-app button simply opens that page in your browser.

• What we store — your email address, the optional free-text note you write, whether you arrived from the app or the website, and the date you signed up.
• Why — to email you an invitation when there is a build to try. Consent, which you can withdraw at any time.
• What we do not do — no newsletter, no marketing, no analytics on the list, and we never share or sell it.
• How long — until the beta ends or you ask us to remove you, whichever comes first.
• Removal — email support@marknote.md and we delete your entry.

Joining the list does not create an account and gives nobody access to your notes.

Marknote Sync (private beta, opt-in)

Marknote Sync is in private beta for invited testers. It is off until you sign in and bind a folder to a vault; a Marknote that never signs in sends nothing to the service.

• Your notes — encrypted on your device, with a key derived from a passphrase only you hold, before anything leaves it. The service stores and relays that ciphertext; it cannot read your notes, and neither can we. If you lose the passphrase we cannot recover them.
• Your account — the email address you sign up with, a password or passkey, and the confirmation that the address is yours. Used to sign you in and to send account mail (confirmation, password reset, a changed address) — nothing else.
• What the service needs to sync — an identifier for each vault, each document and each device, and version markers, so devices can tell what has changed. Document names and contents are inside the ciphertext.
• Health counters — the app reports how many conflicts and how many decrypt failures it met, as counts, so we can see the service is working. No content, no file names.
• Where — the service runs on Microsoft Azure. Its own privacy statement governs the platform.
• Leaving — you can delete your vault and account from the account pages; the service purges the ciphertext.

Third-party components

Marknote uses Microsoft Edge WebView2 to render the "Rich" preview mode. The WebView2 runtime is a Windows system component; its behaviour is governed by the Microsoft Privacy Statement.

All other preview libraries — KaTeX, Mermaid, and highlight.js — are bundled with the application and loaded from local disk only. They do not make network requests during render.

Plugins

Marknote 1.4.0 introduced support for user-installed plugins. Plugins are arbitrary JavaScript code authored by third parties and stored at %LocalAppData%\Marknote\plugins\. They run inside a sandboxed embedded browser, but a malicious plugin could still misuse any surface Marknote exposes to it. Only install plugins from sources you trust. Plugin authors are responsible for their own data-handling practices; we do not audit plugin code or its behaviour at runtime.

Themes and the theme marketplace

A theme is a single file of colours — no code. Themes you install live at %LocalAppData%\Marknote\themes\. Opening Settings → Themes → Get more themes fetches the marketplace listing from marknote.md, and installing one downloads that theme's file from marknote.md and checks it against the checksum in the listing before anything is written. Neither request carries anything about you; they are the same as visiting marknote.md/themes in a browser. An Install in Marknote link on a web page opens the app, which downloads and checks the theme and then asks you before installing it. A theme's optional stylesheet is checked so that it cannot fetch anything or run anything; a theme that tries is refused.

Git integration

When you use the built-in git features (init, fetch, push, etc.), Marknote sends and receives data with the git remote you have configured for that repository. We do not see or store the contents of those communications. Authentication credentials are managed by the operating system's credential store, not by Marknote.

File system access

Marknote reads and writes only files that you explicitly choose through the operating system's standard file pickers, drag-drop, or by selecting a folder as a workspace. The application does not scan or index files outside of folders you have opened.

Children's privacy

Marknote does not knowingly collect personal information from anyone, including children under 13.

Contacting us

For questions about this policy: privacy@marknote.md

Changes

We may update this policy from time to time. The "Last updated" date at the top reflects the current version. Material changes will be highlighted in the app's release notes.