Security

Built assuming our servers could be breached tomorrow.

Defence in depth: the parts that control your money live on your device, and the parts on our servers are designed to be useless to an attacker.

Security

Defense in depth.

Your keys are generated, encrypted, and stored on your device — never on our servers. We don't ask. We can't see. That's the point.

Every piece of Vaulted is engineered to assume our infrastructure could be compromised tomorrow, and your funds would still be safe.

  • BIP-39 12-word recovery phrases
  • TweetNaCl XChaCha20-Poly1305 encryption
  • Biometric device-level authentication
  • Multi-signature transaction approvals
  • Email-based co-signer verification
  • No password recovery — true non-custody

The model, layer by layer

1. Keys

Private keys are derived from a BIP-39 recovery phrase generated on your device and stored in the phone’s secure storage. They are never uploaded.

2. Messages

Chat is encrypted on-device with TweetNaCl (XChaCha20-Poly1305). Our servers relay ciphertext only.

3. Approvals

Large transactions can require a second signature from a co-signer, verified by email, before they move.

4. Access

Biometric device-level authentication protects the app; there is deliberately no password-based key recovery.

5. Safety controls

Users can report and block contacts in chat, and reports are reviewed by our team.

What we can’t see

  • Your recovery phrase or private keys.
  • The content of your encrypted messages.

Found a vulnerability? Email support@phoenix-atlas.com. See also compliance and the wallet.

Get on the waitlist.

We’ll invite you to preview Vaulted as soon as authorized services in your corridor go live. No card required. No spam. One email when we launch.

By joining you agree to the privacy policy and terms. You can unsubscribe at any time.

Prefer to see the app in preview mode first? Preview the app →