Privacy policy
No account, no name, no email: you never have to give us a personal detail to search and compare. The site does measure how it is used, and this is exactly what it measures.
What is measured while you browse
A small script on the site records what was shown and what was clicked on the way to a supplier, and posts it in batches to our server (/api/events, a Cloudflare D1 database). The events are a closed list: page views, searches, results shown, a flight, hotel or deal card seen or clicked, a click out to a supplier, price-alert actions, use of the trip planner, and exposure to an experiment.
Each event stores: a random browser id, a visit id, the page and its type, the page language, the device class (phone or desktop — derived on the server; the user-agent string itself is not stored), origin and destination codes, the supplier name, the price shown and its currency, how fresh that price was, the card's position on the page, the public partner id carried by the link, the utm_source/utm_medium/utm_campaign parameters if you arrived from a campaign, and the referring site's host name (never the full address).
Not stored: IP address, the user-agent string, name, email, phone, anything you typed, or the full address of the page you came from.
The random id is a value your browser creates for itself (bk_anon_v1) so a returning visit can be counted without an account. It identifies a browser, not a person. If your browser sends Do Not Track, it is never created.
How long: these events have no automatic deletion today. They are kept until we delete them; we do not claim a retention period the code does not enforce.
A few key clicks (a search, a booking click, a click out to a supplier) are also sent to an older measurement channel (/api/track, Cloudflare KV) with a reduced set of fields: event name, destination, supplier, price band, position, device class and language. Those are deleted automatically after 90 days.
When you use a feature
- Price alert: the route, dates or month, number of travellers, budget and currency are stored with a hash of a random token your browser creates (
bk_owner_v1). The token itself is not stored by us. Deleting the alert deletes it and its check history. Alerts are shown on the site only — we send no email or message. - Saved search: the route, dates and price threshold are stored with no personal identifier and deleted automatically after 180 days.
- Direct hotel booking (where the booking page offers it): the name, email and phone of the booker and guests that you enter pass through our server to LiteAPI, the booking provider, to make the reservation. Card details are entered directly in LiteAPI's payment form and never pass through us. Booking status updates sent by LiteAPI (booking id and status) are kept for 30 days.
When you search
To fetch prices, our server sends suppliers the search itself — origin, destination, dates and number of travellers — and nothing personal. Supplier performance figures (response time, number of results) are kept for 14 days, with nothing about you in them.
To protect the site from overload, your IP address is used to count requests in server memory for a short time. It is not written to any database.
Partner links and leaving for a supplier
A link to a supplier carries our partner id (for example a Travelpayouts marker, an Agoda cid, or a campaign code) and the search details — route, dates and travellers — so the supplier shows the right offer and credits the commission. Once you are on the supplier's site, its own privacy policy applies, including any cookies it sets.
Third-party services loaded by the site
- Cloudflare hosts the site and injects a cookieless analytics script (Cloudflare Web Analytics) that counts page views and performance. Like any host, Cloudflare processes IP addresses and request data under its own privacy policy.
- Google Fonts — the fonts load from Google's servers, so your browser contacts them.
Cookies and browser storage
The site itself sets no cookies. It does keep values in your browser's own storage (localStorage/sessionStorage). They stay with you and can be cleared at any time in your browser settings:
- Identifiers:
bk_anon_v1 (localStorage),bk_sess_v1, janet_session (sessionStorage),bk_owner_v1 (localStorage)— the random id, the visit id and the price-alert token. - Preferences and things you saved:
janet_i18n_pref,bookallo.origin.v1,janet_hotel_prefs_v1,janet_recent_searches,janet_saved_searches,janet_hotel_searches,janet_favorites,bk_saved_plans_v1,bk_visit_v1,janet_wa_dismissed,bk_utm_v1,bk_visit_rotated,bk_exp_seen_*,janet:hotel-selection— language and currency, home airport, hotel preferences, recent and saved searches, favourites and saved plans. - Kept in the browser only:
janet_analytics,janet_click_log— a local log of views and clicks that is never sent anywhere.
What you can do
- Clear the site's storage in your browser — that detaches you from any earlier id.
- Turn on Do Not Track — the random id will not be created.
- Delete a price alert from the alerts page.
- Ask us anything about this — see contact.
We do not sell data and do not use it for targeted advertising. If anything here changes, this page and the date above change with it.