privacyportal
Back to Compass
Path consoleCommunicatemedium risk

Choose a secure messenger

WhatsApp and iMessage hide message bodies but still leak who talks to whom — metadata your provider, carrier, and many web2 apps collect by default. Pick a messenger that limits contact graphs and routing metadata, not just message content.

30–60 minutesAnyone replacing SMS, Telegram, or WhatsApp for sensitive chats 1 starting tool

Target outcome

Sensitive chats run on a messenger that does not require your phone number

Do this first · quick win

If you only do one thing today: install Session on both devices and exchange Session IDs over a channel you already trust — no phone number involved.

Setup queue

Start with verified tools

Compare the fit, keep the ones you want in My Stack, then open the verified setup guidance.

Session

applications

Choose Session when a phone number is itself a risk or when you need minimal contact and routing metadata.

applicationsOpen source
Visit project
More compatible tools (2)

Status

applications

Choose Status when you want messaging, wallet, and community features in one pseudonymous stack.

applicationsOpen sourcePrivacy by default
Visit project

Adamant

social-and-communications

Choose Adamant when you need blockchain-based accounts without a central phone-number directory.

social-and-communicationsLive status listed
Visit project

Understand · act · verify

Your path

Nothing is detected automatically. You decide when a step is done or needs another review.

  1. 1

    Install Session on every device you will use for sensitive chats — it uses Session IDs instead of phone numbers, reducing web2-style contact metadata.

    Step 1 · Not started

    • Session installed on all devices: Session opens and shows your Session ID on each device you plan to use.
  2. 2

    Create a new contact path (Session ID, username, or invite link) and share it outside the messenger you are replacing.

    Step 2 · Not started

    • Contact path exchanged: At least one contact has your Session ID and you have theirs, shared outside the old messenger.
  3. 3

    Turn on disappearing messages for sensitive threads and disable lock-screen notification previews.

    Step 3 · Not started

  4. 4

    Move one high-risk group or contact to Session and confirm everyone can send and receive before migrating more.

    Step 4 · Not started

    • First sensitive thread live: You sent and received at least one message in Session with a high-risk contact or group.
  5. 5

    Write backup contact instructions on paper in case your primary phone is seized or wiped.

    Step 5 · Not started

How you know it worked

  • Sensitive chats run on a messenger that does not require your phone number
  • Contact metadata exposure is reduced compared to mainstream web2 messengers
  • You have an offline backup plan if devices are lost or seized

Watch out

Cloud backups and linked desktops can copy message history to less protected storage.

A messenger your contacts refuse to install is not an operational plan.

Switching apps does not retroactively protect metadata already collected by web2 services.

Key terms
Metadata
Data about a message — who talked to whom, when, from where, and how often — even when the message body is encrypted.
E2EE
End-to-end encryption; only the people in the chat can read message content, not the service operator.
Sealed sender
A delivery mode that hides which account sent a message from the network or relay, reducing sender metadata.