Tierleap

Privacy

Version 4 · Sat, 14 Nov 2026

This page says what Tierleap collects about you, why, how long it keeps it and what you can do about it. It is written from what the product does and changes when the product does.

Tierleap shows no advertisements, runs no analytics or tracking scripts and does not sell personal data. Some booking links are partner links and are marked as such.

Who runs Tierleap

Tierleap is independent and not affiliated with Singapore Airlines, Thai Airways, Accor or any loyalty program. Program names belong to their owners. Pages and articles are published under the name Tierleap.

Tierleap's servers are in Singapore, rented from the hosting company OVH. Every request reaches them through Cloudflare, which shields the site and sees your IP address on the way.

About Tierleap

If you only read pages

Most of Tierleap can be read without an account. Then it learns only what any web server learns from a request.

  • The web server keeps an access log: your IP address, the time, the page you asked for and your browser's name. Each log is kept for about five weeks.
  • To stop abuse, Tierleap counts requests per IP address. It stores a scrambled copy of the address with the count, never the address itself.
  • Your browser keeps a few things on your device: the Day or Night theme, the display currency, the flights you opened, values you typed into search forms and calculators, how long each kind of request took, whether this browser's display currency has been matched with an account and, once you have an account, your setup progress. An unsent feedback draft and the page to return to after signing in are kept until you close the tab. All of these are stored in your browser, not on Tierleap's servers, and clearing the site's data in your browser removes them.
  • The app also keeps copies of its own files on your device, and of recent answers for up to six hours, so that it opens faster. Answers about your account, your watches, your alerts and your messages are never kept this way.
  • A page with a map loads its map tiles from OpenFreeMap, and a page with hotel photos loads them from Accor's image server. Each sees your IP address when it sends the picture. Tierleap tells your browser not to say which page asked.
  • When you follow a partner booking link, Tierleap records the click: a scrambled copy of your IP address and of your browser's name, the page you came from and where the link led. The record is not tied to an account. The partner's own privacy policy applies from there.
  • Tierleap sets no cookie until you sign in. Cloudflare may set one of its own when it checks that a visitor is a real browser.

If you create an account

An account needs a handle and a display name. Tierleap does not ask for an email address, a phone number or a password.

An account holds:

  • Ways to sign in: the public half of each passkey with the nickname you gave it; a one-way hash of your recovery number; a one-way hash of a client token, if you made one; the secret your authenticator app uses, if you turned on two-step sign-in; your Telegram user id, if you linked Telegram.
  • Sessions: for each sign-in, Tierleap keeps when it started, when it was last used, and the IP address and browser it started from. Account, Security lists your sessions and lets you end them.
  • One cookie that keeps you signed in for up to 30 days. Page scripts cannot read it.
  • What you save: your home airport, your loyalty programs and status (tier, nights, points and expiry date), the flights and routes you watch, the hotel plans you save (the dates, nights, countries and limits you chose, and the last total), your display currency, the country you state if you state one, and your notification settings.
  • Accor details, only if you add them: your ALL membership number and a corporate code, both stored encrypted, and a rate code. After saving, Tierleap shows only the last four characters of the number.
  • Alerts: every alert Tierleap sent to your Inbox. If you turn on push alerts on a device, Tierleap also stores that browser's push address with the browser's name, its platform and a label for the device.
  • Messages you send through Feedback: your words, the page you were on and the details the form lists before you send. Tierleap's operators read them to answer you.
  • A new message that looks automated is held for an operator to read before anyone is notified. To notice the same words sent again, Tierleap keeps a scrambled copy of a new message's words for one day.
  • Tierleap marks an account as a sender of spam when an operator says so or when its sign-up looked automated. A marked account's later messages are held in the same way. When an operator marks an account, Tierleap keeps scrambled copies of the IP addresses it signed in from for 30 days, and a new account that signs up or writes from one of those networks is treated the same.
  • Starting a Telegram sign-in records the IP address and browser it came from.

Tierleap's operators can look up an account to answer a message or to stop abuse.

Tierleap does not ask for your location, except for the optional checks described under Passenger reports.

Passenger reports

Reporting is being introduced in stages. Until it is switched on for your account you will not see it, and nothing in this section applies to you.

A member on a flight can tell Tierleap when boarding starts, when the doors close, when the aircraft pushes back, when it parks and when the first bags arrive, and whether boarding was by jet bridge, bus or stairs. A hotel guest can answer a few questions about a stay. Reporting is always your choice.

Contribution terms

