Privacy Policy
Effective 20 October 2026. Publisher: Rohit Jain.
Vault is a local encrypted file app for iPhone and Mac. This policy describes the upcoming version 1.0 and this website. Earlier test builds may have different features.
Your files stay under your control
Vault reads files or Photos items you choose and stores encrypted copies in its local app storage. Its local filenames, folders and catalog are encrypted too. Filename search runs on your device while the vault is unlocked. Importing does not remove originals from Files, Photos or another source.
Vault has no account service or developer server for your files. The app does not automatically send your vault to Rohit Jain and contains no advertising or developer analytics. System file pickers, Apple services and apps or providers you choose have their own privacy practices.
Authentication and temporary copies
Vault uses a separate local encryption key. Extra app authentication starts off for a new vault; existing protected vaults keep it on. You can change “Require authentication to open Vault” in Settings on iPhone or “About your vault” on Mac. Changing the setting requires system authentication and keeps the same encrypted files. Vault does not receive your device passcode or system password. With the setting off, files stay encrypted, but anyone using your unlocked device can open Vault. With it on, Vault adds a system authentication check before opening.
Previewing and ordinary export require decrypted data. An ordinary exported file is outside Vault’s protection. Temporary data is cleaned up as applicable when an operation ends, the vault locks or the app starts again. This is not a guarantee of forensic erasure or immediate clearing of every memory copy.
Encrypted backups
If you create a backup, Vault prepares a verified encrypted snapshot. You choose where to save it. A cloud or storage provider you select receives that encrypted file and may process associated metadata under its own terms.
The backup and its separate recovery code together unlock the saved files. Keep them apart. Snapshots omit later changes; there is no automatic cloud backup or account-based recovery. Vault cannot reset a lost recovery code. Restore creates a fresh local vault rather than merging into an existing one.
Received shared files and their remembered access keys are excluded from portable backups. Their recovery requires the original encrypted package and its separate unlock code.
Manual encrypted sharing
Sharing creates an encrypted .vaultshare package and a separate unlock code. You choose the transport and communicate the code separately. The package header exposes the original filename, type, byte count, identifier, version and viewing policy. Transport services may also observe participants, timing and size.
The recipient imports a separate encrypted copy. Vault can remember its content key in private, non-synchronizing, device-only Keychain storage for later local viewing. Importing does not delete the external package.
The official received-file viewer disables export, print, copy and reshare actions. The original encrypted package remains copyable: anyone with that package and its code can open it on another compatible installation. There is no screenshot-prevention guarantee, expiry, view-once rule or remote revocation. Another device can photograph or record displayed content. Devices remain independent; changes and deletion do not propagate.
Deletion and recovery
Deleting from Vault removes the selected local entry and stored payload. Removing a received file also removes its remembered key. Originals, exports, saved backups, external packages and other recipients’ copies remain under their holders’ control. Ordinary deletion is not secure forensic erasure.
The local vault and device keys do not provide automatic recovery on another device. Without a usable backup and recovery code, losing a device or its key may permanently lose access. Support cannot recover lost keys or codes. Preserve important originals and checked recovery copies before uninstalling or resetting anything.
Support email and Apple diagnostics
If you email heyrohitjain@gmail.com, your sender address, message and attachments are received through Gmail. They are used to respond and investigate your request. Avoid private documents, passwords, keys, backup recovery codes and package unlock codes. Support messages remain in the support mailbox unless deleted; you can email to request deletion of your correspondence.
Apple may process distribution, crash or diagnostic information under its own services and your device settings. This policy does not claim that Apple, your chosen file providers, email services or transport apps collect no data.
This website
This site is served through Cloudflare. It has no analytics scripts, advertising tags, tracking forms or remote fonts. Cloudflare may process IP addresses and request metadata to deliver and protect the site, under its own privacy policy. No specific Cloudflare log-retention period is promised here. Your email app and Gmail handle messages you choose to send.
Questions and changes
Contact Rohit Jain at heyrohitjain@gmail.com with privacy questions or requests about support correspondence. Material changes will be reflected in this policy and its effective date.