Last updated: September 7, 2026
Depending on the features you use, FlightPack handles:
Every recorded flight is stored locally in FlightPack's SQLite database on your PC. Creating a Free account does not automatically upload full flights. A Free account unlocks unlimited local recording and lets you deliberately publish individual lightweight flight pages.
With an active Pro entitlement, completed private flights are automatically archived to FlightPack's cloud service for the browser logbook and restore. A private archive can contain the flight record, route and coordinates, detailed telemetry, events, aircraft and tail number, notes, scores, callouts, and flight-plan revisions. Cloud traffic is transmitted over HTTPS, and cloud account data is stored with infrastructure providers in the United States.
Publishing is an explicit action. FlightPack uploads a smaller public artifact that can include your username, a reduced route trace, aircraft and tail number, scores, events, and flight-plan details. It does not upload the raw simulator channel stream for a Free published page. Anyone with the link may view, copy, or reshare public information. You can unpublish a flight to remove the hosted artifact, although copies made by others cannot be recalled.
If Pro ends, new flights remain local and private cloud restore stops. Existing private archives remain browser-readable for 30 days after the paid period ends. After that grace period, FlightPack removes those private archives from active cloud storage. Flights stored on your PC are unaffected. Public flight pages remain available until you unpublish them or delete your account.
We use PostHog for consent-gated product analytics. If you opt in from desktop settings, FlightPack sends limited usage events with a random install ID. These events exclude routes, coordinates, aircraft identity, scores, notes, and raw flight telemetry. You can opt out and clear the analytics identifier from Settings.
Builds configured with PostHog may send crash and reliability diagnostics. Reports can include stack traces, app state, operation names, and local record identifiers. They are not intended to contain authentication tokens or raw flight telemetry.
We use service providers for cloud hosting, authentication and transactional email, payment processing, product analytics, and crash reporting. They process data only to provide those services under their own security and privacy obligations. We do not sell personal information or flight data.
We may use de-identified, aggregated statistics such as flight counts, popular airports, and score distributions to operate and improve FlightPack. We do not use an identifiable private flight in marketing without additional permission.
Account deletion permanently removes account-linked cloud flights, published artifacts, authentication records, and related data from active systems, subject to limited billing, fraud-prevention, security, backup, or legal records we must retain. It does not erase FlightPack's local database or other files on your devices.
Applicable privacy laws may provide additional rights. We may verify your identity before completing a request.
Account and account-linked operational data are kept while your account is active and removed from active systems when you delete it. Linked waitlist and pending verification records are removed at the same time. Feedback is kept while needed to respond and improve the service. Payment providers may retain billing and fraud-prevention records under their own legal obligations. Security logs, analytics, crash reports, and backups expire under the configured retention schedules of the systems that process them; deleted data can remain in encrypted backups until normal backup rotation completes.
We may update this policy as FlightPack or applicable law changes. We will post the new version, revise the date above, and provide reasonable notice of material changes.
Questions or privacy requests can be sent to support@flightpack.app.