The short version

On your device by default
- Documents and scans
- Expiry dates and reminders
- Works offline
Optional cloud backup · Pro
- Vault content encrypted before upload
- Your own iCloud or Google Drive
- Some backup metadata remains readable
No TDV account needed.
No advertising trackers
No ad networks, no behavioural analytics, and no tracking pixels inside the app. Optional diagnostic reporting is separate and stays off unless you turn it on.
No document data collection
Your documents, scans, expiry dates, and vault contents are not sent to Travel Document Vault. The app works fully offline for normal document storage and reminders.
On-device by default
Documents stay on your device by default. There is no Travel Document Vault cloud account, document server, or backend database.
AES-256-GCM encryption
The app encrypts document files before saving them to local app storage. Pro users can optionally back up encrypted vault content, with some readable operational metadata, to their own iCloud or Google Drive. Cloud Backup does not send the recovery code or decryption keys to us.
Verification
The steps below help you inspect the app’s behaviour on your own iPhone or Android device, including network connections and permissions. Each check shows only the behaviour visible during your test. These checks are not an independent security audit or a guarantee that every security issue has been found.
1. Network traffic test
Install a network monitor such as mitmproxy (free, open source), Wireshark (free, open source), or Charles Proxy. Open Travel Document Vault, scan a document, browse your vault, and set a reminder. You should not see your documents, scans, expiry dates, or vault contents sent to Travel Document Vault. Network traffic should be limited to specific features: optional Sentry diagnostic (crash and error) reporting, App Store or Google Play purchase checks, optional cloud backup to your own iCloud or Google Drive account, and a bug-fix check explained below.
Settings has a Check for Updates button. In the current released version, this check runs when you tap the button; it does not run automatically when you open the app. An in-progress download may continue after the app moves to the background. The check contacts updates.traveldocumentvault.com - our own update server, run by us on Google Cloud, which serves cryptographically signed update files from a storage bucket. The update handler does not write application request logs. Every update is signed with a key only we hold, and the app refuses anything whose signature does not match the certificate built into it. The same tap also checks the App Store or Google Play for a newer version of the app. It exists so that certain bug fixes can reach you faster than waiting for a whole new App Store or Google Play release, useful for urgent fixes, depending on the nature of the fix. Document storage needs no network; store purchase checks and enabled optional features can make automatic network calls.
2. iOS App Privacy Report
On iPhone, go to Settings > Privacy & Security > App Privacy Report. This built-in Apple feature shows which apps have contacted network domains. Travel Document Vault does not send your documents, scans, expiry dates, or vault contents to us. If you have enabled Pro cloud backup, you will see connections to Apple's iCloud domains - that is your own backup syncing to your own iCloud account.
3. Android - checking your privacy
Android does not have a single built-in privacy report like iPhone. Two simple ways to check for yourself: look at this app's own Data Safety section on its Google Play page for the developer’s store disclosures - or use a network monitor as described in step 1 above.
If you have turned on Cloud Backup, you may notice some activity going to Google's servers (web addresses ending in googleapis.com). These connections carry your encrypted vault files, sign-in checks and unencrypted backup metadata such as device name, counts and timestamps to your own Google Drive account - the same one you already use for photos or Gmail. Cloud Backup does not send these files, your recovery code or decryption keys to us.
4. App Store and Play Store privacy labels
Apple and Google require developers to declare what data their app collects. Check the App Store or Google Play listing for Travel Document Vault and compare it with the behaviour you see in your own network test. The key point to verify is simple: your document data is not collected by Travel Document Vault.
How we test the app's security
We do not just say the app is safe. We check it, using the same open tools and public standards the security industry uses.
Compare the app with a public standard
You can compare Travel Document Vault with the OWASP Mobile Application Security Verification Standard (MASVS), the industry checklist for how a mobile app should store data, use encryption, lock behind Face ID or a PIN, and handle links from other apps. Anyone can read the standard and compare it with how the app behaves.
Source code analysis
Static analysis tools such as Semgrep can flag insecure patterns such as weak encryption or unsafe data handling. This describes a checking method, not proof that every release has passed a scan.
Built app behaviour
The app encrypts document files on your device, and its update configuration requires a code-signing certificate. You can check its network behaviour using the steps above.
Found a problem? Tell us
If you spot a security issue, email [email protected]. Our disclosure details are published at /.well-known/security.txt.
This is our own assessment against a public standard, not an independent audit or a certification. Last reviewed July 2026.
Every permission explained
Android apps declare permissions in their manifest. Some are requested by the app directly, and some are inherited from libraries the app depends on. Here is a transparent breakdown of every permission, grouped by purpose.
Permissions the app uses directly
Permissions inherited from libraries (not used by the app)
Android apps include third-party libraries for features like in-app purchases, crash reporting, and notifications. These libraries declare permissions in their own manifests, which get merged into the final app. The permissions below are declared by dependencies, not by our own feature code.
Permissions we do not request
These are common permissions that many apps ask for. We do not request any of them, and they do not appear in our manifest.
Still have questions? Read our full Privacy Policy or check the FAQ.
Download Free. No Subscription.
Set it up tonight. Let the app remember so you don't have to.