The Private Messenger for People Who De-Google Their Phones

TL;DR: The best degoogled phone messenger in 2026 has a Google-free build (F-Droid or direct APK), reliable push notifications that don't rely on Firebase Cloud Messaging, minimal identifiers, at-rest encryption and audited open source. Strong picks include Signal, Molly-FOSS, SimpleX Chat, Session, Briar and PrivacyPortal's own Graphite Messenger.

By the PrivacyPortal team. Last updated July 2026.

If you've wiped Google off your Android — whether that's GrapheneOS on a Pixel, LineageOS, /e/OS, or a de-Googled handset from us — the hardest app to replace is usually your chat app. A good degoogled phone messenger has to do one thing mainstream apps quietly outsource to Google: deliver push notifications without Firebase Cloud Messaging (FCM), the Google service most apps use to wake up and show a new-message alert. On a phone with no Google Play Services, an FCM-only app simply goes quiet until you open it. This guide explains what to look for, compares the leading private messengers for 2026, and walks you through installing one on a Google-free device. New here? Start with our beginner's guide to de-Googling an Android phone.

Image: A de-Googled Pixel running GrapheneOS with a private messenger open and no Google account signed in.

What makes a good degoogled phone messenger?

Not every "encrypted" app behaves well once Google Play Services is gone. On a Google-free phone, five things actually matter:

• A Google-free build — installable from F-Droid or a verified direct APK, with no hard dependency on Play Services.
• Non-FCM push — reliable notifications delivered by a persistent WebSocket, UnifiedPush, or a foreground service instead of Firebase.
• Minimal identifiers — ideally no phone number and no persistent user ID linking messages back to you.
• At-rest encryption — the message database is encrypted on the device itself.
• Reproducible, audited open source — code others can independently build and review.

Miss the first two and you'll get an app that either won't install or shows notifications hours late. The rest separate a merely functional chat app from a genuine messenger for privacy enthusiasts.

The push-notification problem no one warns you about

This is where most people trip up. On a standard Android phone, apps register with FCM; Google's servers hold one connection open and wake each app when a message arrives. Remove Google and that pipe disappears. A well-built no-Google messenger replaces it in one of three ways: a persistent WebSocket the app keeps open itself, UnifiedPush (an open push standard you can self-host or route through a provider like ntfy), or a foreground service that stays connected in the background.

Signal now automatically falls back to a persistent WebSocket connection when Firebase Cloud Messaging is unavailable, so it delivers notifications on Google-free phones out of the box.

The trade-off is battery and a small "app is running" notification. In practice that's a fair price — and Android's Doze and App Standby power-saving modes are the real enemy, not the connection itself.

Image: Android's battery settings showing a messenger app set to "Unrestricted" so its non-FCM push connection survives Doze mode.

The best private messengers for de-Googled phones, compared

Here's how the leading options stack up for private messaging without Google. This is a privacy messenger 2026 shortlist built around real behaviour on Google-free phones, not marketing claims.

Messenger	Runs without Google/FCM	Push method	Identifier needed	Open source
Signal	Yes (WebSocket fallback)	FCM or persistent WebSocket	Phone number	Yes, reproducible builds
Molly-FOSS	Yes (no Google code)	WebSocket / UnifiedPush	Phone number	Yes
SimpleX Chat	Yes	Background service / notification servers	None	Yes
Session	Yes	Foreground service, onion-routed	Random Session ID	Yes
Briar	Yes	Persistent Tor service (peer-to-peer)	None (local exchange)	Yes
Graphite Messenger	Yes (direct APK)	Non-FCM (public beta)	Minimal	Public beta

Signal and Molly-FOSS

Signal remains the most practical choice for reaching people who aren't privacy nerds, and it now works without Google. Molly-FOSS is a hardened, fully Google-free fork of the Signal Android client with extra security options and UnifiedPush support. Both still tie your account to a phone number, which is the main limitation.

SimpleX Chat

SimpleX Chat uses no user IDs and no phone numbers at all — it is the only major messenger with no persistent account identifier for an attacker to correlate.

Instead of accounts, SimpleX connects you through one-time invitation links routed via relay servers you can self-host. It's the strongest choice for metadata minimisation. See the SimpleX Chat source and protocol docs on GitHub.

Session and Briar

Session gives you a random ID (no phone number) and routes messages over an onion network. Briar goes furthest for resilience: it's peer-to-peer over Tor, Wi-Fi or Bluetooth with no central server at all — ideal when infrastructure is unreliable, though both parties generally need to be reachable.

Which one should you choose?

A quick decision framework for a no google messenger:

• You need to reach ordinary people → Signal, or Molly-FOSS for a stricter Google-free build.
• You want zero identifiers → SimpleX Chat (no ID/number) or Briar.
• You want no phone number but server-backed convenience → Session or SimpleX.
• You expect network outages or censorship → Briar's peer-to-peer design.
• You want a PrivacyPortal-native app to trial → Graphite Messenger.

Where Graphite Messenger fits in

Graphite Messenger v1.13.25 is a free public beta from PrivacyPortal, built on the principle of "private messaging with nothing to hand over."

