We describe Photo Vault by what it does, not by what vault apps are expected to promise. That means precise language about locks and encryption, no account, local storage, careful handling of your originals and clear notes about limits.

1. Say exactly what is protected

An app lock and file encryption are different things. We say which one applies, to what, and with which key. If a capability is missing, we say so on the page where you would look for it.

2. Keep it on the device

Photo Vault is designed without a gallery account or a server that receives your library. Local storage does not mean every operation is offline: Apple services can download an iCloud Photos original during import, supply map tiles or resolve stored coordinates into place names while the gallery is active. We describe those connections alongside the features that use them.

3. Respect the originals

New Photo Vault Lossy imports store compressed media with separate encrypted metadata, without whole source files. Still-image exports reconstruct JPEG or PNG files; existing retained originals remain exportable. Items without a retained original may still need reconstruction, which can lose detail. We distinguish those paths rather than treating a preview as proof that every original was preserved.

After a Photos import, the app can ask iOS to delete eligible originals. Decline that confirmation until you have verified your exported backup. Keep an independently recoverable copy; final-build import, export and recovery checks must come before relying on the archive.

4. No numbers we cannot stand behind

We have not established storage savings for the app. Retaining original resources alongside previews adds data, so a smaller preview does not prove a smaller archive. Quality observations are not measured preservation percentages. Security claims are tied to the source version reviewed and distinguished from behavior verified on your device.

5. Familiar, not mysterious

We build around the system photo picker and device authentication, with export through familiar iOS destinations planned. Secure Share (.pvsecure) exports use a separate password or pattern credential; verify exported copies in an independent destination before deleting originals. A familiar system screen does not by itself prove that every selected file arrived intact; the finished workflow needs an end-to-end check.

6. Teach, do not scare

Our guides explain how to think about privacy for photos, including when Photo Vault is not the right tool. Fear is a poor reason to install an app.

7. Change in the open

When the app changes in ways that matter for privacy or security, we update these pages and the What’s new log. The current source introduces local archive encryption with a device-only installation key; we document that design and its recovery limits..

Keep exploring