/ NOTHING

Watch Pilot Privacy Policy

Privacy policy

Applies to: Watch Pilot Wear OS app (me.ireynolds.watchpilot)


Contact

Questions: vu4rfnz@gmail.com.

What this app does

Watch Pilot fetches aviation weather for the airport nearest to your Wear OS watch (or an airport you’ve pinned) and displays it as complications on your watch face.

Data sent to weather providers

To display weather, the app contacts two APIs operated by the US government:

  • aviationweather.gov — METAR and winds / temps aloft. For METARs the URL contains the ICAO identifier of the nearest or pinned airport (for example, ?ids=KDEN). For the winds / temps aloft bulletin, no per-user parameter is sent.
  • api.weather.gov — daily temperature forecast. The URL contains the NWS grid cell (a ~2.5 km square) covering the airport.

These requests are made from your device’s public IP address. The receiving servers can infer your approximate location from the IP address combined with the airport identifier.

Data sent to the developer via Firebase

The app uses Firebase. Firebase receives:

  • A pseudonymous per-install identifier (app_instance_id). It resets when you uninstall and reinstall the app. It is not linked to your Google account or any other identity.
  • Your public IP address, captured server-side by Firebase. Google uses it for coarse geolocation.
  • General network-activity and app-usage logs used to understand app quality — for example which requests succeeded or failed, latency, session timing, device model, app version, and language.

No location data more precise than your public IP address is sent to Firebase. The airport identifier you are viewing, your pinned airport, your GPS coordinates, and METAR contents are not included.

Data stored on your device

The following data stays on the watch. It is not synced to the cloud.

  • Your pinned airport ICAO, if you’ve set one.
  • The most recent fetched weather bundle (airport info, METAR, forecast) so complications can render immediately at app launch.
  • A rolling 7-day log of the same network-activity and app-usage events sent to Firebase, kept for in-field debugging. The “Send Logs to Phone” button on the Info screen sends this log off the watch to your paired phone over the Wearable DataLayer; sending is user-initiated.

The purposes above — delivering weather to your watch face, and monitoring app quality — are the only purposes for which this app collects or transmits data. The legal basis for processing is legitimate interest: the NOAA / NWS fetches are the core service and cannot be provided without them; the Firebase collection is used to keep the app working and to ship fixes.

You can email vu4rfnz@gmail.com to:

  • Ask what data is associated with your install (access / right to know).
  • Request deletion of data associated with your install.
  • Lodge a complaint.

We may require extra effort from you to collect the information necessary to fulfill your request. We will not discriminate against you for exercising any of these rights.

Google, the Firebase processor, is located in the United States; international transfers rely on Google’s Standard Contractual Clauses. Firebase retains data per its own policies; this app does not impose additional retention and does not aggregate Firebase data outside the Google console.

This app is not directed at children under 16.

Changes to this policy

Any change to what data is collected, where it is sent, what is stored locally, or retention periods will be reflected in an updated version of this file before the change ships.

isaac

Isaac Reynolds

I'm a Googler, product manager, pilot, photographer, videographer. I've been the lead product owner for Pixel Camera Software since its inception. I hold a BS in Computer Engineering from the University of Washington in Seattle, near my hometown. I live near Denver after escaping Mountain View during COVID-19.

Read More