Graphite is our own take on a Google-free messenger, delivered as a direct APK for de-Googled phones and designed around collecting as little about you as possible. Being an honest brand: it's still in public beta, so treat it as one to try alongside a mature default like Signal or SimpleX rather than your only lifeline. If it suits how you work, it's a genuinely private messenger for privacy enthusiasts who'd rather their chat app hand nothing over in the first place. You'll find the download in the Modules, apps & files to try section below.

How to install a Google-free messenger on a de-Googled phone

Prerequisites: a de-Googled Android phone (GrapheneOS, LineageOS, /e/OS or a PrivacyPortal handset), a web browser or F-Droid, the messenger's APK, and a second device or a friend to test with. Allow about 15 minutes.

1. Back up first. Before installing or changing anything, back up your existing chats and your device. This is non-negotiable — sideloading and messenger migrations can lose data.
2. Enable app installs. Go to Settings → Apps → your browser or file manager → "Install unknown apps" and allow it. On GrapheneOS this permission is granted per app.
3. Download the APK. Get Graphite Messenger from the Modules, apps & files to try section below, or install Molly-FOSS, SimpleX Chat or Briar from F-Droid.
4. Verify the source. Prefer F-Droid or the official project site and check the published signature or checksum where available, so you know the file wasn't tampered with.
5. Install and open the app. Tap the APK, install, then launch it. Complete onboarding — SimpleX creates a local profile with no phone number; Signal and Molly register a number.
6. Grant notification permission. Allow notifications when prompted (Android 13 and later require this explicitly).
7. Exempt the app from battery optimisation. This is the single most important step for reliable non-FCM push: Settings → Apps → [your messenger] → Battery → Unrestricted. Without it, Doze mode will eventually kill the background connection.
8. Keep any "running" notification. SimpleX, Session and Briar show a persistent foreground-service notification — leave it on; that's what keeps messages arriving.
9. Verify it works. Lock your phone, wait a couple of minutes, then have your second device or a friend message you. If the alert arrives with the screen off, your Google-free push is working.

Image: Installing the Graphite Messenger APK on a Google-free phone and granting notification permission during setup.

Common pitfalls on de-Googled phones (and fixes)

• Battery "optimisation" killing the connection. The number-one cause of missed messages. Set the app to Unrestricted.
• Expecting FCM-speed delivery. WebSocket and foreground-service push are reliable but can lag a few seconds after your phone re-joins a network.
• Swiping away the persistent notification. On SimpleX, Session and Briar this stops delivery — leave it be.
• Assuming a de-Googled phone hides your number. Signal and Molly still register with, and reveal to contacts, a phone number. Choose SimpleX, Session or Briar if that matters.
• Sideloading from random mirrors. Only use F-Droid or official sources and verify signatures.
• Expecting a messenger to fix your banking app. It can't — see the safety note below.

Rooting, Play Integrity and staying safe

None of these messengers need root — you can run all of them on a locked, de-Googled GrapheneOS phone, which is the more secure setup. That matters, because de-Googling and rooting are different things with real risks:

• Unlocking the bootloader wipes the device. Back up everything first; there is no undo.
• Rooting breaks integrity checks. Using Magisk, KernelSU/KernelSU-Next or APatch reliably fails Google's Play Integrity "Strong" and usually "Device" verdicts, which breaks many banking and payment apps. The GrapheneOS project explicitly recommends against rooting.
• No one can promise universal success. No root method or configuration can honestly guarantee it will pass every integrity or anti-tamper check, and we'd never claim a messenger defeats a specific bank's detection. Be wary of anyone who does.

If banking apps are your worry, read how Play Integrity affects banking apps before you flash anything.

Frequently asked questions

Do I need Google Play Services to send private messages?

No. Private messaging without Google is entirely normal in 2026. Signal (via its WebSocket fallback), Molly-FOSS, SimpleX Chat, Session and Briar all run with no Play Services. The only real hurdle is push notifications, solved by WebSocket, UnifiedPush or a foreground service.

What is the best no-Google messenger for privacy in 2026?

It depends on your threat model. For the fewest identifiers, SimpleX Chat wins — no user IDs and no phone number. For mainstream reach, Signal or Molly-FOSS. For a server-free, censorship-resistant option, Briar.

Do push notifications work without FCM on GrapheneOS?

Yes. Apps that use a persistent WebSocket, UnifiedPush or a foreground service deliver notifications on GrapheneOS with no Google Play Services. The key is exempting the app from battery optimisation so Doze mode doesn't sever the connection.

Will a degoogled phone messenger work on a rooted phone?

The messengers here run fine on de-Googled and even rooted phones. But rooting or unlocking the bootloader fails Play Integrity, which tends to break other apps (banking, some streaming), not usually the messengers themselves. No setup can promise passing all checks.

Is Signal a good choice on a de-Googled phone?

Yes — it falls back to a WebSocket when FCM is missing, so it just works. Its limitation is the required phone number. Molly-FOSS is a hardened, Google-free Signal client, and SimpleX Chat is the pick if you want no number at all.

What is Graphite Messenger?

Graphite Messenger is PrivacyPortal's free public-beta private messenger (v1.13.25), tagline "private messaging with nothing to hand over," built for Google-free phones. You can learn more and download it from the Modules, apps & files to try section below.