Privacy at a glance
The static concept is designed so any handling of booking and enquiry details happens only in the visitor’s own browser. Where the prototype retains booking selections, they remain in browser storage on that device. It does not claim to transmit entered details to Radisson, a hotel, a reservation system, or the concept creator.
Nothing entered creates a live enquiry or reservation. A confirmation shown by the interface only confirms a local preview action on that device.
Data you may enter
Depending on the page and current prototype features, the concept may invite you to enter demonstration information such as:
- guest or enquirer name and contact fields;
- sample arrival and departure dates;
- illustrative room, guest-count, or package selections;
- accessibility, preference, or enquiry text; and
- a local preview reference or status generated by the interface.
Do not enter payment-card numbers, government identifiers, passwords, health details, or other sensitive information. The forms are for design demonstration only.
How browser storage is used
The intended booking and quick-search flows use the browser feature named localStorage. Its purpose is to let the same browser remember selected dates, guest counts, booking choices, and a preview itinerary so visitors can demonstrate reviewing, editing, or clearing a local record.
The enquiry form is different: its field contents are validated within the page and discarded after the preview check. It may use sessionStorage only for a non-personal completion marker that keeps the success panel visible in the same browser tab.
localStorage and sessionStorage are site-specific storage on the visitor’s device. The concept does not present either as secure account storage, a hotel database, or a cloud backup.
Important limitation
Anyone with access to the same browser profile may be able to view locally retained content. Shared or public devices should not be used for personal information, even in a prototype.
What the concept does not claim to do
The static concept does not claim that booking or enquiry content is:
- sent to Radisson, a resort, property staff, or a travel provider;
- submitted to a live booking engine, customer relationship system, or mailing list;
- used to process payments, verify identity, or assess eligibility;
- shared with advertisers or used to build a guest profile; or
- monitored as a real request that will receive a response.
If this concept is viewed through a hosting service, that service may independently receive ordinary technical request information, such as an IP address or browser type, under its own practices. That is separate from the concept’s browser-local handling of the booking and enquiry fields described here.
Retention and deletion
Booking selections retained in localStorage may remain until the concept removes them, you use an available clear or cancel control, or you clear the site’s stored data in your browser settings. Enquiry field contents are not intended to be retained after the browser-only preview check. A sessionStorage completion marker normally disappears when the tab or session ends, but behavior varies by browser.
To remove the preview data
- Use any clear, reset, or cancellation option provided in the relevant concept page.
- Alternatively, open your browser’s privacy or site settings.
- Find stored data for this site and remove it. Clearing all browser data may affect other websites too.
Because the concept does not claim live receipt of the entered content, the concept contact page is not presented as a way to retrieve or delete a server-side guest record.
Your choices and responsibilities
- You may browse the informational pages without completing a booking or enquiry form.
- You may use fictional details to explore form layout and interactions.
- You are responsible for deciding whether a device and browser profile are appropriate for local storage.
- You should verify that local data is cleared before leaving a shared device.
Status of this notice
This is illustrative development-concept content, not legal advice and not a representation of Radisson’s actual privacy practices or terms. A production service would require identified operators, processing purposes, legal bases, retention periods, security controls, user-rights procedures, and jurisdiction-specific review.