Privacy Policy

Effective date: 7 October 2026 · Last updated: 12 October 2026

Contents
  1. Who we are
  2. Summary
  3. Information we collect
  4. How we use information
  5. Sharing and third parties
  6. Affiliate and partner links
  7. Retention
  8. Security
  9. Your choices and rights
  10. Children
  11. International transfers
  12. Changes
  13. Contact

1. Who we are

This Privacy Policy describes how TripEase (“TripEase”, “we”, “us”) handles information when you use the TripEase mobile application for iOS, Android, and iPad, and when you visit this website. For privacy questions, contact us at apptripease@gmail.com.

2. Summary

3. Information we collect

3.1 Information you provide

If you email us (for support, partnerships, or privacy requests), we receive the content of your message and your email address so we can reply. We do not operate in-app user accounts or profiles.

3.2 App content and configuration

The app downloads travel reference data (for example country notes, airport guides, arrival-form links, and partner listings) from Firebase / Cloud Firestore. That content is the same travel information published for users; it is not a personal travel journal tied to your identity.

Preferences you set on your device stay on your device unless a future feature explicitly syncs them — in which case we will update this policy before that happens.

3.3 Travel profile, trips and reminders (stored on your device only)

These features are optional. Everything below stays on your device; TripEase has no server copy and cannot see it.

3.3a Country reference data

Emergency numbers, plug types and voltages (Wikidata, CC0), exchange rates (Exchange Rate API) and customs/embassy links are bundled with the app and refreshed by our data pipeline. The app does not contact these services and sends nothing about you to them. Opening an official link (embassy finder, customs page) takes you to that government site in your browser, under its own privacy policy.

3.4 Camera and passport scanning

The camera is used only when you tap “Scan passport”, to read the two machine-readable lines at the bottom of your passport photo page. Recognition runs entirely on your device: on iPhone and iPad with Apple’s built-in Vision text recognition, and on Android with the open-source Tesseract OCR engine bundled in the app. The scanner makes no network requests and sends nothing to us, Google, Apple or anyone else: no images, no recognised text and no diagnostic or usage data. No photo is taken, saved or uploaded; camera frames are processed in memory and discarded. You review and edit every field before anything is saved, and you can always type the details instead. TripEase does not record audio and does not read the passport chip (NFC).

3.5 Purchases (TripEase Pro)

If you subscribe to TripEase Pro, Apple App Store or Google Play processes the payment. We use RevenueCat to manage entitlements. In connection with that, we may process:

We do not receive your full credit or debit card number. Payment details are handled by Apple or Google under their terms and privacy policies.

3.6 Technical data from network requests

When the app loads content or map tiles, standard network information such as IP address and device/user-agent details may be processed by the providers listed in section 5 (for example Google Firebase, OpenStreetMap). We do not use that traffic to build advertising profiles.

3.7 What we do not collect

4. How we use information

We use the information described above to:

5. Sharing and third parties

We do not sell your personal information. We share data only with service providers needed to run TripEase, or when you choose to open an external link.

5.1 Firebase / Firestore (Google)

Used to host and deliver app content (countries, airports, forms, advisories, and related listings). Google may process technical data such as IP address when the app fetches this content. See Google’s privacy documentation for Firebase / Google Cloud.

5.2 RevenueCat, Apple, and Google Play

Used for subscription management and payment processing for TripEase Pro. RevenueCat receives anonymous identifiers and purchase history needed for entitlements. Apple and Google process payments under their own policies.

5.3 OpenStreetMap

If the app displays map tiles from OpenStreetMap, requests go to OpenStreetMap’s tile infrastructure (or a configured tile provider). Those requests typically include your IP address. OpenStreetMap’s usage policies and privacy notices apply to that traffic.

5.4 Website hosting

This website is hosted on GitHub Pages. When you visit the site, GitHub may process standard server logs (such as IP address and browser type) under GitHub’s privacy policy.

5.5 Legal requirements

We may disclose information if required by law, regulation, legal process, or governmental request, or to protect the rights, safety, and integrity of TripEase and its users.

6. Affiliate and partner links

Partner recommendations in TripEase may include affiliate links to third-party services such as Airalo, Booking.com, Klook, GetYourGuide, Wise, ExpressVPN, Agoda, and similar travel-related providers. If you tap a partner link, you leave the TripEase app and that company’s privacy policy and terms apply. If you complete a qualifying booking or purchase, TripEase may earn a commission at no additional cost to you. Affiliate partners may receive technical information (for example that you arrived from TripEase) according to their own practices.

7. Retention

Support emails are kept only as long as needed to handle your request and for reasonable follow-up or legal records. Purchase entitlement data is retained as needed to provide Pro access, prevent abuse, and meet accounting or tax requirements. On-device data (travel profile, trips, checklists and preferences) remains on your device until you delete it. You can remove all passport and trip details at any time with “Delete all details” in Your travel profile, delete a single trip from its page, or uninstall the app. On a fresh install TripEase clears any secure-storage data left on the device by a previous install.

8. Security

We use industry-standard measures appropriate to a small consumer app (including HTTPS for network traffic and reliance on established providers for content and payments). No method of transmission or storage is 100% secure; please use a current OS and app version.

9. Your choices and rights

10. Children

TripEase is not directed at children under 13 (or the minimum age required in your country). We do not knowingly collect personal information from children. If you believe a child has provided us information, contact apptripease@gmail.com and we will take appropriate steps.

11. International transfers

Our service providers (including Google, Apple, Google Play / RevenueCat infrastructure, and GitHub) may process data in countries other than your own. Where required, we rely on appropriate safeguards offered by those providers’ terms and transfer mechanisms.

12. Changes

We may update this Privacy Policy from time to time. The “Last updated” date at the top will change when we do. Material changes will be reflected on this page; continued use of the app or site after an update means you acknowledge the revised policy.

13. Contact