**Brave**'s new ‘Email Aliases’ feature tackles a significant privacy gap. While the browser already employs data isolation to prevent identity inference through cookies or cached data, email addresses stored on website servers remained a vulnerability. The introduction of aliases directly addresses this, blocking cross-site identity matching, reducing unwanted spam, and offering a crucial defense against phishing attacks that often follow data breaches. “If a website you signed up for is hacked, your information can be leaked and end up with data brokers or worse,” **Brave** explained in its announcement. “Your email address then circulates far beyond the company you originally trusted with it, and can show up in phishing campaigns for years afterward.” ### How Email Aliases Work To leverage this new privacy tool, users must create a free **Brave Account** and register their primary email address. This enables the forwarding of messages from the alias to the user's actual inbox. It's important to note that this is distinct from a **Brave Premium** account.  *Managing email address aliases Source: Brave* **Brave** emphasizes its commitment to security in its account infrastructure. **Brave Accounts** utilize **OPAQUE**, a password-authenticated key exchange standardized as **RFC 9807**. This protocol authenticates users without transmitting their passwords or hashes to **Brave**'s servers, thereby reducing exposure to password logging, memory-scraping attacks, and bulk cracking of leaked password databases. However, users are still advised to use strong passwords and remain vigilant against phishing. ### Pricing and Privacy Safeguards The alias system is currently free, allowing users to create up to five email aliases. **Brave** plans to introduce a paid Premium version in the future, which will remove this limitation. To ensure user privacy, **Brave** stores both the primary address and generated aliases in an encrypted state. Forwarded messages undergo automated spam and malware filtering but are not otherwise inspected. Crucially, messages are deleted from **Brave**'s servers within seconds of delivery. Any notes attached to the aliases remain local or, if synced via **Brave Sync**, are end-to-end encrypted. **Brave** has cautioned that forwarded messages might initially be routed to spam folders as the service establishes its reputation as an email provider. Users testing the feature should be mindful of this potential initial behavior.