The reason behind EndToEnd
A useful boundary you can understand
Something worth making.
When a service holds readable messages, the contents depend on that service’s handling of them. EndToEnd takes a different approach to the message path: seal the contents on the device before sending them, then let the server deliver the encrypted result.
Private messaging still needs to work as a conversation. Friend requests establish who can open a session; replies keep a discussion together; groups and files make the chat useful beyond a single line of text. Those actions sit around the same boundary for message contents.
Privacy is easier to assess when the limits are visible. EndToEnd explains the difference between message contents and service metadata, includes a view of stored ciphertext, and documents its one-device model. The goal is a usable messenger with a clear account of what it protects.
The things that matter.
Encrypt before sending
Keep readable message contents on participating devices and send ciphertext through the relay.
Make trust explicit
Use accepted friendships and contact verification as deliberate parts of starting a conversation.
Explain the boundary
Show what the server stores and describe the information the service can still observe.
Built with someone in mind
A place for you?
People who want private messaging with understandable boundaries
- People sharing private conversations
- Small groups exchanging messages and files
- People who want to inspect how privacy works