Brave Moved Privacy Past the Edge of the Browser

Blocking a tracker on a webpage does not help when two companies compare the same email address on their own servers. Your inbox address is a durable identity key, and the modern advertising system loves durable keys.

Brave desktop version 1.94 now creates forwarding aliases directly from website signup fields. Each site can receive a different address while messages still reach the user's primary inbox. An alias that starts attracting spam can be disabled without abandoning the real account behind it. The first release includes five free aliases, with mobile and a paid tier planned.

The identity layer is equally interesting. Brave Accounts uses the standardized OPAQUE protocol, which lets the server verify a login without receiving the password itself. Brave says the password is not transmitted in plaintext, encrypted form, or as a conventional hash. That is a meaningful reduction in the credential material a server can lose.

Privacy is not magic. Brave stores the primary address and generated aliases, processes forwarded messages for spam and malware, and uses cloud infrastructure to deliver mail. Its policy says delivered messages are deleted within seconds and diagnostic data are limited, but users are still depending on the company and its vendors to implement those promises correctly. Early forwarding reputation may also send some mail to spam.

The broader move is the point. Browsers spent years partitioning cookies and local storage while identity matching moved behind the server. An alias built into the form attacks the leak where it happens. Privacy products get stronger when the safer choice becomes the default action, not a weekend project for people who already understand the threat model.

LaunchPad positionAlias creation can break server-side identity matching across websites, but users still trust Brave to forward mail, store routing metadata, and operate the service reliably.