Information we do not collect
FareGlide does not ask for passport numbers, payment card details, traveler names, dates of birth, airline confirmation numbers, loyalty-program passwords, or ticketing account credentials. The site does not run a booking account system, does not issue e-tickets, and does not store reservations.
If you book after clicking a sponsored search link, the airline, agency, marketplace, or provider that processes the booking controls the checkout data and support records for that transaction.
Operational data FareGlide may process
We may process standard website and product analytics signals such as page URL, route or airport page viewed, search form parameters submitted on FareGlide, device/browser information, approximate geography derived from network data, referrer, timestamp, and whether a sponsored provider link was opened.
This data is used to understand which route pages, airport comparisons, fare-intelligence templates, and search handoffs are useful. It also helps detect broken pages, bad redirects, invalid search parameters, and pages that should be improved or removed.
Google Tag Manager and analytics
FareGlide uses Google Tag Manager to load measurement tags. These tags may set or read cookies, collect event data, or send page and click information to analytics services. We use this data in aggregate to evaluate site quality, crawlable page families, outbound partner clicks, and search UX.
Your browser may let you block cookies, limit tracking, use private browsing, or install privacy tools. Some measurement features may not work when those controls are enabled, but the static route research pages should remain usable.
Affiliate redirects and partner providers
Sponsored buttons and search links can send you to partner flight-search providers. Redirect URLs may include route codes, dates, currency, locale, placement labels, affiliate marker values, and other non-ticketing parameters so the partner can open a relevant search page and attribute the referral.
Once you leave FareGlide, the partner provider's privacy policy, cookie practices, terms, support rules, and checkout flow apply. FareGlide cannot access your booking details from those providers unless you voluntarily send us information while asking for site feedback.
Server logs, security, and retention
Cloudflare and related hosting infrastructure may process IP address, user agent, request URL, timestamps, error logs, and security events to deliver the site, reduce abuse, debug functions, and protect availability. These logs are used for operations and troubleshooting rather than passenger profiling.
We keep analytics and operational records only as long as useful for site measurement, fraud prevention, debugging, or legal/compliance needs. Aggregated reports may be retained longer because they do not identify a booking or traveler.
Corrections and contact
If you believe a FareGlide page exposes personal information, misstates how data is handled, or should be corrected, contact us through the contact page with the exact URL and a short explanation. Do not send payment cards, passport scans, airline passwords, or full booking confirmations.