Beeper is a unified messaging platform that integrates multiple chat services including Whatsapp, Signal, and RCS. Recently, the app enabled direct on-device connections to messaging networks, eliminating the need for their cloud to sync to chat apps.
Chat history is stored e2e in the cloud and their business model seems to be based on selling subscriptions.
What do you think of this service?
Avoid.
Care to elaborate? Iâm sure they collect some telemetry but for those of us with only a few friends on Signal it seems like a good way to declutter
Thanks for offering helpful information in a kind and respectful way
Use it myself.
Works quite well for getting chats into one place.
Ideally more people need to get with the times and get onto signal rather that being stuck in the past with Facebook/whatsapp
Only thing is that as others have pointed out, is that you are trusting a 3rd party to your chats but then you are forced to use Facebook anyhow so itâs not too bothering
I sincerely apologize for that response. I wasnât in a good mood but that is no excuse.
Iâll try again:
The usage of Beeper, even in the on-device mode, is still a breakage of trust the trust of yourself and your contacts by introducing a third-party.
You have to expect this third-party to (re-)implement all of the existing security measures that the original app does and hope they stay in sync.
Even if you donât trust say Facebook, they likely did do their encryption correctly and that canât be said for a third-party like this.
As this app is a bit different compared to say Molly which just forks the official client and makes changes on top, Beeper on the other hand is reverse engineering the implementations for their own implementations which is inherently error prone.
Furthermore even if they have a seemingly clear business model right now, that can always change in the future, especially given the large amount of $$$ invested so far, and there should be no reason to trust them with such sensitive data.
And again, Signal is (nearly entirely) open-source, using Beeper to interact with Signal is just not a great idea.
But you might ask âDidnât we have tools like this in the past like Pidgin?â. Yes, but those services back then were all much similar and simpler protocols, and encryption wasnât really a thing back then so it was far easier to implement.
Iâll re-iterate again, just because youâre having to use one bad company doesnât mean you should subject yourself and your contacts to additional bad companies. This is a very bad outlook.
Iâm not so sure this is true. While it is certainly true that it canât literally be as secure, in my testing connecting WhatsApp and Signal, all Beeper does is use both of those appsâ existing sync solutions. For example, I used Signalâs Linked Device feature in set up.
Idk, for the layperson, it seems like a solid solution.
Connecting via the linked device feature is irrelevant to how theyâre reimplementing protocol, that is just how theyâre binding to your account.
All my points still stand.
Works OK, but Signal isnât well integrated. They use the linked devices feature, which is convenient but as result you canât call people. They could develop their own fork of Signal and integrate it inside, but that could be costlier and uncertain.
I do use Beeper, but I would link to this post as a caveat:
Their privacy policy isnât great. Iâll switch eventually.
It seems pretty standard stuff. They donât share it with advertisers or others. They have Sentry tracking but no Google or Facebook third-party tracking which is good.
I mean, it is a 3rd party anyway.
So if you donât mind your WhatsApp/Discord/Twitter DMs to be public, then feel free to use it. It is actually quite practical to have everything in 1 place and makes it very nice to use.
If itâs for private topics, keep the messaging apps to a minimum (preferably one, like Signal) and skip the middlemen like Beeper. Youâll never know what they do with your credentails/API keys.
I donât know, this statement is pretty broad and cover pretty much any use case:
Service Providers. We may share your information with third parties that perform services for us (âService Providersâ) who perform services for us or on our behalf and require access to such information to do that work. We use Service Providers for payment processing, security, network management, and cloud storage, as well as other Service Providers.
Might as well write, we may share your info (Identifiers, Commercial information, Internet or other electronic network activity information, Geolocation data, Audio, electronic, visual or similar information and Inferences we make) with anyone we deem necessary.
beeper discussion is back on the menu?
weird but ok
I know a friend who uses it and loves it
and I have trie to urge them to use the signal app for signal but safe to say beeper has made them to be dragged away, ugh.
but anywho, unless you are forced to use whatsapp or meta apps or other messengers like it, I donât think I recommend it to anyone, maybe you can use it to get the ânormieâsâ messaging apps declutterred while allowing room for signal but thatâs about as far as I would go for recommendations.
It doesnât cover sharing for ads or profiling. The key phrase is âwho perform services for us or on our behalfâ. So think cloud services for example.
Just to be clear, I donât think we should recommend it.
It will be probably not a recommendation but I wonder if it could be a better client replacement for those who still need to use Whatsapp to avoid at least their embedded AI and trackers.
Their android app has some trackers, but you can use any matrix client instead
I mean you are trusting automattic with metadata or otherwise data coming in transit.
but yeah that was my point, if youâre forced to use say whatsapp this is very viable. And hey if im being honest id trust them more than meta I guess
yep it is self hostable or replicable.
but especially in the area of ânormiesâ, where the argument is, declutter your apps using it and should allow them space for say signal, yes beeper would undermine signalâs security, though I guess it is mitigated with on-device support as of June 2025 which is lovely?
but honestly again in ânormieâ context I consider that a win over not chatting on signal
I just tried it on GOS and it crashes immediately triggering a memory tagging error. 
Not a good start.