How onion routing carries a Session message

The path from sender to swarm

The client locates the group of Session Nodes associated with the recipient’s Account ID, then prepares a multi-hop request. Each relay handles only the layer it needs. The final request reaches a node in the recipient’s swarm, where the encrypted message is stored temporarily for collection. Conversation encryption continues to protect the message body throughout this process.

Why encryption alone is not enough

End-to-end encryption conceals content, but a direct connection can still reveal where traffic originated. Onion routing separates the sender’s IP address from the storage destination, reducing the information available to any single server. This network design is a material difference between Session and a messenger whose clients connect to one centralized service.

Keep the limits in view

Routing protection is not a promise that every feature is anonymous. Session’s official FAQ notes that the current voice and video calling implementation uses peer-to-peer connections, which can reveal IP information to the other participant and supporting infrastructure. A compromised device, voluntary identity disclosure, and broad network surveillance require separate controls.