Privacy

This page describes what the site actually does at launch, rather than what a generic policy would say. It is written from the site's own behaviour, not from a template.

Current behaviour#

• No accounts, no newsletter, no payments. The site has no sign-up, no stored user data and no checkout of any kind.
• No contact form. Contact is by email address only, and using it means you choose to write to us directly.
• The site's own code sets no cookies and no browser storage. There is no cookie banner because the first-party code sets no cookies, and reads or writes no localStorage and no sessionStorage. There is also no external analytics vendor connected at this release.

Analytics, and the fact that it is not decided yet#

The site ships a small first-party script that can emit anonymous events: a page view, and a record of a booking link on the page being shown or followed. Each event carries only identifiers such as the page and which link was involved. It carries no name, no email address, no device identifier, no advertising identifier and no personal data of any kind.

Whether that script is connected to an analytics provider is a deployment decision that has not been made yet. No analytics vendor is wired up at launch. If one is enabled later, this page must be updated on the same day to name it and to state whether it sets cookies, whether it is cookie-free, and where it is based. Until that update is made, treat the event capability as present and unconnected.

Hosting and server logs#

This site is built to be deployed on Cloudflare Pages, and when it is deployed there the hosting provider is Cloudflare. Cloudflare delivers the pages using its own infrastructure. Like any web host, it processes ordinary technical request data — such as an IP address, a user agent, a requested URL and a timestamp — in order to serve pages and prevent abuse. That processing is the hosting provider's own, carried out under its own published terms and privacy policy: Cloudflare's privacy policy. It is not controlled by this site, and this site does not set out what Cloudflare does or does not log.

If the deployment ever moves to a different host, that provider and its policy are named here instead, on the day it changes.

Outbound links#

When you follow a link to an attraction operator's official site, to a booking provider, or to any other third party, that site's own privacy policy applies from the moment you arrive. The operator or booking provider may set its own cookies, collect data under its own terms, and operate in a different jurisdiction. Any booking link on this site is labelled as a booking link, so a commercial link is never presented as an editorial recommendation.

Email#

If you email us, we keep your message and your address in order to reply. That correspondence is not sold, shared or added to a mailing list, and there is no mailing list.

What this page is not#

• It is not legal advice and it does not claim compliance with any specific privacy law. Whether a particular configuration requires a consent banner, a cookie notice or a data-processing agreement depends on the deployment, the analytics choice and the reader's jurisdiction.
• It does not claim "we collect nothing". A static site can still generate hosting logs, and an analytics provider may be added later. The honest statement is the one above: what the code does, and what has not been decided.