RevaultMove a vault to another phone with an encrypted transfer file and a separate transfer key, including when switching between iOS and Android.
Download RevaultSecurity modelChanging phones should not require uploading your private collection to a migration account. Revault prepares a portable encrypted copy that you move through a channel you choose. Its separate transfer key does not unlock the vault on your old phone.
Preparing a transfer creates a separate copy with fresh vault and file identifiers, a fresh master key and fresh encryption nonces. A new transfer key wraps that copy’s master key. Download cloud-only files before preparing the package.
Move the encrypted .qvault file to the receiving phone and communicate the displayed transfer key separately. Direct entry with both phones present avoids leaving the secret alongside the package. No Revault account or transfer relay is required.
The receiving app authenticates the package and creates a new vault with fresh encryption keys. Choose its device pattern and save its new recovery key. Folder relationships and encrypted thumbnails travel with the transfer.
Phone transfer creates a portable copy rather than a permanent relationship between devices. It suits switching platforms, replacing a handset or moving a specific vault while leaving other collections behind. Choose Revault Cloud instead when you need continued changes on both iPhone and Android. Neither route requires sharing the pattern used to unlock the old device.
Make sure the source vault’s files are downloaded and that both devices have space for the package and restored collection. Keep the old phone, its recovery material and an independent backup until verification is complete. Transfer creates fresh encrypted key material, so the displayed transfer key is a new secret to communicate, not a reason to expose your existing vault recovery phrase.
Prepare Move to another phone from the Android vault’s settings, move the .qvault file through a channel you control and enter the transfer key separately on the iPhone. Import the package, choose a unique pattern and save the new recovery phrase. Compare representative files, folders and counts before removing anything from Android. Configure the new vault’s storage provider deliberately after the move.
No. Preparing or importing a transfer is not a remote wipe. Keep the source until you have verified the destination, then decide separately which old device copies, packages and backups to retain or remove.
No. Later edits do not flow through a saved package. Use the appropriate native cloud for same-platform devices or Pro Revault Cloud for live cross-platform sync if ongoing updates are the goal.
The package and its key can be reused while someone retains both. Treat them as an encrypted copy with a separate secret, not an expiring invitation. Controlled sharing is the feature for server-enforced access deadlines.
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.
Choose private iCloud or Google Drive sync, or Pro Revault Cloud for iPhone and Android together. Keep other vaults entirely local.
Export a portable encrypted .qvault backup and keep its recovery key separately. Restore your files without a Revault account.