How it worksApp features

Automatic vault locking

Lock immediately when the app goes into the background, with a configurable inactivity timeout that defaults to 60 seconds per vault.

Download RevaultSecurity model
Illustrative preview. Screens vary by platform.

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

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.

An inactivity timer per vault

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.

Clear the unlocked session

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.

Two lock triggers cover different situations

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.

Choose a timeout for the sensitivity and reading task

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.

What closing a session does to previews and work

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.

Practical checklist

  • Find Lock after inactivity in the current vault’s settings.
  • Test both leaving the app and allowing an idle timeout so the behavior is familiar.
  • Keep the phone’s own screen lock enabled; Revault’s lock protects a different boundary.

Frequently asked questions

Why do I have to unlock again after selecting a file in another app?

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.

Can I turn background locking off with a longer timeout?

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.

Does locking securely erase every trace of a viewed file?

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.

Keep exploring

Put this into practice in your vault

Choose the settings that fit your files, and keep a recovery plan before you rely on a single device.

Download Revault
App features