Cookie Notice

Every cookie this site sets is either strictly necessary to make it work, or a preference you set yourself by clicking a switch in the interface. None of them track you across other websites, build an advertising profile, or feed a marketing network. Consent rules do not require a banner for that category, and putting one in front of you anyway would be theatre.

If that ever changes, this page changes first and a real consent banner goes up before the first non-essential cookie is set, not after. The one candidate is described under analytics below.

These exist so the site can do the thing you asked it to do. They cannot be switched off from within the site, because without them signing in does not work.

The session and CSRF cookies are HTTP-only, so page scripts cannot read them, and are marked secure and same-site over HTTPS.

These only ever appear because you clicked something. Each one stores a single short value, no identifier, and nothing that identifies you personally.

Two things are kept in your own browser and never sent to our servers at all. Clearing site data in your browser removes them.

The site contains the wiring for Google Analytics 4, but it only loads if a measurement ID is configured for the environment. When it is switched off, no Google tag is loaded and no analytics cookie is set. That is the current state of the published code.

No measurement ID is configured on the production environment, so as this is written no Google tag is requested and no analytics cookie exists on this site. You can confirm it yourself: view source on any page and search for gtag.

If analytics is ever switched on, Google Analytics sets its own cookies, typically _ga and _ga_<id>, lasting up to two years, and Google acts as our analytics processor. Those are non-essential cookies, so they are behind a consent gate that is enforced in the code, not merely promised: the analytics tag is wrapped in a component that renders nothing until you choose Allow, and the choice is remembered in your browser's local storage under ll_analytics_consent_v1. Declining, or never answering, means the tag is never requested at all. The banner cannot appear while analytics is switched off, because there would be nothing to consent to.

Your answer on this browser

The privacy policy says this consent is withdrawable in one click, so here is the click. The block below reads the same storage key the banner writes, so it reports what your browser actually holds rather than what we assume it holds, and changing it takes effect on the spot in every open tab.

A few parts of the site load content from someone else's server. Loading anything from another server necessarily discloses your IP address and browser to it, whether or not a cookie is involved.

• Cloudflare Turnstile, on the contact form, the registration form and the concierge. It is a bot check: it decides whether the sender is a human. Cloudflare may set its own storage on its domain. This is a security measure, not tracking, and the forms will not submit without it when it is enabled.
• CARTO basemap tiles, on property maps. Map images are fetched from CARTO's CDN when a map is on screen. No cookie of ours is involved.
• Google Drive and Cloudflare R2, when you download a brochure or load a photograph. These are file hosts serving a file we asked them to serve.

Typefaces are self-hosted from our own domain, so no font request goes to a third party.

Every browser lets you see, block and delete cookies for a site, usually under privacy or site settings. Blocking the strictly necessary ones will stop you signing in; blocking the preference ones just means the site forgets your language, currency and area unit each visit. Nothing else on the site depends on them.

What we do with the data behind all of this is in the Privacy Policy, and you can exercise your rights over it at Your Data Rights.