Privacy Policy - TravelVault

1) Who we are

TravelVault is provided by Saifullah Ahad ("we", "us", "our"). Our website is: https://saifullah.ai.

2) What this policy covers

This Privacy Policy explains what information TravelVault stores, when (if ever) information leaves your device, and the choices you have when you use the App.

Short version: TravelVault is an offline travel-document and trip-organization app. Everything you create stays on your device unless you tap "Send Feedback" on the About screen, which is fully optional and described in section 6.

3) Information stored on your device

TravelVault stores the following categories of information locally in a private app database (Room/SQLite) and a private app file sandbox on your device:

• Trips: title, destination, start and end dates, status, trip type, notes, favorite flag.
• Travelers: name, relation (self, spouse, child, parent, colleague, friend, other), notes.
• Documents: title, type (passport, visa, ticket, booking, ID, insurance, etc.), category, file copy in the app sandbox, sensitive flag, favorite flag, notes.
• Itinerary items: day number, date, time, title, description, location, activity type.
• Emergency contacts: name, phone, email, type (personal, medical, embassy, insurance, local, guide, organizer), notes, primary flag.
• Medical info (per traveler): blood group, allergies, medications, conditions, care instructions. Stored as text you enter, not collected from any health service.
• Checklist items: title, category, completion state.
• App preferences: theme mode, app-lock toggle, biometric toggle, limited-preview toggle, compact-card toggle, readiness-prompts toggle, sort preference, onboarding state.
• Security material for the optional app lock: if you set a PIN, a salted SHA-256 hash of the PIN (plus a random 16-byte salt) is stored in the app's local DataStore. The plain-text PIN is never stored. Biometric unlock uses Android's BiometricPrompt, which never gives your fingerprint or face data to the app.

None of the items above are sent to us or to any third party at any time, with the single exception described in section 6 ("Optional in-app feedback").

4) How the app uses information

• To display your trips, documents, travelers, itinerary, emergency contacts, medical info, and checklist progress inside the app.
• To unlock the app when biometric or PIN unlock is enabled.
• To open files you attach (via Android's system document picker) and copy them into the app's private sandbox so they remain accessible to you inside TravelVault even if the original is later moved or deleted.
• To dial emergency contacts using the system phone dialer (Android ACTION_DIAL) when you tap a "Call" button - the app does not place the call itself, the user confirms in the dialer.

5) Permissions used

• USE_BIOMETRIC - to show the Android system fingerprint or face prompt when you enable biometric unlock for the app. The app receives only "succeeded" or "failed", never the biometric data itself.
• INTERNET - used only by the optional "Send Feedback" button on the About screen (see section 6). The app does not make any other network call.
• System document picker - the app does NOT request READ_EXTERNAL_STORAGE or MANAGE_EXTERNAL_STORAGE. To attach a document you tap "Attach file" and Android's built-in system document picker (Storage Access Framework) opens; only the single file you select is shared with the app.
• System phone dialer - tapping a "Call" row launches the system dialer with the contact's number pre-filled. The app itself does not request CALL_PHONE and does not place the call.
• FileProvider - when you tap "Open with..." on a document, the app uses Android's FileProvider to securely share a temporary URI to the file with the app you choose. No data leaves your device.

Cloud backup is disabled (android:allowBackup="false") so the encrypted PIN hash, salt, and document copies are NOT included in Google Drive auto-backup or device-to-device transfer.

6) Optional in-app feedback messages

TravelVault includes a Send Feedback option on the "About" screen. This feature is fully user-initiated - no message is ever sent unless you tap Send.

If you submit feedback:

• Your message text is delivered to the developer's email inbox.
• Your email address is optional. If you provide it, it is used solely so the developer can reply. If you leave it blank, the message is delivered anonymously and the developer cannot reply.
• A short technical footer is auto-attached to help reproduce bugs: app name, app version, Android version, device manufacturer, and device model. No identifiers, no contacts, no account data, and no content from inside the app (no trip, traveler, document, or contact data) are included.

The message is sent over HTTPS to a third-party email-relay service, Web3Forms (privacy policy: https://web3forms.com/privacy), which delivers it to www.saifullah.ai@gmail.com. Web3Forms processes the submission only to relay it; we do not use it for any other purpose.

7) Data retention

All on-device data is retained until you delete it inside the app (delete a trip, document, traveler, contact, etc.) or uninstall the app, which removes the entire app database and the attached-files sandbox.

Optional feedback messages are retained in the developer's email inbox for support and bug-tracking purposes. You can request deletion at any time by emailing www.saifullah.ai@gmail.com with a description of the message to delete.

8) Your choices and controls

• Delete any item in the app at any time (trips, documents, travelers, contacts, itinerary items, checklist items, medical info).
• Uninstall the app to delete all locally-stored TravelVault data, including the encrypted PIN hash and salt.
• Turn app lock off in Settings > Privacy & access at any time.
• Disable biometric unlock independently of the PIN.
• Clear or change your PIN in Settings > PIN setup.
• Toggle "Limited preview" to require an extra tap before viewing sensitive documents.
• Skip the email field on Send Feedback to send anonymously.

9) Security

On-device storage: SQLite database via Android's Room library, stored in the app's private internal storage that other apps cannot read. Attached files are copied into the app's private internal file sandbox (also unreadable by other apps).

App lock: optional biometric unlock via Android's BiometricPrompt API. Optional 4-to-8-digit PIN, hashed with SHA-256 using a per-install random 16-byte salt; plain-text PIN is never stored anywhere. App locks automatically when sent to background.

Network: HTTPS only, used only for the optional Send Feedback feature.

Cloud backup: disabled (android:allowBackup="false") to keep the encrypted PIN, salt, and attached files off Google Drive auto-backup and off device-transfer flows.

No method of storage is 100% secure, but the design minimizes attack surface by never sending your travel data off the device.

10) Children's privacy

TravelVault is intended for adults managing their own and their family's travel documents. It is not directed at children under 13 and does not knowingly collect personal information from children.

11) International transfers

Your on-device data does not leave your device, so no international transfer occurs. The optional feedback message you send via Web3Forms is processed and stored by Web3Forms (their infrastructure may be located outside your country); see Web3Forms' privacy policy for details.

12) Changes to this policy

We may update this Privacy Policy from time to time. The current version is always available at https://privacy.saifullah.ai/TravelVault with the updated effective date at the top.

13) Contact

For questions or requests, contact: Saifullah Ahad
Email: www.saifullah.ai@gmail.com
Phone: +8801711134346
Website: https://saifullah.ai