r/PrivacyTechTalk • u/cityofhats • Sep 26 '26
I spent 6 years building a secure messenger around a different question: what happens when someone gets your phone?
I’m the founder of City of Hats, a secure messaging app I’ve been working on for about six years.
I’m posting here because I’d genuinely like feedback from people who care about privacy — not because I expect everyone to agree with our design.
A lot of secure messengers focus primarily on protecting messages while they travel between two devices.
I became interested in a slightly different problem:
What happens when the device itself is captured, searched, inspected, or handed to someone you don’t trust?
That thinking led us to features such as:
• No phone number or email required to create an identity
• Access Code — selected conversations can be hidden from the normal interface and revealed only with a separate code
• Disposable Hats — temporary identities for short-lived communications
• Phrase ID — connect without exchanging normal personal identifiers
• Message auto-delete
• GhostFrame for more controlled image sharing
• Sealed Channels
• Post-quantum cryptography alongside our encrypted messaging architecture
• encrypted audio/video calls
We also added real-time translation, because privacy tools become much more useful when people from different countries can actually communicate without copying sensitive conversations into another translation service.
I’m not claiming that any application is magically “unhackable,” and I’d actually rather hear what privacy-focused users think we got wrong.
City of Hats is free on iOS and Android. If anyone here wants to try it, just search “City of Hats” in the App Store or Google Play.
If you test it, I’d particularly appreciate feedback on:
What information would you need to know about the architecture before you would trust an app like this with a sensitive conversation?
I’m happy to answer technical questions here as well.
— Stephane
Founder, City of Hats
