Privacy Policy

Your host keeps flight-board snapshots, settings, personal provider keys, movement history, logs, desktop state, paired-phone details, Remote Companion secrets, and LED matrix settings. Provider keys are stored on that host and sent directly to the provider you chose when Local Flight requests data. LAN browsers, Companion phones, and matrix boards ask your own host for their information.

Mobile Standalone keeps its connection details, selected airport, appearance, diagnostics choice, pinned flight, and recent movement history on the phone. Its movement history is not stored by Beacon Tools.

Home-screen widgets read a small snapshot that the mobile app already saved on the phone. Widgets do not contact your host, the shared service, or aviation providers by themselves.

If you choose Community Relay data, Remote Companion, or mobile Standalone, Local Flight connects to https://relay.beacontools.cc. The service can provide shared airport boards, radar and map helpers, activate a connection, apply fair-use limits, route encrypted paired-phone messages, and deliver reports you choose to send.

The service reuses recent shared results where possible. If you use your own aviation provider keys, those keys stay on your host and are sent only to the provider you selected.

Beacon Tools keeps only the service records needed to make the selected feature work and protect it from abuse: a random installation identifier, usage counts, broad app/device details, encrypted-message routing details, last-connected times, and short-lived shared data.

The Local Flight application database does not store raw IP addresses. Fly.io, Cloudflare, and other network providers may briefly process connection data in infrastructure or security logs under their own policies. The service does not store personal aviation keys from your installation, names or email addresses from normal app use, readable Remote Companion messages, your local movement history, Standalone movement history, payment-card details, or local logs unless you explicitly include sanitized logs in a report.

Detailed purchase record: for optional mobile support, the service stores only a keyed transaction hash, short reference, product ID, store platform and environment, verification status, public install fingerprint, timestamps, and a broad error code. Raw Apple transaction payloads and Google purchase tokens are not retained.

Where data-protection law applies, Beacon Tools relies on legitimate interests for the small service-operation and security records described here, consent for automatic diagnostics you enable, and your request when processing support messages or manual reports. You can change diagnostics choices at any time.

Optional mobile purchases process minimal transaction metadata to perform the purchase you requested, prevent duplicate processing, and satisfy store/security requirements. Apple or Google separately processes the payment under its store terms.

You may have rights to access, correct, erase, restrict, object to, or obtain a portable copy of personal data. Local Flight has no accounts, so include the Support ID shown by the app, a report reference, an approximate time, or the reply email you supplied when asking Beacon Tools to locate a record. Contact privacy@beacontools.cc or use Privacy choices. You may also contact your local data-protection authority.

The mobile app can offer three optional one-time consumable support products. They unlock nothing and create no durable paid entitlement. Store-owned localized pricing is shown before the Apple App Store or Google Play confirmation sheet opens.

After store approval, Local Flight sends the product ID and the store's purchase proof securely to Beacon Tools. The service checks it with Apple or Google before the app finishes the purchase. If that check is interrupted, the app can try again.

Local Flight never receives card details or your Apple/Google account identity. Raw store evidence is not retained and is never added to diagnostics, reports, heartbeats, or operator dashboards.

Manual reports can include the title and description you write, Local Flight version, public Support ID, operating system, Python version, configured airport and data mode, diagnostics choice, display settings, and the app area that sent the report.

Public website contact and bug-report forms can include the fields you submit, such as an optional name/reply email, message, product/area/version/platform fields, and optional text/log files. Uploaded logs are capped, sanitized, and embedded as excerpts rather than stored as raw attachments.

To slow spam and recognize duplicate forms, the service turns the connection address into a one-way tag and discards the raw address. The tag can accompany a support email or developer report. Support messages, report events, and duplicate-protection records may remain in the service database, support mailbox, or developer report system until routine cleanup or a valid deletion request.

Automatic crash reports, if enabled, can include crash details, an error trace, the desktop or mobile area involved, and—only for the stronger diagnostics option—a cleaned recent log excerpt. Reports are cleaned on your device, checked for duplicates and rate limits by Beacon Tools, and sent to the developer's Linear report inbox.

Diagnostics do not intentionally include API keys, activation tokens, raw install IDs, raw IP addresses, screenshots, recordings, stored flight history, full local logs, or account data.

Depending on your setup, Local Flight may communicate with AeroDataBox, AviationStack, ADS-B Exchange/RapidAPI, OpenSky, VATSIM, aviationweather.gov, OurAirports, OpenStreetMap/Overpass, public terrain tile sources, Linear for consent-based report triage, the configured mailbox provider for website contact messages, and Apple App Store or Google Play for an optional mobile purchase. Bring-your-own-key requests use your local provider keys. Relay-backed paths use the hosted relay and shared cache. See Linear, Apple, and Google privacy information.