Unnmute was born from a simple observation: the people closest to a problem almost always know how to fix it — but fear of retaliation keeps them silent. We're changing that with infrastructure built for true anonymity.
Whether it's a student facing bullying, an employee witnessing harassment, or a citizen reporting a broken pipe — we believe accountability starts with the freedom to speak without fear.
We architected the system from the network layer up. IP is stripped at the CDN, no cookies, no fingerprinting. Even our own engineers cannot trace a reporter.
Anonymous reporting is only half the story. Auto-escalation, SLA timers, and full audit trails make sure every voice leads to a resolution.
Per-organisation encryption keys. Zero PII stored. No cross-tenant access — even by us. The system is engineered so trust isn't a promise; it's a property.
The idea came from a conversation in a classroom. A teacher mentioned, almost in passing, that students knew exactly which washrooms were unsafe, which classmates were being bullied, and which staff members were behaving inappropriately — but none of them would ever tell an adult, because the consequences of being identified were too high.
The same story played out elsewhere. Employees who knew the shipping line was cutting corners. Citizens who knew which clerk demanded bribes. Hostel residents who knew the warden was unfit. Everyone knew. Nobody said.
Existing “anonymous” tools couldn't actually guarantee anonymity — emails leak, suggestion boxes get opened, IPs get logged. So we built Unnmute as infrastructure, not as a form. The goal was simple: make it technically impossible to identify a reporter, then add the rails — escalation, analytics, audit — to turn those voices into resolutions.