a.

Nothing useful. The relay sees encrypted envelopes (opaque ciphertext blobs) and 22-character addresses derived from your public key. It cannot read your messages, your contacts, or your recovery phrase.

The same model as Matrix, Session, or Signal's server. We just don't run a discovery service or store anything at all.

Your account is gone. There is no email to reset, no phone to verify, no admin to beg. That's the trade for not trusting anyone with your identity.

Write it down on paper. Use the "Download .txt" button in the app. Store it somewhere offline — not in a cloud-synced folder.

Pending messages addressed to offline recipients are held in the relay's RAM (not disk). On a restart, they're gone. The sender has no way to know whether the message was delivered or not — that's the cost of zero-knowledge.

For important messages, ask the recipient to confirm receipt.

Yes. The relay is one file: server/index.js. It's zero-knowledge by design (no database, no logs, no persistence). On first run, the app asks you for a relay URL like wss://your-server/ws.

See the project's GitHub for a one-shot setup script.

Building and signing a mobile app costs money and requires a developer account in Apple's and Google's walled gardens. For now: Windows desktop.

Run the desktop app on a laptop if you need mobility. The chat history lives encrypted on that device, not on the server.

Yes. The relay is small enough to read in one sitting. The client uses standard primitives: Ed25519 for signing, X25519 for key agreement, XSalsa20-Poly1305 for encryption, all via audited NaCl libraries.

No, but Windows can't tell. Code-signing certificates cost ~$200/year and require a registered business. We haven't crossed that threshold yet.

What you can do: verify the SHA-256 of your download against SHA256SUMS. If the hashes match, the file is exactly what we published.