How Graphite Messenger Encrypts Your Chats: E2EE, Double Ratchet & Post-Quantum

TL;DR: Graphite Messenger encryption uses end-to-end encryption built on the Signal Protocol's Double Ratchet, giving every message its own key plus forward secrecy, and it aligns with the industry's move to hybrid post-quantum protection (ML-KEM). Only your own devices hold the keys, so PrivacyPortal's servers only ever see ciphertext — nothing to hand over.

By the PrivacyPortal team. Last updated July 2026. Written against Graphite Messenger v1.13.25 (public beta).

If you want the short version of how Graphite Messenger encryption keeps your chats private, here it is: every conversation is protected by end-to-end encryption (E2EE), meaning messages are encrypted on your device and only decrypted on your contact's device. The maths behind it is the Signal Protocol's Double Ratchet, which generates a fresh key for every single message. That gives you forward secrecy (stealing today's key doesn't unlock yesterday's messages) and self-healing security. The frontier — post-quantum messaging — adds lattice-based keys so a future quantum computer can't decrypt harvested traffic. Below we explain end to end encryption clearly, show how encrypted messaging works step by step, and walk you through installing and verifying Graphite on your own phone.

First, a name clash worth knowing about

Search "Graphite" alongside messaging security and you'll hit two very different things. Graphite Messenger is PrivacyPortal's free, privacy-first chat app (graphite.chat), currently in public beta at v1.13.25. Paragon Graphite is commercial mercenary spyware that filled security headlines across 2025–2026. They share only a name.

The distinction matters technically. Paragon's Graphite doesn't break encryption at all — it compromises the phone itself and reads messages after your device has already decrypted them. That is the key lesson of this whole article: strong encryption protects data in transit and at rest, but nothing protects a plaintext message from spyware sitting on a compromised endpoint. Encryption and device security are two separate jobs, and you need both.

End-to-end encryption, explained

End-to-end encryption means the two "ends" — your device and your contact's device — hold the only keys that can read a message. In between, the server that relays it (and anyone tapping the wire) sees only ciphertext.

Here is what actually happens when you send a message in a well-built E2EE app:

• Your app encrypts the message locally using a key only your devices and your recipient's devices possess.
• The server stores and forwards the encrypted blob. It never holds a key that can open it.
• Your recipient's app decrypts it locally.

This is why Graphite's tagline is "private messaging with nothing to hand over": if a provider genuinely cannot decrypt your chats, it has nothing meaningful to disclose when someone comes asking. Contrast that with transport encryption (like plain HTTPS to a website), where the provider can read your content because it terminates the encryption.

How encrypted messaging works: the Double Ratchet

Modern secure messengers — Signal, WhatsApp and Graphite Messenger among them — build their end-to-end encryption on the Double Ratchet specification. It is the engine that turns a single shared secret into a near-endless stream of unique per-message keys.

"Double" refers to two ratchets working together:

• The Diffie-Hellman (DH) ratchet: each side periodically sends a new public key, and both parties mix these to derive fresh shared secrets. This is what heals the session after a compromise.
• The symmetric-key (KDF chain) ratchet: a key derivation function advances one step per message, producing a new message key each time and then discarding the old one.

A ratchet, like the tool, only turns one way. Once a key has been used and thrown away, there is no turning back to recover it — which is exactly the property you want.

A simplified diagram of the Double Ratchet: a Diffie-Hellman ratchet feeding a symmetric key-derivation chain that produces one key per message.

Double ratchet forward secrecy and self-healing

Two security properties fall out of this design, and they are why the double ratchet forward secrecy model is the gold standard:

• Forward secrecy: because each message key is deleted after use, an attacker who seizes your phone and extracts today's keys still cannot decrypt the messages you sent last week. Past traffic stays sealed.
• Post-compromise ("self-healing") security: if an attacker briefly steals your keys, the next DH ratchet step introduces fresh randomness they do not have — so the conversation automatically recovers and locks them back out.

The Double Ratchet gives per-message keys: a device seized today cannot decrypt messages that were sent, and whose keys were already deleted, yesterday.

Post-quantum messaging: why "harvest now, decrypt later" matters

Classic E2EE relies on elliptic-curve Diffie-Hellman, which a large-scale quantum computer could eventually break. No such machine exists yet, but adversaries can record your encrypted traffic today and store it to decrypt once one does. Researchers call this "harvest now, decrypt later," and it is why post-quantum messaging is the industry's current frontier.

The building block is NIST's FIPS 203 (ML-KEM), a lattice-based key encapsulation mechanism derived from CRYSTALS-Kyber. Messengers do not rip out their existing crypto to add it — they run it in hybrid mode, layering a post-quantum key alongside the classic elliptic-curve key so an attacker has to break both.

NIST standardised ML-KEM, the lattice-based key encapsulation mechanism derived from CRYSTALS-Kyber, as FIPS 203 in August 2024.

Hybrid post-quantum key exchange: a classic X25519 key and an ML-KEM key are combined so an attacker must break both to compromise the session.

Where the major apps stand in 2026

Signal moved first and furthest. Its 2023 PQXDH handshake added a one-time post-quantum key exchange; then it went further.

Signal shipped its "Triple Ratchet" — adding the Sparse Post-Quantum Ratchet (SPQR), built on ML-KEM-768 — on 2 October 2025, extending post-quantum protection from a single handshake to continuous ratcheting.

Apple's iMessage introduced PQ3 in 2024, and Google Messages/RCS is pursuing similar hybrid protection. Graphite Messenger is built on the same Signal Protocol foundations that this hybrid approach targets, so continuous post-quantum protection is the direction this class of app is heading. If a messenger still has no post-quantum layer at all in 2026, that is now a meaningful gap rather than a nice-to-have.

Graphite vs the big messengers: an encryption cheat-sheet

Every mainstream secure app here uses strong E2EE by default; the differences are in the details.

App	Underlying protocol	Per-message keys (Double Ratchet)	Post-quantum status (2026)	Can the server read your chats?
Graphite Messenger	Signal Protocol / Double Ratchet	Yes	Hybrid PQ is the roadmap direction	No — ciphertext only
Signal	Signal Protocol / Triple Ratchet	Yes	Yes — SPQR (ML-KEM-768), Oct 2025	No
WhatsApp	Signal Protocol	Yes	Following Signal's work; check release notes	No (content)
Apple iMessage	PQ3	Yes	Yes — PQ3, 2024	No
Telegram (default cloud chats)	MTProto (cloud)	No	No	Yes — only "Secret Chats" are E2EE

A quick framework for judging any messenger

Whatever app you use, run its encryption past these five questions:

• Is E2EE on by default, or only in a special mode you have to remember to enable?
• Does it use per-message keys (a Double Ratchet), giving forward secrecy?
• Is there a post-quantum layer, at least in hybrid mode?
• Can you verify a contact's keys (safety numbers or QR) to defeat a man-in-the-middle?
• How much metadata — who you talk to, and when — does the server retain?

Graphite Messenger is designed to answer the first four "yes" and to keep the fifth as close to nothing as possible — the "nothing to hand over" principle.

How to install and verify Graphite Messenger encryption

This is the part you can do right now. It takes about ten minutes and works on any modern Android phone, including a de-Googled handset.

Before you start — the honest warnings:

• Back up first. Installing a messenger is low-risk in itself, but if you plan to switch phones or re-flash, read our guide on how to back up your Android before flashing so you never lose your keys or history.
• Your keys live only on your device. If you lose the device and your recovery details, no one — including PrivacyPortal — can restore your encrypted messages. That is the price of true E2EE.
• Encryption cannot save a compromised phone. Because spyware reads plaintext at the endpoint, the device matters as much as the app. That is the thinking behind our de-Googled Android phones, which cut the always-on data collection that widens your attack surface.

Prerequisites: an Android phone, a network connection, and a contact who also installs Graphite so you can test a real conversation.

1. Install Graphite Messenger from the verified build in the "Modules, apps & files to try" section at the end of this article. Use the official build and avoid third-party mirrors.
2. Create your account by following the on-screen prompts, then store your recovery details somewhere safe and offline. The app generates your encryption keys locally during this step.
3. Start a chat with a contact who also uses Graphite. The first message you exchange establishes the Double Ratchet session automatically — there is nothing to configure.
4. Verify the encryption. Open the conversation's verification screen and compare your safety numbers (or scan each other's QR code) in person or over another trusted channel. Matching numbers prove no one is intercepting your keys. This is the single most important step.
5. Confirm forward secrecy in practice by sending several messages, then noting that each one is sealed with a key that is used once and discarded — a stolen device key cannot reopen earlier messages.
6. Harden the endpoint. Enable an app passcode or biometric lock and turn off message previews on your lock screen, so a shoulder-surfer (or screenshotting malware) has less to grab.

