PasswordFix is in development. Features and timing may change before release.

Security should be clear about what it protects.

PasswordFix is being designed around independent vault keys, device-scoped authorization, and explicit recovery boundaries.

Read the security approach →
Independent vault keys, device-scoped authorization, explicit recovery boundaries.

01

Separate cryptographic boundaries

Your Vault and your Emergency Safe have separate keys and separate ways to unlock, not just labels or folders.

02

Account sign-in is not vault access

Signing in to our website never unlocks your data, and can't add a new device on its own. We'll never ask for your master password or PasswordFix Key by email, phone or chat.

Account sign-in (Web session): Does not authorize a new device. Device authorization (Separate approval). Vault access (Requires vault key).

03

Recovery without a hidden backdoor

Proving who you are can never replace missing keys.

We can't read your passwords.

They're encrypted on your device with keys we never have. What we can see: account details we need to run the service, such as your email address and the devices you add. Never what's inside your Vault or Emergency Safe.

Independent review required

Security claims will be updated as implementation and external assessment are completed.

  • Design principles

    Defined

    Independent vault keys, device-scoped authorization, and explicit recovery boundaries.

  • Implementation

    In progress

    Core architecture and security controls are being implemented.

  • External assessment

    Planned

    Each major version of PasswordFix will be independently security reviewed and penetration tested before release.

  • Ongoing updates

    Planned

    Security claims will be kept up to date as new information becomes available.

Report a security issue →