Naven
Glossary
End-to-end encryption
A way of scrambling a message so that only the sender's device and the recipient's device can read it — the server carrying it cannot.
The keys live on the two devices and never reach the server. That is the whole idea: the company running the service is not trusted, because it does not need to be. It is the strongest privacy guarantee a messenger can make, and it is why Signal and WhatsApp are described the way they are.
It also rules out anything the server would have to read the message to do. Screening a message before it sends, scanning an attachment, translating a thread — none of these are possible on content the server cannot see. Systems that claim both are usually doing the work on the device, or not doing it.
Where Naven stands
Naven is not end-to-end encrypted, and says so plainly. Messages are screened against twelve published categories before they send, and a server that cannot read a message cannot screen it. Anyone whose first requirement is end-to-end encryption should use Signal — that is the honest answer, and it is on Naven's comparison pages too.