Inside EndToEnd

See the boundary for yourself

Inspect stored ciphertext and understand which information the messaging service can still observe.

The everyday friction.

The word private can leave too much unexplained. Encrypting message text does not make handles, friendships, or delivery activity disappear. People assessing a messenger need to understand both protected contents and the information outside that boundary.

A different way through.

EndToEnd includes a server view of stored ciphertext, alongside protocol and limits pages. Message envelopes have no sender column; attachment rows omit filenames and media types. The documentation describes visible information, including handles, friendships, delivery timing, and connection addresses.

See the idea take shape.

Three moments in the experience. Explore the intended flow below.

  1. Open the server view
  2. Inspect the stored ciphertext
  3. Read the protocol and limits
EndToEnd / See the boundary for yourselfIllustrative walkthrough

Inspect a stored result

Look at the ciphertext view to connect the explanation of encryption with what the server keeps.

The difference it can make.

Inspect a stored result

Look at the ciphertext view to connect the explanation of encryption with what the server keeps.

Separate contents from metadata

Understand why encrypted messages and an invisible social graph are different properties.

Read the limits alongside the promise

Assess the application using its documented boundaries rather than a broad privacy label alone.

Where it stands.

Good ideas deserve an honest description of where they are today.

In development

The server can still observe account relationships and delivery activity; encrypted contents do not hide the social graph.

Follow EndToEnd in the journal