Site feedback
For corrections, data questions, disclosure questions, or page-quality feedback, use feedback@fareglide.online. Include the FareGlide URL, the route or airport involved, and a short description of what should be reviewed.
Useful reports include stale route wording, incorrect airport naming, a broken sponsored handoff, missing noindex behavior, confusing affiliate language, or a page that no longer answers a real traveler decision.
Booking and trip support
FareGlide does not sell tickets and cannot access reservations. If you booked after leaving FareGlide, contact the provider shown on your confirmation email or payment receipt for ticket changes, refunds, schedule changes, baggage, seats, or account access.
Affiliate and data questions
FareGlide uses sponsored partner links and cached fare observations as planning context. If a page appears to overstate a cached price, route, airline, or airport option, we can review the wording and data snapshot behind that page.
Correction review process
When a correction request is actionable, the likely fixes are wording changes, data refreshes, redirect parameter updates, sitemap/noindex adjustments, or removal from a public page flow. We prioritize issues that can mislead travelers about price, airport choice, partner booking boundaries, or route availability.
Please do not send passport scans, payment-card numbers, airline passwords, or full booking receipts. FareGlide cannot safely process booking-sensitive documents and does not need them to review site copy.
Business and partnership notes
Partnership questions should describe the program, tracking requirement, allowed traffic sources, brand policy, and whether deep links can preserve route and date parameters. FareGlide only uses partners when the handoff can remain clear to travelers.
What happens after a report
A report does not guarantee a specific change, but it gives us a concrete page to inspect. We may compare the generated HTML, cached data, sitemap placement, redirect target, and visible copy before deciding whether to update the page. For route or airport pages, the most useful reports are specific: the exact URL, the expected correction, and why the current wording could mislead a traveler.
If the issue belongs to a provider checkout page, we may still improve the FareGlide handoff text, but the provider must handle the booking-specific problem.
Useful details to include
For a route issue, include the origin, destination, dates if relevant, and whether the problem is price, airport, airline, stop count, or partner handoff. For an airport issue, include the airport code and the nearby or alternate airport being compared. For a disclosure or privacy issue, include the wording that seems unclear and the page where you found it.
Short, specific reports are easier to verify than broad requests. We can compare them against the current generated page and the cached snapshot behind that page.