Privacy & your data.

Updated 16 September 2026. Publisher: FlightWire. Contact: connect.flightwire@gmail.com.

Your flight records

Logbook stores flight records, notes, plans, screenshots, attachments and preferences on your Windows computer. The normal location is %LOCALAPPDATA%/FlightWire/Logbook; imported originals and user-selected folders can be elsewhere. Flight records are not included in the automatic usage report. Local files remain until you remove them or use the relevant retention/removal controls. Uninstalling or replacing the executable does not remove your career. Keep backups before removing data.

Optional cloud backups

Connecting OneDrive, Google Drive or Dropbox uses that provider's sign-in page. Logbook does not receive your password. It stores the resulting refresh token encrypted for your Windows account using Windows DPAPI. The access token is held in memory.

A backup sends a database snapshot and included flight evidence, plans, notes and attachments to the provider you selected. These files can contain flight identifiers, routes, personal notes and images. Account tokens, activation data and diagnostic logs are excluded from the backup inventory. Database-only backups do not include attachments. Custom/NAS backups write to the destination you select.

Logbook lists included and missing files so an incomplete backup is not reported as complete. Retention controls affect backups managed by Logbook; a provider may separately retain deleted files or earlier versions. Disconnecting stops Logbook's use of that saved connection but does not delete backups already stored with the provider. You can revoke access through the provider's account settings and remove stored backups there. Provider processing and international transfers are governed by your agreement with that provider.

Usage and version checks

At startup, Logbook may send its product version, build identifier, release channel, licensing compatibility mode, UTC event time and a randomly generated installation pseudonym to FlightWire's usage service. A successful usage report is limited to once per rolling 24 hours. It contains no flight records, routes, callsigns, registration numbers, notes, screenshots, email address or activation key. The pseudonym is separate from the licensing identity. The purpose is to understand application/version usage and support maintenance.

A separate version-policy request contains product/build/channel information and an existing policy identifier, if available. It is not a flight-data upload. These requests are non-blocking; service failure does not prevent the free features from working. Existing activations may independently refresh against the entitlement service under the retained key contract. Raw usage events older than 30 days are scheduled for removal when new events are processed. Pseudonymous installation summaries do not currently have an automatic deletion limit. Operational backup copies use a separate retention policy. Contact FlightWire to ask about retention or removal of your information.

External services you choose to use

Maps, weather, ATC/traffic overlays, airport information, aircraft images, SimBrief and other integrations contact their named providers. Requests can include information needed for the feature, such as a location, airport, aircraft identifier or SimBrief identifier. External services and network infrastructure receive connection information such as IP addresses and HTTP headers. API keys entered in Settings are protected for the current Windows account. Opening external links or signing in to embedded provider pages also subjects that session to the provider's privacy and cookie policies.

Support and diagnostics

Crash reports are written locally. Sending a bug report or contacting support sends the information and attachments included in that report or message. Review them before sending. Do not include passwords or activation keys. To ask about your data, request correction/removal of support information or raise a privacy concern, contact connect.flightwire@gmail.com. Information needed to investigate a request may be required to locate the relevant pseudonymous record.

Website

The FlightWire website is hosted through Cloudflare. The static pages do not run advertising trackers. Cloudflare Web Analytics may run a browser beacon to count browser-loaded visits and page views, allow bot traffic to be excluded from reporting, and measure page-load performance. Cloudflare describes this analytics service as cookie-free and says it does not collect or use visitors' personal data. A local theme preference can be saved in your browser. Cloudflare and linked third-party sites process connection information under their own policies. Email links open your chosen email application; the website does not receive your message unless you send it.