✨ From vibe coding to vibe deployment. UBOS MCP turns ideas into infra with one message.

Learn more
Andrii Bidochko
  • Updated: February 28, 2026
  • 6 min read

Passkeys PRF Warning: Risks and Recommendations

Passkeys and PRF risk illustration
Understanding the hidden danger of using passkeys for encryption.

Passkeys that also serve as PRF‑derived encryption keys dramatically increase the risk of permanent data loss, because losing the passkey means losing the encrypted data it protects.

Security professionals have long praised passkeys for eliminating phishing‑prone passwords, but a growing body of evidence warns that extending these credentials to encrypt user data creates a single point of failure. The original warning, published by Tim Cappalli, outlines real‑world scenarios where users unintentionally destroy priceless memories, legal documents, or crypto wallets simply by deleting a passkey. Read the full analysis here.

What the Original Warning Says

The article highlights three core concerns:

  • Credential overload: Using a passkey for both authentication and encryption expands the “blast radius” of a lost credential.
  • UI opacity: Most apps do not clearly indicate that a passkey also protects encrypted backups, leaving users unaware of the consequences.
  • Deletion cascade: When a user removes a passkey from a password manager, any data encrypted with the derived PRF key becomes unrecoverable.

The warning is not a call to abandon PRF entirely—its legitimate uses in credential managers are valuable—but it urges the identity ecosystem to stop conflating authentication with data protection without explicit user consent.

Why Mixing Passkeys and PRF Is a Risky Design Choice

1. Data loss through credential deletion

When a passkey is the sole source of the PRF‑derived encryption key, deleting that passkey erases the decryption material. Unlike traditional encryption where a recovery key or master password can restore access, PRF‑based schemes often lack a fallback. Users who clean up “old” credentials in Apple Passwords, Google Password Manager, or Bitwarden may inadvertently delete the only key that can unlock their encrypted backups.

2. Cascading impact on multiple data types

The risk is not limited to chat histories. Developers are increasingly using PRF to protect:

  • End‑to‑end encrypted messages and media files.
  • Encrypted documents, such as property deeds or medical records.
  • Crypto wallet seed phrases stored in encrypted vaults.
  • Credential manager vaults themselves, when the same passkey unlocks the vault and encrypts its contents.

A single lost passkey can therefore wipe out a user’s entire digital identity footprint.

3. Lack of user awareness and UI guidance

Most consumer‑facing applications present a single “Enable backup” toggle that silently binds the backup to the existing passkey. Without a dedicated warning screen, users like Erika (the fictional example from the original article) have no reason to suspect that deleting a passkey will also delete their photo archive, legal documents, or crypto assets.

4. Inadequate recovery mechanisms

Traditional credential managers mitigate loss through master passwords, recovery keys, or social recovery. When a passkey is the only source of the PRF key, those safeguards are bypassed. Even if the manager offers a recovery flow, it cannot reconstruct the missing PRF‑derived key without the original passkey.

Real‑World Scenarios That Illustrate the Danger

The warning article cites three concrete UI flows where users can unintentionally destroy data:

  1. Apple Passwords: Deleting a passkey from the iOS “Passwords” app removes the underlying PRF key, making any iCloud‑backed encrypted messages unrecoverable.
  2. Google Password Manager: Users who prune “unused” credentials from Chrome’s password manager may lose the decryption key for Android app backups that rely on PRF.
  3. Bitwarden: The open‑source vault allows bulk deletion of credentials; if a passkey used for PRF is removed, the associated encrypted vault entries become permanently inaccessible.

In each case, the UI does not surface a clear warning that the deletion will also erase encrypted data, leading to silent, irreversible loss.

Actionable Recommendations

For the Identity Industry

  • Stop promoting passkeys as a universal solution for both authentication and encryption without explicit user consent.
  • Provide a separate, clearly labeled “Encryption Key” option that is generated independently from the authentication passkey.
  • Publish a well‑structured About UBOS page that explains the distinction between authentication credentials and encryption keys.

For Credential Managers

  • Introduce a mandatory warning dialog when a user attempts to delete a passkey that has PRF usage attached.
  • Display the relying party’s (RP) information page (via the prfUsageDetails well‑known URL) so users can understand the downstream impact.
  • Offer a “Export PRF backup” feature that lets users store a recovery copy of the derived key in a secure location.
  • Leverage the Workflow automation studio to create automated alerts for risky credential deletions.

For Services Using Passkeys

  • Publish an informational support page that details how the service uses passkeys beyond login (e.g., for encrypted backups). See the UBOS templates for quick start for a template you can adapt.
  • Include the support page URL in the .well-known/prfUsageDetails endpoint so browsers can surface the warning automatically.
  • During the “Enable backup” flow, present a concise, bold warning: “If you delete this passkey, all encrypted backups will be lost forever.”
  • Consider integrating OpenAI ChatGPT integration to provide an interactive FAQ that explains the risks in plain language.

Take the Next Step with UBOS

If you’re building a product that handles sensitive user data, UBOS offers a suite of tools designed to keep authentication and encryption separate, while still delivering a seamless experience.

By adopting a platform that respects the separation of concerns, you protect your users from the very data‑loss scenarios described above.

Conclusion

Passkeys are a powerful tool for phishing‑resistant authentication, but when they are also used as PRF‑derived encryption keys, they become a single point of failure that can lead to irreversible data loss. The industry must adopt clear UI warnings, robust recovery mechanisms, and a strict separation between authentication credentials and encryption keys. By following the recommendations outlined above—and by leveraging platforms like UBOS homepage—organizations can enjoy the security benefits of passkeys without exposing users to catastrophic data loss.

Stay informed, design responsibly, and protect the digital memories that matter most.


Andrii Bidochko

CTO UBOS

Andrii Bidochko is an AI entrepreneur and researcher focused on AI agents, reinforcement learning, and autonomous systems. He writes about the technologies shaping the future of machine intelligence, from frontier models and agent architectures to real-world AI applications.

Sign up for our newsletter

Stay up to date with the roadmap progress, announcements and exclusive discounts feel free to sign up with your email.

Sign In

Register

Reset Password

Please enter your username or email address, you will receive a link to create a new password via email.