1527 results found

1. Autofill Toggle (email+password / username+password)

   Some accounts may have relevant usernames and emails associated with them but only allow for sign in access with one credential type.

   For example, Microsoft allows one to log-in via email, phone number, or Skype in their main webpage. I must use my email for this, but Proton Pass' auto-fill defaults to my Microsoft username which is relevant for some aspects of the the account but not relevant for signing into their main webpage.

   21 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

2. Toggle to exclude a specific login from autofill

   I would like a toggle on logins in the vault to exclude them from being available for autofill, similar to the "Exclude from monitoring" toggle that already exists.

   For example, I have logins for 15+ Google accounts related to clients or organizations I'm involved with, or old personal accounts that I no longer use but don't want to delete yet, but I only regularly log into about three of those accounts. Each time I log in, I have to wade through the full list of 15+ to select the correct one, and autofill does not float the most recently used to the top of the list.

   I'd love to toggle some of them off, and if I ever need those logins again, I can toggle them back on or simply copy and paste the credentials from my vault.

   I would like a toggle on logins in the vault to exclude them from being available for autofill, similar to the "Exclude from monitoring" toggle that already exists.

   For example, I have logins for 15+ Google accounts related to clients or organizations I'm involved with, or old personal accounts that I no longer use but don't want to delete yet, but I only regularly log into about three of those accounts. Each time I log in, I have to wade through the full list of 15+ to select the correct one, and autofill does not float the most recently used… more

   5 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

3. Add Safe-in-the-Cloud to the Proton Pass import list

   Please add Safe-in-Cloud to the Proton Pass password manager import list.

   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

   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

4. Dark Web Monitoring for Phone Numbers

   Dark Web Monitoring is Goated but it shall also include Phone Numbers, not only E-Mails.

   12 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

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

   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

   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

6. ssh generate keys

   Please add an SSH key generator so that public and private keys can be generated.

   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

   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

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

   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

   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

8. Samsung Pass import, please

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

   48 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

9. Bitdefender SecurePass Import

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

   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

   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

10. 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,

    13 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. Proton Pass in MacOS Appstore

    Please make Proton Pass available in the MacOS Appstore so it updates automatically

    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  ·  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. Let AI agents sign in without receiving credentials

    Proton Pass access tokens currently allow agents retrieve plaintext credentials through the cli.
    Please add brokered browser autofill for AI agents, similar to 1Password for Claude. When an agent requests a website login and the user approves, Proton Pass should fill the login directly into the webpage. The agent should receive only success or failure—never credential values.

    Requested outcome: an AI agent can complete a website sign-in without receiving the credentials.

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

    36 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

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

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

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

17. 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?

    56 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

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.

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

20. Feature Request – Virtual / Disposable Payment Cards

    Hi Proton team,

    I would love to see virtual payment cards added as a future feature to Proton, potentially integrated with Proton Pass.

    I’m referring to a service similar to Privacy, where users can create virtual card numbers for online purchases instead of providing their real credit or debit card details to merchants.

    This would add an extra layer of privacy and security when shopping online. If a merchant suffers a data breach, the user’s actual card details would remain protected. Ideally, users could create separate virtual cards for different merchants, set spending limits, freeze or delete cards, and possibly create single-use/disposable cards.

    I think this would fit very well with Proton’s focus on privacy and security, especially when combined with Proton Pass.

    It would also be great to make this available to users in Europe, as services such as Privacy are currently primarily focused on the US market.

    Thank you for considering this as a future feature!

    Hi Proton team,

    I would love to see virtual payment cards added as a future feature to Proton, potentially integrated with Proton Pass.

    I’m referring to a service similar to Privacy, where users can create virtual card numbers for online purchases instead of providing their real credit or debit card details to merchants.

    This would add an extra layer of privacy and security when shopping online. If a merchant suffers a data breach, the user’s actual card details would remain protected. Ideally, users could create separate virtual cards for different merchants, set spending limits, freeze or delete cards, and possibly… 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

    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