Know when the vault locks
Revault locks when it goes into the background and releases the active vault session. By default it also locks after 60 seconds of inactivity. Change the timeout in that vault’s settings; choosing a longer timeout does not disable background locking.
Revault’s own Android camera is part of the foreground capture session, so finishing a capture can return to the current vault without another pattern. Leaving Revault during capture still ends access. External camera apps and system pickers do not receive this exception.
Choose settings deliberately
- Review sync, import optimisation, automatic naming and metadata removal in the current vault’s settings. These preferences affect this collection, not every vault on the device.
- Enable activity logs only if you want that vault to retain interaction records. Optional break-in alerts require camera permission; camera indicators still apply, and an alert is not proof of someone’s identity.
- Keep a separate recovery phrase and backup. A privacy tool that hides a collection or removes metadata cannot recover a lost encryption secret or remove copies already saved elsewhere.
A protected vault still has a viewing boundary
Decrypted information must exist temporarily while you view or edit it. Preview copies are private working files, removed when the preview closes or the vault locks. Exporting a decrypted copy deliberately creates a file outside that boundary. Encryption does not protect an unlocked, compromised phone from everything it can observe.