Skip to main content
Help Center & Practical Documentation

How Can We Help You Protect Your Vault?

Concise, practical guides on your 128-bit Secret Key, signing in from new devices, 15-minute auto-lock, encrypted sharing, and KeePass (.kdbx) migration.

Step-by-Step Guide

Quick Start: 3 Steps to Your First Encrypted Vault

Get started with PassKee in under three minutes while keeping 100% ownership of your encryption keys.

  1. 01 Registration

    Create Your Master Password

    Enter your email and choose a strong Master Password (minimum 10 characters with uppercase, lowercase, and digits). Your Master Password never leaves your browser.

    Keys generated locally via Argon2id
  2. 02 Critical Step

    Save Your Emergency Secret Key

    Click Copy Secret Key (PK-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX), store it offline, and confirm the checkbox "I have saved my Secret Key and understand PassKee cannot recover it."

    Cannot be recovered by PassKee servers
  3. 03 Ready to Use

    Create a Vault or Import .kdbx

    Organize 8 credential types into nested directories, share items with # fragment links, or import your KeePass (.kdbx) database via the vault menu.

    Sealed with AES-256-GCM + X25519

Knowledge Base

Practical Frequently Asked Questions

Showing direct answers without filler

Auto-Lock & Zero-Knowledge

What happens after 15 minutes of inactivity or when I click Lock?

After 15 minutes of inactivity—or immediately when you click the Lock button in the header—PassKee closes all open modals, zeroes out your decrypted Private Key and active Vault AES Key in memory (RAM), and navigates to the Unlock Session screen. If you close the browser tab or click Logout, sessionStorage is completely cleared.

Auto-Lock & Zero-Knowledge

Can PassKee servers or administrators read my vault or folder names?

No. PassKee servers store only raw binary ciphertext (PostgreSQL bytea). Each vault has its own 256-bit AES-GCM key wrapped with your Curve25519 (X25519) keypair, and both directory names and credential payloads are encrypted on your device before transmission.

Want a Deeper Dive Into Our Cryptography?

Read our Security & Zero-Knowledge architecture overview to see how Argon2id, AES-256-GCM, and #fragment links work under the hood.

Read Security Architecture