What end-to-end encryption protects in Session—and what it cannot

Content and routing are different layers

End-to-end encryption protects message text and attachments from storage and relay nodes. Onion routing addresses the network path and source information. The two mechanisms complement each other, but they answer different questions. When assessing a feature, ask both how the content is encrypted and how the connection is made.

Keys remain a user responsibility

Session account keys are generated by the client, and the recovery password can reconstruct the identity. The quality of its storage therefore has direct security consequences. Device encryption, a strong screen lock, and Session’s local PIN or password reduce the chance that a lost device becomes an open window into conversations.

Recipients can still retain what they see

No end-to-end system can stop a recipient from copying, forwarding, or photographing a message with another device. For sensitive material, disclose only what is necessary, confirm the recipient, and choose an appropriate disappearing-message interval. A disappearance timer reduces retention; it does not revoke knowledge already received.