Security at Handlebook

Passwords are encrypted with AES-256-GCM in the creator’s browser. The database accepts ciphertext, a unique encryption nonce, and key-wrapping metadata—not a readable password. Vault keys are wrapped using device approval, a vault password, and a one-time recovery key. Handlebook staff do not possess the key needed to decrypt vault contents.

Database row-level security scopes workspace records to their authenticated owner. Provider credentials remain server-side. Sensitive phone messages are available only through authenticated, rate-limited, audited calls and expire automatically. Device approval (Face ID, Touch ID, and similar) is checked on your device; the server does not yet verify it before showing a full phone number or message.

Alias creation, vault-password attempts, and phone requests are rate-limited. Phone purchases use idempotency keys, capacity limits, price revalidation, and replacement safeguards to reduce duplicate charges and number-reuse mistakes.

Protect your sign-in account, store your recovery key somewhere safe, use a unique vault password, confirm recovery details on each social platform, and report unexpected activity promptly. No system can eliminate every risk. Handlebook has not yet completed an independent security assessment.