Security, explained

Trust the process.
Verify the details.

Privacy is a set of concrete boundaries, not a badge. Here is what the implementation does and what it does not promise.

Encrypted before it leaves your device

X25519 key exchange and XChaCha20-Poly1305 protect message contents. Ed25519 signatures cover the message, participants, UTC timestamp and attachment hashes before encryption. The recipient verifies the original signature after decryption.

On your deviceOn the central server
Private keys, decrypted messages, encrypted local history and document keys.Account/routing metadata, public keys, encrypted offline messages and attachment blobs.
Fingerprint comparison, signature verification and transcript exports.Authentication, public directory and real-time encrypted routing.

A fingerprint checks a key

Compare the full fingerprint using an independently trusted channel. A signature attributes bytes to a key; it does not automatically establish the legal identity of its holder. Unexpected key changes require renewed verification.

Your local vault

Encrypted storage uses SQLite3MultipleCiphers’ SQLCipher cipher, with a random vault key wrapped under an Argon2id-derived passphrase key. Optional Windows DPAPI unlock relies on the logged-in account; it does not require a fresh biometric challenge each time.

Evidence with explicit limits

Exports preserve original signatures and seal the PDF and JSON through a signed manifest. The verifier checks integrity, not legal admissibility, true historical time or completeness. Identity labels and local comparison dates are exporter assertions.

Important boundaries

  • The current protocol has no forward secrecy against later compromise of the recipient’s long-term private key.
  • Encryption cannot protect plaintext on a compromised, unlocked endpoint.
  • The server sees routing metadata and can delay or deny delivery.
  • Exported transcripts and intentionally exported documents are plaintext copies.
  • A key backup restores identity keys, not conversation history.
  • Independent security review, Windows validation and signed distribution remain release gates.
No independent audit certification, regulatory approval or guaranteed courtroom admissibility is claimed.

Reporting a security concern

During private evaluation, contact your project administrator through an existing trusted channel. Include version and reproduction details, but never send private keys, recovery passwords or confidential client conversations. A public security contact must be configured before launch.