Why QxChat exists
#You have seen what happened to Session. And do not get us started on Telegram, we would be here all day.
Session shut down. Telegram became a running joke for privacy: encryption you have to manually turn on (seriously?), metadata leaking out of every seam, and a CEO who cannot decide if he is running a messenger or a crypto casino. Every single platform that promised you anonymity is either dead, compromised, or slowly selling you out to advertisers.
Nothing reliable came along. Nothing that actually respected the people using it. So we stopped waiting and built it ourselves.
QxChat is zero-logs by architectural design. E2EE is not buried behind a hidden toggle in settings that you will never find. It is on by default, handled entirely on your device. Not on "our" servers, not in "the cloud". On your hardware.
And because the entire project is open source (not "open core", not "source available", genuinely open source), you can read every single line of code. Audit it, fork it, host it, break it. That is the kind of transparency Discord and Telegram will never give you.
- Store your metadata on servers you cannot inspect: Yes
- Make encryption opt-in so 99% of people never use it: Yes
- Keep the backend code closed because "trust us bro": Yes
- Change their privacy policy whenever advertisers ask: Absolutely
- Ship a 200 MB Electron app that eats a gigabyte of RAM: Every single time
- Store metadata: No. Zero. None.
- Telemetry or trackers: No, never.
- Client-side E2EE on by default: Yes, always.
- Fully open source (Rust + Vue 3): Every single line.
- You host it, you own everything: Yes, that is the entire point.
- 45 MB RAM, 6 MB installer: Yes, seriously.