
Most communication platforms store everything: messages, metadata, call logs, IP addresses. Even "encrypted" services often hold the keys. When a breach happens, or a subpoena arrives, all of it is exposed.
Hushroom takes a different approach. We designed the system so that we cannot access your conversations. Not "won't", technically cannot. Encryption keys live in the URL fragment, which by the HTTP specification never reaches our server. Room data is stored only in RAM and auto-deletes when the timer expires.
There is nothing to subpoena, nothing to breach, nothing to leak. That's not a policy promise. It's how the system is built.
Hushroom is built by Benbo.se, a Swedish software company focused on privacy-first digital tools.
We believe privacy is a right, not a feature. Every architectural decision in Hushroom is made with one question: "What happens if our server is fully compromised?" If the answer involves exposing user data, we redesign until it doesn't.
The encryption key is embedded in the URL fragment (#key=...), which never reaches our server. We cannot read your messages, even if we wanted to.
All room data auto-deletes when the timer expires. No backups, no archives, no recovery. Data stored only in RAM (Redis), never written to disk.
We collect only what's strictly necessary to prevent abuse. No IP logging, no browser fingerprints, no user accounts for participants.
Our security architecture is publicly documented. We explain exactly what the server stores, what it can disclose, and what it cannot. No black boxes.
| Frontend | React + TypeScript |
| Text encryption | TweetNaCl (xsalsa20-poly1305) |
| Voice / Video | LiveKit with E2EE (self-hosted) |
| Backend | Node.js + Express + WebSocket |
| Data store | Redis (in-memory only, no disk persistence) |
| Hosting | Self-hosted in Sweden (EU) |
Create an encrypted room in about 10 seconds. No sign-up required for participants.