1435 results found

1. Modern Digital Assets Recovery Firm Don't worry about losing your Digital assets; ZEUS RECOVERY SERVICES provide digital assets recovery a

   Modern Digital Assets Recovery Firm

   Don't worry about losing your Digital assets; ZEUS RECOVERY SERVICES provide digital assets recovery assistance for people facing digital-related losses or access issues. The company focuses on professional support and guidance.

   Learn More On Their Website: https://zeusrecoveryservices.com

   2 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

2. 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

   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

   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

3. 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

   2 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. My former password manager was McAfee TrueKey.
   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

   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

5. Keyboard Navigation for item management

   Intuitively, I am missing an ability to navigate around the items with my keyboard.

   Be it the arrow keys, vi's "HJKL" or the forsaken "WASD" for these pesky gamers (guilty). Holding the Shift key, whilst navigating between these items, could intuitively multi-select them and an Escape key could cancel the multi-selection. And I'd assume the Delete/Backspace button could do just that - delete an item(s) selected.

   Without going crazy and implementing pretty much anything anyone would ever ask for (don't default to WASD or HJKL), I do believe there are some fundamentals that could be implemented into - well, not only Proton Pass, but frankly any of these desktop/web apps.

   Intuitively, I am missing an ability to navigate around the items with my keyboard.

   Be it the arrow keys, vi's "HJKL" or the forsaken "WASD" for these pesky gamers (guilty). Holding the Shift key, whilst navigating between these items, could intuitively multi-select them and an Escape key could cancel the multi-selection. And I'd assume the Delete/Backspace button could do just that - delete an item(s) selected.

   Without going crazy and implementing pretty much anything anyone would ever ask for (don't default to WASD or HJKL), I do believe there are some fundamentals that could be implemented into - well, not… more

   2 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

6. .JSON

   L'option de pouvoir exporter en .json devrait être plus claire. Il faut dézipper le fichier de sortie pour le savoir. C'est un autre programme qui offrait l'option d'importer de Proton Pass en .json qui m'a informé que cela était possible.
   Juste une petite note... Merci

   2 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. When I use a 6 digits code that locks my screen after x mins,

   When I use a 6 digits code to unlock my screen after x mins, I would like to improve the loginscreen. Today you need to click on the first textbox to enter the code (it is usually already selected but sometimes not) I want the first empty textbox to ALWAYS have the focus, regardless of where I click or where the moon is. There should not be any reason to not have the focus on the textboxes :-)

   2 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

8. 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

   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

   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. ME GUSTARIA UNA APP DE LINUX EN PAQUETE FLATPAK PORQUE USO ARCH, Y TIENEN APP EN .deb Y .rpm

   ME GUSTARIA UNA APP DE LINUX EN PAQUETE FLATPAK PORQUE USO ARCH, Y TIENEN APP EN .deb Y .rpm

   2 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

10. Can't get it to sync no matter what I try. Someone suggested it's because I'm using a VPN?

    I'm really not sure what I'm doing wrong but I've been trying to find a replacement for Authy every since they abandoned desktop support, and I'm not a fan of Microsoft. I tried Proton Authenticator but the five or so sites I have tried thus far have completely failed to sync and I'm currently locked out of my own website and can't use it to log into ProtonMail either (I have YubiKeys, luckily). Really not sure what's going on there, but someone suggested it's because I'm using a VPN? Surely that can't be right; it's not been a problem before. I'm very happy with NordPass and NordVPN and won't be changing those, but equally I thought it unwise to put everything in one boat. That said, I only just found out Nord have an integrated 2FA authenticator themselves, just for some bizarre reason they never advertise it. I've been with them for 2 years. Any advice on why Proton specifically is not syncing would be welcome. It's getting a bit annoying trying different authenticators all the time.

    I'm really not sure what I'm doing wrong but I've been trying to find a replacement for Authy every since they abandoned desktop support, and I'm not a fan of Microsoft. I tried Proton Authenticator but the five or so sites I have tried thus far have completely failed to sync and I'm currently locked out of my own website and can't use it to log into ProtonMail either (I have YubiKeys, luckily). Really not sure what's going on there, but someone suggested it's because I'm using a VPN? Surely that can't be right; it's not been a problem before.… more

    2 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

11. pass-cli: item view prints Hidden-typed values in plaintext; no safe way to discover an item's structure

    pass-cli is aimed at automation and agent workflows, but it currently forces agents to make a choice between guessing blind and over-exposing secrets:

    1. item view (human format) renders secret fields as Hidden("<full plaintext value>"). The type system clearly knows the field is Hidden — it just doesn't redact it. Default output should be Hidden(<redacted, N chars>), with an explicit --reveal (or the existing --field X) opting into the value. That one change makes bare view a safe discovery command: field names, note, and attachment metadata are exactly what a script needs to learn before requesting a specific value. --output json has the same problem and the same fix.

    2. There is no other discovery path. item list returns no field or attachment info, there's no describe-item command, and a wrong --field guess returns only Field does not exist: X — no hint of what fields do exist (field names are metadata, not secrets). An item whose only secret is a file attachment has zero fields, so every --field attempt fails identically with nothing pointing at the attachment. Callers today must pull the full plaintext item and build their own redaction just to learn a field name — the opposite of what a secrets manager should encourage.

    3. item attachment download is the one command that refuses friendly selectors. Everything else accepts --vault-name/--item-title; attachment download demands raw --share-id/--item-id/--attachment-id, which are only discoverable via the unredacted JSON view. It should accept the friendly selectors plus --file-name.

    4. Onboarding: pass-cli agent instructions emits the session token in plaintext inside the markdown it tells users to paste to an agent. Convenient, but it normalizes putting a live credential into a chat transcript — the exact anti-pattern a password manager should design against. The instructions should reference an env var or keychain path, never the token value itself.

    pass-cli is aimed at automation and agent workflows, but it currently forces agents to make a choice between guessing blind and over-exposing secrets:

    1. item view (human format) renders secret fields as Hidden("<full plaintext value>"). The type system clearly knows the field is Hidden — it just doesn't redact it. Default output should be Hidden(<redacted, N chars>), with an explicit --reveal (or the existing --field X) opting into the value. That one change makes bare view a safe discovery command: field names, note, and attachment metadata are exactly what a script needs to learn before requesting a specific value. --output json… more

    2 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

12. Merge/De-duplicate the Suggestion Box!!

    Autofind and remove duplicates - 1818 votes
    Merge passwords and aliases - 1285 votes
    Let us merge entries in ProtonPass... - 726 votes
    Remove Duplicate entries - 262 votes

    = 4,091 Votes

    2 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

13. Improve Visibility and Organization of Shared Items and Vaults in Proton Pass

    1. Display Vault Icons in Browser Extension and Web Version

    Problem:
    In the mobile app, a Vault icon is displayed next to each item’s name (password, note, etc.), making it easy to see which Vault it belongs to. This icon is missing in the browser extension and web version, which makes navigation less intuitive, especially when using multiple Vaults to organize data.

    Proposed Solution:
    - Add the Vault icon next to each item’s name in the browser extension and web version, just like on mobile.
    - Display this icon in the dropdown menu when selecting a password on a website, to clarify which Vault it belongs to.

    2. Clarify the Origin of Shared Items

    Problem:
    Shared items display an icon indicating they are shared, but there is no visual indication of who shared them or with whom they are shared. This causes confusion, especially when multiple shared items have the same name (e.g., 3 passwords named "Netflix," but shared by/with 3 different people).

    Proposed Solution:
    - Display the name of the person (or a short identifier) next to the sharing icon, both in the item list and in the password manager.
    - Include this information in the dropdown menu when using a shared password on a website.

    3. Organization of Shared Items in "Shared with Me" and "Shared by Me" Groups

    Problem:
    Items shared with admin rights appear in both "Shared with Me" and "Shared by Me", which is redundant and illogical. Even if I have admin rights on a Vault shared by someone else, that Vault doesn’t belong to me and shouldn’t be classified under "Shared by Me."

    Proposed Solution:
    - Create a third group (e.g., "Shared and Managed by Me") for items where I have admin rights but don’t own them.
    - Or: Keep only "Shared with Me" for these cases, and reserve "Shared by Me" for Vaults I created and shared myself.

    4. Optional: Assign a Vault to Shared Items

    Problem:
    Currently, it’s not possible to move a shared item into a personal Vault for better organization.

    Proposed Solution:
    Allow users to set a default Vault for shared items they receive, so they can automatically organize them into a clear structure.

    1. Display Vault Icons in Browser Extension and Web Version

    Problem:
    In the mobile app, a Vault icon is displayed next to each item’s name (password, note, etc.), making it easy to see which Vault it belongs to. This icon is missing in the browser extension and web version, which makes navigation less intuitive, especially when using multiple Vaults to organize data.

    Proposed Solution:
    - Add the Vault icon next to each item’s name in the browser extension and web version, just like on mobile.
    - Display this icon in the dropdown menu when selecting a password on a website,… more

    2 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

14. Improve AutoType for seamless desktop app autofill

    Proton Pass already supports AutoType for desktop applications, but the workflow still requires opening Proton Pass and manually selecting the login and field to fill. It would be much more seamless if Proton Pass could automatically detect login fields in Windows/macOS desktop apps and offer the matching saved login directly, similar to browser autofill. Ideally, it should support username, password, 2FA, and custom fields without requiring copy/paste or manually navigating the vault.

    2 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

15. Do not overwrite previously completed fields with blanks

    Selecting a second Identity/address/email should fill only relevant populated fields, not overwrite previously completed fields with blanks.

    2 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

16. Dedicated item-type navigation instead of all item types mixed together and filtering

    Instead of: All items → filter → Credit cards have persistent "User Profile" (or similar) sections/tab which holds: Identities | Cards | Bank Accounts | Passports | Vehicle

    Additionally, have dedicated sections/tabs for other item types instead of being mixed with logins: Notes | Aliases | Etc...

    This was one of the places RoboForm felt more mature compared to Proton Pass.

    2 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

17. Proton suite browser versions including ProtonPass vs the app versions.

    If I have Proton suite browser versions including ProtonPass, my logons and passwords populate fine on my web pages. If I have the app Proton suite including ProtonPass, my web pages do not populate logons and passwords. I must have Proton Pass browser version installed. I would like1) The app version of ProtonPass to populate my browsers logons and Password. 2) I would like to unlock my ProtonPass app version with Proton Authenticator.

    2 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

