Application data
This page describes the FlightWatch behaviour specified for the Public Beta. It does not state that external services have the same privacy practices.
| Information | How FlightWatch handles it |
|---|---|
| Hardware identifiers | No hardware fingerprinting and no collection of MAC addresses, disk serials or motherboard serials. |
| Public Beta licensing | Uses a username and a random installation ID. Local licensing state is protected with Windows DPAPI. Normal MSI uninstall preserves the local licensing identity. |
| Hoppie access code | Stored locally by the application. Treat it as a secret and never include it in screenshots, support messages or shared files. |
| Mobile Receiver | Operates on the local LAN / Wi-Fi. No cloud relay is required. The current receiver is read-only. |
| Flight History | Flight events and history are stored locally. |
| Diagnostic ZIP | Created locally after confirmation. Includes callsign, route and public ATC identifiers. Excludes credentials, private messages and raw settings. Sharing is your choice. |
This website
This static website includes no analytics scripts, contact form, advertising trackers or application credentials. Its hosting provider may process normal connection information to deliver and secure the site. Following a download or support link to an external service is subject to that service’s practices.
Connected services
VATSIM, vPilot, Hoppie and the FlightWatch licensing service are separate from this website. This page does not claim that these services collect no data, specify their retention periods or replace their policies. The local storage statements above apply to the FlightWatch application.