The author of your identity

Never give a website your email again.

Your email does two jobs: it proves who you are, and it lets services reach you. Lauther does both — anonymous sign-in plus a push inbox you control — so the signup form finally has nothing left to ask for.

INBOX 2 NEW ACME SHOP Order shipped Your package is on the way VAULT Approve sign-in? as @shadowfox · expires 2:00 HOME SERVER Backup finished Nightly job · 4m12s CAFÉ NOVA Free coffee unlocked ☕ Loyalty stamp 10 of 10 INBOX APPS YOU
Why email is the problem

The two jobs of an email address

Every signup form wants your email because it does two jobs at once: it identifies you, and it reaches you. That's also why it leaks — one address ties every account you own together, forever, and puts a spam channel in every database that ever gets breached. Lauther splits the two jobs and hands them back to you.

YOUR EMAIL you@real.name JOB 1 · IDENTIFY …and correlate you everywhere JOB 2 · REACH …and spam you forever PAIRWISE IDENTITY a different generated you, per service PUSH INBOX YOU OWN reachable, prioritised, revocable in one tap
Split the jobs · nothing to leak, nothing to correlate, nothing to spam
Where Lauther sits

Honest comparisons

vs. Passkeys

Passkeys fix passwords brilliantly — and we'd tell you to use them. But after a passkey signup, the site still asks for your email, because passkeys prove who you are and can't reach you. Lauther replaces both jobs. Passkeys are half the answer; this is the other half.

vs. Pushover & ntfy

Excellent notification pipes — Lauther even speaks Pushover's API so their whole ecosystem works here. But a pipe has no idea who you are: no sign-in, no approvals, no consented data. Notifications are our wedge; identity is the point.

vs. Sign in with Apple

Hide My Email is our closest cousin — per-app relay identities, philosophically kin. But it's Apple-only, email-shaped underneath, and gives the service no direct channel. Lauther is cross-platform and drops email entirely.

vs. Duo, Okta & authenticators

Approve-on-phone with a QR enrollment — sound familiar? Enterprises have trusted this exact interaction for a decade. They rent it to your employer; Lauther gives it to every website, anonymously, with you as the only tenant.

For you

Your phone becomes the key to everything

No passwords to remember, no email address handed to every site that asks. You approve things; Lauther does the rest.

AS A USER

You stay in control

  • One inbox for every service — orders, alerts, chats, offers — with priorities and quiet hours you set.
  • Sign in with a tap. A QR or a button, an approve on your phone, done. Biometric-protected.
  • Be @nova here, @shadowfox there. Every service knows a different you, and they can't compare notes.
  • Revoke anything, instantly. One tap and a service can never reach you again.
  • Share more only if you want. Anonymity is the default, not a cage — hand a service your real details the day it earns them.
AS A SERVICE

Reach users without owning their data

  • No password database. Nothing to hash, leak, or reset. Sign-in is two HTTP endpoints and a QR.
  • A push channel without email. Notify users of events directly — no spam folder, no unsubscribe rot.
  • Radically less PII liability. You store an opaque ID and an alias. A breach leaks nothing personal.
  • Built-in step-up auth. Big action? Fire a verification — the user confirms on their phone with fingerprint or face.
  • Ask for more when you need it. Need a shipping address or an email? Request it — the user decides. Trust becomes a feature, not a form.
acme.example K7Q2-9F3D Acme wants to identify you APPEAR AS @nova-7 Approve Deny acme.example Signed in as @nova-7 id: bcn_8f3k… · no email · no password Welcome back. We know exactly one thing about you — and that's the point.
Sign in with Lauther · scan or tap, approve, done
Anonymity is an option — yours

Anonymous by default. Generous by choice.

Every service gets its own generated ID and alias — two sites can never work out you're the same person. But anonymity isn't a cage: when a shop needs a delivery address or a community wants your real name, they can ask — and you decide what to hand over, service by service. Lauther authorizes; you author.

You CAFÉ NOVA · LOYALTY knows you as @latte_ghost bcn_2xw9… · + nothing else ACME SHOP knows you as @nova-7 bcn_8f3k… · + address you chose to share CAN'T CORRELATE
Pairwise identity · different you, everywhere, on purpose
Use cases

Where a private channel changes everything

Service events

Order shipped, invoice due, ticket answered, server down — any web service notifies you the moment it happens. No email address given, no inbox spammed.

Chats & messages

Marketplaces, forums, dating, support — talk to strangers as @your-alias with real-time pings, and never hand out a phone number again.

Loyalty cards

Your pairwise ID is the card number. Collect stamps and get offers pushed — without surrendering your name, birthday and shopping history to a marketing database.

Passwordless 2FA

High-value action on a site? It fires a challenge; your phone shows who's asking and you confirm with a fingerprint. Stronger than SMS, kinder than codes.

Home lab & IoT

Backups, sensors, 3D prints, CI pipelines — anything that can hit a URL can reach your pocket. Pushover-compatible, webhook-lenient.

Queues & bookings

Barber, clinic, restaurant waitlist, parcel locker: "you're up in 10 minutes" — no app of theirs installed, no account created, no number left behind.

Price & stock watch

Back-in-stock, price-drop, auction outbid, ticket-release alerts — services compete for your attention with signal, not newsletters.

Whistle-safe reporting

Report an issue to a company, municipality or school — provably reachable for follow-up questions, yet impossible to identify. The alias does the talking.

Thirty seconds to first push

Made for people who script things

# In the app: Apps → + → New token
curl -X POST https://europe-west1-beacon-app-491068.cloudfunctions.net/api/v1/push \
  -H "Content-Type: application/json" \
  -d '{
    "token":    "bpt_YOURTOKEN",
    "title":    "Backup finished",
    "message":  "Nightly job completed in 4m12s",
    "priority": 1
  }'
Get Lauther

On your phone

COMING SOON
Google Play
COMING SOON · TESTFLIGHT FIRST
App Store
TEST BUILD · AVAILABLE NOW
Direct APK

Installing the APK: open the download, allow “install unknown apps” for your browser if prompted, install, done.

Integrate

Their email was never yours to keep

Add Sign in with Lauther with two endpoints and a QR code — no SDK. You get login, re-verification and a direct push channel to every user — the two things you wanted their email for — while storing zero PII. No password database, no breach headlines, no spam-folder fights.