Think Amazon, Apple, etc.
I use different emails via SimpleLogin for many services just to make it easier to spot when an email is caught in a breach and to spot just which service is the one that got breached (think of big paste breaches). Another example is if I have my real email address breached, some malicious person could see if I have an account with a service by entering my email and seeing if anything comes up (your password was incorrect, profile picture I have on the account, a password reset email has been sent to redac***@censor.com. I’ve seen this a lot with my Microsoft account, which I disabled my email for, and instead use my Gmail address for, but I digress.
I use my Amazon account a lot, but was holding off on using an alias on it. Obviously if I stop paying for a relay service I won’t have access to the email relay service and possible forwarding, but this shouldn’t be a problem. I was curious about how people here utilize aliases and the way you personal have your system/workflow setup.
Thanks!
Good thinking!
I highly recommend getting your own domain name! Then you can setup google workspaces, or fastmail, or proton mail, or tutanota with the domain name and have all email to that domain go to your one inbox.
Fast mail has a nice feature where if you reply to a email X@domain.example the from address for your message will be X@domain.example automatically!
This allows you to have infinite address for services, and you can block an address that gets spammed or breached. If you want to be extra spicy setup a second level domain to avoid any automatic bot spam to the top level domain. i.e. AmazonLogin@service.domain.example.
My workflow is ServiceName@type.domain.example, then I can sort all email by ServiceName on the To line. Really helps reduce spam. So far I’ve only had a data breach with Xfinity, so I’m on Xfinity3@type.domain.example with xfinity and xfinity1 both blocked.