Privacy policy

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

Last updated: 2026-05-14

Contact

Questions: tallycast.wear@gmail.com.

What this app does

TallyCast 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. 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, so we can monitor how fresh and how local the data shown to users actually is.
• Diagnostic information when the app crashes or encounters an uncaught error: the stack trace of the failure, the device model, the operating system version, and the app version. This is used to identify and fix bugs.

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 sent to Firebase is retained indefinitely.

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. By design the on-device log contains nothing Firebase doesn't already receive; this is enforced by an automated parity test in the codebase. The "Email Bug Report" button on the Info screen bundles these logs into a zip and pushes the zip over the Wearable DataLayer to a small companion app on your paired phone. The companion app opens your phone's email composer with the zip pre-attached and the developer's contact address pre-filled. Choosing whether to send the email — and editing the recipient, subject, body, or attachment before sending — requires explicit action by you on the phone.

Your rights, legal basis, and related disclosures

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 tallycast.wear@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 indefinitely; 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.