The feature
Why it matters
Shorten the time sensitive content remains available by closing the active vault session when attention moves elsewhere.
01
Lock when attention moves elsewhere
A private vault should not stay open indefinitely because a call arrived or the user switched apps. NullVault treats lifecycle changes as a security boundary: it cancels sensitive work where possible, detaches the active session, and returns to locked access.
This limits accidental exposure and reduces the window in which someone picking up the phone can continue from an already-open vault. The exact transition follows operating-system lifecycle events rather than assuming the app is always running in the foreground.
02
A clear session boundary
Locking invalidates the active session so returning to the app requires opening the intended vault again.
The exact timing follows each operating system's lifecycle events and the lock interval configured in the app.
Documentation basis
Documented claims
- Android locks on background, timeout, or screen-off.
- iOS detaches the key-bearing session on lock and locks on inactive or background transitions.
Know the boundary
Important limitations
- Lifecycle events and timeout behavior are controlled partly by the operating system.
- A compromised operating system or already-unlocked device can still expose plaintext during use.
- Any content legitimately exported before lock remains outside the session boundary.
Clear answers
Questions about this feature
Does NullVault lock when I switch apps?
Yes. Both apps lock the active vault when they leave the foreground according to the platform lifecycle and configured lock timing.
What happens when I return to NullVault?
After the active session has locked, you must draw the pattern for the vault you want to open again.
