Device identity
Keys on your device establish your cryptographic identity. Public keys help other devices set up protected conversations.
Security, explained
How Vault encrypts your messages, delivers them through devices and protects the history stored on your phone.
Keys on your device establish your cryptographic identity. Public keys help other devices set up protected conversations.
The app derives conversation keys and authenticates encrypted content. Private key material stays within the device’s protected storage and unlocked session.
Direct connections, peers and relays carry encrypted payloads. Delivery and notification services do not need the plaintext message.
Your recipient’s app verifies and decrypts content. Saved local history is encrypted, with access governed by the vault’s lock state.
The delivery layer
Direct and mesh routes deliver without a central message mailbox. The relay provides encrypted backup in supported modes; connectivity and device availability determine which route can work.
When both devices can connect, encrypted messages travel straight from sender to recipient. No central message mailbox sits in that route. Connection setup still uses signaling.
Recipient available · sending directly
Direct and mesh delivery do not need a central message mailbox. An encrypted relay can provide backup in supported modes. Internet, account, connection setup and notification services are still required.
Explore how delivery worksAsynchronous conversations
Eligible encrypted messages can be held by the central relay and participating devices for later retrieval. A push notification can prompt the recipient’s app to reconnect. Operating systems control when background work can run.
Strict direct conversations · Pro
Strict conversations avoid payload mailboxes. Both participants need the required live connection. That reduces delivery storage, with a corresponding trade-off in availability.
“Mesh” describes Vault’s network of participating internet-connected devices. It does not mean Bluetooth walkie-talkie messaging, guaranteed delivery without internet, or independence from every backend service.
Content and context
Protecting the words inside a message does not make every part of a connection anonymous.
Message and attachment payloads are encrypted before transmission. Local message history is encrypted at rest.
Services process account records, device keys, routing information, network addresses, timing and operational logs.
A compromised device or a recipient who copies content can undermine confidentiality. Screen controls cannot prevent every form of capture.
Practical protection
Never share your password, recovery secrets or verification codes, including with support. Account recovery can replace an encryption identity; it does not restore lost local message history.
Temporary histories, Strict delivery and the panic password have different effects. Read the app’s confirmation carefully before changing a mode or deleting data.
This is an architectural overview, not an independent security audit or certification. For processing, retention and provider details, read the privacy notice. To report a concern, contact Vault Support without including secrets.