Privacy Policy

1. Overview

The App is a personal travel tracker. It does not require a user account and the App does not include a developer-operated backend that receives or stores your travel history, airport history, profile, QR profile, or share images.

Most travel information you use in the App stays on your device and, where Apple's services are enabled for your device and account, may also be stored or synced through Apple's infrastructure as described below. The App also uses Firebase Analytics for limited usage analytics.

2. Information You Can Store in the App

The App can store the following information for its features:

• Your visited trip entries, including country codes and optional trip dates.
• Your wish-list entries, including optional planned dates.
• Your lived-country entries, including start dates, optional end dates, and whether an entry is marked as currently living there.
• Your city entries, including city name, GeoNames identifier, country code, status, optional dates, and whether a lived-city entry is marked as currently living there.
• Your visited airport entries, including airport identifier, IATA code, airport name, optional city name, and optional country code.
• Timestamps associated with trip, wish, lived-entry, city-entry, airport-entry, and profile creation or updates.
• Your chosen profile name.
• Your optional emoji avatar selection.
• Your optional residency country selection.
• A locally generated device identifier used for QR comparison.
• Local notification preferences and reminder scheduling state.
• Cached purchase entitlement state used to show whether There Pro is active.

3. Local Storage and Cached Data

The App uses SwiftData to store trip records, city entries, airport entries, and your profile data. It also uses local app storage for limited settings such as onboarding completion, local notification preferences, cached Pro access state, and a locally generated QR identity value.

Country list data used for the main map experience, city search data derived from GeoNames, and airport search data derived from OurAirports are bundled inside the App. Country statistics requested from the World Bank are cached on your device so they can be reused later. Cached files may be removed by iOS according to system behavior.

If you use the travel map widget, the App may write a generated map image and a small widget payload, such as completion percentage, visited count, and last-updated date, to an Apple App Group container shared with the widget extension. This data is used to render the widget on your device.

4. iCloud and Cloud Sync

The App includes Apple iCloud / CloudKit entitlements and uses SwiftData for its stored app data. Based on the current configuration, trip, city-entry, airport-entry, and profile data may sync through Apple's iCloud / CloudKit services when those services are available and enabled for your device and Apple account.

Sync is handled by Apple's iCloud infrastructure. The App does not implement its own separate sync account system, custom sync dashboard, developer-operated travel-data sync server, or custom conflict-resolution flow. If iCloud is disabled, unavailable, or later re-enabled, sync behavior depends on Apple's services, your Apple account, your device settings, and network availability.

When you use the App's delete-all-data action, the App deletes stored trip, city-entry, airport-entry, and profile records from its model store and clears the locally generated QR identity value. The App does not present a separate restore or recovery tool.

5. QR Comparison, Sharing and User-Directed Disclosure

The App includes a social comparison feature based on QR codes. Your QR code is generated on-device and can encode a limited travel profile: your local comparison identifier, your display name, your optional emoji avatar, and your visited country codes. Those country codes may be derived from both country trip entries and visited city entries.

When another person scans your QR code, that information is shared directly by the code you choose to display. The App does not send that QR profile to the developer's own servers.

The App also lets you generate shareable images of your travel map and comparison results. If you use the system share sheet, the selected destination or recipient will process what you choose to share under that service's own terms and privacy practices.

6. Camera Access

The App requests camera access only for scanning another person's QR code in the comparison feature.

The camera feed is used on-device for QR detection. The App does not send the camera feed to the developer or to a developer-operated backend.

7. Network Requests and Third-Party Services

The App can make network requests directly from your device to third parties, including:

• The World Bank public API for country statistics shown in country details.
• Apple services involved in App Store purchases, purchase restoration, and Apple-hosted sync, if enabled.
• Firebase / Google Analytics for app usage analytics.
• External websites or apps that you choose to open, such as Instagram, TikTok, Apple Maps, Google Maps, email, and the hosted legal pages.

Those third parties may receive technical request data such as your IP address and standard device or network metadata according to their own privacy practices.

8. Purchases, Subscriptions, and Donations

The App includes optional paid There Pro features processed through Apple's StoreKit and the App Store. Current paid products may include auto-renewable subscription options, a lifetime non-consumable purchase, and optional one-time consumable tip / donation products.

The App can check current App Store entitlements and can ask Apple to restore purchases through App Store sync. The developer does not receive your full payment card details through the App. Apple processes purchase transactions under Apple's own terms and privacy policies.

9. Notifications

The App includes optional local reminders. If you allow notifications, the App may schedule reminders related to completing your map, adding the travel map widget, revisiting your wishlist, or adding your latest travel entry.

These reminders are scheduled on your device using Apple's local notification system. You can enable or disable reminders in the App's settings, and you can manage notification permission in iOS, iPadOS, or macOS Settings.

10. Analytics

The App uses Firebase Analytics to understand feature usage, improve the App, and identify product issues. Analytics events may include screen views, onboarding completion, feature usage, paywall interactions, purchase and restore-purchase flow events, notification permission results, sharing actions, QR comparison actions, and country, city, airport, or trip actions.

Analytics events are designed to use limited event names and categories, counts, buckets, status values, and feature names. They should not include your profile name, email address, exact location, user-generated text, personal travel notes, or the precise list of countries, cities, airports, or trip dates you store in the App.

Firebase / Google may also collect technical app and device information associated with analytics, such as app version, device model, operating system version, usage events, and related identifiers according to Firebase's own policies. The App does not include App Tracking Transparency prompts, advertising SDKs, or cross-app advertising tracking in the reviewed code.

11. Data Retention and Deletion

App data remains stored until you edit it, delete it through the App, or remove the App, subject to Apple's storage, sync, and backup behavior.

The App does not currently provide a dedicated export feature, import feature, backup manager, or restore workflow. If you contact the developer by email, the developer may retain that correspondence for as long as reasonably necessary to respond and keep basic records.

12. Your Choices and Rights

You can manage your stored travel data directly in the App by adding, editing, or deleting trips, city entries, and airport entries, changing your name or emoji avatar, or using the App's delete-all-data action.

You can also control certain Apple-managed processing by adjusting iCloud, camera, and notification permissions in your device settings. If applicable law gives you additional privacy rights, you may contact the developer at beucaalexandru@icloud.com.

13. Children's Privacy

The App is not designed to intentionally collect personal data from children. The developer does not knowingly collect children's personal data through a developer-operated backend in the App.

If you believe a child has sent personal information directly to the developer by email, contact the developer so appropriate steps can be taken.

14. Security

Data handled by the App relies mainly on protections provided by iOS, your device, and, where applicable, Apple's services such as iCloud, CloudKit, and the App Store.

No method of storage or transmission can be guaranteed to be completely secure, but the App is designed to avoid sending your personal travel records to a developer-operated travel profile backend.

15. Changes to This Policy

This Privacy Policy may be updated from time to time to reflect changes to the App or legal requirements.

When this page is updated, the "Last updated" date at the top will also be updated.

16. Contact

If you have questions about this Privacy Policy, you can contact the developer at:

beucaalexandru@icloud.com