The privacy policy for terragear.org, which is short because the site is: no accounts, no shop, no newsletter, no comments. What follows is the whole of it.
What this site collects
Nothing you type. There is nothing to type into: no forms, no sign-ups, no comment boxes, no email field.
No advertising and no social scripts. One third-party resource is requested: a measurement script from Cloudflare, which this site’s content security policy refuses to execute, so it never runs and nothing is reported. Apart from that request the pages load only from this domain.
The web server records requests, as web servers do: IP address, timestamp, the URL, and the browser’s user-agent string. That is operational logging: keeping the site up and noticing abuse. It is not used to build a profile.
Cookies
Two cookies, both set by Google Analytics: _ga and a second whose name begins _ga_. They hold a random identifier so that a returning visitor is counted as one person rather than two. Both expire after two years.
Analytics records which pages were opened, roughly where the visitor was — country and city, worked out from the IP address, which Google then discards rather than stores — which browser and device were used, and which site the visit arrived from. It does not record a name, an address, or anything typed here.
That data goes to Google and is held under Google’s terms, not ours. If you would rather not be counted, most browsers can block these cookies, and Google publishes an opt-out extension for the purpose.
One further value sits in local storage rather than a cookie: the notice at the foot of the page writes it when you close the notice, so that the notice does not come back.
Links to other sites
Outbound links go to the FlightGear wiki, the project’s GitLab repository, the GitHub mirror, Docker Hub, the data sources named in the data guide, and Creative Commons for the content licence. Those are separate services with their own practices, and this page does not cover them.
Contact
Questions about this site, including anything on this page, belong on the project issue tracker. There is also a security.txt for reports that should not be public.