The alias feature is genuinely useful. Being able to generate an alias directly inside Pass and instantly tie it to a login is one of the strongest privacy workflows in any password manager. Full credit for that.

The problem: ALIASES DON'T BELONG IN VAULTS

Currently, each alias is stored as a standalone vault item. When you then create a login using that alias, a second item appears — same service, two entries. This creates two structural problems:

1. CLUTTER: Vaults become noisy fast. Users with many aliases effectively have a doubled item count, making search, review, and sharing more cumbersome. The workaround — using a dedicated "Aliases" vault — partially helps, but it's not aligned with the Pass wallet purpose.

2. ARCHITECTURAL MISMATCH: Vaults are Proton Pass's E2EE layer. Aliases are not E2EE — they originate from SimpleLogin, which operates outside the E2EE perimeter. Storing aliases as vault items implies a level of encryption parity that doesn't actually exist. It's a category error. It defeats the architectural purpose.

PROPOSED SOLUTION:

1. Alias → Login merge on conversion. When an alias is used to create a Login item, the alias should be absorbed into that Login item (as the email field) and the standalone alias item should disappear. No duplicate. One item, complete.

2. Remove aliases from Vaults entirely. Vaults should contain E2EE items only: logins, notes, cards, identities. Aliases are a different class of data and shouldn't live there.

3.Exclude aliases from All Items / All Vaults search. Alias items currently pollute the global search and item list. They should not appear there.

1. Create a dedicated Aliases directory. Orphaned aliases — those not yet tied to a Login item — should live in a separate, clearly labelled section (e.g., alongside the existing Trash or as a top-level sidebar item). This keeps them accessible and manageable without contaminating vault structure.

This aligns Pass with its own security model, reduces friction for power users, and makes the alias feature feel like a first-class privacy tool rather than an afterthought bolted onto a password manager.