1525 results found

1. Bitdefender SecurePass Import

   Would love to be able to import passwords directly from Bitdefender's SecurePass!

   25 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   5 comments  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Disable hard to distinguish characters from passwords

   Currently one has the option to enable/disable the following in the password generator:
   - special characters
   - large cap letters
   - numbers

   I think it should be possible to also disable the following:
   - hard to distinguish characters such as i, l, 1, L, o, 0, O

   33 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   5 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Option to hide hide-my-email aliases

   Have an option to hide hide-my-email aliases. I use aliases a lot, and everytime I log into Proton Pass, it's clogged with these entries and I always have to filter by login, as I always look for the login entry with the alias, not the alias entry itself.

   8 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Android's keyboard button feature change, pops up a pop-up window instead of open the app

   On android, the button at the keyboard just opens the app, but in some cases it just takes you out of what you were doing, right? For example, logging in a game, it takes you out of the game when you're trying to look for the account through the button, and when you come back you're already out! Examples: Minecraft, requires Microsoft account, obviously, proton Pass shows you your Microsoft accounts through the keyboard, but sometimes doesn't show them all, so through the button at the right you open proton Pass, the problem is that takes you out of the game, closing it, and when you finally find your account and come back, you have to start again.

   This would be different, if the button opens a pop-up, a small windows like the chrome's extension on PC. Using window's already there function, the pop-up windows.

   On android, the button at the keyboard just opens the app, but in some cases it just takes you out of what you were doing, right? For example, logging in a game, it takes you out of the game when you're trying to look for the account through the button, and when you come back you're already out! Examples: Minecraft, requires Microsoft account, obviously, proton Pass shows you your Microsoft accounts through the keyboard, but sometimes doesn't show them all, so through the button at the right you open proton Pass, the problem is that takes you out of the… more

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   30 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Samsung Pass import, please

   I have too many passwords and too many keys for me to manually enter them all into Proton Pass.

   45 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Choose Username or Email for Autofill

   It would be useful if Proton Pass allowed users to choose whether the Username or Email field should be used for autofill on a specific website or app.

   Some services require both a username and email address when creating an account, so both fields may be stored within the Proton Pass entry. However, certain services only allow login using the email address, while Proton Pass currently appears to prioritise the username field when one is present.

   A per-login option such as “Preferred autofill identifier: Username / Email” would allow users to explicitly choose which value Proton Pass should use when filling login forms.

   This would make autofill more reliable without requiring users to remove useful account information from their saved login entry.

   It would be useful if Proton Pass allowed users to choose whether the Username or Email field should be used for autofill on a specific website or app.

   Some services require both a username and email address when creating an account, so both fields may be stored within the Proton Pass entry. However, certain services only allow login using the email address, while Proton Pass currently appears to prioritise the username field when one is present.

   A per-login option such as “Preferred autofill identifier: Username / Email” would allow users to explicitly choose which value Proton Pass should use when… more

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Deterministic PGP Keys for Reverse Aliases

   Goal

   Provide each SimpleLogin reverse alias with its own independent OpenPGP identity, while keeping key management simple and preventing external observers from linking different aliases to the same Proton account.

   Design

   Proton maintains a dedicated secret AliasPGPRoot for the user.

   For every immutable reverse alias, Proton derives deterministic key material from:

   AliasPGPRoot + normalized alias address

   using a cryptographic KDF such as HKDF.

   Example:

   AliasPGPRoot
       |
       +-- HKDF("alias-a@simplelogin.com")
       |       -> OpenPGP key A
       |
       +-- HKDF("alias-b@simplelogin.com")
       |       -> OpenPGP key B
       |
       +-- HKDF("alias-c@simplelogin.com")
               -> OpenPGP key C
   

   Separate derivation contexts should be used for signing and encryption keys.

   The resulting OpenPGP certificates are completely independent. They contain only the reverse alias as their identity and no reference to the user's real Proton address, root secret, or other aliases.

   The public key for each alias is stored in SimpleLogin. The private key does not need to be stored separately: Proton clients can deterministically reconstruct it locally when needed.

   Privacy Properties

   An external observer seeing:

   alias A -> public key A
   alias B -> public key B
   alias C -> public key C
   

   should have no cryptographic way to determine that these keys originate from the same Proton account.

   Compromise of one derived alias private key should also not allow derivation of the root secret or keys belonging to other aliases.

   Architecture

   Encrypted AliasPGPRoot
           |
           v
    Proton client
           |
           +-- Alias address
           |
          HKDF
         /    \
    signing   encryption
     seed *     seed
         \      /
      Independent
      OpenPGP key
           |
      Public certificate
           |
       SimpleLogin
   

   * optional
   Private alias keys can therefore be generated on demand and discarded after use.

   Important Design Requirements

   • Use a strong domain-separated KDF such as HKDF.
   • Derive signing and encryption key material independently (optional).
   • Prefer deterministic ECC-based key generation rather than deterministic RSA generation.
   • Alias OpenPGP certificates must not contain metadata linking them to the Proton account or other aliases.
   • The alias address must be canonicalized consistently before derivation.
   • The derivation format must be versioned, e.g. proton-reverse-pgp/v1, so future algorithms can be introduced safely.

   Risks and Considerations

   Root-secret compromise:
   Compromise of AliasPGPRoot exposes all alias keys. It therefore needs the same level of protection as other high-value Proton secrets.

   Deterministic derivation stability:
   Changing the KDF, canonicalization rules, curve, or OpenPGP key-generation procedure would otherwise produce different keys. The derivation specification therefore needs strict versioning and long-term compatibility.

   Alias reuse:
   If a deleted alias address could ever be reassigned, address-only derivation would reproduce the same key for the same user. Ideally SimpleLogin should guarantee that reverse aliases are never reused, or an immutable alias identifier should additionally be included in the derivation.

   Metadata correlation:
   The scheme prevents cryptographic linking of aliases, but correlation may still be possible through mail headers, timing, account metadata, identical OpenPGP preferences, or server-side information. Generated certificates should therefore minimize unnecessary shared metadata.

   Result

   This design provides:

   • one independent PGP identity per reverse alias,
   • no externally visible cryptographic relationship between aliases,
   • deterministic recovery without storing large numbers of private keys,
   • local/on-demand private-key generation by Proton clients,
   • straightforward integration with SimpleLogin through per-alias public keys.

   Goal

   Provide each SimpleLogin reverse alias with its own independent OpenPGP identity, while keeping key management simple and preventing external observers from linking different aliases to the same Proton account.

   Design

   Proton maintains a dedicated secret AliasPGPRoot for the user.

   For every immutable reverse alias, Proton derives deterministic key material from:

   AliasPGPRoot + normalized alias address

   using a cryptographic KDF such as HKDF.

   Example:

   AliasPGPRoot
       |
       +-- HKDF("alias-a@simplelogin.com")
       |       -> OpenPGP key A
       |
       +-- HKDF("alias-b@simplelogin.com")
       |       -> OpenPGP key B
       |
       +-- HKDF("alias-c@simplelogin.com")
               -> OpenPGP key C
   

   Separate derivation contexts should be used for signing and encryption keys.

   The… more

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Please add an Archive feature to Proton Pass

   Please add an Archive feature to Proton Pass. It would be useful for storing old or rarely used items without deleting them or cluttering the main vault. An Archive section with the option to restore items later would be great.

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Fully Customizable Proton Pass Entries

   Proton Pass stores more than logins — Notes, Credit Cards, Identities, Custom Items, and more. But no matter the item type, every entry comes pre-loaded with default fields you can't remove and an order you can't change.

   The ask, across ALL item types:

   1. Removable defaults — any built-in field can be deleted (or auto-hides when left blank). If an Identity item doesn't need a middle name, or a Custom Item doesn't need a Note, it shouldn't sit there empty forever.
   2. Drag-to-reorder — arrange every field, default and custom alike, in whatever order fits the item.

   The current "workaround" for reordering is deleting fields and re-adding them one by one just to slot a new field into the right spot. That's unpacking the entire suitcase to add a pair of socks.

   Pass already keeps our data safe. This would keep it tidy, too. If you've ever scrolled past blank fields to reach the one you actually needed, this vote is for you.

   Proton Pass stores more than logins — Notes, Credit Cards, Identities, Custom Items, and more. But no matter the item type, every entry comes pre-loaded with default fields you can't remove and an order you can't change.

   The ask, across ALL item types:

   1. Removable defaults — any built-in field can be deleted (or auto-hides when left blank). If an Identity item doesn't need a middle name, or a Custom Item doesn't need a Note, it shouldn't sit there empty forever.
   2. Drag-to-reorder — arrange every field, default and custom alike, in whatever order fits the item.

   The current "workaround" for reordering… more

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Invalidate local encryption keys on new biometric enrollment (Android / iOS)

    Summary:
    When a user adds a new fingerprint/biometric credential to their device, Proton Pass currently allows access using the newly added biometric. To protect vault contents from device PIN compromise and rogue biometric enrollment, we propose adding an option that automatically invalidates local unlock keys when the device's biometric set changes, forcing a Master Password re-authentication.

    1. Background & Threat Model:
       Currently, if an attacker obtains a user's device PIN/passcode and registers their own fingerprint or face in the OS settings, they can seamlessly unlock the Proton Pass app using that newly added biometric. This leaves stored credentials and Passkeys vulnerable to device PIN compromise followed by rogue biometric enrollment.

    2. Technical Analysis & Current Gap:
       Both Android and iOS/iPadOS provide OS-level APIs designed to mitigate this exact threat by invalidating cryptographic keys stored in KeyStore / Secure Enclave when the biometric set changes:

    Android: setInvalidatedByBiometricEnrollment(true) in KeyGenParameterSpec.Builder. When enabled, adding a new fingerprint throws a KeyPermanentlyInvalidatedException upon use.

    iOS / iPadOS: kSecAccessControlBiometricCurrentSet flag in Keychain services. The key becomes invalid if evaluatedPolicyDomainState changes.

    Our testing confirmed that Proton Pass currently allows access even after a new fingerprint is enrolled. This indicates that the app either explicitly sets setInvalidatedByBiometricEnrollment(false) (or equivalent) or relies on biometric prompt evaluation without binding decryption directly to an invalidated key.

    1. Proposed Solution: We request implementing an option to bind local app authentication directly to the current biometric set:

    Enforce Key Invalidation: When a new biometric is enrolled, the local key used for app unlock/decryption should be automatically invalidated by the OS.

    Fallback to Master Password: When key invalidation is detected (KeyPermanentlyInvalidatedException or domain state change), force the user to re-authenticate with their Master Password to re-generate the local biometric unlock key.

    Optional User Toggle (User Control): To balance security and convenience, provide a toggle setting in the app:

    Option: "Require Master Password if biometrics change" (Default: ON or Optional for high-security users).

    1. Secondary Benefits (Security Awareness & Incident Response): Requiring a Master Password upon key invalidation also provides a critical early-warning mechanism for users:

    Detection of Rogue Biometrics: If a user is suddenly prompted for their Master Password despite not adding a fingerprint themselves, they are immediately alerted to potential unauthorized access to their device settings.

    Prompting Incident Response: This notification allows users to audit their registered biometrics, remove unauthorized fingerprints, and recognize that their device PIN/passcode has likely been compromised—prompting them to change their PIN immediately.

    Summary:
    When a user adds a new fingerprint/biometric credential to their device, Proton Pass currently allows access using the newly added biometric. To protect vault contents from device PIN compromise and rogue biometric enrollment, we propose adding an option that automatically invalidates local unlock keys when the device's biometric set changes, forcing a Master Password re-authentication.

    1. Background & Threat Model:
       Currently, if an attacker obtains a user's device PIN/passcode and registers their own fingerprint or face in the OS settings, they can seamlessly unlock the Proton Pass app using that newly added biometric. This leaves stored credentials and Passkeys vulnerable… more

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Securely get a password from a friend (reverse share feature)

    Feature that allows people to securely share secrets with a Proton pass user.

    Right now, if I (as a Proton Pass user) want to send a secret to a friend, I can use the share feature. But if my friend (who isn't a Proton Pass user) wants to send a secret to me, there’s no simple way to do it.

    A nice feature would be the ability to generate a secure link that I could send to them, where they can paste their secret. That secret would then appear directly in my vault.

    76 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Add Camera feature to scan QR for Passkey logins Inside Protonpass (Mobile & Desktop)

    Lately sites like Google and Amazon have been forcing me to scan a QR code to log in using passkey, which i found the following issues:

    1. On desktop, protonpass extention used to pop up to select the passkey, but lately when the site forces you to scan the QR code to use another device (such as a smartphone)

    2. On my Android smartphone, when I scan the QR code, it says I don't have a passkey, this is because it's looking in my Google & Samsung Pass, even though I've selected Protonpass for Autofill & Passkeys. The only solution for me is to go to Settings > (Passwords, passkeys, and autofill) then select None then Protonpass (after I unlock it)

    The suggested solution:
    Add a Camera scan button inside the App (on both Mobile & Desktop) so the user is able to Scan the QR Code just by opening the app, and then selecting the passkey.

    Lately sites like Google and Amazon have been forcing me to scan a QR code to log in using passkey, which i found the following issues:

    1. On desktop, protonpass extention used to pop up to select the passkey, but lately when the site forces you to scan the QR code to use another device (such as a smartphone)

    2. On my Android smartphone, when I scan the QR code, it says I don't have a passkey, this is because it's looking in my Google & Samsung Pass, even though I've selected Protonpass for Autofill & Passkeys. The only solution for me… more

    26 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Proton Pass browser extension keyboard shortcuts

    The browser extension of Proton Pass currently only allows to auto-fill passwords with the iframe popup that appears over the login input fields. While this works fine, this popup is distracting and time-consuming to manually click it with the mouse.
    Thus, I suggest to add keyboard shortcuts that can be customized in the browser settings. For me personally, autofill of the last used login-credentials for the current page would be the most important feature to get a shortcut, but password/alias generation or manual lock etc would also be nice to have as shortcuts, too.

    35 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Add spell-checking settings: disable spell checker and select languages

    Description

    Please add spell-checking settings to Proton Pass, especially to the desktop application.

    Currently, Proton Pass performs spell checking automatically, but there does not appear to be any user-accessible setting to control it. On Linux, this can result in valid words being underlined in red when Proton Pass uses a different language from the language being typed.

    For example, using Proton Pass Desktop on EndeavourOS (Arch Linux) and regularly work in both Estonian and English. English text is currently shown with red spell-check underlines, and I cannot find any way in Proton Pass to either select the correct language or disable spell checking.

    Requested settings

    Please add the following options under Proton Pass settings:

    • Enable spell checking — on/off
    • Spell-check languages — allow one or more languages to be selected simultaneously
    • Ideally, allow automatic language detection as an additional option

    For example:

    • Estonian (et)
    • English (United Kingdom) (en-GB)
    • English (United States) (en-US)

    It is important to support multiple languages simultaneously because many users regularly enter notes, item names and other text in more than one language.

    Expected behaviour

    If spell checking is enabled, Proton Pass should use the languages selected by the user.

    If spell checking is disabled, no spell-check underlines should be shown.

    The selected setting should persist between application restarts.

    Technical note

    Proton Pass Desktop is Electron-based, and Electron already provides APIs for controlling spell checking and selecting spell-check languages, including:

    session.setSpellCheckerEnabled(false)
    session.setSpellCheckerLanguages(['et', 'en-GB', 'en-US'])
    

    Therefore, the underlying Electron functionality already exists; Proton Pass mainly needs to expose it as a user preference.

    This would be particularly useful on Linux, where relying only on the operating system locale is insufficient for multilingual users.

    Description

    Please add spell-checking settings to Proton Pass, especially to the desktop application.

    Currently, Proton Pass performs spell checking automatically, but there does not appear to be any user-accessible setting to control it. On Linux, this can result in valid words being underlined in red when Proton Pass uses a different language from the language being typed.

    For example, using Proton Pass Desktop on EndeavourOS (Arch Linux) and regularly work in both Estonian and English. English text is currently shown with red spell-check underlines, and I cannot find any way in Proton Pass to either select the correct language or… more

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Re: Import passwords into Proton Pass---Could you please include Norton Password as an option?

    Re: Import passwords into Proton Pass---Could you please include Norton Password as an option?

    54 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Save custom item types as templates

    Now that it is possible to create 'Other' items – even completely from scratch – it would be nice if I could save these custom items as templates.

    This would allow me to re-use my custom item types, instead of having to re-create them every single time.

    67 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    10 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Proton Pass browser extension should retain settings

    Extension settings should be stored server side, and when signed-in again, they should be automatically applied.

    7 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Unlock the Proton Pass extension with Windows Hello; a PIN code isn't secure enough.

    Unlock the Proton Pass extension with Windows Hello or 2FA ; a PIN code isn't secure enough.

    20 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Folders instead of vaults

    The existing "Vaults" Feature is not good in my opinion. Its little bit confusing, so if this feature should be handled as a folder, why not name it "Folder", and pls let us create unlimited folders, not only 50. I think about to switch to Proton but this holding me back, i have NordPass where i can create unlimited Folders for better organisation... considder this update pls.

    47 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Unlock Proton Pass with Yubikey (or other U2F or FIDO2 standards)

    It seems like Yubikey or ohter 2FA key (standard U2F or FIDO2) are available for Proton Mail, Drive and Calendar.

    But please, implement it for Proton Pass.
    Password only for Windows app is not confortable and PIN is not enough secured.

    Regards,

    11 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating