Executive Summary

Full report

On this page

Signal is a leading secure messenger that end-to-end encrypts all chats, calls, and media by default. Its open-source design and minimalist data retention mean Signal’s servers only see encrypted payloads and minimal metadata (account creation and last‐login timestamps). Nonetheless, Signal does not hide all metadata (e.g. IP addresses) by default, and certain usability choices (like phone number registration) trade anonymity for convenience. For maximum security, users should combine Signal’s strong cryptography with robust device and OPSEC practices. Key best practices include: enabling registration lock and a strong Signal PIN, verifying safety numbers (QR codes) with contacts, using disappearing/view-once messages for sensitive content, hiding notification previews, and disabling unnecessary features like contact uploading or cloud backups. Advanced users may also use a VPN/Tor to conceal IP addresses, a secondary phone number, and strict OS hardening. This report analyzes Signal’s threat model, architecture, and features; summarizes recent security audits; and gives a prioritized checklist of actionable hardening steps.

Threat Model & Assumptions

Signal’s threat model assumes powerful adversaries (e.g. hostile governments or network attackers) who can intercept network traffic or even compromise Signal’s servers. Signal protects message content against such adversaries via its encryption; even Signal’s own servers “cannot access the content of your messages or calls”. Signal also minimizes on-server metadata: by design it does not know your contact list or group membership, and it “only maintains two types of user data … [for] law enforcement: timestamps of when each account was created and last connected”. However, by default Signal does not provide anonymity; network-level metadata (IP addresses, timing, data volumes) are visible to the user’s ISP or to Signal’s servers unless mitigated (e.g. via VPN). Signal also requires a phone number for registration (though a username can later mask it). Finally, Signal does not protect against device compromise or social engineering – if an attacker has full control of your device or tricks you into revealing data, Signal’s crypto offers no defense. In summary, Signal’s strong guarantees cover confidentiality and forward-secrecy of communication, but users concerned about anonymity or endpoint security must apply additional measures (VPN/Tor, strong device passwords, etc.).

Architecture & Cryptography

Signal’s core protocol is the Signal Protocol, a modern cryptographic scheme using X3DH key agreement and the Double Ratchet algorithm. For each 1:1 chat it derives ephemeral keys ensuring perfect forward secrecy and post-compromise security. Groups use an extended protocol: a pairwise double-ratchet plus multicast encryption provides E2EE with “speaker consistency”. All text, voice, video, and attachments are encrypted end-to-end; even profile names, pictures, and reactions are sent only to devices in the chat. Signal’s code is open-source and has been subjected to formal review (audits of X3DH, Double Ratchet, Sealed Sender, etc.). Key distribution includes “Sealed Sender” to hide sender identity from Signal’s servers. In practice, a message flow is: Alice’s client encrypts the message for Bob (or group) and sends it to the Signal server, which queues it; then the server delivers the encrypted blob to Bob’s devices, where Bob’s client decrypts it. The server only sees opaque envelopes – it cannot read contents or easily link which user sent to whom.

However, Signal makes some explicit trade-offs: it does not anonymize IP addresses on its own (calls use IP hiding only when calling someone not in your contacts), and contact discovery (hashed or SGX-protected) can in theory leak minimal info (see section below on metadata). Importantly, Signal does not store conversation history on servers; messages live only on endpoints, except fleetingly in transit. These design choices minimize trust in Signal: “by design, [Signal] does not store a record of your contacts, social graph, conversation…”. In short, Signal’s architecture is robust: it uses well-studied cryptographic protocols, keeps metadata minimal, and provides verifiable safety numbers.

flowchart LR
    subgraph Clients
      Alice[Client (Alice)]
      Bob[Client (Bob)]
    end
    subgraph SignalService
      S[Signal Server (Encrypted Relay)]
    end
    Alice -- Encrypt with Signal Protocol --> S
    S -- Relay Encrypted Message --> Bob
    style S fill:#f9f,stroke:#333,stroke-width:2px

Account Setup & Device Linking

