Cookies
This draft sets
no cookies.
Which makes for a short page.
A draft. If a booking widget, statistics or an embedded map are added later, this page has to be rewritten and a consent banner will be needed.
Nothing is set
This version of the site sets no cookie of any kind, neither its own nor anybody else's, so there is nothing to consent to and no banner to click away.
Two things are remembered, for the visit
In your browser's session storage, for as long as the tab is open: that you have already seen the opening of the home page (castello-intro), so it does not play again, and how far down each page you had scrolled (tsr-scroll-restoration-v1_3), so the back button brings you back to the same place. Neither is a cookie: they are never sent to a server, no other site can read them, and they are gone when you close the tab. The language you read the site in is part of its address (/de/ for German, for example), so it needs no storage at all. Only the briefing page keeps your answers and its language in local storage (castello-briefing-v4, castello-briefing-lang).
What would change that
An embedded booking engine, a map in the page rather than a link to one, a video from another site, or any kind of statistics. Each of those sets something, and each would have to be listed here and asked about first.
Planned for the published site: nothing. It is meant to manage without cookies too.
To be confirmed
Our proposal. Statistics or an embedded booking engine would change it.