Understand Phase 1 device preferences, analytics consent, private booking protection and future data-access controls.
Public discovery is available without an account. Sample inventory and fictional cinema details are labelled. The foundation does not accept payments, store traveller documents or create supplier reservations.
Search inputs and AURA messages are sent to same-origin preview endpoints for validation and a guided response. They are not intentionally stored in a transactional database or analytics destination. Infrastructure may process ordinary request metadata; production retention and processor details must be documented before launch.
Theme and cookie consent choices stay on your device. Up to three recent selected routes use tab-scoped session storage and can be cleared; no traveller data or AURA messages are stored there. An installed app caches static assets and an offline page. Private account, booking, payment and API responses are excluded from service-worker storage. No third-party analytics provider is connected.
Appearance and consent preferences stay on this device. Analytics has no connected destination. No traveller data is saved in your browser.
IETA Central Identity will supply a verified session when its actual protocol is integrated. Traveller documents must use restricted references and encrypted backend storage; do not enter sensitive data into demo interfaces.
Non-essential analytics and notifications require your choice. Future account access, correction, export and deletion requests will require verified identity and a backend privacy workflow. The current support pathway explains its connection status and does not submit a request.