A list that doesn't exist can't leak

Why I built a messenger that never asks for your email, your phone number, or a password.


You have probably had the email. "We recently became aware of an incident involving some of your information." Your address, sometimes your phone number, sometimes a password, is now in a file that strangers trade.

The usual response is to promise better locks. Stronger encryption at rest, more audits, a bigger security team. All of that is good. None of it changes the basic shape of the problem: the company is holding a list, and a list can be taken.

I wanted to try the other answer. Don't hold the list.

What LILAC doesn't ask for

LILAC is a messaging app for iPhone and Android. When you open it for the first time, there is no sign-up screen. No email field. No phone number. No password to invent.

That is not a shortcut we plan to close later. It is the design.

If you picture our user table, it has the columns you would expect — email, phone, password — and zero rows.

So how do people reach you?

With an invite. You show a QR code in person, or send a link. The other person opens it and you are talking. They don't register either.

The part I care about most is what happens afterwards. On most apps, "blocking" someone leaves you on their contact list; you are one tap away from being reachable again. In LILAC you shared a link, not your number, so you can take the link back. Once you do, it stops working and nothing new from them can reach you.

What our server actually sees

Messages are sealed end to end. Our relay stores three things: a sealed envelope, the random mailbox address it is going to, and a timestamp of when that mailbox was last used. It cannot open the envelope. It does not hold your keys, your contact list or your name. A mailbox nobody touches for 24 hours is forgotten, mail included.

If someone seized the server, they would find sealed text waiting for delivery, random mailbox addresses and those timestamps. No keys, no contacts, no readable messages.

One thing no relay can avoid: the network it runs on (ours is hosted on Cloudflare) sees the IP address of each connection. Our code does not store it, but LILAC does not hide it the way Tor would.

What LILAC can't do

I would rather say this plainly than have you find out later.

That last one is a real trade-off, not a footnote. The same property that means we have nothing to leak means we have nothing to hand back.

Why bother

Most of us have accepted a strange bargain: to talk to one person, you hand a company a permanent identifier that connects to your bank, your logins and everything else you do. Then you hope they look after it.

For a lot of conversations — someone you met once, a buyer on a marketplace, a group that will dissolve in a month — that bargain is far too expensive. A link you can take back is enough.

LILAC is free, with no account, no ads and no tracking. It is out now:

I am one person building this. If you find a claim here that doesn't hold up, I want to hear about it: hello@lila-c.com.