RevaultDesignate a vault whose pattern opens that space while removing other vaults’ local access and data from this device.
Download RevaultSecurity modelSafe Exit is an optional, deliberate response for situations where keeping other local vaults accessible is no longer appropriate. You configure a designated vault in advance. Entering its pattern opens it and triggers the local cleanup of the others.
Enable Safe Exit in the designated vault’s security settings and confirm the consequences before using it. Its pattern must not collide with another locally enrolled vault. Use a separate encrypted backup for any offline-only vault you may need again.
Activation removes other vaults’ local keys, files and queued work. A persisted allowlist prevents normal listing and sync from immediately bringing excluded vaults back. Unsynced local changes can be lost, and already in-flight encrypted requests may finish.
Cloud copies and data on other devices are not deleted. Recover an excluded cloud vault deliberately with its recovery key and the original native cloud account. An offline-only vault removed from this device needs a separate backup to recover its files.
Ordinary Exit locks the current vault and returns to the pattern screen. Safe Exit has a different purpose: the pattern for a designated vault opens that space and removes other local vault access and data. It can destroy the only copy of an offline collection. Choose it only after understanding that consequence, rather than treating it as an alternative appearance or ordinary lock button.
Make verified encrypted backups and keep matching recovery phrases where you can reach them without the device. Check that any cloud copy you intend to rely on is complete. A phrase without surviving encrypted files cannot restore a removed local-only vault, and a stale cloud copy will not contain unsynced changes. Do not test a destructive trigger using the only copy of important records.
The trigger is local. It does not delete encrypted provider copies, content on another device, earlier shares or independent exports. Device settings and store records may still identify Revault, and encrypted network operations already in progress can finish. Safe Exit therefore cannot promise that another person will be unaware of the app, the cloud data or the fact that other information once existed.
No. It removes other vaults’ local access and data from the triggering device. It is not a remote wipe of native cloud storage, another phone or copies that were previously exported or shared.
Only if encrypted file data also survives, such as in a separate .qvault backup. The recovery phrase unlocks key material; it cannot recreate files lost with their only device copy.
No. It cannot control all operating-system records, storage remnants, cloud-provider information or another person’s conclusions. Its documented local cleanup is narrower than a guarantee about what an investigation could discover.
Choose the settings that fit your files, and keep a recovery plan before you rely on a single device.
Download RevaultExport a portable encrypted .qvault backup and keep its recovery key separately. Restore your files without a Revault account.
Lock immediately when the app goes into the background, with a configurable inactivity timeout that defaults to 60 seconds per vault.
Choose an available alternate icon and personalize the name shown inside Revault, using appearance options supported by your platform.