Privacy Policy

Identity and account data

• Public username. You choose a unique Jetstream username. It is the public pilot identity shown to other pilots on surfaces such as the shared in-flight map and global activity leaderboard. Usernames are case-insensitively unique.
• No legal-name collection. Jetstream does not ask for, derive, or store your first name, last name, full name, or a name from your Google/provider profile. You do not need to use your real name as your username, and you should not put sensitive personal information in it.
• Authentication. Firebase Authentication stores the stable account identifier, email address, authentication-provider identifier, and session/security data needed to sign you in. Password accounts must verify their email address. Google sign-in requests OpenID identity and email access; Jetstream does not request Google's profile scope or copy a provider profile name or photo.

The username-only identity migration removes retired first-name, last-name, full-name, provider-name, provider-photo, display-name, and authentication-display-name fields from recognized local and cloud records as those records are opened, migrated, or rewritten.

Career, profile, and product data

• Local career data. Your public username, pilot profile, routes, schedules, flight history, career progress, settings, and entitlements are stored locally under your authenticated account on the Windows device.
• Cloud career backup. To support restore on another device, Jetstream backs up your public username, career rank, XP, balance, entitlements, completed flights, and flight hours to Firebase under your exact authenticated account ID. A backup is accepted only when its embedded account ID matches the signed-in account.
• Local profile photo. If you choose a profile photo, Jetstream copies it into local app data. Other users cannot see it, and Jetstream does not upload it to Firebase or include it in cloud career backup.
• Home country. You choose a home country during onboarding. Jetstream stores the two-letter country code in the server-owned pilot profile and local career cache. The country can affect airline application odds and can currently be changed only once every 30 days.
• Product analytics. Jetstream sends three bounded, authenticated product signals: one activity marker per account per app day, a one-time marker when the intro tour is completed, and a counter when an airline has no routes to show. Product Insights does not receive page views, free-form analytics properties, simulator position, or identity fields.
• Feedback. The feedback action opens Jetstream's Discord. Jetstream does not collect an in-app feedback message in Firebase. Anything you post in Discord is handled under Discord's terms and channel practices.

Live map and public activity

While you fly an active leg, Jetstream sends one temporary live marker to a fixed Firebase presence slot. Other signed-in pilots can see your public username, callsign, aircraft, rank, member number, departure, arrival, and current in-sim position and heading.

The marker is refreshed at most once per minute. About once per minute, the app requests a compact snapshot from a separate authenticated live-map function. That function is capped at one instance, shares one recent query with a maximum of 500 markers for a minute, and excludes markers older than five minutes.

Firebase uses the stable account ID only as the private ownership path. The live-map function replaces it with a session-scoped marker ID, does not return the account ID, and does not store a flight-position history. Normal completion or cancellation removes the marker; after an app, simulator, or network crash, the backend stops returning it once the last refresh is more than five minutes old.

The global activity leaderboard shows each ranked pilot's public username, qualified flight count, and server-timed activity. It does not expose Firebase account IDs, grades, XP, money, reputation, or simulator telemetry, and it has no public-alpha prizes.

Flight grading and anti-cheat telemetry

During a career flight, Jetstream samples simulator measurements about once per second. These can include time, position, altitude, speed, vertical speed, heading, on-ground state, pitch, bank, G force, pause/slew/time-acceleration warnings, aircraft title, simulator generation, aircraft compatibility provider, and basic landing/configuration states.

The app keeps a bounded local retry journal, saves it periodically and around important flight-phase, safety, and touchdown events, and sends compact batches at those events or otherwise on a five-minute heartbeat. The backend uses the samples to check takeoff and landing, route coverage or diversion, implausible movement, aircraft identity, and the resulting grade and reward instead of accepting a result claimed by the desktop app.

While a flight is active, the backend converts each raw batch into one bounded running summary and discards the raw batch. That active summary may retain a bounded, downsampled trail of up to 720 coordinate points for an administrator-only development preview; it is not included in the normal public live-map response. The backend deletes the active summary and trail after settlement or abandonment. The compact final receipt keeps the resulting grade and reward facts with limited evidence such as active time, route coverage, diversion status, touchdown summary, detected aircraft title, simulator generation, and compatibility provider—not the full position history.

Connected services and external requests

• SimBrief. If connected, Jetstream sends the Pilot ID or username you entered to SimBrief to fetch the latest operational flight plan. The selected ID and relevant plan data are kept locally and are not included in cloud career backup.
• Weather and airport images. Jetstream sends airport codes to the U.S. NOAA Aviation Weather API for weather and runway information, and airport codes or names to Wikidata, Wikipedia, and Wikimedia Commons to find and cache credited airport images.
• Map tiles. The in-app map loads tiles from Esri and CARTO, using OpenStreetMap-derived data where credited. Those providers receive normal request information such as IP address, user agent, tile coordinates, and request time. Tile coordinates reveal the approximate map area being viewed, but Jetstream does not put the account ID, username, or aircraft-marker coordinates into the tile request.
• External actions. Discord, SimBrief, and flightsim.to searches open in the default browser. The destination receives the requested URL or query and normal browser request information under its own policy.

Payments

Stripe Checkout processes card details. Jetstream does not store card numbers or payment credentials. Jetstream receives payment status and product metadata needed to unlock purchased items and stores non-card fulfillment records such as checkout ID, purchased product keys, amount, currency, and account ID.

Local files and security

Jetstream stores local app data under your Windows user profile, including career saves and recovery copies, route data, settings, profile photos, logs, cached assets, and a local SimBrief identifier where configured. Authentication sessions are protected with Windows user-scope data protection where supported.

Jetstream uses Firebase Authentication, email verification for password accounts, server-owned username records, backend-only Stripe secrets, Firebase security rules, Windows-protected authentication sessions, and local save integrity checks. No system is perfectly secure, especially local desktop saves, but the alpha is designed to avoid shipping payment secrets in the desktop app and to prevent clients from claiming another pilot's username.

How we use and share data

We use data to run the app, show your chosen public identity, restore career progress and paid purchases, recover interrupted purchases, settle flights, prevent abuse, troubleshoot bugs, improve product quality, and ship route and catalog updates with app releases.

We use Firebase/Google Cloud for authentication, database, cloud career backup, and backend hosting; Stripe for payments; Discord for feedback; SimBrief for optional flight-plan features; NOAA Aviation Weather for weather and runway data; and Wikimedia services for airport images. Public-alpha route/catalog data ships inside the app release, and Firebase Storage is closed to clients. We do not sell personal data.

Retention

Local career data, local SimBrief identifiers, and local profile photos remain on the device until removed. Cloud career backup is retained for restore. Username ownership records, authoritative flight receipts, payment fulfillment records, and historical product telemetry collected by earlier builds may be retained for support, fraud prevention, dispute handling, identity integrity, and product operations.

The local flight retry journal is removed after confirmed settlement or abandonment. Firebase keeps one replaceable live-presence slot per account, and stale markers are ignored after five minutes. Discord controls retention of messages posted there.

Your choices

You can change your public username in Settings subject to current product rules, change your home country once every 30 days, sign out, and remove the local profile photo or SimBrief identifier. The live marker is shared only while you fly an active leg.

To request deletion of your account and associated cloud data—including public profile, career backup, authoritative flight records, and historical telemetry—use the Discord feedback/support action in Jetstream.