Registration: Signal requires a working phone number to register (used only to confirm identity and limit to one account). For maximum privacy, users can obtain a secondary SIM or VoIP number not tied to their personal identity. During setup, Signal may prompt for Contacts permission; if granted, Signal performs a private contact discovery (via hashing or Intel SGX enclave) to match you with existing users. If you decline, you can still use Signal by manually entering numbers. You can also create a username as an alternative identity; then others can contact you without knowing your phone number. By default “Who can find me by my number” is set to Everyone; for greater privacy you can change this to Nobody (meaning only your username is used).

Linked Devices: Signal supports linking multiple devices (e.g. Desktop, iPad) to the same account via a QR-code scan. Chats and the last ~45 days of media can sync to each new link. Users get up to 5 linked devices; after 45 days of inactivity a device is automatically unlinked. It’s crucial to remove any unknown or unused devices via Settings → Linked Devices, since each linked device has full access to your chats. When switching phones, Signal provides device-to-device transfers: on Android or iOS, you can use a QR-code pairing process that moves your message history to the new phone (the old device is unregistered). This does not require any cloud backup. Note: iCloud backups are currently not compatible with Signal, so on iOS the only way to retain history is this direct transfer. On Android, Signal has introduced a “Secure Backups” feature (opt-in, see next section) for cloud recovery. Always use the official Signal apps from Google Play, App Store, or signal.org to avoid malicious forks.

Device & OS Hardening

• Operating System Security: Keep your device’s OS fully up-to-date with the latest security patches. Use a strong device passcode or biometric lock on both phone and desktop. Avoid jailbreaking or rooting your device. On desktop (Windows/macOS/Linux), ensure full-disk encryption (BitLocker, FileVault, LUKS) and a strong login password.

• App Lock / Screen Lock: In Signal’s settings, enable Screen Lock (App Passcode/Biometric) so the app auto-locks after brief inactivity. This prevents easy access if your unlocked phone is stolen. On Android, set Screen Lock to 1 minute or less; on iOS, enable “Require Passcode” within Signal (it will prompt you for Face/Touch ID to open). On desktop, Signal cannot lock itself, so rely on your OS session lock.

• Notifications: Disable message content in notifications. In Signal’s Settings → Notifications, choose “Show no name or content” (only “Signal” pops up). Also disable lock-screen previews at the OS level. This stops sensitive info from appearing if you glance at your phone’s lock screen.

• Keyboard Security: On Android, enable Signal’s Incognito Keyboard (Settings → Privacy → Incognito keyboard). This blocks third-party keyboards from learning what you type (extra privacy for passwords or secret messages). On iOS, third-party keyboards are already disabled by default in secure input fields.

• Privacy & Permissions: In Settings → Privacy, disable any features you don’t need. For example, Signal can obscure your contacts from the app (“Who can find me by my number” set to “Nobody”). Only grant Signal the Contacts permission if you trust it; if compromised, SGX contact discovery can be attacked (see audits below). On Android, make sure Signal has restricted background data and that Battery/Low-Power modes don’t disable its networking unexpectedly.

• App Updates: Always run the latest Signal version. Signal is audited and updated frequently. Outdated versions may lack recent security fixes (for example, Signal security fixes have been issued as recently as 2025). Verify automatic updates on mobile app stores or manually check if needed.

In short, treat your device as part of Signal’s defense: keep it locked and updated, minimize unnecessary apps/permissions, and only run Signal on trusted hardware.

Contact Verification & Safety Numbers

Signal provides safety numbers (unique key fingerprints) for each conversation. Verifying a safety number ensures the encryption keys are correct and guards against a man-in-the-middle. In practice, you should exchange safety numbers via a trusted channel (face-to-face QR scan or voice call) at least once with high-risk contacts. To do this: open a chat, tap the contact’s name, choose “View Safety Number,” then scan or compare the displayed QR code or 60-digit number. If they match, tap “Mark as Verified”. A checkmark will then appear next to that contact’s name. If a safety number changes unexpectedly (e.g. frequent changes without you reinstalling Signal), treat it as suspicious. (Most safety-number alerts are benign – for example, if your friend reinstalls Signal or switches phones – but repeated changes could indicate tampering.) Note: Signal also offers Automatic Key Verification when you know each other’s phone numbers (it shows “Encryption Verified”), but this is less stringent than manual QR-scanning. In all cases, never ignore persistent safety-number mismatch warnings.

