Account access
One-time verification and reset links expire and cannot be reused. Customer sessions use secure HttpOnly cookies.
Security
Private by design, useful by default.
How account, booking, payment and contact boundaries protect traveller information.
Booking ownership
Private trip, payment and document routes verify the current customer and selected booking on the server.
Payment integrity
Prices, deposits and balances are calculated from the server-owned booking snapshot; browser-supplied amounts are ignored.
Contact safety
Requests use CSRF protection, international-number validation, rate limits, quotas and idempotency. Provider credentials never reach the browser.