1. Overview
This Privacy Policy explains what happens to your data when you use the FlightOps Hub desktop application (the "Software") and this website. In short: the Software itself doesn't collect or share any personal data, and purchases are handled by a third-party Merchant of Record.
2. Data the Software does not collect
FlightOps Hub runs entirely on your own PC. It reads and writes files only inside your own
Microsoft Flight Simulator installation (Community folder, exe.xml) and its own local
settings file under %LocalAppData%\FlightOpsHub. It does not phone home, does not run
analytics or telemetry, and does not collect or transmit your files, flight data, or personal
information to us or to any third party — with the specific exceptions listed below, all of which
are requests the app makes directly from your PC to the named third-party service, not to us.
- SimBrief: if you use the SimBrief integration, your entered SimBrief username is sent directly to SimBrief's own API from your PC to fetch your flight plan, per SimBrief's own privacy policy.
- VATSIM / IVAO: if enabled, live ATC data is fetched directly from VATSIM's/IVAO's public data feeds.
- GitHub: update checks query the public GitHub Releases API directly from your PC to see if a newer version exists.
- Airport weather (VATSIM METAR service): the standalone airport check and the Companion request the current METAR from VATSIM's public METAR service directly from your PC; only the airport's four-letter ICAO code is sent.
- Current weather for the Briefing tab (aviationweather.gov): if the Briefing ("Tahák") tab is on (it is by default), opening it requests the current METAR and TAF for the airports of your SimBrief plan from the U.S. National Weather Service's Aviation Weather Center (aviationweather.gov) directly from your PC, and falls back to VATSIM's public METAR service if that has none. Only the airports' four-letter ICAO codes are sent, together with an app identifier (
FlightOpsHub/version). Switch the tab off in Settings and nothing is requested. - Original SimBrief OFP (simbrief.com): if you open the original OFP in the Briefing tab, the route-map images in it are loaded from SimBrief's own image folder (www.simbrief.com/ofp/uads/) by your PC - or by your phone, if you open it in the Companion - only at that moment. Images from any other address are never loaded. Open as PDF opens SimBrief's PDF in your browser, on your click.
- Map tiles (OpenStreetMap): the Scenery map and the In flight map draw their background from OpenStreetMap's public tile servers (tile.openstreetmap.org). Your PC - or your phone, if you open the map in the Companion - requests the map tiles for the area you are looking at, so OpenStreetMap's servers see your IP address and which map area you view, per the OpenStreetMap Foundation's privacy policy. No flight data is part of these requests.
- License validation: see section 3 — this is the one case where data leaves your PC toward a service we work with.
Companion (optional, off by default). If you switch on the Companion, FlightOps Hub runs a small web server on your PC so a phone or tablet on your own network can show your flight plan, weather and ATC information. That data travels only between your PC and the paired device on your local network; it is not sent to us or to any third party, and the Companion has no cloud component and no account. Access requires a random pairing token carried in the QR code, which you can regenerate at any time. The connection uses plain, unencrypted HTTP, so it is intended for your own home network only. If you install the optional vPilot Tablet Bridge plugin, its page is served the same way, from your PC to your device on your local network.
In flight tab (optional, off by default). If you switch on the In flight tab in Settings, FlightOps Hub reads your aircraft's position, altitude, speed, heading, fuel and touchdown data from the simulator through SimConnect on your own PC, only while that tab is open, and only reads - nothing is written to the simulator. These readings are shown in the app and, if the Companion is on, on your paired phone or tablet over your local network. They are not stored beyond the running session, not sent to us and not sent to any third party.
3. License purchase & validation (Creem.io)
When you buy a license, the purchase and payment are handled entirely by our Merchant of Record, Creem.io. Creem collects and processes whatever billing information they require to complete the transaction (e.g. email address, payment method) under their own privacy policy — we do not see or store your payment details. When the Software validates your license key, the request goes through a small proxy we run (which never sees your billing details, only the license key and an anonymous per-install device identifier) and on to Creem's API to confirm the key is valid and record which device it's currently activated on — that's what makes the "one PC at a time, deactivate to move it" limit work. Deactivating a license from Settings clears that device record.
If you buy on SimMarket instead, SimMarket handles the purchase, payment and your billing data under their own privacy policy, and we do not see or store your payment details. The license key is validated in the same way as described above.
4. This website
This marketing website does not use cookies, analytics, or third-party trackers. It remembers a single preference — your chosen display language (English/Czech) — in your browser's local storage, which stays on your device and is never sent to us.
It also makes no requests to any third-party server while you read it: the webfonts are served from this site itself rather than from Google Fonts, so your IP address is not passed to anyone else simply by opening the page. The only outbound links are the ones you deliberately click (Creem checkout, GitHub, flightsim.to, Discord), each of which is then governed by that site's own privacy policy.
5. Data retention & your rights
Since the Software doesn't collect personal data itself, there is nothing for us to retain, export, or delete on your behalf beyond your license record and its device activation held by Creem — see Creem's own privacy policy for how to exercise rights (access, deletion, etc.) over that data. Contact support@opossumdev.com if you'd like help reaching Creem about your own record.
6. Changes to this policy
We may update this Privacy Policy from time to time; the "Last updated" date above will reflect the most recent revision.
7. Contact
Questions about this policy? Contact us at support@opossumdev.com.