Because usernames can replace phone numbers, you can also verify via username if your friend is in your address book and discoverable. However, remember usernames are changeable and Signal will record username changes in chats, so set your final username before joining large public groups.

Messaging & Media Handling

• Disappearing Messages: Use disappearing messages to limit data retention. In any chat, you can set a timer (from 5 seconds up to 4 weeks) after which messages vanish. Enable this in chats with sensitive info or by default for all new chats (via Settings → Privacy → Default Timer). Even if an attacker later gains device access, expired messages cannot be recovered. Caveat: Disappearing messages only auto-delete from devices of people who have the setting on. If you set a timer, other participants will be prompted to turn it on; if they decline, their chat won’t auto-delete your messages. Also, messages sent before a timer change will not be resent after a safety-number change.

• View-Once Media: When sending photos/videos, use the “view once” mode to make them non-persistent. Such media self-destruct after a single view. Note that such images still travel encrypted, but the Signal client will delete them upon opening. Regular media (photos/videos) are end-to-end encrypted in transit and stored in the chat; Signal automatically strips identifiable metadata (EXIF) from images. For sensitive media, prefer view-once or ensure recipients do not save images.

• Screen Security: Signal automatically prevents other apps from reading its screen (no Android “overview” thumbnails or iOS app switcher previews). However, it cannot prevent the user from screenshotting or taking a photo of the screen. Remind contacts not to screenshot or record conversations if privacy is critical. In high-risk situations, consider memorizing or manually erasing content.

• Keyboard & Previews: As noted, use Incognito Keyboard on Android to stop keylogging by third-party IMEs. Also, turn off URL previews in Settings to avoid leaking link metadata to GIPHY or external services. In privacy-sensitive contexts, avoid using any online sticker/GIF service.

• Backups & Attachments: By default, Signal does not back up messages to the cloud. (See “Backups” below.) Be cautious when transferring chat history or attachments outside Signal; any copy outside the Signal ecosystem (emailing, saving to an insecure folder) breaks encryption.

In summary, use Signal’s built-in privacy features (disappearing, view-once, incognito) liberally, and educate contacts to do the same. The most common messaging mistake is human error: e.g. adding the wrong person to a group, sharing screenshots, or ignoring safety-number alerts.

Groups & Communities

Signal groups (including the newer Communities feature) are end-to-end encrypted like 1:1 chats. Group metadata (membership list, name, icon) is not stored on Signal’s servers – membership is managed privately between participants. Groups now support admin roles, invite links (with optional approval), @-mentions, and up to 1000 members. To maximize security in groups: only join groups where members are vetted. Treat large groups as essentially public – do not share any information you consider secret. It’s recommended to create a Signal username before joining large group chats for anonymity. Remember that Signal will broadcast username changes to the group, so finalize your username early if you wish to stay anonymous. Group admins can enforce disappearing timers and membership removal; use these controls to prune inactive or untrusted members. Be careful with group invite links – if a link leaks, reset it (Signal allows revoking links).

Note that any member in a group can screenshot or share content externally, so Signal cannot prevent insider leaks. For very sensitive communities, keep group sizes small or use direct chats where possible. Voice and video calls can also be initiated within groups, but those follow the same protocols as 1:1 calls (see below).

Voice & Video Calls

Signal supports end-to-end encrypted voice and video calls for 1:1 and group conversations. Calls use WebRTC (DTLS-SRTP) with selective forwarding units (SFUs) for group scalability. The media streams are not accessible to the server; in a group call, each client sends encrypted packets to the SFU, which merely forwards them to others. By default, calls are peer-to-peer when possible for lowest latency. Importantly, Signal obscures your IP address during calling: if someone not in your contacts calls you, their call is automatically relayed through Signal’s servers, hiding both parties’ IPs. (If you call a stranger, you can also turn on “Always relay calls” in Settings.) Remember that voice/video call data (duration, endpoints) may still be visible on your network or phone logs. Use a VPN/Tor to hide your location from all network observers if needed. Finally, callers should also verify safety numbers (you see “Encryption Verified” on call screens) if confirming identities is critical.

Registration Lock & PIN

