Thanks for testing Essenger
You are among the first to try private messenger before the public launch. The goal of the beta is to find everything that breaks or confuses while there are few users. Your feedback directly affects the release.
How to get started
In the browser
Works immediately on your computer and phone - no need to install anything. Can be added to the home screen as an application (PWA).
Open Essenger →On iPhone (TestFlight)
1.Install the free app TestFlight from the App Store.
2.Open the invitation link below on iPhone and click "Accept".
The link must be opened on the iPhone itself.
What is encrypted and what is not yet
Honestly, without marketing: personal and group messages, files and voice protected by end-to-end encryption (E2E) - the server sees only the ciphertext, the keys do not leave your device; added post-quantum layer (ML-KEM-768). Calls they work on standard WebRTC encryption: the media stream is encrypted point-to-point (DTLS-SRTP), but end-to-end encryption of the signaling itself is still being finalized - this is protection against passive eavesdropping, but not full E2E like messages. There has not yet been an independent external audit of cryptography.
What is especially important to check
- Registration, login, restoration of access using seed phrase and PIN.
- Personal messages and groups: replies, reactions, disappearing messages.
- Photos, files and voice - sending and receiving, including between iPhone and browser.
- 1-on-1 calls (web ↔ iOS): dial-up, audio, end, chat summary.
- Changing device / re-login - are the history and keys saved?
- Anything that looks strange, slow or unclear is also a bug.
Found a bug? Tell me
This is the main benefit of beta. The more detailed you describe, the faster we will fix it:
- Device and platform (browser/iPhone model, version).
- What did you do step by step?
- What they expected to see - and what actually happened.
- Screenshot or screen recording if possible.
What to wait for now
- This is an active development - there may be some rough edges and occasional glitches.
- The calls are experimental (see the block about encryption above).
- One server without geographic redundancy - short-term interruptions are possible.
- The cryptography has not yet undergone an independent external audit.