Privacy, explained plainly.
This notice describes the data handled by the current ESPFlight website and Application services.
Website browsing
The public website does not include advertising scripts or third-party analytics in this release. Theme preference may be stored locally in your browser. Like most web hosting, the server or hosting provider may still process standard request information such as IP address, time, requested URL, and user agent for delivery, security, and operational logs.
Application device registration
When a compatible ESPFlight Application installation uses the ESPFlight application-service API, the server can receive and store controller/application registration data.
| Controller identity | MAC address and a SHA-256 MAC hash; controller IP when supplied. |
| Application context | Source, application name/version, and platform when supplied. |
| Request metadata | Request IP address and user-agent string. |
| Registration history | First/last seen time, seen count, latest registration payload, and per-device event records. |
The current server configuration keeps a bounded history of up to 500 recent registration events per device . The device summary record remains until it is administratively deleted.
Why this data is used
These records support controller recognition, application compatibility/operations, diagnostics, abuse prevention, and administration of the ESPFlight application services. The current package contains no advertising integration that sends these registration records to ad networks.
Security and disclosure
Registration endpoints require HTTPS and use client/rate-limit controls in the current server package. No internet-connected service can be guaranteed absolutely secure, so do not deliberately place secrets or unnecessary personal information in controller/app registration fields.
Your requests
For non-confidential privacy questions, use the Contact page . Do not post MAC addresses, IP addresses, device payloads, or other private identifiers in a public GitHub discussion. A private contact channel should be used before sending sensitive identifiers.
Changes
If ESPFlight later adds analytics, accounts, cloud features, crash reporting, or materially different data handling, this notice should be updated before or with that change.