Cookie Policy
Which cookies and similar technologies the Rahlio website, the agents’ portal and the app use, why, and how to choose. In short: cookies for your language, your currency and staying signed in; maps by Google only if you allow it; analytics by Google and advertising by Google and Meta only if you allow them in the European Union, the European Economic Area, the United Kingdom and Switzerland, on by default elsewhere, and refusable everywhere; none of them on the payment page; our own record of how the website and the app are used, which sets no cookie and goes to no one else; in the app, install and link measurement by AppsFlyer and, while you allow it, measurement of activity in the app, with an iPhone’s advertising identifier only if you allow tracking.
Last updated:
Operator details
- Trading name
- Rahlio
- Legal name
- Rahlio, Inc.
- File number
- 10824133
- Contact
- support@rahlio.com
Rahlio is operated by Rahlio, Inc. (Delaware file no. 10824133)
On this page
1. What cookies are
1.1. A cookie is a small text file that a website stores in your browser. Similar technologies include browser storage (local storage and session storage) and, in an app, files and identifiers kept on the device. In this policy, "cookies" means all of them.
2. Our approach
2.1. We use what the Service needs in order to work and to remember choices you made. Beyond that there are three categories: maps drawn by Google, analytics by Google Analytics, and advertising by Google and Meta. Maps by Google stay off until you allow them. Analytics and advertising stay off until you allow them in the European Union, the European Economic Area, the United Kingdom and Switzerland, and wherever we cannot tell your country; everywhere else they are on from your first page, and you can turn them off at any time (see “The cookie notice”). None of them is used on the payment page, and the agents’ portal uses none of them. In the app, AppsFlyer measures installs and the links we send and, while you allow it, what you do in the app, with an iPhone’s advertising identifier only if you allow tracking (see “In the app”).
2.2. To know whether the website performs well, your browser sends us a measurement of how fast the page loaded, with the type of page and its language only. It carries no cookie, and we record no IP address or identifier with it.
2.3. To understand how the Service is used, the website and the app also send our own server a record of the steps taken towards a Booking — a door opened, a search and how it ended, a hotel or flight opened, a room or fare chosen, a payment opened and whether it went through — as categories and counts, never what you typed, as the Privacy Policy describes under “What we collect”. It sets no cookie and does not depend on this notice; it stays on our systems, is read only by our staff and is shared with no advertiser or anyone else. Nothing of it is a tag loaded in the page: the payment steps it holds are recorded by our server as it handles them.
2.4. We also count visits to the website ourselves, without cookies and without storing anything in your browser: for each page, its address without what follows it, its kind and the type of device, and for the first page of a visit, the site or campaign that sent you. A visitor is counted by a code our server makes from the internet address and the browser’s description together with a random value that changes every day and is then deleted — never kept with an account, and impossible to follow from one day to the next (see “Visits to the website” in the Privacy Policy). It does not depend on this notice either.
2.5. Your browser sends none of these if it signals “Do Not Track” or Global Privacy Control; what our server itself sees happen — a search it ran, an order it took — it still records. In the app there is no switch for this record; the “Ads measurement” switch concerns AppsFlyer only.
3. The cookie notice
3.1. The first time you open the website, a short notice appears. What it says depends on where you are, which we tell from the country of your internet address, looked up on our own server, or — when the address cannot be placed — from your browser’s time zone and language; nothing of it is stored.
3.2. In the European Union, the European Economic Area, the United Kingdom and Switzerland, and wherever we cannot tell your country, the notice asks before anything optional is used: “Accept all”, “Necessary only”, or “Choose”.
3.3. Everywhere else, Analytics and Advertising are on from your first page, and the notice tells you so, with “OK”, which keeps things as they are and closes the notice, and “Settings or decline”, which opens the switches with “Necessary only” beside them.
3.4. “Choose”, “Settings or decline” and “Cookie settings” show each category with its own switch:
- Necessary — always on: your language and currency, keeping you signed in, and the payment form’s protection against fraud. The website cannot work properly without them, so they cannot be switched off there.
- Maps by Google — off until you turn it on: hotel maps drawn by Google Maps, which may use Google’s own cookies or similar technologies. While it is off, the same maps are drawn by OpenStreetMap instead.
- Analytics — off until you turn it on where the notice asks first, on until you turn it off everywhere else: Google Analytics, which tells us how visitors find and use the website — which pages are opened and which searches lead to a Booking. It uses Google Analytics’ cookies, listed below.
- Advertising — off until you turn it on where the notice asks first, on until you turn it off everywhere else: the Google Ads tag and the Meta pixel, which tell Google and Meta which of our advertisements brought a visit or a Booking and let them show our advertisements to people who visited the website. It uses their cookies, listed below, and lets our server report a paid order to Meta — and to Google, if “Analytics” is on too — with the email address and phone number in hashed form (see the Privacy Policy).
3.5. Until you choose, only what is necessary is used where the notice asks first, and what is necessary with Analytics and Advertising everywhere else. If your browser sends Global Privacy Control or "Do Not Track", we take it as “Necessary only”, wherever you are, and do not show the notice; a choice you then make yourself in “Cookie settings” is the one we follow. A choice you made always takes precedence over what applies by default.
3.6. Your choice is kept in the cookie "rahlio_consent" for 180 days. “OK” on the notice is kept the same way, marked as no choice: it only stops the notice from appearing again, and if you later open the website from a place where the notice asks first, it asks. After 180 days the notice appears again, and it also appears again if we add a category or change what one covers.
4. What the website stores
4.1. The website uses the following, all first-party:
- "rahlio_locale" — a cookie kept for one year that remembers the language you chose.
- "rahlio_currency" — a cookie kept for one year that remembers the currency you chose.
- "rahlio_consent" — a cookie kept for 180 days that remembers your choice in the cookie notice, or that you pressed “OK” on it.
- "rahlio_session" — a cookie set by our API (api.rahlio.com) only when you choose to stay signed in. Your browser's scripts cannot read it, it is sent only to our sign-in service, and it ends when your session does (at most 60 days) or when you sign out.
- "rahlio.session" — session storage that holds a short-lived sign-in pass while the tab is open; it is removed when the tab is closed.
- "rahlio.session.kept" — local storage that notes that you chose to stay signed in on this browser, so the website knows to ask our sign-in service for your session; it is removed when you sign out.
- "rahlio.guest.token" — session storage that lets you plan and search without an account; it is removed when the tab is closed.
- "rahlio.locale.chosen" — session storage that carries a language you have just chosen to the page it opens; it is removed as soon as that page has read it.
- "rahlio.checkout.draft.stay", "rahlio.checkout.draft.flight" and "rahlio.checkout.draft.package" — session storage that keeps what you typed in a booking form while its price is updated, for at most 30 minutes; it is removed once it has been read back, or when the tab is closed.
- "rahlio.holderKey" — local storage that shows a hold or an order started in this browser is yours; it stays until you clear your browser’s storage.
- "rahlio.referral" — local storage that keeps a friend’s invite code for 30 days after you open their invitation link, so that it can join your account when you sign in; it is removed once it has been used.
- "rahlio.recent-searches.v1" — local storage that keeps your last few searches on this browser (the place, the dates, the number of travellers — never anything you typed as free text) for up to 60 days, so that the home page can offer to pick them up again; it is not written while your browser signals Global Privacy Control or “Do Not Track”, and it stays on your device.
- "rahlio.appBanner.dismissedAt" — local storage that remembers, for 14 days, that you closed the “get the app” strip on a phone.
4.2. All of these are strictly necessary for the Service or remember a choice you made.
5. Analytics and advertising
5.1. Only while the category each belongs to is on — because you allowed it, or by default where the notice does not ask first — and never on the payment page, the website uses the following:
- "_ga" and "_ga_" followed by a code — Google Analytics cookies, under “Analytics”, that tell one browser and one visit from another; kept for 13 months.
- "_gcl_au", "_gcl_aw" and "_gcl_gb" — Google Ads cookies, under “Advertising”, that connect a visit to the Google advertisement that brought it (the last two only when you arrive by clicking one); kept for 90 days.
- "_fbp" and "_fbc" — Meta pixel cookies, under “Advertising”, that tell one browser from another and keep the identifier of a click on a Meta advertisement (the second only when you arrive by clicking one); kept for 90 days.
- "rahlio_attribution" — our own local storage, written only while “Analytics” or “Advertising” is on, that keeps for 30 days what brought you to the website — the campaign named in the link, the advertisement’s click identifier (only under “Advertising”), the page you landed on and the website that sent you — so that a Booking made in that time can be credited to it. A later campaign replaces it; a visit that came from no campaign does not. It is deleted when you turn both categories off.
5.2. Google and Meta may also read or set cookies on their own domains, such as google.com, doubleclick.net and facebook.com, when their tags run in your browser, under their own cookie and privacy policies. We clean every page address before it reaches them: only the page and the parameters of a search or a campaign, never a booking code, a token, an email address or a phone number; pages about your account, a Booking, a payment, an agent’s proposal or a support request send nothing at all.
6. In the agents’ portal
6.1. The portal in which travel agents work uses the following, all first-party:
- "rahlio_agent_session" — a cookie set by our API (api.rahlio.com) when you sign in to the portal. Your browser's scripts cannot read it, it is sent only to our sign-in service, and it ends when your session does or when you sign out.
- A remembered-browser cookie, named "rahlio_td_" followed by a code — set by our API only if, after entering a sign-in code, you ask us to remember this browser. It lets your next sign-in skip the code, never the password; it lasts for a limited time after you last used it (currently 30 days), and ends earlier if your password is changed or reset.
- "rahlio_agent_locale" — a cookie kept for one year that remembers the portal’s language.
- "rahlio_consent" — a cookie kept for 180 days that remembers that you have read the portal’s cookie notice.
- Local storage that holds the short-lived pass of your current sign-in (about fifteen minutes, renewed while you work and removed when you sign out), and choices you made in the portal, such as the desk’s currency and a report’s period.
6.2. Nothing in the portal is optional, so its notice informs and asks nothing. If you choose to sign in with Google, the sign-in button and window come from Google and use Google’s own cookies, under Google’s Privacy Policy.
7. Third parties on our pages
7.1. On the payment page, the Supplier’s payment form (with its payment processor Stripe) is loaded inside our page and may use its own cookies to process the payment securely and prevent fraud; no analytics or advertising tag is loaded on that page. A map is loaded only when one is shown: it is drawn by Google Maps only if you allowed “Maps by Google” in the cookie notice, and by OpenStreetMap otherwise. Whichever draws it receives your IP address with each request for it, and Google Maps may also use its own cookies or similar technologies, under Google’s Privacy Policy. Google’s and Meta’s tags are loaded only while “Analytics” or “Advertising” is on, as described above. Where we offer sign-in with Google or Apple, their button and sign-in window come from them and may use their own cookies. We do not control these cookies; the providers’ own policies apply to them.
8. In the app
8.1. The app keeps on your device: your sign-in tokens, in the device’s secure storage (the Keychain on iOS, encrypted storage on Android); your language, currency and onboarding choices; a copy of your trips so that you can read them offline; and a cache of hotel images. If you opened a friend’s invitation, the app keeps their invite code until you sign in; on Android, Google Play passes the code to the app when it was installed from the invitation. Signing out removes the sign-in tokens and the offline trips.
8.2. If you allow notifications, the app registers a push token with Google Firebase Cloud Messaging. The app also contains AppsFlyer’s software, which keeps an installation identifier on the device so that an install can be matched to the link or campaign that led to it, and so that a link you opened before installing the app can open the right screen after it. It also contains Google Firebase Crashlytics, which keeps on the device an identifier it creates for the installation and any crash or error report not yet sent, until it is sent.
8.3. While the “Ads measurement” switch in the app’s privacy settings is on, the app also tells AppsFlyer what you do towards a Booking — searches, the hotels and flights you view, the booking and payment steps you reach, an account created — and each paid order with its value, currency and our order reference, so that we can see which campaigns bring Bookings; never your name, contact details or travellers. The switch starts off in the European Union, the European Economic Area, the United Kingdom and Switzerland, and wherever the app cannot tell your country, and on elsewhere; you can turn it on or off at any time. At its first launch on an iPhone, the app shows Apple’s question whether to allow it to track you. Only if you allow it does AppsFlyer read the iPhone’s advertising identifier and pass it on, with what it measures, to Google and Meta, so that they can tell which advertisement brought you; allowing it also turns the “Ads measurement” switch on unless you have already set it. If you do not allow it, the identifier stays hidden and nothing else changes. You can change your answer at any time in the iPhone’s Settings → Privacy & Security → Tracking. On Android the app never reads the advertising identifier.
9. Your choices
9.1. You can change your choice at any time with “Cookie settings” at the foot of every page of the website; in the agents’ portal, the notice can be shown again from your account page and from the sign-in page. A change applies from that moment: nothing more is sent under a category you turned off, Google’s and Meta’s tags on the page are told that you withdrew it, and the cookies they set on our website under it (listed above) are deleted. What they keep on their own domains stays until it expires or you delete it.
9.2. You can also delete or block cookies and browser storage in your browser settings; the website will then forget your language, your currency and your cookie choice, ask you again, and sign you out, but will otherwise keep working.
9.3. In the app, turn “Ads measurement” on or off in the privacy settings. You can also limit the advertising you are shown in Google’s and Meta’s own settings: Google’s My Ad Center, and the ad preferences of your Facebook or Instagram account.
9.4. If we ever add another cookie that is not strictly necessary, we will update this policy first, and the notice will appear again.
10. Contact
10.1. Questions about this policy: privacy@rahlio.com.