Searching needs no account and sets no cookies, and the only measurement is a cookieless page-view count. This page explains what that leaves — a search term, an IP address our infrastructure sees, whatever happens after you click through to book — and what the invite-only Jumbo account keeps.
To search: nothing. You can use every flight search, calendar and board without telling us anything about yourself.
Two things on the site do take personal details, and only if you use them: the our contact form (your email address and your message, section 09) and the invite-only Jumbo account (section 05).
When you look up a route, a price calendar or a destination board, your departure and destination codes and dates go to our own endpoints on this domain, which pass them to the Travelpayouts flight-data API and return prices.
Those requests describe a route, not a person. We cache the answer by route and month so the next visitor asking the same question is served instantly. That cache holds prices, not people, and it contains nothing that identifies you.
To start the FROM field at your nearest city, our server asks Travelpayouts' location service which city your IP address is in. Travelpayouts receives your IP address for that one lookup. We keep only the answer, a city, cached by area for a day so most visitors cause no lookup at all; it is not stored against you.
Searching sets no cookies, uses no local storage and carries no advertising or social scripts. The one measurement script, Cloudflare Web Analytics, sets no cookies either (section 06). There is nothing to consent to, which is why you have not been shown a cookie banner.
Two exceptions you should know about: signing in to a Jumbo account sets the cookies that keep you signed in (section 05), and the search results page is a different service on a different subdomain (section 07). The Cookie Policy lists both.
The Jumbo account at jumboradar.com/account is one sign-in for the Jumbo group. Today it is open only to people we invite, to try the hotels preview; it is not needed for anything else on this site.
If you have one, it keeps:
Codes and links are emailed from our own domain mailbox. The account is stored on Cloudflare (section 06). Signing in sets two cookies on jumboradar.com and its subdomains, listed in the Cookie Policy.
We use none of this for marketing and share it with no one. To delete your account, ask at our contact form.
The site runs on Cloudflare. Like any web host, Cloudflare processes the technical details of a request — IP address, browser user-agent, the URL requested, timestamps — to deliver pages, cache them and defend against attacks and abuse. That is standard infrastructure logging and it is not used by us to build any profile of you.
Pages also load Cloudflare Web Analytics, a small script from static.cloudflareinsights.com that counts page views and measures how fast pages load. It sets no cookies and keeps nothing in your browser, and Cloudflare says it does not fingerprint visitors or follow them across sites. What we see are totals: pages viewed, the site that sent the visit, country, device type, browser and operating system, and load times. We use them to know how many people the site serves and whether it is fast; never for advertising.
When you run a search, results are shown on flights.jumboradar.com. That page is a White Label search interface provided by Travelpayouts (Aviasales) and running on their technology. It is branded as JumboRadar but it is their service: it sets its own cookies — including a marker identifying JumboRadar as the referring site, and cookies remembering your recent searches and filters — and shows its own cookie notice.
Their handling of that data is governed by Travelpayouts' and Aviasales' own privacy policies rather than this one.
Choosing a fare takes you to the airline or online travel agency selling it. From that moment you are on their site, under their privacy policy, and anything you give them — name, passport details, payment card — goes to them, never through us.
What travels with you is an affiliate marker saying the visit came from JumboRadar. It identifies the referring site so a commission can be attributed. It does not identify you, and it tells us nothing about what you searched for or whether you booked beyond an aggregate count.
Writing to our contact form means we receive your email address and whatever you put in the message. We use it to answer you and nothing else: no mailing list, no marketing, no sharing or selling. We keep it no longer than we need to deal with what you raised.
So that the form cannot be used to flood us, each message also counts against a limit kept as a keyed hash of the sending IP address, not the address itself. Those counts expire after a day.
JumboRadar is a general travel research tool, not directed at children. The flight search collects no personal information from anyone, children included, and the Jumbo account is open only to people we invite.
Privacy law gives you rights to access, correct, delete and object to the use of your personal data. We hold little to which those rights could attach: no profile, no contact record unless you have written to us, and a Jumbo account only if you were invited to one.
If you want a copy of what we hold, a correction, or your messages or Jumbo account deleted, ask at our contact form and we will do it. For data held by the search partner or by an airline you booked with, the request has to go to them, because we cannot reach it.
If what we do with data changes, this page changes with it and the date at the top moves. Material changes will be described here rather than made quietly.
Questions about this policy: our contact form.
