The shortest useful distinction
| Recovery phrase | Encrypted backup | |
|---|---|---|
| What it is | A high-value secret that authorizes a recovery operation | A protected copy of vault content and authenticated metadata |
| What it solves | Forgotten access credentials or key recovery, as defined by the platform | Device loss, damage, reinstall, or local storage failure |
| What happens if it is stolen | Another person may gain the authority the phrase conveys | Ciphertext should remain protected without the required secret, though metadata may be observable |
| What happens if it is lost | Recovery may become impossible | Another valid copy may still exist, but this backup cannot help if deleted or corrupted |
| Can it work alone? | Only for local recovery when the encrypted state is still present | No; it needs the correct recovery authority |
Android: device recovery and portable restore
NullVault for Android separates same-device recovery from portable backup recovery. A vault's device-recovery phrase can replace a forgotten pattern only while the encrypted vault remains on the original device. Restoring elsewhere requires a valid portable encrypted backup file and its separate backup recovery phrase.
Both parts matter:
- The matching backup recovery phrase must be correct and complete.
- The portable encrypted backup file must still exist and remain valid.
NullVault cannot reset or retrieve the phrase. A missing backup, wrong phrase, incomplete export, or modified backup is designed to fail closed.
Read encrypted backup for the feature status and security limitations for cloud boundaries.
Why a screenshot of the phrase is risky
A recovery phrase can transfer powerful authority. A screenshot may enter the system photo library, cloud synchronization, thumbnails, search indexes, backups, or another device. Email and notes apps can create similar copies.
Prefer an accurate offline record stored separately from the device and backup. Do not paste the phrase into chat, a support ticket, a password-strength checker, or an untrusted website.
Why one backup is not always enough
An encrypted backup can be corrupted, deleted, stranded in an unavailable account, or written incorrectly. For irreplaceable content, a recovery plan should answer:
- Where is the encrypted copy?
- Where is the phrase?
- Are they stored separately?
- Which platform and app version can restore it?
- When was the restore path last tested with non-sensitive sample data?
Do not discover during an emergency that the phrase is incomplete or the only package is damaged.
Recovery is not account recovery
NullVault does not maintain a NullVault login or a server-side master key for local vaults. Google Play may provide purchase restoration and its own account-recovery process, but that does not give NullVault the ability to decrypt a vault or reconstruct a missing phrase.
This is a deliberate privacy boundary with a real consequence: support cannot bypass it.
A practical storage plan
- Write the phrase exactly, including order and spelling.
- Verify it using the app's confirmation flow.
- Keep it separate from the unlocked phone.
- Do not label the record with unnecessary identifying detail.
- Protect the encrypted backup from accidental editing or deletion.
- Test recovery with non-sensitive data before relying on it.
- Update the plan after changing platform, account, backup method, or phrase.
Questions people ask
Can support recover my phrase?
No. Do not send it to support; anyone asking for it should be treated as untrusted.
If my phone is lost, is the phrase enough?
No. Restoring on another Android installation requires both the valid portable encrypted backup file and its matching backup recovery phrase. A phrase alone does not recreate missing ciphertext.
Does an encrypted backup reveal nothing to the provider?
No. The content payload can remain encrypted while account, timing, object-size, network, and storage metadata are still processed by the provider.
Should I store the phrase beside the backup?
Usually no. Separating them reduces the chance that one lost or stolen location gives someone both the ciphertext and its recovery authority.
Guide reviewed: 11 August 2026.