Vaulty’s privacy label links user content and several account or operational data categories to identity. Its linked PDF describes data processing but does not establish the media-key design. Those disclosures should guide questions about recovery and access, not be treated as a technical audit.
Scope and identity
We reviewed App Store ID 1616386868 and its linked privacy PDF on 20 October 2026. We build Photo Vault, a competing app, and have not tested Vaulty’s cloud service or account recovery.
Vaulty by Squid Tooth LLC is a different listed product from the Mappvate app reviewed here. Squid Tooth’s Google Play listing uses package com.theronrogers.vaultyfree, and its help site describes optional backup to Google Drive. Those instructions do not establish the backup provider, credentials or restore process for Mappvate’s App Store ID 1616386868. Match the developer before following a recovery guide.
Read the purposes separately
The store label places photos and videos under app functionality. It lists purchase and interaction data for developer marketing, and other categories for analytics. It does not say that photo content is used for advertising.
A linked-to-identity label also does not tell you who holds a decryption key. To assess confidentiality, ask whether encryption happens before upload, whether the provider can decrypt the media and how a password reset affects access.
What the linked policy establishes
The PDF identifies Mappvate as the controller and lists services including Firebase, Mixpanel and RevenueCat. It uses the generic term “This Application”; the text we retrieved names neither Vaulty nor Expena. We therefore do not describe it as an Expena policy.
A list of processors is not a measurement of which services run during a particular session. Ask the publisher for an explanation of the current Vaulty build’s media storage, retention, account deletion and key-management behavior.
What the developer says about account access
In an App Store response dated May 3, 2024, Mappvate describes images as cloud-stored and says signing into the account on another device provides access. This is a historical support statement, not our test of the current service. It makes account access an important part of the recovery questions, but does not establish encryption-key ownership or an unconditional guarantee against loss.
Before replacing a device, confirm which sign-in method and account your installed app uses, and check representative files on a second device. Keep an independent export until access is verified. Do not substitute Google Drive instructions from another Vaulty product.
Evaluate recovery without risking originals
- Import a small disposable collection and confirm upload completion before attempting access elsewhere.
- Use a second device to check sign-in and recovery while retaining the source copy.
- Compare downloaded files with the originals, including dimensions, duration and important dates.
- Ask whether deleting an item propagates to other devices and whether a recovery window exists. Test only disposable items.
- Verify a normal export route that does not depend on continued access to the service.
Assessment
The cloud-backup claim makes recovery worth testing, but it is not a guarantee against loss. We have not established restoration reliability, offline availability or end-to-end encryption. Photo Vault’s new archive format uses local encryption with a device-only installation key, but final-build and recovery verification are pending. This review does not rank either app as more secure.
Sources & further reading
- Vaulty on the App Store
- Policy linked from Vaulty listing (PDF)
- Mappvate website
- Squid Tooth Vaulty on Google Play — a different product
- Squid Tooth Vaulty help — not Mappvate backup documentation