Qmacs Editor
Security RQmod Support License

Privacy

Privacy Policy

Effective date: July 5, 2026

Summary

Qmacs Editor is designed as an offline-first encrypted macOS workspace. The current app build does not require an account, does not include analytics, and does not transmit note contents to a developer-operated server.

Landing Page

This website is hosted on Vercel. Vercel may process standard hosting logs such as IP address, request path, user agent, timestamp, and similar operational data needed to deliver and secure the site.

macOS App

The app stores user-created buffers locally. Ordinary file buffers remain editable without unlocking the encrypted vault. Vault payloads are encrypted before durable storage using the app's Rust cryptographic core and are saved in the selected local vault folder, defaulting to ~/.qmacs. The current build does not sync data to a Qmacs server.

Master Password

Qmacs Editor does not store the master password. The vault file stores an encrypted verifier derived through Argon2id and protected with XChaCha20-Poly1305. Changing the master password re-encrypts the local vault with the new password.

Multi-Factor Authentication

TOTP MFA secrets are encrypted inside the local vault file before storage. Security-key code mode stores only an encrypted verifier for the key code. MFA data is local and is not transmitted by the current build.

RQmod Models

RQmod text buffers are treated like other editor buffers. They remain local unless you export or distribute them yourself.

Themes and Syntax

Theme JSON, selected palette, and selected syntax mode are local app preferences. They are not sent to Qmacs servers by the current build.

Contact

For privacy questions, contact the project maintainer through the support channel listed in the App Store or project repository.

Qmacs Editor Home · Support · License