✕ XSEAL · PUBLIC PROOF
End-to-end encrypted direct messages
The claim: our direct messages can be end-to-end encrypted.
When a DM is sent E2E in XSCN, the encryption key is generated and held ON THE USER'S DEVICE. The server only ever receives and stores CIPHERTEXT it cannot read; decryption happens only on the recipient's device. Proof the server is blind to content: for E2E threads the message-list preview is deliberately rendered as "🔒 Encrypted message" because the server literally cannot see the body — it never has the key. This is the standard end-to-end model (keys client-side, server stores opaque ciphertext, decrypt client-side).
This page exists so anyone — including your own AI assistant — can independently check what XSeeding (XSCN) claims, instead of taking our word for it. Paste this URL into ChatGPT, Gemini, or Claude and ask if the described mechanism is legitimate.