Hide My Email is fundamentally broken in two major ways: 1. Services those emails are used with cannot unilaterally send email to them. They must pre-register how they will send email to them, which breaks services with third-party relationships such as online retail with payment processors or shipping companies. Users don't like not receiving shipping notifications, and users don't like not seeing invoices or at wor…
For now I think Hide My Email is for power users! It's on the user side to manage their identities. My current workflow: - Label Hide My Email with the service name I registered with it. Add number or nickname if I have multiple accounts on that service. - Add an email rules to move the email addressed to that Hide My Email addressuu to a separate inbox. - Use the same label in password manager, also save the email t…
> - Label Hide My Email with the service name I registered with it.
I think the ‘normal’ way to do it is way simpler:
- a site asks for an email address
- click “Hide My Email”
- use Apple’s flow to create a new email address
- use Apple’s flow to pick a password
- phone or Mac automatically associates the email address with the site and stores the password in the KeyChain
AFAICT, the only thing that doesn’t do that you describe is “Add an email rules to move the email addressed to that Hide My Email address to a separate inbox”.
I think that’s orthogonal to using Hide My Email, though. If you want that, you likely would do the same for mail from the site’s domain.