Encamera is worth examining for a camera-first private library. Its public file-handling core provides material for technical review, but that alone does not verify the complete App Store build. This assessment separates vendor statements from the device and recovery tests still needed.

What this review covers

We reviewed the product site, privacy policy and EncameraCore README. We have not independently inspected the installed app, captured network traffic, measured performance or restored a library. The assessment is written by a competing app developer, and it should be read with that relationship in mind.

Public source: useful, with a defined boundary

The repository describes its published portion as file handling and references SwiftSodium. Its README is not evidence that every component of the distributed app is public or that a particular store release matches the repository. A stronger technical assessment would identify the release, dependencies, key lifecycle and build correspondence before drawing conclusions.

Read the privacy policy alongside the feature list

The policy describes Piwik usage analytics and RevenueCat subscription processing. The App Store privacy label lists product-interaction usage data for analytics as not linked to identity. These are developer disclosures, not findings from a network audit; Apple says it has not verified the label. No-account use does not mean that no operational data is processed.

The encryption descriptions differ. The privacy policy names AES-256. Encamera’s June 2026 key-phrase article names XChaCha20-Poly1305, and the selected public file-encryption code we checked uses that algorithm. This identifies a documentation mismatch; it does not establish which code ships in a particular App Store build.

Features to check in your own workflow

The listing documents in-app and lock-screen-widget capture, Live Photos, share-sheet import, album-by-album local or iCloud storage, hidden albums and alternate icons. These are vendor-described features; hidden albums or an alternate icon should not be assumed to implement a decoy vault or a destructive duress mode.

  • Capture a disposable photo and video, then check Photos for an unintended copy.
  • For an iCloud album, confirm that the actual full-size test files open on the intended device; an album thumbnail is not a completed recovery test.
  • Check the exact purchase offer: the listing distinguishes Limited Lifetime from Lifetime Unlimited, with different access to future features. No price or entitlement has been tested here.

A practical capture-and-export checklist

Use an ordinary test subject. Take one photo and one short video, close and reopen the app, and check whether the expected unlock control appears. Inspect Photos for an unintended copy. Export the test items to a destination you control and verify that the video plays with sound. Record each result against the exact app version and device.

Test recovery without risking your library

Encamera’s recovery article describes a ten-word phrase under Settings > Backup Key Phrase. It also documents an optional Back up Key to iCloud setting using iCloud Keychain. The vendor says it cannot regenerate a lost key without the phrase. Keep the phrase private and stored separately from the only device containing your library.

Key recovery and file recovery are separate. The phrase can recreate a key; it does not recreate deleted or missing encrypted photos. Preserve your original device and test material, confirm that the intended replacement device can obtain the files, then test the documented key-restoration route. Do not uninstall the only copy to discover whether recovery works.

Our assessment

The documented capture route is a meaningful feature to investigate when importing from Photos does not fit your needs. Public core code improves the opportunity for scrutiny; it does not remove the need for it. PhotoVault: Encrypt & Compress instead imports existing media, storing compressed media and separate encrypted metadata for new Lossy imports, without whole source files. Existing retained originals remain exportable. Its device-only installation key is separate from the app credential. Compare local encryption, Secure Share export, and backup requirements on your own device before migrating sensitive libraries.

Sources & further reading

Keep exploring

At a Glance: 2026 Feature & Pricing Comparison

PlatformsiPhone and iPad (iOS 26 or later; iPadOS 26 or later). Official App Store ID: 6824412013.
FeaturesOn-device AES-256-GCM encrypted photo and video vault; Password, Pattern, Face ID and Touch ID unlock; optional lossy HEVC storage compression with separate searchable metadata and on-device OCR text search; local Collections, year-month timeline, Map view, and password/pattern-protected Secure Share (.pvsecure) archives.
PriceFree to download ($0.00 USD) on the App Store with optional Personal Monthly, Personal Yearly, Family Monthly, Family Yearly (supporting Apple Family Sharing), and one-time Lifetime plans. Current regional prices are shown in the App Store.
PrivacyMedia files and metadata indexes are encrypted locally on the device using a device-bound installation key stored in the iOS Keychain (no Arte Soft cloud account or gallery-upload server). Free tier displays Google AdMob ads; paid plans remove ads. See the privacy policy for details.
Compare your optionsUse Apple Hidden Album for basic hiding inside the shared Photos library, or choose PhotoVault: Encrypt & Compress when you need an independent Password or Pattern credential, AES-256-GCM encrypted local storage outside Apple Photos, optional HEVC space compression, on-device OCR text search, and encrypted portable Secure Share archives.
Is PhotoVault: Encrypt & Compress free to download?

Free to download ($0.00 USD) on the App Store with optional Personal Monthly, Personal Yearly, Family Monthly, Family Yearly (supporting Apple Family Sharing), and one-time Lifetime plans. Current regional prices are shown in the App Store.