Set up recovery
Create passkey-preferred authorization, TOTP, a Recovery Key, and one-time codes.
← All features
Vault
A separate secure zone inside an already encrypted workspace.
Protect credentials, secure text, files, and nested Chambers with passkey-preferred unlock, TOTP, recovery options, and independent short sessions.
Purpose
Why Vault exists.
Vault creates a stronger boundary for the most sensitive material. Its keys, sessions, search, storage, and feature access remain separate from the regular workspace.
PRODUCTIVITY EFFECTKeep critical secrets organized and retrievable without mixing them into general Files, Search, sharing, or AI context.
How you will use it
Useful from the first action to the next.
Open a short session
Unlock the separate Vault boundary and navigate encrypted Chambers.
Reveal deliberately
View or copy a secret with timed hiding and clean lock behavior.
In real work
Different roles. A specific advantage.
These examples show how the same feature can remove a different kind of friction depending on the work around it.
Freelancer
Separate client credentials and secure files from the general project workspace.
Engineer
Organize sensitive recovery material without exposing it to Search or AI.
Professional
Keep essential personal secrets behind an independent session and recovery boundary.
Data & privacy
What it uses. What it stores. Where the boundary sits.
Only Vault items and Chamber organization you intentionally place inside the secure zone.
Summaries, payloads, and file bytes use separate encrypted layers and per-item keys; storage accounting remains operational.
Vault is excluded from AI, Global Search, sharing, offline cache, export, autofill, and the native mobile client.
Connected system
Vault is deliberately isolated.
This separation is part of the feature: no Global Search, AI, sharing, or regular Files bridge is allowed across the Vault boundary.
Make it part of one system
Start with Vault. Connect the rest when it helps.
No imported complexity. No privacy compromise.