Keep a copy. Control access.

Know where your work goes

Calculations and notes live on your device. The app has no built-in cloud synchronization or telemetry. Optional semantic search can download a model or import it from disk; indexing and queries stay local.

Set up protection

Use Settings → Security to configure your desktop vault and keys, then protect the notes you choose. Note protection uses AES-256-GCM with Argon2id for password-based key derivation. Store recovery material separately.

• Lock the UI when you do not want its protected content available.
• Keep the master password and recovery material accessible to you.
• Treat an authorized MCP grant as separate access: UI locking does not revoke it.

Keep a separate backup

In Settings → Files & sync, choose All — full library backup → Back up to folder. This saves accepted state, notes, images, snapshots, trash, and security files into a new directory, with a file manifest and RESTORE.txt.

• Protected content stays encrypted; plain content stays plain. A folder backup does not automatically encrypt the whole library.
• Notes, images & keys saves the note library and workspace identity/settings while excluding calculator history, variables, and graphs.
• Unsaved drafts and unaccepted incoming changes are excluded. Save and review them first.
• Semantic caches and MCP grants are excluded from normal library backups.

Match the export to its purpose

Markdown and plain text are useful for moving notes into other editors, but their contents are readable. Folder backups preserve each file’s existing protection. Use encrypted secure note exchange when you want to send an encrypted note bundle.

After restoring

Follow the backup’s RESTORE.txt. With CQS closed, restore state.json, notes, and security together into an empty application-data directory. Verify the restored library before removing the original backup. Rebuild semantic search if needed and create fresh MCP grants on a new installation.