The verification screen in Graphite Messenger: compare safety numbers or scan a QR code to confirm no one is intercepting your keys.

What Graphite Messenger encryption does — and doesn't — protect

Encryption is necessary but not sufficient. Here is the honest boundary of what even perfect graphite messenger encryption can and cannot do.

It protects:

• Message content in transit across the network.
• Message content on the server, which only ever holds ciphertext.
• Past messages if a current key leaks (forward secrecy).

It does not protect against:

• A compromised endpoint. Spyware such as Paragon's Graphite reads messages after your device decrypts them. No messaging encryption can stop malware that already owns the phone.
• Screenshots and plaintext backups. If the person you message screenshots the chat or backs it up unencrypted to a cloud, the maths is moot.
• Metadata. Depending on the service, the fact that two people messaged at a certain time can still be observable.
• Unverified contacts. If you never check safety numbers, a determined attacker could attempt a man-in-the-middle before the session is pinned.

Frequently asked questions

Is Graphite Messenger encryption end-to-end by default?

Yes. Every conversation uses end-to-end encryption from the first message, with no separate "secret chat" mode to switch on. Your keys are generated and stored on your device, and the server only ever relays ciphertext.

What is the Double Ratchet in simple terms?

It is the algorithm that gives every message its own encryption key. One ratchet mixes in fresh Diffie-Hellman keys to heal the session after any compromise; another advances a key-derivation chain so each message key is used once and then deleted. Together they provide forward secrecy and self-healing security.

