No. An alias hides which inbox receives the mail — it does not hide who you are. You typed your real name into the same form, and usually your delivery address and card details too. Worth knowing as well: a custom domain used by one person is in some respects less anonymous than a shared masking domain, because it's a consistent identifier across every service you use it on. Aliases are a spam-control and attribution tool, not a disguise.
What an alias actually conceals
One specific thing: the address that mail is ultimately delivered to. The company you signed up with learns shop@yourdomain.com and never learns you@gmail.com.
That's genuinely useful. It means a breach at that company doesn't expose the address your bank uses, and it means their list can't be cross-matched against other datasets using your primary address as the key. Why email is the join key
But concealing the destination inbox is not the same as concealing you.
What it doesn't conceal
- Your name, which you typed into the form.
- Your delivery address, for anything physical.
- Your payment details, and the identity attached to them.
- Your IP address when you visited.
- Everything you write in any correspondence.
- Your display name, if you reply and your client attaches it.
For most signups the company knows exactly who you are. The alias controls the communication channel, not the relationship.
The custom-domain paradox
An address at @duck.com is one of millions. It says nothing about you and can't be linked to your other accounts, because the domain is shared with everybody else using the service.
An address at @yourdomain.com is used by exactly one person: you. Anyone correlating datasets can link every account on that domain together, and the domain itself is registered to someone — which is why WHOIS privacy matters. It's a stable, unique identifier, which is precisely what makes attribution work for you and correlation work for others.
These are the same property viewed from two sides. The full trade-off · WHOIS privacy
Which should you pick, then?
Depends what you're defending against:
| Concern | Better choice |
|---|---|
| Marketing lists and data trading | Either. Both break the join key. |
| Knowing which company leaked you | Either, with one address per company |
| Keeping addresses if you change provider | Your own domain |
| Not being correlated across services | A shared provider domain |
| Genuine anonymity from a determined party | Neither. This is the wrong tool entirely. |
If you actually need anonymity
That's a different discipline with different tools, different threat modelling, and much less room for error. It involves not giving your real name, not paying with a traceable method, and managing network-level identifiers — none of which an email alias touches.
Treating an alias as anonymity is the dangerous mistake, because it feels like protection while leaving your actual identity exactly where it was. Being clear about the boundary is what makes the tool useful within it.