Basically create an alias for every combination to prevent privacy cross contamination.
For instance, not only should you make an email alias for an Eventbrite account, but for every organization you sign up for events with. You are required to enter an email (any email) for the event, which can be seen by both Eventbrite and the organization. If you enter in the email of your Eventbrite account then the org could give that away, resulting in email spam and you can’t be sure if it was either Eventbrite itself or the org that sold you out. If that happens then you would probably want to delete email address but then you have to change it in other places you need to send/receive emails from.
Another example is Discourse forum sites. While Discourse is open source and self-hostable, you may not always be sure if a Discourse site is self-hosted or using paid hosting. A lot online places have both their own website and a separate discourse site. Bitwarden’s forum site doesn’t have a sign-in option using your Bitwarden.com account, and Raindrop.io uses canny.io to track app feedback which has also uses its own login. (I’m actually glad I made an alias for every single Discourse forum site before realizing all of this).
There’s no shoulds and shouldn’ts, it’s all about your personal privacy needs and tradeoffs you’re willing to take
Unless you’re using a password manager that makes creating aliases at least as easy as clicking a button, that’s probably not worth it to most people.
For example, all my email aliases go to an email that’s just for nonsense emails like newsletters anyway, so I’m not too worried about it to begin with. My main email, which I use for important stuff and personal contacts only, doesn’t have anything forwarded to it.
As with a lot of privacy things, my answer is can I be bothered? I’m not sure it would provide enough benefit to make it worth the effort, but if I was using a service that could easily create new aliases with minimal effort then it probably would be.
