Back to Privacy Hub

JetLag Privacy Policy

Last Updated: July 8, 2026

Quick Summary

A Wear OS travel utility that stores pinned cities, unit preferences, cached city/weather display state, tile/complication state, and phone/watch sync state where enabled.

App-Specific Details

Specific data handling practices for JetLag.

  • Stores locally: pinned cities, time display preferences, temperature units, cached weather display state, tile and complication state, phone/watch sync state, app preferences.
  • Uses only the app permissions needed for current functionality: INTERNET or network access where weather lookups are enabled.
  • Uses platform services where required: weather provider requests where weather is enabled, Google Play services Wear OS Data Layer where phone/watch sync is enabled, Google Play app distribution and updates, Wear OS tiles and complications.
  • Not described by the current app code: account system, developer backend account database, ads, analytics SDK, microphone, camera, contacts, calendar, files/photos, health/body sensors, advertising ID.
  • Local app data is removed when you clear app storage or uninstall the app.
  • Weather lookups may send the selected city or query to the configured weather provider so that weather can be returned.

Detailed Official Policy

Full technical and legal disclosure for JetLag.

# JetLag Privacy Policy Last updated: July 5, 2026 JetLag is published by Quazmoz / Quinn Favo. ## Summary A Wear OS travel utility that stores pinned cities, unit preferences, cached city/weather display state, tile/complication state, and phone/watch sync state where enabled. The app is designed to minimize data collection. Unless a feature explicitly uses a platform service listed below, app content is stored locally on your device and is not sent to a developer-operated backend. ## Data stored locally The app may store the following data locally on your device: - pinned cities - time display preferences - temperature units - cached weather display state - tile and complication state - phone/watch sync state - app preferences This data is used only to operate the app features you choose to use. ## Permissions The current app code may use the following permissions or permission-backed capabilities: - INTERNET or network access where weather lookups are enabled ## Platform services The app may rely on these platform or user-selected services: - weather provider requests where weather is enabled - Google Play services Wear OS Data Layer where phone/watch sync is enabled - Google Play app distribution and updates - Wear OS tiles and complications These providers may process limited technical or transaction data according to their own policies. ## Data collection and sharing The developer does not sell personal information and does not share personal information with advertisers. The current app code does not include a developer-operated account system, advertising SDK, or analytics SDK unless specifically stated in this policy. ## What the app does not use The following are not described by the current app code: - account system - developer backend account database - ads - analytics SDK - microphone - camera - contacts - calendar - files/photos - health/body sensors - advertising ID ## Data deletion You can delete local app data by clearing app storage in Android or Wear OS settings or by uninstalling the app. If the app includes an in-app reset, clear-history, delete-data, or export feature, that feature applies only to local app data unless explicitly stated otherwise. ## Contact For privacy questions or support, contact Quazmoz@vivaldi.net.

General Privacy Terms

These terms apply across all our applications.

Questions or privacy requests? Contact us at Quazmoz@vivaldi.net