I would say no, but not because of their malice.

Reading over the FAQ they use Matrix to bridge the various messaging services to your one app which means the e2e encryption offered by those services ends at the beeper servers. If their servers were compromised they would be able to see the messages before matrix can forward them to beeper.

I have no experience with it and can’t claim to know, but the privacy advocate in me tells me it can use everything because it wants access to everything so it can datamine from every app at once.

Again, I don’t know this specific app, but literally every other non Foss app is just a front for granted permissions.

Ehhhh, depends on what you want to trust them with.

Dank memes and dad jokes, sure.

Communicating with a friend about something personal, I wouldn’t.

Honestly, I use it. For my purposes it’s good enough and the reduced security is worth it for the availability it provides me.

I don’t use it for work and I use signal separately for secure transmission.

Can you trust anyone? How much trust do they need to have. If you actually want to be secure. Don’t use any encryption provided inside a program. Even if code is supposedly open source. If you didn’t audit the code before compiling it yourself. It may as well still be a black box. If tight security is a must. Then nothing beats negotiating one time pads with those you are going to interact with. They’re one of the few things that are actually uncrackable unless someone gets a hold of your pad. Write whatever it is you need to write encrypted using a program for one-time pads or just a basic algorithm and then send it in clear text or any other messenger you want. Only people who have access to your pads will be able to decrypt it.

You can self host and the main matrix bridge maker works with them… also this year self hosted bridges locally on your phone incoming .