Why We'll Never Send a 'Someone Likes You' Notification

There is a genre of notification dating apps keep rediscovering, because it works: Someone likes you. Three words, no name attached, engineered to be opened. It costs the sender nothing to generate, and it pays out in the only currency that kind of app actually banks — your return visit. Often the name behind the tease sits on the far side of a paywall, which tells you what the notification really is. Not news. An invoice.

We built AnonymousCrush around a different bet, and it pushed us somewhere companies don't usually go: publishing every email our system can send, in full, at /emails. This is the story of why that page exists, why everything on it is deliberately dull, and why the dullness is a safety feature — starting with the part that's useful even if you never touch our product.

Your lock screen has an audience

A notification feels private because it's addressed to you. But it isn't delivered to you; it's delivered to your phone, and your phone is face-up on the kitchen table, mirrored onto a laptop in a meeting, glowing in your hand on a crowded train. Email is no better. Preview lines render in shared inboxes, on smartwatches, in the corner of a projected screen.

Most of the time the audience is harmless — a coworker, a roommate, a curious seatmate. Sometimes it isn't. For someone quietly leaving a bad relationship, a subject line that says the wrong thing at the wrong moment is not an embarrassment. It's a hazard. We think about that person constantly; our safety page is written with them in mind.

So the design question is never "what does this message tell the recipient?" It's "what does it tell everyone else who can see the recipient's screen?" Judge any app's notifications by the second question and a lot of playful copy stops looking playful.

The entire outbox, published

AnonymousCrush can send exactly five emails. Not five kinds, roughly — five, and you can read every word of each at /emails: an address-verification link, a password reset, a notice when someone tries to register an address that already has an account, a one-time confirmation for people who ask to be excluded from matching, and one all-purpose message titled "You have a private account update."

That page is not a marketing summary of our emails. It renders from the same code our mail system reads when it actually sends, so the published list and the real one cannot quietly drift apart. If we ever added a sixth email, it would appear there in the same release. We wanted "this is the complete list" to be a fact enforced by how the software is built, not a promise resting on our ongoing good behavior.

Boring on purpose

Every one of the five reads like it was written by a bank, and that is the compliment we were aiming for. No names. No hearts. No "we have news!" Nothing romantic anywhere, ever. Each subject line had to earn its place under one assumption: a stranger will read it, because eventually a stranger will.

An email from us does reveal one thing we cannot avoid — that your address has crossed paths with AnonymousCrush. An inbox always discloses that much about any service, and we won't pretend otherwise. What we can control is that it reveals nothing more: not what happened, not who is involved, not whether the news is good.

The email that doesn't exist

There is no "someone likes you" template on that page because there is no such email in the system — not toned down, not opt-in, not reserved for later. The words have simply never been written.

We refuse it for two reasons. The first is the bait problem. An anonymous tease is a lever that moves people, and a company holding that lever will eventually be tempted to pull it — to re-engage you, to upsell you, to fish. The clean solution is to never build the lever.

The second reason is quieter. On AnonymousCrush, naming a crush sends nothing to anyone. The person you name is never told, never notified, never shown a list to browse; their address is stored only as a keyed cryptographic fingerprint plus a display mask. If they never feel the same, no email ever announces it — the silence simply continues, indistinguishable from you never having typed their name. A "someone likes you" email would demolish that guarantee in a single send. About a crush, our system speaks only when it has something mutual to say: you named each other, and you're both told in the same moment. The full mechanics are at /how-it-works.

One envelope, whatever the news

That mutual moment arrives as the fifth email — "You have a private account update" — and here is the discipline we're proudest of: those are always the exact same words. The identical subject and body announce a match that needs your answer, a match that completed, and the quiet reminder that a crush of yours is about to lapse. Because the email never varies, receiving one never reveals which kind of news it carries — not to a glance at your lock screen, not to whoever administers your mail server, not to anyone reading over your shoulder. The sorting happens after you sign in, behind your password, where it belongs.

The same rule holds in less romantic corners. If someone tries to register with your email address, the notice you receive is worded identically whether the attempt was yours or a stranger's, so even that message confirms nothing to anyone watching.

What we send people who never signed up

Nothing — with one exception they have to request themselves. Anyone can permanently exclude their address from matching at /privacy/opt-out, no account required. That triggers exactly one confirmation email, and then silence, unless they come asking again. Being the object of someone's affection, by itself, generates no email at all. That is the whole point of the product.

Ask this of any app

You don't need to use AnonymousCrush to use the standard behind it. Ask, of any service that holds something delicate about you: Can I see the complete list of what you might send me? Would every subject line be safe read aloud in my kitchen? Does receiving your message reveal what happened — or only that something did?

Most products can't answer cleanly, because their notification systems were designed to maximize opens, and opens are maximized by leaking a little intrigue. We had to answer, because our entire product is a held secret, and a secret-keeping service with a chatty outbox is a contradiction in terms.

So the outbox is public, in full, at /emails. Read it before you ever trust us with a name. That's what it's for.