Description / Context
Background – When users create custom domain aliases in Proton Pass, they often need to export the list of generated passwords/aliases to another password‑manager or service. Currently there is no built‑in way to bulk‑download these credentials in a portable format that also respects security best practices.

Proposed feature – Add an “Export as locked .txt” option to the alias‑management screen. The exported file would:

Contain the alias names and their associated passwords (or a user‑chosen subset).
Be encrypted/locked with a passphrase supplied by the user at export time, so the file cannot be opened without that passphrase.
Include a small “self‑destruct” flag: after the user confirms a successful import into the target provider (e.g., via a one‑click “Import completed” button), Proton Pass automatically deletes the local copy of the .txt file and clears any temporary buffers, ensuring the plaintext data does not linger on the device.
Why it matters –

Security – Users can move large batches of credentials without exposing them in plain text on disk. The lock‑and‑destroy workflow aligns with Proton’s zero‑access encryption philosophy.
Convenience – Bulk export/import is a common workflow for teams migrating between password managers or onboarding new devices. Providing a secure, automated path reduces manual copy‑paste errors and saves time.
Compliance – Some organizations require that credential exports be encrypted and that temporary files be removed after use. This feature would help Proton Pass meet those policy requirements out‑of‑the‑box.
Expected user flow
Select aliases (or choose “All”) in the Proton Pass UI.
Click “Export as locked .txt”.
Prompt appears:
Enter a passphrase for the file (optionally confirm).
Choose whether the file should be stored locally or sent directly to a cloud storage location.
Proton Pass creates an AES‑256‑encrypted .txt file containing the selected alias‑password pairs.
User imports the file into the target password manager/provider.
After the user clicks “Import completed” (or after a configurable timeout), Proton Pass securely wipes the .txt file from the device and clears any cached copies.
Technical considerations (optional)
Encryption – Use the same client‑side encryption library that protects the vault (AES‑256‑GCM).
Self‑destruct – Implement a secure delete routine (e.g., overwrite the file with random data before unlinking) to mitigate forensic recovery.
UI – Add the export button next to the existing “Export vault” option, with a tooltip explaining the lock‑and‑destroy behavior.
Permissions – Require the user’s master password or a secondary confirmation before generating the file, to prevent accidental exposure.
Suggested next steps
Submit the request through the official Proton Pass feedback channel: https://proton.me/support/pass
Attach this description (or a shortened version) to give the product team clear context and a concrete user story.
Optionally, vote for the request if you see it listed on Proton’s public roadmap or community forum, to increase visibility.