Does Graphite Messenger use post-quantum encryption?

Post-quantum messaging is the current frontier, built on NIST's ML-KEM (FIPS 203, August 2024) and run in hybrid mode alongside classic elliptic-curve keys. Signal shipped continuous post-quantum ratcheting in October 2025, and Graphite is built on the same Signal Protocol foundations that this hybrid approach targets. Check your version's release notes for the exact status.

Is Graphite Messenger the same as Paragon "Graphite" spyware?

No. Graphite Messenger is PrivacyPortal's private chat app. Paragon Graphite is unrelated mercenary spyware that compromises a phone and reads messages after they are decrypted on the device — it bypasses encryption at the endpoint rather than breaking it. They only share a name.

Can PrivacyPortal read my messages or hand them over?

No. Because the encryption keys never leave your devices, PrivacyPortal's servers hold only unreadable ciphertext — the "nothing to hand over" design. The trade-off is that if you lose your device and your recovery details, your message history cannot be restored.

How do I know the encryption is actually working?

Verify safety numbers. Open a conversation's verification screen and compare the safety number (or scan the QR code) with your contact through a trusted channel. If they match, you have a confirmed end-to-end encrypted session with no man-in-the-middle.

Encryption is only half the story — the other half is the device it runs on. Install Graphite Messenger from the verified download below, verify your safety numbers, and you will have a chat that is genuinely private end to end.