Privacy in the current validation build.
This page describes the staging product as it exists now. It should be reviewed again before paid booking, accounts, or production analytics are enabled.
Information the route checker uses
The checker asks for travel-profile inputs such as passport nationality, passport type, application or departure country, destination, travel purpose, travel date, urgency, and—where relevant—your status in the application country. It does not ask for passport number, date of birth, payment details, or a scan of your passport.
Validation telemetry
Route checks may be recorded as technical or demand events so we can identify which route combinations need research. During validation, some counters are held temporarily in application memory and structured events may be written to application logs. Analytics events are only sent when the configured analytics integration is active.
Provider links and future checkout
No paid provider recommendation is enabled in the current build. Before any affiliate, direct-booking, payment, account, or customer-support integration goes live, this notice should be expanded to explain the relevant data flows and third parties.
What not to enter
Do not put passport numbers, payment card numbers, passwords, or other sensitive identifiers into free-text fields. The current checker does not require them.