Phantom Chat is the messenger I built because every other one felt like a compromise.
Signal wants my phone number. WhatsApp wants it too. iMessage is tied to my Apple ID. Telegram's encryption is opt-in. Wire wants an email. Threema is decent but the local export still leaks structure. I wanted to message a friend without handing over a permanent identifier first.
So I started building Phantom Chat — solo, in evenings and weekends, from Western Australia. Two design choices were locked in from day one:
1. Anonymous sign-up. No phone, no email, no real-name field. You pick a username, that's it. Contact discovery is invite-code-only — there's no way to search for or browse other users. If your invite code never leaves the people you sent it to, your account essentially doesn't exist outside that circle.
2. Post-quantum encryption from day one. Apple shipped PQ3 on iMessage in 2024. Signal added PQXDH the same year. WhatsApp still doesn't have it. I figured if the giants were finally doing it, an indie shipping in 2026 had no excuse not to. Every conversation runs through a hybrid Signal Protocol Double Ratchet + NIST FIPS 203 ML-KEM-768 (Kyber). "Store now, decrypt later" attacks don't work on it.
The business model is the part I'm most opinionated about: no VC, no ads, no data sales. I've capped lifetime "Founder" seats at 500 specifically so I never have enough runway pressure to take outside investment or sell user data. Subscribers fund the company. If I run out of subscribers I run out of company — but I never become a different company that wants to sell your messages to a model trainer.
The fight with myself for the last six months has been honesty in marketing — I do code-vs-claim audits before every release and have removed three site claims that didn't quite hold up (Sealed Sender, an outdated iMessage comparison, and the word "air-gapped"). I'd rather lose a hook than ship spin.
Now in public TestFlight beta, Apple-approved on first submission. Looking for testers, technical critique on the cryptography, and the IH crowd's perspective on the indie-bootstrapping side. Happy to chat about any of it.
This is one of the stronger privacy-product posts I’ve seen here because you’re not just saying “secure messenger.” You’re showing the tradeoffs you refused to accept.
The strongest part is actually the code-vs-claim discipline. In privacy tools, that matters more than clever copy because the buyer is already trained to distrust marketing language.
I’d be careful with one thing though: the post is very strong for technical readers, but the homepage/beta funnel probably needs two layers.
For technical users: post-quantum encryption, no permanent identifier, invite-only discovery, claim audits.
For normal privacy-conscious users: “message without handing over your phone number, email, or identity first.”
If those two audiences see the same dense explanation too early, you may earn respect but lose activation.
The sharper test might be: can Phantom Chat turn privacy skepticism into a beta install in under 30 seconds?
That means the first screen has to make the trust promise extremely simple, then let the technical proof sit one click deeper.
Thank you Aryan, I am going to make some changes to the website now.
Glad it helped.
The website changes are probably worth doing carefully because privacy products can lose people fast if the first screen feels too technical or too vague.
Drop your email and I’ll send over a tighter version. I’d keep it focused on the homepage message, trust layers, and how to turn privacy skepticism into beta installs without overwhelming people.
contact @ veilusdigital . co
Just sent you a note.
Kept it focused on the homepage trust layer, first-screen message, and how to turn privacy skepticism into beta installs without making the page too technical too early.