Account and access data
The product includes account and sign-in flows. The final notice must name the identifiers and technical records used for registration, authentication, session management, and account protection.
Travel and booking data
Searches and bookings may involve routes, dates, passenger or guest details, selected options, order references, statuses, tickets, and vouchers. Exact fields differ by service and must be documented.
Wallet and transaction data
Wallet flows present balances, transaction history, transaction details, statuses, and receipts. The final notice must document the legal basis, processing parties, and retention for financial records.
Support data
Support requests can include a selected service, an available order, messages, and files supported by the conversation flow. The final notice must explain access and retention.
Sharing and retention
Provider categories, processor names, cross-border handling, and retention periods are intentionally not stated in this draft because they require verified legal and operational input.
Rights and contact
The final notice must identify the applicable privacy rights, request procedure, response rules, controller identity, and verified privacy contact route.
