Privacy policy

Who runs the site

I run the site and the Telegram channel. My name is Shlomo, and I am a private individual in Israel. For any privacy question or request: contact@pricelog.fyi.

What this site collects

The site itself collects nothing. There is no analytics of mine, no tracking pixel, no ad network, no account and no sign-in.

Most pages — the flight pages, the destination pages and documents like this one — have no JavaScript of any kind and set no cookies. No font, script, image or stylesheet on them loads from anyone else's server, so no third party learns that you visited them. Four pages are different: the home page and the search page, in English and in Hebrew, which carry a flight search engine. The next section is about them.

The search engine on the search pages and the home page

The search form and the search results on these pages are a search engine provided by Travelpayouts, the affiliate network I work through. For it to work, your browser loads its code from Travelpayouts' servers and talks to them directly.

The engine does not load on its own. Each of these pages has a small script of mine that first shows an explanation and a "Turn on the search engine" button, and only a click on it loads the engine. The script saves the click in your browser, under the name pricelog-search, so that the engine loads on its own on your next visit, in either language. That is all it saves, and it is not sent anywhere. To be asked again, clear this site's data in your browser. The script also adds the page's language to the address for a moment, so the engine opens in the same language as the page; the engine removes it once read.

Both search pages, in English and in Hebrew, have one more small script of mine, which shows the numbers PriceLog collected for the destination you chose next to the search. It reads the page address and a file of numbers from this site only. It saves nothing in your browser, sends nothing anywhere, and works without turning on the engine.

Once you turn on the engine, and on these pages only:

• Your browser loads JavaScript from tpwgts.com and contacts servers at apistp.com and avsplow.com. They receive your IP address and browser details, like any site you contact.
• What you choose in the form — origin, destination, dates and number of passengers — is sent to them to search for prices. These searches do not reach me.
• The engine saves cookies and local data in your browser: the language and currency you chose, a visit ID, and IDs for the measurement tool the provider uses to count use of the engine (Snowplow). I do not see that tool's data.
• The engine loads fonts from Google Fonts, so Google also receives your IP address and browser details.
• Clicking a result goes, like the booking buttons elsewhere on the site, through Travelpayouts to the booking site. That is covered under "What happens when you click a booking link".

If you do not want any of this, you can use the rest of the site, which has no such code: the flights found page and the destination pages.

What the host necessarily sees

The site is hosted on Cloudflare Pages. To serve you a page at all, Cloudflare receives your IP address, the page you requested, your browser's user agent and the time of the request, and records them in server logs used for serving, abuse prevention and aggregate traffic counts. In Cloudflare's dashboard I see only aggregate numbers, such as how many requests arrived and from which countries. I do not see who you are, and I do not try to identify individual visitors. Cloudflare processes this data as my hosting provider, under its own terms.

What happens when you click a booking link

This is the part that actually matters, so it is not hidden at the bottom.

On a flight's page, the booking button is an affiliate link that leads to a search for that flight. Every result in the search engine is such a link too. (The link to other dates below that button leads to this site's search page, covered in the previous section.) When you click an affiliate link, your browser first goes through Travelpayouts, the affiliate network I work through, and from there to a flight search and booking site. On the way:

• Travelpayouts and the booking site receive your IP address and browser details, like any site you visit.
• The button on a flight's page carries an ID of the flight — for example 20261005_ROM_RT — so I know which link was clicked. The ID describes the flight, not you.
• The booking site sets a cookie in your browser, usually for 30 days, to credit me with a commission if you book.

What I get back is an aggregate report: how many clicks and bookings each such ID had, and the booking amounts. I do not get your name, your contact details or your payment details. Once you leave this site, the privacy policies of Travelpayouts and of the booking site apply, not this one.

The Telegram channel

Joining the channel is between you and Telegram, under Telegram's privacy policy. As the channel owner I see the number of subscribers, and Telegram also shows channel owners a list of subscribers by their display name. I do not get your phone number, and I do not keep, copy or use that list for any purpose.

If you email me

Mail sent to contact@pricelog.fyi is forwarded by Cloudflare Email Routing to a Gmail inbox, so your message and address are handled by Cloudflare and Google in transit and in storage. I use the correspondence only to answer you, and keep it only as long as that requires.

Information processed outside Israel

Cloudflare, Google, Travelpayouts, the booking site and Telegram are foreign companies, and the information described above may be processed on their servers outside Israel.

Your rights

Under Israel's Protection of Privacy Law, you may review the information held about you, and ask to correct or delete it. The site itself keeps no records about you, so in practice this concerns email correspondence. Write to the address above, and I will answer within 30 days.

If you believe your information was not handled properly, you may also contact the Privacy Protection Authority at the Ministry of Justice.

Changes

If the site ever starts collecting anything, such as analytics, I will write it here before it happens and update the date below. I do not intend to expand this document quietly.

Last updated: 15 Oct 2026