Signal offers a PIN (numeric or alphanumeric) to protect your account and enable features like profile recovery and two-factor registration lock. You should set a strong PIN (no length limit). The PIN is never known by Signal; it is used for Secure Value Recovery so that Signal’s servers need not know your social graph. Crucially, enable Registration Lock (two-step) under Settings → Account. With this on, any attempt to register your number on a new device will require your PIN after 7 days. This prevents someone from stealing your number/SIM and immediately re-registering. However, be aware: if you forget your PIN while Registration Lock is on, you will be locked out for up to 7 days. Use a password manager or handwritten copy to avoid this. In summary: use an alphanumeric PIN and registration lock for maximum security, but do not share or reuse it as a device unlock – it is not your normal screen passcode.

Recovery & Backups

Until recently, Signal did not offer cloud backup. As of 2025, Secure Backups are available on Android (and rolling out to iOS/Desktop). When enabled, Signal creates an end-to-end encrypted backup archive of all text messages and the last 45 days of media. This archive is protected by a 64-character recovery key that never leaves your device. Without that key, no one (not even Signal) can decrypt your backup. The free tier includes 100 MiB (enough for ~45 days of messages), with a $1.99/mo option for up to 100 GB if you need more media. View-once and messages disappearing within 24h are excluded from backups. To enable, go to Settings → Backups and follow the prompts to record your recovery key.

If you do not use Secure Backups, you will lose message history if your device is lost or reset. As of mid-2026, iOS does not yet have secure backups, and iCloud backups are not compatible with Signal. The only way to retain chat history on iPhone is the device-transfer process (which requires the old iPhone and QR scanning). Android users can use Android-to-Android transfer in a similar way. In other words, until cross-platform encrypted backups arrive, always plan message recovery carefully: use direct device transfer or the new secure backup feature. Finally, remember that backing up to general cloud services (iCloud, Google Drive) is not end-to-end encrypted by Signal, so disable any automated cloud backup for Signal data to avoid leaks.

Metadata Leakage & Mitigations

Signal minimizes metadata, but does not entirely hide it. What Signal doesn’t know (by policy and design) includes: your contacts list, who you message (due to Sealed Sender), message content, and profile data. However, Signal’s servers do see that someone (your device) is connecting at a given time. In fact, Signal “only maintains … timestamps” of account creation and last use. The server knows nothing about the content of queues or group names.

What Signal does reveal or store: (1) Your phone number on account creation (used as user ID) – though you can hide it from others by using a username. (2) The fact that you connected (timestamp). (3) Delivery addresses on packets – however, Sealed Sender obscures which actual registered user sent which message, so the server sees “somebody is sending to this number,” without linking to a specific account. (4) Your IP address when you connect (for messaging, and for calls if not relayed) – this is visible to Signal’s server and your ISP. (5) If you enable contact discovery, Signal receives hashes of your contacts (mitigated by SGX enclaves).

To mitigate metadata risks:

• Use Signal’s Sealed Sender (on by default) so senders are hidden from the server.
• Turn off contact uploading if unneeded; if the adversary can compromise SGX or break it (see below), you may avoid contact leaks by not granting that permission.
• Consider using a VPN or Tor to hide your IP address from Signal and network observers. (Experts note that using Signal over Tor gives metadata-privacy by design.)
• Choose “Who can find me by number → Nobody” and use a username for truly anonymous discovery. Remember that usernames are still linkable to messages you send.
• Enable “Always relay calls” if you want to hide IPs even in 1:1 calls (though this may slightly reduce call quality).
• Use local features (contacts, images) instead of third-party services. For instance, Signal’s GIPHY integration sends queries to GIPHY; if metadata privacy is critical, disable that in Settings and use local GIFs. Note that any integration (e.g. Map APIs) can leak IP or query data to third parties.

In summary, recognize that Signal is not anonymous: network observers will see that you are using Signal and potentially your rough location/IP. For greater anonymity, pair Signal with privacy networks (VPN/Tor) and non-personal phone numbers.

Operational Security & Common Pitfalls

Even the most secure app can be undermined by poor OPSEC. Common user mistakes include:

