Practical guidance

A clear start.
A verifiable finish.

Prepare your account, protect your keys, and understand what your exported evidence can prove.

01. Get ready

  1. Obtain the validated release from the download page.
  2. Check SHA-256 and the Windows publisher signature.
  3. Get your administrator’s HTTPS server address and invitation.
  4. Register and complete email verification.

02. Protect your keys

  1. Create a long, unique local vault passphrase.
  2. Save an encrypted .key backup with a separate password.
  3. Reselect the file and test recovery before activation.
  4. Store it safely. It does not contain chat history.

03. Compare fingerprints

  1. Add the exact handle your counterparty provided.
  2. Compare the full fingerprint independently.
  3. Confirm the match on both devices.
  4. Stop and investigate unexpected key changes or failed verification.

04. Exchange documents

  1. Select a file in a verified conversation.
  2. The client encrypts it locally and signs its hash within the message.
  3. The recipient chooses where to export a verified copy.
  4. Protect plaintext copies. A valid signature does not make an executable safe to run.
For independent reviewers

Verify an exported conversation.

Keep transcript.pdf, audit.json and the attachments directory together. Obtain the verifier through a trusted software channel. Only Node.js 24 is required.

node verify-transcript.mjs "C:\Evidence\EXPORT_FOLDER"
node verify-transcript.mjs "C:\Evidence\EXPORT_FOLDER" --trust FIRST_FINGERPRINT --trust SECOND_FINGERPRINT

Replace the placeholders with independently authenticated 64-character lowercase hexadecimal fingerprints. Do not take keys solely from the export and assume they establish trust.

ExitMeaning
0Integrity checks pass and participant keys match supplied trust fingerprints. Review all warnings.
1Verification failed, input is invalid or required files are missing.
2Integrity passes, but participant-key trust is incomplete.

Completeness remains unproven. UTC timestamps are sender assertions. Included document bytes are checked against signed hashes; hash-only references do not prove the file was supplied. The PDF hash binds its bytes to the manifest, not the semantic agreement of its visible statements with every signed JSON message.

Download the offline verifier ↓

Complete auditor guide · Third-party notices