HappyFares Cookie and Tracking Notice
Effective date: 29 October 2026
Updated 30 October 2026
On this page
This notice explains the cookies, browser storage and tags that run on www.happyfares.in and in the HappyFares app, what each is for, how long it lasts, and how to switch it off. Read it with our Privacy Policy.
HappyFares is run by Travelogy Online Private Limited, A4, Level 1, Krine Vista, Anand Nagar, Lane 3, GS Road, Guwahati, Assam 781005. Questions: help@happyfares.in.
1. What cookies, storage and tags are
A cookie is a small file a website puts in your browser so it can remember something between pages or visits. Browser storage (local storage and session storage) works the same way but stays inside your browser; session storage clears when you close the tab. A tag or pixel is a small piece of code from another company that runs on our page and tells that company what happened, for example that a booking was completed. Some measurement also happens from our servers: we send a company a booking's value and reference without a tag on the page.
Some cookies are ours. Others are set by companies whose services run on our pages. We describe them by what they do. The app uses the same kinds of on-device storage and measurement for the same reasons.
2. Strictly necessary
These make the site work and keep it safe. Without them you cannot sign in, book or pay.
| Name | Set by | What it does | Lasts |
|---|---|---|---|
| hf_token, hf_user | HappyFares | Keep you signed in and load your bookings | Until you sign out |
| hf_session_id and other hf_ items in session storage | HappyFares | Hold your booking together as you move from search to payment | Until you close the tab |
| hf_site | HappyFares | Remembers which version of our website to show you, if you chose one | 1 year |
| hf_sp | HappyFares | A signed visitor pass that helps us tell real visitors from automated programs | 30 days |
| hf_sv, hf_sv_ok, hf_tap | HappyFares, with our security provider's check | Show that your browser passed our security check, so your searches go through | 1 day |
| The security check itself | Our hosting and security provider | Reads browser and device signals for a moment to tell a person from an automated program. On some networks it asks you to tick a box | During the check |
| rzp_unified_session_id, rzp_device_id, rzp_checkout_anon_id, __rzp_risk | Razorpay, our payment partner | Keep a payment secure and spot payment fraud | As Razorpay needs for payment security |
3. Preferences and details kept on your device
These remember choices and details you gave us, so you do not type them again. They stay in your browser; we do not see them unless you use them in a booking.
| Name | What it does | Lasts |
|---|---|---|
| hf_saved_travellers, hf_saved_contact, hf_last_party | Saved travellers, contact details and the people you booked for last time | Until you clear them |
| hf_saved_passports | Saved passport details. Set only if you tick the box asking us to save them | 90 days; deleted the first time you open our booking page after that |
| hf_recall_v1 | Your last search and last trip, for the Welcome back card | Until you clear it |
| hf_seen | Remembers that you visited before, so first-visit messages do not repeat | 2 years |
| hf_visit_v1 | Counts your visits to our homepage | Until you clear it |
| hf_alert_uid | Links the price alerts you set to this browser | Until you clear it |
| hf_lock_banner_dismiss | Remembers that you closed the Fare Lock message on a route | 12 hours |
| hf_srp_y_v2, hf_flt_v1 | Keep your place and filters on the results page when you go back | Until you close the tab |
| Easy Read and 12-hour clock choices | Remember how you like the page shown | Until you clear them |
| hf_col | Remembers which aircraft prints you have seen in our collection | Until you clear it |
| hf_from_v1, RecentSearch | The last city you searched from and your recent searches, to fill the search box | Until you clear them |
| FO_ items, PAX_ items, SETTINGS_IN | The booking engine's search options, traveller numbers and settings for your search | Until you clear them |
| hf_apn_v2 | Airport and terminal names, kept so the booking page loads faster | 30 days |
| hf_proof_v1 | A copy of figures shown on our pages, kept so they load faster | Until you clear it |
| meera. items | Your Meera chat settings and recent chat on this device, so a chat can carry on | Until you clear them |
| g_state | Google, only if you use "Sign in with Google": remembers your sign-in choice | As set by Google |
4. Analytics, advertising and measurement
These help us see how the site is used, fix problems, and measure whether our advertising works.
| Name or tag | Set by | What it does | Lasts |
|---|---|---|---|
| _ga, _ga_D0KN9QBNX7, FPID, FPLC | Google Analytics, from Google. How Google uses data from sites that use its services. Opt-out add-on | Counts visits and pages and shows where people get stuck. Our servers also send it each booking's reference and value | _ga and _ga_D0KN9QBNX7 2 years; FPLC 20 hours |
| _gcl_au, _gcl_aw, _gcl_gb, _gcl_ls and the Google Ads tag | Google Ads, from Google. How Google uses information for advertising | Loads on our pages for every visitor, whether or not you came from an advert, and tells the search engine which page you opened. It uses this to measure our adverts, to build lists of visitors to show our adverts to, and to leave out people who already booked, and may use it for its own purposes under its own privacy terms | 90 days |
| hf_gcl | HappyFares | Keeps the advert's click id from the address you arrived on, so we can tell Google Ads which of its adverts led to a booking. A click id kept with a booking is deleted after 13 months | 90 days |
| Purchase tag on the confirmation page | Google Ads, from Google | When you complete a booking, it sends the booking reference and value and, as a hash (a code made from them), your email and phone number, so Google can match the booking to an advert you clicked. A hash is still personal data: Google can use it to find your account if you have one, and may use it for its own purposes under its own privacy terms. It does not receive your email or phone number as plain text | Sent once per booking |
| oaiq_ items | ChatGPT advertising, from OpenAI. OpenAI privacy policy | Records that you arrived from one of its adverts and whether you booked | Until you close the tab |
| Meta Pixel (Facebook and Instagram advertising tag) | Meta Platforms. Meta privacy policy | Loads on our pages for every visitor, whether or not you came from an advert, and tells Meta which page you opened and whether you booked, so it can measure our adverts and show them to people who visited us. On the confirmation page only, it also receives the booking contact's email and phone number as a hash, to match the booking to an advert. It never reads the travellers' details on the booking form. Meta also uses this information for its own purposes, such as measuring and improving its advertising, under its own privacy terms | As set by Meta |
| Travel comparison site tags (on the booking and confirmation pages, when you arrive from such a site) | The travel comparison site you came from | Tell that site you landed and booked, with the booking reference, the amount and its own click id, so we pay it its due. No name, email or phone is sent | Sent once per booking |
| _clck, _clsk, _cltk | Microsoft Clarity, from Microsoft. Microsoft privacy statement. Clarity terms | Records how a visit goes (clicks, scrolls, the pages you open) so we can see what is confusing or broken. What you type is masked before it is recorded. We do not record the steps where you enter traveller, passport, PAN, payment or health details. You can switch recording off with the "Do not record my visits" link in the footer. Recordings are kept 30 days; a small sample, and recordings we mark to fix a problem, up to 9 months | _clck 1 year, _clsk 1 day, _cltk until you close the tab |
| Error monitoring | Our error-monitoring service | When the page breaks, sends a technical report (the page address, the error, the browser) so we can fix it. It does not record your screen | No cookie |
| hf_ab, hf_pb, hf_pre_b, hf_fast_b | HappyFares | A random number that decides which version of a screen you see while we try out or roll out a change, so we can compare them | hf_pb 1 year; the others until you clear them |
| cf_zaraz_client | Our tag manager | Loads the visit-recording tag above and keeps it consistent across your pages | As set by the tag manager |
| hf_uid | HappyFares | A random identifier linking your visits to a booking you started, so we can send the one reminder described in our Privacy Policy | The identifier lasts 90 days. The booking details it links to are also deleted after 90 days |
We name Google Analytics and Microsoft Clarity here, with links to their own pages. We describe the other companies by what they do.
We use these tools to measure and improve our own service. Some of these companies also use what their tags collect under their own privacy terms, for example to measure and improve their own services. You can limit that as section 5 explains.
Sharing from our servers and customer lists. Not everything is a tag on the page. From our servers we send Google Analytics and the advertising platforms each booking's reference and value and, for some, the booking contact's email and phone number as a hash. From time to time we also give Meta (Facebook and Instagram) the hashes of past customers' emails and phone numbers, so they can show those customers our offers or leave them out of an advert. For those customer lists, the platform uses the hashes only to find matching accounts and deletes them after matching. We never send travellers' names, dates of birth or any details of children.
5. How to switch them off
In your browser. Every browser lets you block or delete cookies and site data, for one site or all sites. Look under Settings, then Privacy, then "Cookies and site data" or "Clear browsing data". Your browser's help pages show the exact steps for Chrome, Safari, Firefox, Edge and phone browsers.
With the advertising and analytics companies. Many offer their own settings to limit personalised adverts or opt out of analytics. For Google Analytics and Microsoft Clarity, use the links in the table above. For any other company in this notice, write to help@happyfares.in with "Cookies" in the subject (see section 7) and we send you its name and opt-out link.
Do not record my visits. The footer of every page has a "Do not record my visits" link. Press it and we stop recording your visits on that browser. We also never record the steps where you enter traveller, passport, PAN, payment or health details.
To stop us sharing your email and phone number for advertising. Browser settings limit cookies on one device only. They do not stop events sent from our servers or customer lists. To stop all of it for your email and phone number, unsubscribe from our emails, reply STOP on WhatsApp, or write to help@happyfares.in with "Privacy" in the subject. We then stop sending your hashes, leave you out of future lists, and ask the platforms to remove you from lists already in use, within 2 working days where the platform allows it. A platform may keep what it has already lawfully processed under its own terms. This does not affect your booking or the service messages about it.
In the app. Use your phone's privacy settings for tracking and notifications.
If you block strictly necessary cookies, you may be signed out, lose a booking in progress, fail our security check, or be unable to pay.
6. What changes in 2027
India's Digital Personal Data Protection Act, 2023 applies its main duties from 13 May 2027. Before then we will review this notice and add the choices that law requires for cookies that identify you, including a way to say no to analytics, recording and advertising tags.
7. Questions
Write to help@happyfares.in with "Cookies" in the subject. If you want to know the name of any other company in this notice, ask us and we will send you its name and its opt-out link.