Privacy
Minimal, purpose-bound data handling.
The product collects only the personal and travel details needed to process a temporary reservation support request, support the customer, and keep auditable compliance records.
Data categories and purpose
- Passenger names, contact details, itinerary details, validity options, policy acknowledgments, and support communications are collected for order fulfillment, customer support, dispute handling, and compliance auditability.
- Payment events are linked to orders, but production card data must be handled by a trusted payment provider rather than stored by this application.
- Support, compliance, finance, and operations users should receive role-based access only to the data needed for their work.
- The service does not need passport scans, national ID numbers, passwords, bank-account credentials, or unrelated sensitive documents for the standard request flow.
Retention and deletion
- Passenger and itinerary data should be removed or anonymized when it is no longer needed for fulfillment, support, dispute handling, compliance, tax, accounting, or legal obligations.
- Production launch must define retention windows for delivered orders, failed orders, refunded orders, support tickets, and payment records.
- Customers should be able to request access, correction, or deletion where applicable law allows, using the published support email.
Cookie choices and consent controls
- Visitors can accept cookies, reject optional cookies, or accept selected items before non-essential storage is enabled.
- Necessary cookies remain on only for essential site functions, consent storage, security, and request integrity.
- Optional analytics, advertising, conversion, remarketing, and personalization storage stay off until the visitor explicitly accepts them.
- Consent records should capture the chosen action, selected categories, version, and timestamp so the banner does not reappear after a valid choice.
Analytics, cookies, and advertising data
- Analytics events should measure funnel progress without exposing passenger names, routes, booking references, email addresses, phone numbers, or other unnecessary personal data.
- Personally identifiable information must not be sent to Google through page URLs, analytics parameters, conversion tags, remarketing lists, feeds, or tracking templates.
- The Google Ads tag AW-11215492157 uses Consent Mode defaults so advertising, personalization, user-data, and analytics storage remain denied unless the visitor's cookie choice allows the relevant optional category.
- The website-traffic conversion action AW-11215492157/GVbmCIm-4KkYEL2o--Mp is limited to selected non-PII click targets and should navigate normally without sending the conversion event when advertising consent is not granted.
- If cookies, local storage, remarketing, conversion tracking, or personalized ads are used in the EEA or UK, production launch must include appropriate consent and disclosure controls.
Security and processors
- Sensitive collection and checkout flows must use HTTPS in production.
- Production payment, email, analytics, hosting, and support processors must be disclosed once selected.
- Administrative access should be authenticated, logged, and limited by role so sensitive travel data is not exposed unnecessarily.