Skip to main content

Security

Security model

What Ledger Chat protects you from, what it does not, and what you can do yourself.

No product protects against everything. This page explains, in plain terms, which risks Ledger Chat is designed to handle and which ones remain your responsibility or are still open.

What we protect against

RiskHow Ledger Chat handles it
Someone reading your direct messages on the wayMessages are encrypted on your device and only decrypted on the recipient's.
Our own servers being breachedDirect messages delivered through XMTP are not on our servers in readable form. The private wallet's keys never reach our servers; a passkey backup is ciphertext we cannot open.
Someone pretending to be youSigning in needs a signature from your wallet. Our servers ignore any identity the browser claims that is not backed by a valid session.
Password leaks and SIM swapsThere is no password to leak and no phone number to steal.
A private payment going to the wrong personBefore you pay, Ledger Chat checks a proof that the Aztec address belongs to the person in the conversation. The proof names the network, so an address announced on the test network cannot receive a payment of real value.
Losing your Ethereum walletA passkey you enrolled opens the same private wallet. Before any key is used, the wallet checks that what the passkey unlocked is your own account.
A wrong or tampered configurationThe private wallet refuses an Aztec node on another network. The Ethereum portal, once deployed, turns itself off if a token address is not the official one.
An incident in progressWe can stop new private payments from the app at once. Claims, refunds and withdrawals of your own money keep working.

What we do not protect against yet

  • Messages sent through the fallback path, community posts and attachments can be read by our servers. See Encryption for the full list.
  • Metadata. Our servers know who your contacts are, which communities you belong to and when you are online. XMTP nodes can see when encrypted messages are sent.
  • Your IP address in calls, unless you turn on the setting that relays every call.
  • Someone using your unlocked browser profile. The local message history and the private wallet live in your browser. Anyone who can use it while it is unlocked can read the history and open the wallet.
  • The fee payer of a private payment. Your account pays each network fee publicly, so its transactions can be linked to each other, although amounts and recipients stay private.
  • Contracts without an audit. No independent firm has audited our contracts yet.

What no messenger can protect against

  • Malware on your device, which can see whatever you see.
  • A person you are talking to who saves or shares what you send.
  • Someone who has your wallet's recovery phrase. They are you, as far as any system can tell.

What you can do

  1. Protect your recovery phrase

    Write it down, keep it offline, and never type it into a website or a chat.

  2. Check what you sign

    A sign in message for Ledger Chat names this website. A message for any other domain, or a request to approve a transaction, is not our sign in.

  3. Watch for the label

    If a message is marked Not end to end encrypted, treat it like an email: fine for most things, not for secrets.

  4. Lock your devices

    Use a screen lock on every device where you use Ledger Chat.

  5. Review your passkeys

    In the private wallet, open Security. Remove any passkey on a device you no longer control: it can spend like your wallet.