Privacy Policy

Last updated: 2026-08-14

MONA is a desktop font manager. This policy explains what data MONA accesses, what leaves your machine, and your choices.

The short version

MONA is local-first. Your font collection, catalog metadata, collections, tags, favorites, and settings all live on your machine in a local SQLite database. There is no account, no cloud server operated by MONA, and no telemetry or analytics in the app.

Font files in folders you add as sources — read to build the catalog; never moved or modified.
The system font registry (Windows: HKCU\...\Fonts; macOS: CoreText) — only when you explicitly activate a font so other apps can use it.
An app-data directory for its catalog database (mona.db) and a rotating log file (MONA.log).

Marketplace browse / install: read-only catalog and font-download requests to Fontsource, Fontshare, Google Fonts, and jsDelivr.
Font identification (opt-in, off by default): an image you explicitly choose, sent to api.lipi.ai using your own API key. The key is stored locally and redacted from error messages.
Automatic sync (if enabled): a mona-sync.json file with collection/tag/favorite metadata — never font files — written to a cloud folder you choose. MONA does not operate the transport.
The in-app updater: checks a MONA-controlled URL for new versions and downloads signed update packages.
Crash logs never leave your machine automatically; you can export the log file yourself to attach to a bug report.

This website is static. It sets no cookies and runs no analytics of its own.
Checkout and delivery are processed by Lemon Squeezy (our merchant of record). When you check out, Lemon Squeezy receives your email address, payment details, and order information, and sends you order emails and download links. See Lemon Squeezy’s privacy policy for their handling of that data.