Skip to content
Encryption
5 min read · June 16, 2026

Encrypted chat without a phone number

Signal, WhatsApp and Telegram all want a phone number. Why that matters, what the alternatives are, and how key-based chat works when there is no account behind it.

Signal is the best-regarded encrypted messenger there is, and it requires a phone number. So does WhatsApp. So does Telegram. For most people this is a non-issue. For some it is the whole issue.

Why a phone number is a meaningful cost

It is a strong identifier. A phone number is tied to a SIM, usually to an identity document, and to a billing relationship. It is one of the most reliable ways to link an online presence to a person, which is exactly why so many services ask for one.

It is visible to your contacts. In most phone-number-based messengers, starting a conversation means the other person learns your number. That is fine for friends and a real problem for a source, a marketplace buyer, or anyone contacting a stranger.

It leaks your social graph. Contact discovery — "these people from your address book are on this app" — is convenient and inherently reveals who you know. Signal works hard to minimise what its servers learn from this; most competitors do not.

It is hard to change and impossible to compartmentalise. One number, one identity, across everything.

It is not available to everyone. Getting a number can require identification, an address, or money, and a second number for separation is an ongoing cost.

None of this makes Signal a bad choice — for most people it is the right one, and its cryptography is the reference implementation the field measures itself against. But "encrypted" and "anonymous" are different properties, and Signal optimises hard for the first.

What the alternatives look like

Session. Forks the Signal protocol onto an onion routing network with no phone number. Genuinely anonymous by design. Trade-offs: it dropped forward secrecy for its account model, it needs an app install, and message delivery over the network can be slow.

Briar. Peer-to-peer over Tor, no servers at all. Excellent threat model, Android-only in practice, and both parties need to be online.

Matrix / Element. Federated, end-to-end encrypted, usernames rather than phone numbers. Powerful and flexible; the setup and key-verification experience is a genuine obstacle for non-technical users.

XMPP with OMEMO. Mature, open, no phone number. Requires choosing a server, a client, and enabling encryption — three decisions before saying hello.

Key-based web chat. No install, no account, no phone number; identity is a key pair in your browser. Trade-off: you are trusting the code the site serves, and losing your key loses your history.

There is no option without a trade-off. The honest framing is which trade-off suits what you are doing.

How key-based identity works

Instead of "who are you, prove it with an SMS", the model is "what key do you hold".

Your browser generates a key pair. The public half is published under a readable alias — quiet_forest_owl — so people can address you. The private half never leaves the device and is the only thing that decrypts what arrives.

Some consequences worth understanding:

Identity is possession, not registration. Whoever holds the private key is the mailbox. There is no separate account to compromise, and no credential a server could leak.

There is no password reset. The flip side of the same fact. If the key is gone, the identity is gone. Backing it up is not optional.

Contact discovery does not exist. Nobody can look you up by phone number or email, because the system holds neither. You share an alias or a link deliberately. This eliminates the social-graph leak and means you have to actually tell people how to reach you.

One person can hold many identities. Separate mailboxes for separate contexts, with nothing linking them. A phone number cannot do this.

What AliasCloak's chat does

A conversation is a set of participants identified by public key. Each message payload is encrypted once with a fresh random content key. That small key is then wrapped separately for every participant — including yourself, so your own history is readable on a second device. The server stores one shared ciphertext plus one opaque key envelope per recipient and holds no key that opens any of them.

Delivery uses a live server-sent event stream with a polling fallback, so messages arrive immediately when the connection is healthy and still arrive when it is not — a corporate proxy blocking the stream degrades latency, not reliability. Messages carry a monotonic id and the client tracks a cursor, so a reconnect resumes exactly where it left off without duplicating or skipping anything.

Attachments reuse the same encrypted file pipeline as the mailbox: encrypted in the browser, uploaded in chunks that survive a dropped connection, decrypted on the recipient's device. Up to 4 GB each.

The starting friction is deliberately near zero. Send someone an invite link and clicking it creates a mailbox for them and opens the conversation in one step. They never see a key, a password, or a sign-up form.

The limits

Browser-delivered code. Every web-based encryption tool shares this: you are trusting that the JavaScript served today is what you expect. A native app can be signed and reproducibly built; a web page cannot offer the same assurance. This is a real difference from Signal and it is the main reason to prefer a native app for high-stakes use.

Metadata. We cannot read messages, but we can see that a mailbox received an envelope of a certain size at a certain time. Signal goes considerably further to minimise this — sealed sender, private contact discovery — and if metadata resistance is your primary requirement, Signal or Briar are better tools.

Retention. Chat history is held encrypted for a limited window so a device that has been offline can catch up, then deleted. Local history on your device is yours and stays until you remove it.

Lost keys. Say it again: no recovery.

Choosing

  • Talking to friends and family, want strong encryption: Signal. It is better than this at almost everything except the phone number.
  • Need to talk to someone who must not learn your number: a key-based tool. This is the case that phone-number messengers cannot serve at all.
  • Need to be contactable in public without publishing an identifier: an alias, and see the alternative to publishing an email address.
  • Threat model includes a state adversary: Briar or Session, on a device you control, and read considerably more than this article.
  • Just want to send a colleague a 3 GB file without a cloud account: any of them; this is the easy case.

Try the chat — a mailbox takes one click and no phone number.


Private by design

Start private. Stay in control.

Create a free AliasCloak mailbox in seconds, then use the same private identity for encrypted mail, chat, and file delivery.