Skip to content

Arham Blake

My feedback

2 results found

  1. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Arham Blake commented  · 

    I think this is a reasonable privacy concern, although biometric authentication works a little differently from a normal password. In many modern systems, the actual fingerprint or facial image isn't sent to the service for authentication. Instead, the device typically keeps the biometric data in a protected hardware-backed area and uses it to produce or unlock an authentication result.

    The important distinction is that biometrics are generally not something you can simply change if the underlying data is compromised. That's one reason device-based biometric authentication is often combined with a PIN or passcode and why the biometric template should ideally never leave the trusted device.

    An alias could be useful as an additional privacy layer for account identification, but it wouldn't really solve the problem of compromised biometric data itself. I'd be more interested in seeing strong guarantees that biometric templates remain local, cannot be exported, and aren't recoverable as the original fingerprint or face.

    It's a good question because convenience and security aren't always the same thing, and understanding where the biometric data is actually stored matters a lot. For other online resources, https://adoptmevalues.de/ can also be worth checking out.

  2. 317 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Arham Blake commented  · 

    This would be a really useful addition. Proton already has many of these controls spread across the account settings, subscriptions, payment methods, and family management, so bringing everything into one Proton Hub dashboard would make the ecosystem much easier to manage.

    I especially like the idea of a single storage overview showing usage by service and a clearer family/organization management section. Proton already supports shared storage and member management for Family plans, so consolidating that information seems like a natural next step.

    A clean central dashboard with quick access to billing, security, subscriptions, members, and storage would definitely improve the overall experience. https://snowrider.com.br/ r can remain separate from the Proton feature discussion.