Engineered so we can't read your messages.
VAULT is built on end-to-end encryption from the very first message. Below is exactly what protects your data, what we store, and what we cannot see — no marketing hand-waving.
Six pillars of privacy by default.
End-to-end encryption
Every message and call is encrypted on your device before it leaves it. VAULT servers store ciphertext only — even we cannot read your conversations or hear your calls.
Modern cryptography
XChaCha20-Poly1305 for symmetric message encryption, X25519 for key exchange, Ed25519 for identity signatures. No legacy ciphers, no home-grown crypto.
Forward secrecy
Per-conversation session keys rotate. A compromise of one session does not roll backwards to past messages.
Verified handshakes
You can compare a short safety code between devices in person to verify the peer is the real holder of the handle.
Peer-to-peer calls
Voice and video run over WebRTC, end-to-end encrypted by SRTP/DTLS. Audio never traverses our application servers.
No third-party trackers
No Google Analytics, no Facebook pixel, no advertising SDKs. The web client and apps load only assets we serve ourselves.
Exactly what's on our servers.
We collect the minimum needed to make the product work. Nothing is sold, nothing is shared with advertisers, and we do not allow third parties to mine the data we hold.
| Account identifier | A handle you choose (e.g. @member). Required. |
|---|---|
| Phone number | Stored only if you verify one. Used for sign-in OTP and contact discovery (hashed). |
| Email address | Stored only if you verify one. Used for sign-in OTP fallback. |
| First and last name | Optional. Shown to your contacts in conversations. |
| Push token | Required to deliver notifications. Rotated on device change. |
| Encrypted message blobs | Stored briefly to deliver to offline recipients. Server never has the keys. |
| Billing records | Customer ID with our payment processor, plan, credit balance, transaction history. Card details are held by our payment processor — VAULT never sees them. |
- Plaintext message content
- Plaintext call audio or video
- Address-book copies — only SHA-256 hashes used for matching
- Credit-card numbers — our payment processor holds these, never VAULT
- Browsing history outside the app
- Location data
How we run the service.
Infrastructure
VAULT runs on Supabase (managed Postgres + edge functions) and Cloudflare. Database access is restricted by row-level security. Edge functions handle authentication, billing, and push delivery — never plaintext message content.
Payments
Payments go through a trusted third-party payment provider. VAULT never sees, stores, or handles your card number — we hold only the customer and subscription identifiers our provider returns.
Phone-book matching
To help you find friends who already use VAULT we accept SHA-256 hashes of phone numbers — never the numbers themselves. Hashes are computed on your device.
Account deletion
You can delete your account from Settings at any time. We purge your account record, verified contact data, and any queued ciphertext. Payment records are retained as required by tax and accounting law.
Security reports
Found a vulnerability? Email security@vault-messenger.com. We respond within two business days and credit researchers who follow responsible disclosure.
Government requests
We respond to valid legal process. Because we have no access to plaintext message content or call audio, the only records we can produce are account metadata (handle, sign-up date, last-seen, billing history).
Privacy that doesn't make you choose.
End-to-end encryption, modern AI, and a credit-based model that keeps your conversations off the advertising market.