Privacy-first. On-device by default. No TDV account needed.

Privacy Verification

You should be able to check privacy claims for yourself. This page explains what the app sends, what it does not send, and why each permission appears.

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.

This summary covers vault storage. Store and cloud-provider accounts may be needed. Update checks, store purchases and restores, support and optional diagnostic reports involve separate data flows described below and in the Privacy Policy.

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

Camera

iOS + Android

Why we ask: To scan your passport, visa, or travel document pages directly from the app.

What we do not do: Photos are saved locally on your device. We do not upload them to Travel Document Vault. A photo leaves the app only if you choose to export, share, or back up your vault.

Photo Library / Photos / Storage

iOS + Android

Why we ask: So you can import an existing photo of a document. On Android the app uses the system photo picker, so READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE and READ_MEDIA_IMAGES are removed from the final build. Encrypted backup files (.tdvault) are exported through your phone's share sheet, which needs no storage permission.

What we do not do: The app reads only the image you select. It does not scan, index, or browse your photo library or file system.

Face ID / Touch ID / Biometric unlock

iOS + Android

Why we ask: To lock and unlock the app so only you can access your documents. On Android 6–8, USE_FINGERPRINT is used. On Android 9+, USE_BIOMETRIC is used instead.

What we do not do: The app does not receive your biometric data. The operating system handles authentication and returns only a pass/fail result to the app.

Notifications, Vibration, Boot Completed, Wake Lock

Android

Why we ask: To deliver on-device expiry reminders for your documents. RECEIVE_BOOT_COMPLETED re-schedules your reminders after a device restart. WAKE_LOCK supports notification handling. VIBRATE accompanies notification delivery.

What we do not do: We do not send marketing, promotional, or third-party notifications. Reminders are scheduled entirely on your device.

Internet, Network State, Wi-Fi State

Android

Why these appear: These are required for network-aware features: Sentry diagnostic (crash and error) reporting (opt-in, disabled by default), App Store or Google Play billing for the Pro upgrade purchase, Pro cloud backup (optional) which syncs your encrypted vault to your own iCloud or Google Drive, and the Check for Updates button in Settings (in the current released version, runs only when you tap it). ACCESS_NETWORK_STATE and ACCESS_WIFI_STATE let these features check whether a connection is available before attempting to send.

What we do not do: The app does not upload your documents, scans, expiry dates, photos, or vault contents to Travel Document Vault. It works fully offline for normal document storage and reminders.

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.

Record Audio

Inherited, removed

Why it appears: This permission is declared by the camera libraries included in the build. Travel Document Vault removes it from the final Android manifest, because the app captures still images of documents and never records audio or video.

How you can confirm: The app should not prompt you for microphone access. You can also check your device's permission manager to confirm microphone access has not been granted to Travel Document Vault.

System Alert Window

Inherited

Declared by a React Native framework dependency for development and debugging overlays. Travel Document Vault removes it from the final Android manifest and does not use overlay windows.

Detect Screen Capture

Inherited

Declared by a framework dependency. Travel Document Vault enables screen-capture protection by default on document screens where supported. You can change this in Settings.

Badge count permissions

Inherited

READ_APP_BADGE, UPDATE_BADGE, BADGE_COUNT_READ, BADGE_COUNT_WRITE, READ_SETTINGS, WRITE_SETTINGS, UPDATE_COUNT, CHANGE_BADGE, BROADCAST_BADGE, and PROVIDER_INSERT_BADGE are declared by the notification library to display unread badge counts on your home screen icon across different Android manufacturers (Samsung, Huawei, Xiaomi, etc.). They only affect the number shown on the app icon.

Billing, Check License, Install Referrer

Google Play

Declared by the Google Play Billing library for the Pro upgrade purchase and by the Play Install Referrer library. These support store purchases and install attribution handled by Google Play. They do not give Travel Document Vault access to your documents.

Download Without Notification

Inherited

Declared by a framework dependency. An update download started in the app may continue after it moves to the background, and iCloud can manage file transfers through the operating system.

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.

Location: no GPS, no geofencing, no tracking
Contacts: no access to your address book
Bluetooth: no local network or device scanning
Calendar: reminders are handled on-device, not via your calendar

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.