Immediate background locking
Sending the app into the background locks the active vault. On iOS, a privacy shield also covers previews and sheets in app-switcher snapshots. Coming back requires unlocking again.
Lock immediately when the app goes into the background, with a configurable inactivity timeout that defaults to 60 seconds per vault.
Download RevaultSecurity modelOpening a private file is temporary access, not a permanent unlocked state. Revault locks when you leave the mobile app and when an idle vault reaches its timeout. You can choose the timeout that fits each vault without weakening background locking.
Sending the app into the background locks the active vault. On iOS, a privacy shield also covers previews and sheets in app-switcher snapshots. Coming back requires unlocking again.
The default timeout is 60 seconds. Choose 30 seconds, 1 minute, 2 minutes, 5 minutes or 10 minutes in that vault’s settings. Shared vaults use the 60-second default; background locking applies regardless of the selected timeout.
Locking cancels session work and clears decrypted file information, thumbnails, search and sharing state. Owned key buffers and session temporary files are cleaned up, and preview controllers and media players receive cleanup callbacks.
Background locking covers leaving Revault, such as switching to another app. Inactivity locking covers leaving an unlocked vault on screen without interacting with it. Increasing the inactivity timeout does not postpone background locking. This distinction matters when you are reading a long document: a longer idle setting can be more convenient, while leaving the app still ends the unlocked session.
Use a short setting for records you consult briefly in public, and consider a longer setting for a collection you read while seated in a private place. The options run from 30 seconds to 10 minutes and default to 60 seconds. Set this separately for each vault instead of assuming a convenience setting should apply to every private collection.
Locking clears the current decrypted file list and search, releases session-owned keys and temporary previews, and cancels active session work. A photo editor or sharing screen is part of that session too. If you leave during an import or edit, return and check what completed before assuming the change was saved. Explicit exports already handed to another application remain outside this cleanup boundary.
A system picker or another application can background Revault. Immediate locking takes priority over keeping the vault open through that transition. On return, unlock the intended vault again before the protected operation continues.
No. The configurable timeout governs inactivity while the vault is open in the foreground. Backgrounding still locks immediately, regardless of whether you selected 30 seconds or 10 minutes.
Session cleanup reduces the lifetime of keys and temporary data under the app’s control. Managed memory, operating-system caches and storage do not provide a guarantee of forensic erasure. Saved exports and screenshots are separate copies.
Choose the settings that fit your files, and keep a recovery plan before you rely on a single device.
Download RevaultCreate separate encrypted spaces on your phone. Each pattern opens only its matching vault, without a Revault account or sign-up.
Designate a vault whose pattern opens that space while removing other vaults’ local access and data from this device.
Opt a vault into encrypted local photo alerts after repeated failed patterns. Review the evidence only after unlocking that vault.