• Ignoring Safety Warnings: Don’t dismiss the “Safety number changed” alert without verifying why. Sudden key changes can signal a takeover attempt. Always verify with your contact through a trusted channel if you see a change.
• Lax Device Security: If your phone or computer is unlocked or infected with malware, attackers can read decrypted messages or exfiltrate keys. Never install untrusted apps, and use anti-malware tools. Lock your devices and uninstall Signal from lost/stolen devices immediately.
• Backing Up Insecurely: Users sometimes copy a Signal database manually or use unencrypted OS backups. This breaks E2EE. Only use Signal’s built-in Secure Backups (protected by your recovery key) or direct device-transfer; disable any system-level cloud backup for Signal.
• Insecure Contact Sharing: Adding unknown people (in error or via scam) to chats leaks info. Be wary of message requests or group invites from strangers. Signal’s “Message Requests” feature shows unknown senders – use it to screen before replying. Never share your verification code/SMS to anyone (this is for your account only).
• Social Engineering: Remember that Signal cannot verify real-world identity. Attackers may impersonate trusted contacts via username or copycat accounts. Verifying safety numbers is the only defense. Also, never click suspicious links or phone calls claiming to be “Signal support” – Signal does not initiate contact to request info.
• Large Group Dynamics: In big groups, any member can save or forward information. Follow the advice for groups above: assume groups are public, use usernames, and minimize personal info.

By applying strong passwords, enabling all of Signal’s recommended security settings, and staying vigilant (e.g. re-verify contacts if reinstalling), users avoid the majority of common pitfalls. As one expert noted: “even the most secure technology can’t prevent human error” – so encourage security practices among your contacts as well.

Trade-offs & Usability Considerations

Some security measures reduce convenience. For example: hiding your phone number (“Nobody” discoverability) means others must use your username, which can make finding each other harder. Enabling disappearing messages means losing chat history. Registration Lock adds a 7-day recovery wait if you forget your PIN. Incognito keyboard on Android disables personalized typing suggestions. VPN/Tor can slightly slow message delivery. Users must balance these trade-offs based on threat level: for high-risk contexts, prioritize privacy (VPN, minimal metadata), while casual users may accept some exposure for ease of use.

Signal’s design choices themselves are trade-offs: requiring a phone number simplifies the user base but ties an identity; limiting metadata storage enhances privacy but means service providers must trust the policy (Signal has proven in court that it has no logs). Unlike anonymous messengers (e.g. Briar), Signal sacrifices complete anonymity for practicality. The recommended approach is defense in depth: use Signal’s strong encryption along with good OPSEC (device lock, verifying contacts, etc.) so that usability costs are incremental but security gains are large.

Actionable Best Practices (Checklist)

• Update Everything: Always run the latest Signal version and OS security patches.
• Device Security: Set a strong passcode/biometric on your phone and enable full-disk encryption on desktop. Don’t root/jailbreak.
• App Lock: In Signal settings, enable Screen Lock (passcode or biometric) so the app locks when idle.
• Registration Lock: Turn on Registration Lock (two-step PIN) and choose a long alphanumeric Signal PIN. Memorize/store it securely.
• Contact Verification: Verify safety numbers with each important contact at least once (scan QR codes).
• Disappearing Messages: For sensitive chats, set a short disappearing timer (e.g. days or weeks) to auto-delete old messages.
• View-Once Media: Use the “view once” option for sensitive photos/videos so they don’t persist.
• Hide Number: In Settings → Privacy, set “Who can find me by my number” to Nobody (and share your username instead).
• Notifications: Disable message previews in notifications (show no name/content).
• Block Unknowns: In Settings → Privacy, disable “Allow message requests from people you have not talked to” (if available) to block unsolicited messages.
• Safety Number Alerts: Never ignore an unexpected safety-number change alert – re-verify before continuing to chat.
• Secure Backups: On Android, enable Signal Secure Backups and safely store the recovery key. iOS users should wait for this feature or always use device-to-device transfer.
• Limit Permissions: Do not grant Signal more permissions than needed. If adversaries are a concern, consider disabling Contacts permission (use manual invites).
• Keyboard Security: On Android, enable Incognito Keyboard to protect your typing.
• Use VPN/Tor: For anonymity, run Signal through a VPN or Tor (especially on insecure networks).
• Remove Devices: Periodically check Linked Devices in settings and revoke any you no longer use.
• Logout Lost Devices: If your phone is compromised or replaced, use Settings → Account → Delete Signal account to unlink old copies (note: this is drastic and deletes your data on Signal’s servers).

