Help with Vault
For questions, email heyrohitjain@gmail.com.
These instructions describe the upcoming version 1.0 for iPhone (iOS 18 or later) and native Mac (macOS 14 or later). Earlier test builds may differ.
Tell us what happened
Include your app version, device model, operating-system version and the steps that failed. A harmless example can help. Do not send private documents, system passwords, encryption keys, recovery codes or package unlock codes.
Set up and unlock
Configure an iPhone passcode first. Open Vault, choose “Set up Vault”, read the separate-copy explanation and acknowledge it before “Create my vault”. Extra app authentication starts off for a new vault; existing protected vaults keep it on. There is no Vault account or account-password reset.
In Settings on iPhone or “About your vault” on Mac, use “Require authentication to open Vault” to add a system check. Changing this setting requires system authentication and keeps the same encrypted files. With it off, anyone using your unlocked device can open Vault. Files remain encrypted in either setting.
With extra authentication on, use “Lock Vault” and “Unlock Vault”. With it off, use “Close Vault” and “Open Vault”; reopening has no extra app authentication check. iPhone backgrounding closes the open library. On Mac switching apps conceals content; sleep or session lock closes it.
Import and find files
On iPhone choose “Import files” and select files or use the Photos picker. On Mac choose regular files or drag them into Vault. Originals remain at source. Directories and filesystem packages are not supported. A cloud file provider may need to download a selected file first.
Use folders, file-type filters and filename search to organize local copies. Search does not search document contents. Preview availability depends on format and operating system. Photos imports preserve the representation supplied by the picker, not every resource or edit history of a Photos asset.
Export an ordinary library file
Choose “Export a copy” from a file’s actions. It creates an ordinary unencrypted file in your selected destination, outside Vault’s protection. Manage that copy in its destination. This action is available for ordinary library files; it is disabled for received restricted copies.
Create and check a backup
- Open Settings → “Encrypted backup” on iPhone, or “About your vault” → “Encrypted backup…” on Mac.
- Select “Prepare an encrypted backup”. Save the recovery code separately, acknowledge it and complete the code confirmation.
- Choose “2. Create and verify backup”, then “3. Save encrypted backup…”. Save the file outside the original device.
- Use “Choose a backup…” with its recovery code and select “Verify backup” to check the copy actually saved at the destination.
Make a new snapshot for later changes. Anyone with a snapshot and its code can recover its files. Vault cannot reset a lost code. A snapshot stored only on a lost device is not a recovery copy.
Restore into a fresh vault
Before creating a vault, choose “Restore an encrypted backup” (Mac adds an ellipsis). Select the saved backup, enter its recovery code and choose “Verify and restore”. Restore creates a new vault and does not overwrite or merge an existing one. Do not reset a real vault merely to test recovery.
If a code is rejected or a backup cannot be read, preserve the original backup and existing vault. Check the selected file, code and provider access. Received shared files and their remembered keys are excluded from backups; keep their original encrypted packages and unlock codes instead.
Send an encrypted file
Use “Share encrypted copy” for a supported ordinary library file. Save and acknowledge its unlock code, then share or save the encrypted file through the offered action. Communicate the code separately. Supported types are PNG, JPEG, HEIC, PDF and UTF-8 text: up to 20 MiB per package, with text limited to 1 MiB and PDFs to 200 pages.
A package header exposes the original filename, type and size. The package remains copyable. Anyone with package and code can import it on another compatible installation. A newly prepared share has a new code; Vault cannot recover a lost code.
Open a shared file
Open “Shared files” → “Choose a shared file…”, select the package, enter its code and choose “Unlock and remember on this device”. Open it later from “Received on this device”. If remembered access is unavailable, use the original package and code. Importing does not remove the source package.
The received-file viewer disables export, print, copy and reshare actions for its local copy. It does not prevent forwarding the original package. There is no screenshot-prevention guarantee, expiry, view-once or remote revocation. Another camera can record displayed content. “Remove from this device” deletes the local received copy and its remembered key; external copies remain.
Each device stays independent
Sharing is a manual transfer, not automatic sync. Edits and deletion do not propagate between devices. The current interface uses Shared files and has no Nearby sync control.
Before changing device security or removing the app
Keep important originals until you have saved and checked recovery copies. Do not uninstall, reset a vault or remove device security when Vault holds your only copy. A lost device or key can mean permanent loss without its backup and recovery code. Removing a Mac app bundle does not guarantee deletion of app data or Keychain state. Deletion is not forensic erasure.