Privacy
What the site stores, why, and what it does not.
Ratings
A rating records the carrier, route, date, optional flight number and aircraft, the star score, the landing description, and whether you reported applause or turbulence. Ratings are public on the carrier, airport and route pages and on the rating’s own link. A rating never shows your name or email. It is labelled either “Signed in” or with a guest code.
Signing in
Signing in uses Google. The site stores your Google account identifier, name, email address and profile picture link. The email address is used to recognise your account and, if you turn it on, to send the follow digest. Signing in is not needed to rate a landing.
Guest codes and cookies
If you rate without an account, the site sets a cookie named fl_guest holding a random 8-character code, kept for one year. The code is saved with your ratings so ratings from one browser can be grouped. It is not linked to a name and does not identify you. Signing in sets the cookies the sign-in system needs to keep you signed in. The site sets no advertising cookies.
Analytics
The site uses Google Analytics to count which pages are used. It asks first. If you accept, Google sets analytics cookies and receives the pages you visit, your approximate location and your device and browser type. If you decline, no analytics cookie is set and the choice is kept in your browser. Advertising storage is never granted. You can change the choice at any time with “Analytics choice” in the page footer.
Stored in your browser
Your browser keeps the last few airline and route combinations you rated, so you can rate them again in one tap, and a marker for flights you opened from an imported log. A half-finished rating is held for the length of a Google sign-in and then removed. This data stays on your device.
Counters
The site counts steps such as “rating published” as a daily total. The count holds no cookie, IP address, page or user detail, so it cannot be traced to a person.
Flight lookup
The optional flight lookup sends a flight number and a date to an aviation data provider. Results are stored so the same lookup is not repeated. No account details are sent.
Imports
A flight-log file you load on the import page is read in your browser and is not uploaded.
Third parties
Carrier logos are loaded from images.kiwi.com, so that host receives your IP address and the logo requested when a page shows a carrier. Google Analytics is described above. Pages are served by Vercel and data is held in a hosted PostgreSQL database.
Follows and the digest
Follows are stored against your account and shown on the My landings page. The monthly digest is off unless you turn it on there, and you can turn it off at any time.