A shorter window.
Honest limits.
When you lock Vault, its decrypted views disappear. Mutable buffers owned by our code are cleared. That reduces exposure; it is not a promise that all copies disappear from a computer’s memory.
What is enforced
- Idle lock defaults to 5 minutes, with local settings for 1, 5 or 15 minutes. A one-second timer checks the deadline.
- Hidden pages and page exit lock the web app. Native desktop sleep, screen lock and window blur lock the app. Native background events lock mobile apps.
- Passphrase inputs reset immediately after submission, including failed confirmations. Lock removes entry views, editor drafts, search text and revealed values.
- Owned Argon2 input copies, temporary protected master values, replaced credential hashes, fields, histories and attachment buffers are cleared. A pending initial hash cannot repopulate a cleared session.
- Android already uses secure-window protection. Updated iOS source covers inactive views and detected recording. Installers must be rebuilt and tested before those changes reach devices.
What the checks establish
Automated tests retain references to owned mutable buffers and assert they contain zeros after lock. Regression checks cover lock during credential creation, master rotation, clone isolation, protected custom fields, Unicode and an independently saved KeePassXC 2.7.12 corpus. Browser checks exercise idle lock, input clearing and removal of secret markers from the DOM, including an in-flight save.
These are scoped observations of buffers and visible DOM, not a forensic heap scan. They do not measure every browser, garbage collector, operating system or library allocation. No percentage of total secret-memory erasure is claimed.
What remains
JavaScript strings and copies in React, browser tooling, crypto libraries, WASM memory, swap and OS snapshots can remain until the platform reclaims them. An in-flight cryptographic operation clears its working copy when it settles; lock hides its views immediately. iOS public APIs do not universally block screenshots, and recording detection is reactive. Clipboard history and other applications can retain copied values. A compromised OS or browser can read an unlocked vault.
Use a trusted device, lock it when leaving, and keep an encrypted backup. This preview has no independent security audit.