TravelTracker Privacy Policy

This policy describes TravelTracker’s current pre-release iOS implementation. The app is in late-stage release preparation; an App Store release is not announced here.

Sergey Balashov is the contact for privacy questions: [email protected].

TravelTracker stores travel history, country/city/day information, location records, labels, passport records and visa records locally on the device. The current app has no app-level CloudKit synchronization.

The widget uses a local shared snapshot of derived travel information. Device security and operating-system backups are controlled by the platform and your settings. Local-first storage is not a promise that device backups or exported copies cannot exist.

Location-assisted updates use Apple Core Location and require your permission. Background updates depend on iOS settings and lifecycle. You can change or revoke location permissions in the device settings.

The app uses Apple reverse geocoding to resolve locations into country/city information. This service can involve Apple processing location information; its operation is subject to Apple’s privacy terms. Manual history remains available without automatic location collection.

TravelTracker includes a local diagnostic queue and a technical-diagnostics upload path. Upload is enabled only when the build enables telemetry and configures an HTTPS ingestion endpoint.

Diagnostic events can include event timestamps/categories, app and OS versions, locale, coarse permission states, power/thermal states, queue health and performance/crash-related diagnostics. The telemetry filter excludes coordinates, city/address, labels, travel/document contents, passport/visa values, contact details and stable user/device identifiers.

This is distinct from uploading your travel history. No advertising analytics SDK or cross-app tracking integration was found in the reviewed app. Backend processing location, access and retention arrangements must be confirmed before a release enables production diagnostic upload.

Local records persist in the app’s storage until you edit/delete them or remove the app data. The travel-data clearing action removes travel entries, location pings and stay periods; it should not be treated as deletion of every document or diagnostic record.

Manage document records through their app workflows. Deleting the app does not necessarily remove separate backups or copies you have shared. For questions about a diagnostic record or data held in a support conversation, contact us.

If you email support, you choose which contact information, message and attachments to send. That information is processed outside the app by email services to respond to your request. Do not send passport numbers, visa documents or raw location history unless needed and explicitly agreed.

Any change to data transmission, cloud synchronization or diagnostics requires this policy and App Store privacy disclosures to be reviewed. This policy does not announce App Store availability or complete the app’s release/privacy acceptance.