Privacy Policy

Summary

Qmacs Editor 0.2.0 is a local macOS workspace with separate ordinary files and encrypted vault documents. The app does not require an account, does not include analytics, and does not transmit document 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

Documents in Files are ordinary plaintext files saved at locations you choose. They remain editable without unlocking the vault. Documents in Vault are encrypted before durable storage using the app’s Rust cryptographic core and saved inside vault.qmacs. The vault uses the app’s default local folder or a folder you select; in a sandboxed build, the default .qmacs folder is inside the app’s local container. The displayed vault path identifies its location. Version 0.2.0 does not sync data to a Qmacs server.

Encrypted Backups

When saving an existing vault, the app retains the preceding encrypted file as vault.qmacs.backup in the same folder. After a master password change, that backup still requires the previous password. Explicit legacy import also preserves the encrypted original as a backup. These copies remain local and encrypted; they are separate from ordinary plaintext files.

Local Configuration and Folder Access

Preferences are stored in your account’s ~/.qmacs/config.json. They include appearance, syntax selection, the auto-lock interval, folder paths, and access bookmarks, without document text, master passwords, or supplemental authentication codes. A sandboxed app needs your folder selection through Settings › Files › Allow ~/.qmacs Access to save configuration there. App defaults retain the bootstrap security-scoped bookmark; current preferences are stored in the configuration file. Selected folder bookmarks allow local access and do not enable network sync.

Master Password

Qmacs Editor does not persist the master password in its configuration. The unlocked app holds it in memory so it can save encrypted changes. 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.

Vault Lock and Editing History

Locking the vault clears loaded vault documents, saved baselines, preview text, and their undo histories. Ordinary Files documents remain available separately. Clearing application state does not guarantee that every copy of text or credentials has been overwritten in process memory; Swift strings do not provide a reliable memory-wiping guarantee. Vault encryption protects stored vault data, while an unlocked process or compromised operating system can expose its contents.

Supplemental Unlock Checks

TOTP secrets are encrypted inside the local vault file with the master password. Static-code mode stores an encrypted verifier for the code. These are supplemental local application checks, not an independent cryptographic factor against someone who has the vault file and master password. The current build does not implement FIDO2 hardware authentication or transmit this data.

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, use the contact details on the Support page.