What stays on the page, in the browser, and out of the network.

Contact demonstration

The Contact route asks for a name, email, planning topic, and optional note only to demonstrate local form behavior. Values remain in the current page controls, are reset before the completion state, and are not sent, saved, logged, added to the URL, or written to browser storage.

Booking guest details

The booking simulation asks for a lead guest name and email, with an optional phone number. These values exist only in current journey memory. They are not restored after refresh and are cleared on restart or simulated completion.

Payment data, passports, government identifiers, passwords, addresses, dietary details, access requests, celebration details, and open booking notes are not requested.

Browser-session draft

A versioned sessionStorage draft may hold dates, adult/child/infant counts, the selected accommodation, rate plan, transfer choice, and earliest safe journey step. It does not hold names, email addresses, or phone numbers. Invalid, stale, or unsupported drafts are discarded, and the draft is cleared on restart and simulated completion.

The application does not use localStorage for visitor or journey data.

Shareable search URL

Check-in, check-out, and adult, child, and infant age-band counts may appear in the URL so a stay search can be shared or revisited. Names, emails, phone numbers, exact child ages, contact fields, and guest free text do not enter the URL.

Network and hosting

No contact or booking field is submitted to a hotel, reservation system, email service, CRM, payment provider, database, analytics service, or public application endpoint. There is no real availability, reservation, payment, or enquiry request.

Like any hosted website, the public portfolio is delivered through hosting infrastructure that receives ordinary web requests. This page does not claim control over the host's operational request data or promise a retention period that has not been established here.

Tracking and external services

No analytics, advertising, external error reporting, chat, CMS, external map, remote font, third-party form service, or third-party client script is enabled. Fonts and imagery used by the experience are held within the project.

Browser-managed features

Information a visitor chooses to retain through browser history, autofill, a password manager, screenshots, or device features remains controlled by that browser or device, not by Dalisara.