18. Biometrics disabled when in airports, ports, borders, courthouses, government buildings, police stations

    Biometrics unlock is convenient but the app should know when it's being accessed where authorities could force one to unlock a password safe. Nobody wants all their logins, CCs, sensitive info syphoned into a database things such as GDPR/privacy laws would have no authority over.

    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

    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. Add option to sort lists by 'last used' / 'recently copied from' in desktop app (Linux & Windows)

    Specific issue:
    No current sorting option enables formatting of the user list by which specific items (logins, aliases, etc.,) were most recently used / had credentials copied from.

    Context:
    Users with higher threat models (or users who simply just prefer) the native desktop app (for Linux and Windows) do not currently have the 'import usr/pwd with' functionality of the browser extensions, and are required to manually copy credentials between Pass/Auth and the target application. As a result of the increased required user actions, the net time for a user to access any service with Pass/Auth to increases (marginally but not insignificantly).

    Compounding effect:
    The current Pass sorting options are: most recent, alphabetical, newest to oldest, & oldest to newest.

    With the currently available options, as a user's list grows, frequently accessed/used items are less readily accessible within the list and must be located either through manually searching in the search bar or by scrolling through the list until visually identified. This is a second source contributing to increased total required used actions to successfully input credentials from the Pass/Auth services.

    The compounding effect elevates the UX tradeoff, of using the browser extension vs the native app, from being marginally poorer into being substantially poorer.

    Expectation: Adding sorting by last used / recently copied from options (and their inverse) to the sorting list would greatly enhance UX through improved efficiency and reduced manual interaction requirements; it would also bring the native desktop apps to closer to functional parity with their browser extension peers.

    A similar request is detailed at: https://protonmail.uservoice.com/forums/953584-proton-pass-authenticator/suggestions/50326692-treat-copied-passwords-as-recently-used

    Specific issue:
    No current sorting option enables formatting of the user list by which specific items (logins, aliases, etc.,) were most recently used / had credentials copied from.

    Context:
    Users with higher threat models (or users who simply just prefer) the native desktop app (for Linux and Windows) do not currently have the 'import usr/pwd with' functionality of the browser extensions, and are required to manually copy credentials between Pass/Auth and the target application. As a result of the increased required user actions, the net time for a user to access any service with Pass/Auth to increases (marginally but not… more

    2 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

20. Add a toggle for a simpler, more minimal Proton Auth interface!

    I’d prefer Proton Auth to have a simpler interface, similar to Google Authenticator, where it only displays the website or brand name and the authentication code. The current use of logos often results in incorrect or pixelated images, and requiring an issuer to avoid displaying “No Issuer” adds unnecessary information. I’d like Proton Auth to focus on a minimal design that makes it easy to search for a website and immediately find its authentication code.

    I've added a visual representation of what I'm suggesting below.
    https://imgur.com/a/xkR75pc

    2 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