The short version
No advertising trackers
No ad networks, no behavioural analytics, and no tracking pixels inside the app. Optional crash 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. Pro users can optionally back up an encrypted vault file to their own iCloud or Google Drive account - only they hold the recovery key.
AES-256-GCM encryption
The app encrypts document data before saving it to local app storage.
Verification
You do not need to take this on trust. These checks show the important parts: whether your vault data leaves the app, which domains appear, and which permissions Android reports.
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 crash reporting, App Store or Google Play purchase checks, optional cloud backup to your own iCloud or Google Drive account, and a manual bug-fix check explained below.
Settings has a Check for Updates button. This is a manual check, never automatic, it runs only when you tap it yourself, never in the background and never on its own. 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. We keep no record of the check: request logs are disabled on our side, so no IP addresses are retained. 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. Same rule as everything else on this page: no network call without you asking for it.
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 (it plainly states what is collected, what is shared, that your data is encrypted in transit, and that it cannot be deleted) - 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). That is expected and safe: it is only your locked, encrypted backup file and a sign-in check being sent straight to your own Google Drive account - the same one you already use for photos or Gmail. We never see it, receive it, or keep a copy anywhere. Only you hold the recovery code that can unlock it.
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.
We hold the app to a public standard
We review Travel Document Vault against 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.
We scan our own code
Before a build ships we run static analysis on our code with Semgrep, an open source tool that flags insecure patterns such as weak encryption or unsafe data handling, so we catch them early.
We scan the built app
We also review our release builds with mobile app security scanning tools, checking how the build stores data, what it is allowed to reach, and how it is signed.
Found a problem? Tell us
If you spot a security issue, email support@traveldocumentvault.com. 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.