Privacy Policy
Updated:
How IGC Master handles data associated with flight analysis, website use and user accounts.
1. Accounts and communication
We store your name, email, language, optional club and country, verification and sign-in details, permissions and account status. Passwords are stored as one-way hashes. Contact messages and correspondence are stored as private support cases so we can answer your enquiry.
We use these data to provide the service you request and answer enquiries. Security, abuse prevention and administrative logging serve our legitimate interests. Newsletters require a separate subscription; you can withdraw consent through the contact page. Requesting a coupon does not subscribe you to a newsletter.
Data controller
2. IGC files and flight data
An uploaded file may contain pilot names, aircraft identifiers, timestamps, positions and altitudes. We process it and the supplied aircraft details to generate reports, previews and flight statistics. Account imports are linked to your private flight library; browser report access is session-controlled. Uploading does not itself publish the original file or report.
The OGN view and thermal map separately use external flight and competition sources, including OGN, SoaringSpot, SoaringWeb and public flight archives. These displays depend on the identifiers and data supplied by their sources. Contact us about corrections or removal of personal flight data.
3. Optional publication of a flight
Each upload offers a separate, initially unchecked choice to share a prepared report in Latest flights and to use its track as a website illustration. Consent is optional: declining it does not prevent your requested analysis. We record the consent version and UTC time. Names, aircraft and recorder identifiers are removed from the published asset; the original IGC is not publicly downloadable. A route and its times can nevertheless remain recognisable in combination with other information.
The active example library keeps the latest nine unique shared flights; three are designated as Compact demonstrations. Opening an example displays stored results, not a new analysis. Publication lasts until rotation out of this library or removal following a request. Existing browser sessions may retain an expiring snapshot.
You can withdraw this publication consent through Contact, without affecting the lawfulness of earlier processing. Give the report reference or enough flight details to locate it. Removing a private analysis does not itself withdraw a separately published asset. We can remove our publication but cannot recall copies already downloaded by others.
4. Thermal measurements and duplicate prevention
Uploaded flights can also contribute to the thermal collection independently of public-flight sharing. This processing supports our legitimate interest in improving the thermal map; you may object through Contact. The processing data retain measurement times, coordinates, heights and available quality fields, together with file hashes for duplicate prevention. They exclude pilot names, aircraft and recorder identifiers, declarations and comments.
Thermal results and duplicate-prevention hashes remain part of the collection while needed for this purpose; removing the browser report does not automatically remove them. A hash is not a guarantee of anonymity, and precise positions and times may be linkable to other data. Contact us about access, correction or erasure.
5. Google, Facebook and external providers
Google or Facebook sign-in supplies a provider identifier, name and permitted email address. We do not receive your provider password or persist access and refresh tokens. We do not request contacts or permission to post. Email and password sign-in is also available.
Technical providers support hosting and email delivery. Selected map layers can contact external providers such as OpenFreeMap, OpenStreetMap and Mapterhorn, which can receive your IP address and requested map area. Google and Meta may process data outside the EEA; their privacy notices describe locations and applicable safeguards.
6. Google sign-in and Google Drive imports
Google sign-in requests openid, email and profile permissions. We use the Google account identifier, name, email address and email verification status to create, link and authenticate your IGC Master account. We do not receive your Google password.
Drive import separately requests the https://www.googleapis.com/auth/drive.file permission. Google Picker lets you choose IGC, turnpoint and airspace files, including ZIP archives; we receive the selected file identifiers, filenames, available sizes and file contents. We download only the files you select, without scanning your whole Drive or editing or deleting its files. We do not request Gmail, contacts or calendar data.
Your browser downloads the selected files from Google and sends them to IGC Master for the analysis or account import you request. Imported files follow the same private storage, report generation and thermal processing described below as local uploads. A public example requires the separate per-flight publication consent. Google sign-in alone does not grant Drive access.
Drive access tokens stay temporarily in browser memory for the selection and import. We do not persist them in browser storage or our database, and do not store Google refresh tokens. Imported file copies and account details can remain after the Google connection is revoked; their retention and erasure are described below.
We protect transfers using HTTPS and restrict private files and account data through access controls. Hosting providers process the data to operate these features. We do not sell Google user data, use it for advertising or train general-purpose AI models with it. Human access to Google data is limited to your explicit support permission, necessary security investigations or legal obligations. Our use and transfer of Google API data follow the Google API Services User Data Policy, including its Limited Use requirements.
7. Payments
Stripe processes card payments through Stripe Checkout. We send Stripe the selected packages, amounts, currency and an internal payment reference. We store the purchased packages, amounts, currency, order and transaction identifiers, status, coupon discounts and access or credit validity dates. Card numbers and security codes are entered on Stripe’s payment page and do not reach IGC Master.
Stripe — Privacy Policy8. Cookies and browser storage
Session and security cookies support sign-in, protected forms and report access. Your browser can retain theme, unit and map preferences. Clearing storage can end your session and remove preferences.
We use Google Analytics 4 to understand website usage and improve the service. Google receives usage data such as page views, referring pages, session information, browser and device details and approximate location. Analytics uses cookies, including _ga and _ga_<id>, to distinguish visitors and sessions. You can manage cookies in your browser and use Google’s Analytics opt-out browser add-on in supported browsers.
Google Analytics loads only after you accept analytics cookies. Rejecting them does not restrict access to the website. We remember your choice in this browser for 180 days. You can change it or withdraw consent at any time using Cookie settings in the footer or on this page. Withdrawal stops further analytics collection and removes our Analytics cookies; it does not erase data already collected by Google.
9. Retention and access
Account file imports, report results and metadata are retained for your flight library and requested analyses. Removing a flight from the list removes its account link; raw IGC files are not automatically erased by this action or by report-session expiry. Request physical erasure through Contact. Unlinked originals remain in private storage until administrative removal. Report sessions expire independently. Coupon and payment records retain the data needed to administer credits, access periods and transactions.
Account and correspondence records are retained while needed to operate the account, resolve the request, administer the promotion or address necessary legal claims. Suspension is not deletion; imported legacy accounts can also request erasure. Technical mail logs are kept for 14 days. Permissions restrict access to stored data.
10. Data deletion and social account disconnection
Request deletion of your account and data received through Google/Facebook using the contact page or the email above. Include your account email and the scope of your request. We may need to verify your identity; never send your password or login tokens.
Disconnect Google or Facebook sign-in in Profile → Connected services. You can also revoke IGC Master access in your Google Account connections or Facebook app settings. Revoking access stops future authorised access but does not erase files already imported or delete your IGC Master account. Request erasure separately; we will explain any legal requirement to retain particular records.
Request data deletion Contact11. Your privacy rights
Subject to applicable conditions, you can request access, a copy, correction, erasure, restriction and portability, object to legitimate-interest processing and withdraw consent. We normally respond within one month. You can complain to NAIH or your competent data protection authority. Flight analysis does not make automated decisions about you with legal effects.
Data protection authority — NAIH