What a report holds

  • The flight or the stay, the event or the answer, the time on your phone when you tapped, the time Tierleap received it, and the difference between your phone's clock and Tierleap's.
  • A random key that your browser makes the first time you report. It shows that two reports came from one browser, so that two accounts on one browser cannot confirm each other. It is a random number, not a description of your device.
  • A random number made for each tap, so that a report sent twice is counted once, and the version of the notice you agreed to.
  • No photo, no sound, no free text and no seat number.

Location checks

Location checks are optional. Tierleap asks the first time you report, and you can report without them.

If you allow them, each report asks your phone for its position once. The position travels with the report through Cloudflare to Tierleap's server, which compares it with the airport or the hotel and discards it in the same step. The position is never written to Tierleap's database, its logs or its backups.

If your phone is offline, the report and its position wait on the phone until it is online again. Then they are sent and removed from the phone. A position that has waited three days is dropped from the phone unsent; the report is still sent, without it.

From each check Tierleap keeps:

  • The result: inside, near, outside or unknown.
  • How far the position was from the airport or the hotel, as a band such as 1.5 to 6 km, and how precise your phone said the position was, also as a band.
  • The square of about 5 km by 5 km that the position fell in.
  • A scrambled code for the square of about 100 m by 100 m that the position fell in. The key that makes the code changes every day, is kept outside the database and is destroyed after 4 days. The code lets Tierleap notice different accounts reporting from the same spot on the same day. Once the key is destroyed, nobody can tell which square a code stands for.

The 5 km square and the code are blanked 30 days after the report. The result and the two bands stay with the report.

A report without a location check is still recorded. It does not count as proof that you were at the airport or the hotel.

What Tierleap does with reports

Tierleap collects reports to improve its forecasts and to train its forecast models. For now it only stores and checks them: it compares your report with other passengers' reports and with flight data, and keeps a count of how often your reports matched.

At a later stage, times that hold up will feed the forecasts and the models, and Tierleap will show them to other people as passenger reports, for example “Pushed back 10:42, reported by 3 passengers”. Nobody is shown who reported or where they were.

How long reports are kept

A report stays linked to your account for as long as the account exists. A confirmed time worked out from several reports holds no link to anyone and is kept.

Stopping and withdrawing

  • Stop reporting whenever you like: no report is ever required.
  • Turn location checks off in Account. Reports after that carry no location check. Each time you allow or turn off location checks, Tierleap records the choice with the time, your IP address and your browser, as proof of what you chose.
  • Delete your account to remove the link between you and your reports. The reports stay as times with no person attached.
  • To have your reports unlinked without deleting your account, ask through Feedback.

Passenger reports are for people aged 18 or older.

Who else receives data

  • OVH hosts the servers, and Cloudflare carries every request to them.
  • The sign-up page can load a check from Cloudflare that tells a person from a robot. When it does, Cloudflare reads details of your browser and sees your IP address.
  • Your browser maker's push service (Apple, Google or Mozilla) carries each push alert to your device when you turned push alerts on. The alert is encrypted, so the service cannot read it.
  • Accor receives your membership number and codes when Tierleap prices a hotel plan at your own rates, and only then.
  • Telegram delivers the sign-in message when you sign in with Telegram.
  • OpenFreeMap and Accor's image server see your IP address when a page loads a map or a photo.
  • Flight and fare data providers receive flight numbers, airports and dates. They are never told who asked.
  • A storage provider holds the encrypted backups of the database.

Tierleap gives personal data to nobody else, unless a law requires it.

How long Tierleap keeps things

  • Web server logs: about five weeks.
  • Your account and everything saved in it: until the account is deleted.
  • Passenger reports: as the section above says.
  • Backups: a copy of the database is made every night and kept on a rolling schedule for up to six months: on the server, encrypted with a storage provider outside it and, for 14 days, on a private server that Tierleap's operator runs. What a deleted account held stays in those copies until they age out.

Your choices

  • See and change what you saved: Account.
  • End a session or remove a way to sign in: Account, Security.
  • Turn alerts off: Account, Notifications. Turn push alerts off on a device: the Inbox on that device.
  • Delete your account: Account, Your data. The account is erased 30 days after you ask. What stays: the record of the request (its date, the reason you gave and the IP address it came from), your Feedback threads with their words blanked, your passenger reports as times with no person attached, and the backup copies until they age out.
  • Get a copy of your data: a download is not available yet. Ask through Feedback and choose My account.
  • Ask a question or complain: use Feedback, or the line “Something wrong on this page? Tell us.” at the foot of a page. Sending needs an account, because Tierleap replies to the account. Replies arrive in your messages and in your Inbox.

Changes to this page

Every edit changes the version and the date at the top of this page.