Why Session does not require a phone number—and what that does not solve

A phone number is a powerful join key

Phone numbers connect carrier records, address books, identity documents, and years of social relationships. When a messenger uses one as the account root, activities can be correlated around a stable identifier. Session’s randomized Account IDs let a person begin without surrendering that identifier, reducing one of the most common sources of metadata.

No number does not mean automatic anonymity

A real name, recognizable portrait, public Account ID, or distinctive writing style can reconnect the account to its owner. Attachments, timing, and the people contacted may reveal context as well. The product removes a default disclosure; it cannot design a separation strategy on the user’s behalf.

Choose a boundary that fits the risk

A single stable ID may be right for family and close friends. People who separate professional, research, or public roles should define different account and device rules. Start with a threat model: are you avoiding advertising profiles, reducing harassment, or preventing a capable adversary from linking two identities? The answer changes what good practice looks like.