Many people currently have your home address because you sent them a single email. I couldn't answer that with any confidence, and that gap is exactly why I stopped using my old address for consultancy work at all. Every pitch I sent from a free inbox was doubling as a breadcrumb, doing more to help data brokers connect the dots than it ever did to make me look professional. Moving my digital marketing practice onto a custom domain in Proton Mail solved the professionalism problem in an afternoon. What it didn't solve on its own was the privacy one, and figuring out where the two split apart turned into its own project.
Two setups get pitched as "the" answer for consultants who want to look legitimate without leaking a home address to every people-search site with a subscription model. One is what I'll call the single custom address: pick name@yourbusiness.com, use it everywhere, and let the domain do the professionalism work. The other is the catch-all approach — same domain, but a fresh, disposable alias for every vendor, tool, and client intake form. Proton Mail happens to support both without much friction, which makes it a decent lab for comparing them instead of just picking one on faith.
Custom Domain Ownership vs the Free Email Default
Getting either setup running starts the same way: pointing your DNS settings at Proton instead of a free provider's default. You're editing MX records, SPF, DKIM, and DMARC entries inside your registrar's dashboard, which sounds like alphabet soup until you think of it as building a certified mail system instead of relying on postcards anyone can read. Skip a step and messages either bounce or land in spam, because the receiving server doesn't recognize your setup as legitimate. None of it is the one-click affair some marketing pages imply (no one has ever called DNS propagation exciting, and I won't be the first) — expect to spend real time copying strings of text between Proton's settings and your registrar's, then waiting for the checkmark to turn green.
Once it's live, the domain itself does something a free inbox never could: it signals, at a glance, that a client is dealing with an established business rather than someone working out of a decade-old Gmail account. That's the case for the single-address setup — consistency reads as credibility. Every broker site catalogs a slightly different slice of a person, one holds the address, another the relatives, another the phone number, so a domain-based address doesn't make you more exposed than a name search already would; it just makes the connection tidier for whoever's looking.
Single Address or Catch-All: Which Actually Protects a Consultant?
Here's the trade-off nobody puts in the setup guide: a single, consistent address at your own domain is also a permanent, searchable link between your identity and every place you've ever used it. Sign every pitch, every tool signup, every newsletter with the same address, and you've built a tag that's easier to trace than a generic one ever was. I turned this over during a swim at Barton Springs Pool, trying to work out whether the professionalism win was worth the traceability cost. A friend of mine who spends his weekends refurbishing vintage motorcycles in his garage doesn't have this problem — nobody's searching his name before hiring him to repaint a tank. Client-facing work changes the math.
This is where the best services to remove personal info from Spokeo and Whitepages come in, and where I'll admit one attempt at outsourcing the problem didn't pan out. I paid for a single month of DeleteMe once, watched it churn through a handful of sites, then canceled the moment the renewal price jumped; the coverage wasn't bad, it just wasn't worth what they wanted for a second month. No subscription covers every broker anyway, which is the gap the marketing pages tend to leave out. Whitepages, for what it's worth, had my consultancy's address relisted before I'd even finished feeling good about the first removal.
The Catch-All System in Practice
The catch-all half of the comparison works differently. Turn it on for the domain and you can invent addresses on the fly — marketingtool@, webinarsignup@, vendorname@ — without pre-creating a single one in settings. Nothing about it is complicated once it's switched on; the complexity was all in the DNS step already covered. What it buys you is a tripwire: if an alias built for one tool starts getting mail from unrelated senders, you know exactly who sold the list, the same way a paper flyer from a lawn service you never called tells you someone sold your street address.
Hand-managing that many aliases the old-fashioned way costs real hours; paying a service to automate the equivalent cleanup costs money instead, and neither option is free in the way people want it to be. The payoff showed up somewhere I wasn't watching for it: a stack of forwarded mail from my old rental stopped including catalog flyers addressed to a name I don't use anymore, and I hadn't done anything specific to cause that — the aliases had just quietly stopped feeding the list. Every so often a removal confirmation still lands well after I've forgotten submitting the request in the first place, the kind of notification that shows up on your phone at an hour you'd rather not be awake for. None of this touches old hardware, by the way — a clean inbox doesn't help if a retired laptop is still holding client files, which is the whole reason I finally sat down and worked out how to erase client files from old external drives permanently instead of leaving the drive in a desk drawer.
Where a Single Custom Address Wins
None of this means catch-all wins by default. A recurring client who's going to email you every month for the next few years doesn't need a disposable-feeling alias — a consistent, professional address is part of what they're paying for, and swapping addresses on an established relationship just creates friction nobody asked for. The distinction that matters is between people you're building a relationship with and tools you're only testing once. Each alias still needs its own generated password rather than a reused one, since a shared password across aliases defeats the entire point of separating them in the first place — that's a job for whatever password manager you're already running, not something Proton's domain features handle on their own (my partner still maintains the Yubikey clipped to my keyring is overkill; jury's out). Worth keeping straight, too: the VPN bundled alongside Proton Mail protects the connection you're sending from, not the inbox or the aliases inside it — different layer, different job. And when any one login turns up in a breach notice, having it tied to its own alias makes it obvious which single password needs rotating instead of guessing across a dozen shared logins.
Choosing the Setup That Fits Your Client List
Put plainly: use a single, consistent address at your custom domain for anyone you expect to have a real, ongoing relationship with — clients, collaborators, referral partners, the people who need to find you again easily. Switch to a catch-all alias for anything transactional — a new tool's free trial, a webinar registration, a vendor you're evaluating once. Kill the alias the moment it starts pulling in mail that has nothing to do with why you created it; that takes seconds and costs nothing, unlike untangling a compromised address you've used everywhere for years. Owning the domain was never really about looking bigger than a one-person consultancy. It's about deciding, alias by alias, exactly who gets to keep finding you.