Don’t send crash reports
Crashes stay on your device. App label: Manual reports only on desktop or Pi, and Ask me first on mobile.
Privacy / Controls
Change what gets sent—or remove what is stored.
Choose the result you want: change crash-report settings, update setup, remove a paired phone, erase local data, or ask Beacon Tools to locate an online service record.
01 / CRASH REPORTS
Choose how crash reports work.
Manual reports leave your device only when you press Send. Automatic crash reports remain off unless you choose one of the automatic options.
Send cleaned crash reports
A crash can send cleaned error details and broad device context. App label: Auto crash reports on desktop or Pi, and Send crash reports on mobile.
Include a short cleaned log excerpt
The stronger option can add a short cleaned excerpt from the latest text log. App label: Auto crash reports + logs on desktop or Pi, and Crash reports + context on mobile.
Send a report yourself
App and website reports remain user-triggered. They are cleaned before delivery and send only when you choose Submit or Send.
Manual app reports and enabled automatic diagnostics are cleaned on your device. Website bug reports pass through Beacon Tools, are size-limited, and are cleaned before reaching the developer’s Linear report inbox. Read Linear’s privacy information.
02 / RESET AND ERASE
Choose how much you want to change.
Changing setup, removing a paired phone, resetting an app, and completely erasing an installation are separate actions.
- 01 / SETUPChange setup without deleting everything
Use Reset Setup in Local Flight Settings. This keeps the installation identity and Community Relay link while letting you change the airport, data source, or setup path.
- 02 / PHONERemove a paired phone
Revoke Remote Companion in the Local Flight computer’s Settings before choosing Forget on the phone. Forgetting only on the phone does not cancel the computer’s remote-access permission.
- 03 / MOBILEReset the mobile app
Use the in-app reset to choose Companion or Standalone again. For a complete mobile erase, revoke Remote Companion first, then remove the app from the phone.
- 04 / DESKTOPCompletely erase desktop or Pi data
Stop Local Flight, then remove
~/.localflight/and~/.localflight_identity.json. The next launch is treated as a new installation. - 05 / SERVERCompletely erase Linux server data
Remove the server package, then explicitly delete
/var/lib/localflightand/etc/localflight. Normal package removal preserves these folders for an upgrade or reinstall. - 06 / KEYSRemove saved aviation-data keys
Your own aviation-data API keys stay in the Local Flight installation. A complete local erase removes Local Flight’s saved copy.
03 / SHARED RECORDS
Online features may leave a small service record—not a personal profile.
A random service ID, usage counts, broad app and device details, encrypted-message routing details, last-connected times, and short-lived shared data can be used to run and protect the online features you select.
- Not intendedRaw IP addresses, names or emails from normal use, your aviation-data keys, readable Remote Companion messages, histories, full logs, screenshots, recordings, or account profiles.
- RequestsInclude the public Support ID, report reference, approximate time, or reply email you supplied so a record can be located.
04 / CONTACT
Send privacy requests here.
Local Flight does not require an account or email address. Provide only the identifiers needed to locate the record you are asking about.
PRVPrivacy and diagnostics
SUPGeneral support