Advanced Users:

• Use a burner phone/SIM number for registration.
• Avoid any automatic cloud backup (Signal or OS) that could be decrypted by outsiders.
• Disable location/data sharing in chat (do not send map locations unless absolutely needed).
• For highest opsec, do not keep highly sensitive data on the same device (store it offline).

Platform Settings Comparison

Mermaid Diagrams: Signal Architecture & Message Flow

Signal Architecture (simplified)

graph LR
    Alice[Client (Alice)] --- E2E ---> Server[Signal Server]
    Bob[Client (Bob)] -----< E2E ---- Server
    Alice --- "Contact Discovery" ---> Server
    Note left of Server: *Stores only queues & keys*\n*No plain data or metadata*
    Note right of Alice: *Encrypt with Double Ratchet*\n*Verifies Sealed Sender*\n*Check Safety Numbers*
    Note right of Bob: *Decrypts Double Ratchet*\n*Verifies Safety Numbers*

Diagram: Alice’s and Bob’s devices exchange E2E-encrypted messages via Signal’s server. Only encrypted packets traverse the server (which only queues data, never sees plaintext).

Secure Message Lifecycle

flowchart TD
  A[Compose Message] --> B{Encrypt}
  B -->|X3DH handshake & Double Ratchet| C[Encrypted Blob]
  C --> D[Upload to Signal Server]
  D --> E[Queued/Stored briefly]
  E --> F[Deliver to Recipient]
  F --> G{Recipient Decrypt}
  G -->|Keys + Ratchet| H[Plaintext Message]
  H --> I[Display to User]

Flow: A user composes a message (A), Signal’s protocol encrypts it (B), the encrypted data (C) is sent to Signal’s server (D–E), and then delivered to the recipient (F), where the app decrypts it (G) for display (H–I). Throughout, only ciphertext traverses networks and servers.

FAQ: Common User Concerns

A: Yes, Signal provides state-of-the-art end-to-end encryption on every message, call, and file. Only you and your recipients can read content or media. Signal’s open-source code and audits reinforce trust. However, remember that metadata (like your IP or who you call) is not completely hidden by default. For stronger anonymity, use additional tools (VPN/Tor, non-identifying phone number).

• Q: Is Signal truly private and secure?

A: Signal’s servers keep minimal data. By design, Signal only knows when your account was created and last used. It does not store your contact list, group memberships, or content of messages. That said, the server does learn your IP address and that someone is sending some encrypted packet. Features like Sealed Sender hide who is sending.

• Q: What metadata does Signal collect?

A: If switching devices, use Signal’s device transfer. On Android or iPhone, use the in-app Transfer flow (QR code) to move chats. If you enabled Secure Backups (Android only currently), restore from your cloud backup with your recovery key. If neither is possible, your chat history cannot be recovered (it lives only on your old device).

• Q: What if I lose my phone or get a new one?

A: Signal encrypts group chats so outsiders can’t read them. But any group member (or anyone they forward to) could screenshot or leak content. For very sensitive info, limit group size and share only on a need-to-know basis. Group links should be shared carefully and reset if misused. Signal itself learns nothing of group titles or participants.

• Q: Are my group chats safe if a member is compromised?

A: No. Signal’s messages and attachments are not end-to-end encrypted in standard iCloud or Google backups. An adversary who obtains your cloud backup could read your Signal data. Until Signal’s own secure backups are available on iOS, avoid backing up Signal in iCloud or Google Drive (you may even disable app backups entirely).

• Q: Is it okay to use iCloud/Google backups?

A: Keep Signal and your OS updated; new versions address bugs found in audits. Use long alphanumeric PINs, and consider disabling features like contact discovery if you do not need them (a known SGX-related attack in 2020 could leak hashed contacts, but this is mitigated by Intel patches and by not uploading contacts). Signal responds quickly to reported issues (see recent fixes for screen lock bypasses, call bugs, etc. in its audit history). In general, follow the best practices above, and stay informed via Signal’s official blog or community updates.

• Q: How do I protect myself from future vulnerabilities?

Sources: Official Signal documentation and blogs, recent audits and expert analyses. These references include Signal’s own support articles and policy, the Signal Foundation blog, and reviews by security researchers.