In that case, something like SimpleLogin would secure you from this specific treat model. The whole point of that is to have a unique email for each service.

If you're worried about your mail provider getting a data breach, then you're stuck to a free account with bullshit info and trow something like SimpleLogin over that. Most paid accounts require some sort of verifiable info.

There are no doubt more services that do the same aliasing kinda stuff, SimpleLogin simply comes to mind as an example of what kind of service you need. In fact, I dunno if it's free or payable witbout tracking (ie likely crypto).

A bunch of fake bullshit emails on free accounts are also an option ofc. As in, one fake account per service you use. I guess that would be the hardest to trace, unless a hacker is getting into the providers servers and check logs for login time, IP, cookies, general browser fingerprinting etc. But then, so the could on you visiting anything online including Lemmy instances.

A catch all on a domain could also, since people don't need to know it's a catch all and everything leads to your mailbox. But it would require a domain likely linkable to you.

Question is really, how far do you wanna go? Assuming everything cán be breached and shouldn't be trusted without looking at the likeliness of the databreach(es) needed (as in some cases multiple servi es need to be breached to specific levels): does it seem likely you're new boss (or whatever) will actually take this effort to look for and link al that data and how much effort is it worth. To go with your use-case, I doubt the average bus driver would be screened that harsly.

Not to forget most hacks still happen by social engineering. You could have the most secure set-up ever, then screw it up by saying sometging stupid once to the wrong person.

In the end, the savest bet against this is to stay of the internet. There is always something, be it difficult.