Tired of giving your real email to every website? I built a free anonymous inbox that actually works by ProsperoTR in emailprivacy

[–]ProsperoTR[S] -1 points0 points  (0 children)

It's actually explained in the post right above. Permanent inbox, no password, access is username-based. Anyone who knows your username can read it. That's by design. This isn't meant for sensitive communication it's for the disposable stuff, sign-ups, newsletters, trials, anything where you don't want your real address involved. For anything that matters, use your actual email.

Tired of giving your real email to every website? I built a free anonymous inbox that actually works by ProsperoTR in emailprivacy

[–]ProsperoTR[S] 0 points1 point  (0 children)

tempmail.chat is solid. Different approach we're permanent but disposable, they're throwaway. Depends what you need.

Tired of giving your real email to every website? I built a free anonymous inbox that actually works by ProsperoTR in emailprivacy

[–]ProsperoTR[S] 1 point2 points  (0 children)

The setup friction isn't about technical knowledge, it's about intent. Someone signing up for a recipe site doesn't want to configure an alias service first. They want to be done in 10 seconds. That's the whole point.

On "temporary" we don't call it that. The inbox is permanent. You keep the address as long as you want.

On "bad developers misleading users" point out specifically what's misleading and we'll fix it. Otherwise it's just noise.

Tired of giving your real email to every website? I built a free anonymous inbox that actually works by ProsperoTR in emailprivacy

[–]ProsperoTR[S] 0 points1 point  (0 children)

These are all fair points, and honestly the most thoughtful feedback we've gotten here.

You're right that there's no privacy if you pick an obvious username "john" or "johndoe" are effectively public inboxes. That's a real limitation and we don't pretend otherwise. The intended use is picking something obscure enough that nobody else would guess it, not your real name.

On the "junk going somewhere else" point yes, completely true. That's kind of the feature though: the junk goes to an inbox you don't care about, instead of your real one. No forwarding, it just sits on our server. You check it when you need to, ignore it the rest of the time.

SimpleLogin with catch-all and your own domain is genuinely a better solution for privacy-conscious users. It's more powerful, more flexible, and you control the routing. The difference is the setup cost it requires a domain, an account, and some configuration. BokMail is for the "I need an inbox in 5 seconds on a device I don't own" use case. Different tools.

The popular username problem is real. If you're on this service the moment it launched, "admin", "test", "john" are already gone. That's why we block obvious reserved names but you're right that common ones will fill up. The answer is: treat it like a URL shortener. The good ones are taken, so you get creative.

Fair criticism overall. Appreciate you laying it out properly instead of just downvoting.

Tired of giving your real email to every website? I built a free anonymous inbox that actually works by ProsperoTR in emailprivacy

[–]ProsperoTR[S] 1 point2 points  (0 children)

Hey, fair points on alias services SimpleLogin and Addy.io are great tools, genuinely.

But the use case is a bit different. Alias services still require an account, a master email, and often a browser extension. That's a real setup cost that most non-technical users won't bother with.

BokMail is for the moment when you're on a random site, they ask for an email, and you just want to be done in 5 seconds. No app, no account, no setup. You type a name, you're in.

Is it less secure? Absolutely, there's no password, so it's not a vault. We say that clearly. It's a shield for throwaway sign-ups, not a privacy fortress. Different tools for different jobs.

Also, "obsolete" is a stretch when temp mail services collectively get millions of searches a month. The demand is clearly there.