A decoy gallery can change what an app displays after a particular password. Plausible deniability is a broader claim: whether available evidence can establish that other protected content exists. A convincing screen alone cannot answer that question.
Name the property you need
An alternate icon changes presentation. An access lock controls entry. Encryption protects stored content under a key. A decoy displays an alternative collection. These features can coexist, but none automatically establishes the others.
For example, Safe Lock advertises a fake-password gallery. That is a developer claim about a feature, not independent evidence that other data cannot be detected. We have not performed a forensic assessment of that product.
Why cryptographic claims require more evidence
VeraCrypt documents hidden volumes and hidden operating systems as mechanisms for plausible deniability, subject to security requirements and precautions. Its documentation specifically discusses data leaks and distinguishes storage arrangements.
Those desktop mechanisms do not establish the properties of an iPhone photo app. A mobile product making a comparable claim needs to explain its own file layout, key handling, backups and remaining traces, with a review that covers those details.
Compare the platform and the stated limits
DueProcess is an Android research project based on a work profile and a profile-owner controller. Its university project page links a 2020 thesis examining the design and limitations. That is a different mechanism and platform from an iPhone photo gallery; it is not evidence that the same protection exists on iOS.
Vaultaire’s current guide says its normal interface omits a vault list, while its local storage has countable directories for configured vaults. The developer distinguishes that interface separation from hiding the vault count during app-container inspection. This is an attributed design disclosure, not our forensic test.
Before comparing two claims, specify what an observer can access: the visible screen, a single copy of storage, repeated copies over time, the running app, or a cloud account. Evidence for one case does not establish the others.
Evaluate separate layers
| Layer | Question to answer |
|---|---|
| Visible interface | What appears after each credential, relaunch and background return? |
| Stored content | What is encrypted, and are collections protected by independent keys? |
| Storage over time | Can allocation, file counts or backup changes reveal activity even if a single file looks encrypted? |
| Copies elsewhere | Do originals, exports or synchronized copies remain outside the app? |
| Recovery and backup | What can be restored, by whom and using which credentials? |
| Independent assessment | Which version, device conditions and attacker capabilities were actually evaluated? |
Use a practical test without overstating it
With disposable files, check normal and alternative credentials, biometric unlock, return from the background and a fresh launch. Note unexpected collection names, counts or previews in the interfaces you can inspect. Repeat after changes to lock settings.
These observations can identify an interface problem. Passing the trial cannot prove that every storage trace is absent. That stronger conclusion requires a different kind of assessment, not more confidence in the same screen test.
Do not confuse a decoy with deletion or recovery
Some products advertise emergency or duress actions alongside decoys. An action that removes access to data is a separate operation with different consequences. Read its exact behavior before enabling it; do not test destructive actions against unique files.
A decoy is also not a backup. Keep a verified recovery plan for files you need, and understand which additional copies that plan creates. No app interface can guarantee how another person will respond to what they see.
Photo Vault’s current boundary
Photo Vault has alternate icons and app-access controls, but no decoy gallery, duress mode or deniable-storage design. New and successfully migrated archives use local encryption with a device-only installation key. It should not be selected on a claim of plausible deniability.
Choose requirements first, then ask each developer for evidence addressing those requirements. An attractive icon, a biometric prompt or the word vault does not supply that evidence.
PhotoVault: Encrypt & Compress 1.0 is available on the App Store for iPhone and iPad (id6824412013). Archive tests covered image reconstruction, metadata, video and Live Photo handling, append and deletion compaction. This is not a verified public release or a complete test of the workflow in this guide. Physical-device launch, final ZIP and sharing behavior, and portable recovery remain unverified. Encryption requires a new archive or successful migration; the device-only key is not a portable backup service.
Sources & further reading
- Safe Lock: developer description on the App Store
- VeraCrypt: plausible deniability and its assumptions
- Johannes Kepler University: DueProcess Android research project
- Vaultaire: current deniability scope and storage limitations