People ask the same question every time. If the message is gone after one view, where did it go, and who could have copied it. This post traces one message end to end.
On the sender device
You write the message. Before it leaves the device it is encrypted with the recipient public key using a fresh per message key derived from a ratcheting protocol. The plaintext never exists outside the app memory, and it is wiped from memory the moment encryption completes.
Across the relay
The encrypted blob is sent to a relay node. The relay sees bytes it cannot decrypt, a destination token, and a short time to live. It holds the ciphertext only in memory for the seconds needed to forward it, then discards it.
sender --encrypt(recipient_pubkey)--> relay(memory only) --> recipientThere is no database. There is no queue that survives a restart. If the relay crashes, the in flight message is simply lost, the sender is told to retry.
On the receiver device
The recipient device decrypts the message and renders it exactly once. A screenshot guard blurs the content the instant the app loses focus. The moment the view closes, the decrypted bytes and the ciphertext are both erased from memory and from any local store.
The network relays ciphertext it cannot read and stores nothing it could read later. That is the whole trick, and it is the whole point.
No server log, no backup job, and no moderator console can ever contain your words, because by the time anything persistent would run, the data is already gone.