Sealed Sender and Sender Anonymity
What you'll learn: How sealed sender mechanisms hide who sent a message from the messaging service itself, not just eavesdroppers.
The Privacy Gap in E2EE
Even with end-to-end encryption, messaging services typically know who is talking to whom and when—this is metadata. While message content is encrypted, the server must know the sender's identity to route the message to the recipient. This creates a privacy leak: the service provider can build social graphs, track communication patterns, and identify relationships.
What is Sealed Sender?
Sealed sender is a mechanism that hides the sender's identity from the messaging service during transmission. Instead of the server seeing "Alice → Bob," it only sees "unknown → Bob." The server can deliver the message but cannot identify who sent it.
How It Works
The sender encrypts both the message and their identity using the recipient's public key. The server sees only:
- The recipient (necessary for delivery)
- An encrypted blob containing both sender identity and message
When Bob decrypts the message, he learns who sent it, but the server never does.
Analogy: Imagine dropping a sealed envelope at the post office with only the recipient's address visible. Inside the envelope, your return address and letter are sealed together. The postal service delivers it without ever knowing who sent it.
Limitations and Tradeoffs
- Recipient must be known for delivery routing
- Abuse prevention becomes harder (blocking spam/harassers is more difficult)
- Group messages may leak sender metadata through delivery patterns
- Requires trust infrastructure (sender must have recipient's current keys)
Key Takeaway: Sealed sender protects sender anonymity from the service provider itself by encrypting sender identity along with message content, though the recipient's identity must remain visible for delivery.