Cookies & analytics

Storage used by this website

Cookies, session storage, local storage and browser history serve different purposes. Some records have a validity period rather than being physically removed at that exact moment.

Session and form security

Cookies such as milvexa-session and XSRF-TOKEN support the session and CSRF protection. The configured session lifetime is 120 minutes of inactivity. Browser settings can end it earlier.

Temporary language and package handoff

Session storage (milvexa.demo-language-handoff.v1 and milvexa.lead-package) carries preview choices or the selected package to the requested page. A handoff is valid for 60 seconds and removed when read. Otherwise it can remain until the tab’s browser session ends. It does not store personal lead-form fields.

Preview history and shared URLs

Browser history can retain the restaurant name and design choices for returning from a demo. These remain until the history entry is removed or replaced. A shared URL also contains its selected options. Do not include confidential information in it.

Analytics preference

milvexa.analytics-consent stores your choice, policy/provider scope and expiry in local storage, with a same-named cookie as fallback. Both choices are valid for 180 days. An expired local-storage entry can remain until replaced or cleared. The fallback cookie expires through the browser. This is a preference, not a visitor identifier.

Consented demo-action context

When analytics is allowed, milvexa.analytics-demo-entry in session storage carries only an action category, destination path and expiry. It is valid for 60 seconds and removed when read. Otherwise it can remain for the tab’s session. It contains no restaurant name, form content or URL query. After consent, language changes and confirmed contact enquiries also use a short-lived category or expiry in session storage, for at most two minutes. No form content or visitor ID.

Optional analytics and consent

Our own first-party analytics integration with the Milvexa Business Panel can be switched off completely. By default, no events or analytics requests are sent before consent. Accept and Reject are both available. Earlier actions are not replayed.

We measure only visits and actions with fixed categories such as language, page, layout, package, device and action ID. Form content, restaurant names, contact details, enquiry references, IP addresses, browser information, URL queries and referrers are not forwarded to the Panel. No tracking cookies, fingerprinting or visitor ID. Each event has only its own random event reference.

Your preference is valid for 180 days and can be changed through Analytics preferences in the footer, live viewer or below. A provider or policy change may ask you to choose again. If browser storage is blocked, a choice may apply only to the current page. The notice explains this.

Optional analytics is currently available on this website. You can manage your choice through Analytics preferences.

Changing or clearing your choice

Open Analytics preferences and choose Reject to stop future tracking, or Accept to allow it. Your preference is checked again before events and on return to a page. Withdrawing cannot recall a request that has already reached a provider.

You can also clear this site’s storage through your browser. This may remove your analytics choice and preview history, and end the form session. Your browser may then ask for a new choice. Rejecting analytics through our controls leaves the essential features available.