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.
Create 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.