Privacy Policy
Static pages, no cookies, no analytics — and a plain list of the third parties involved.
The short version
This site is made of static pages. It sets no first-party cookies, runs no analytics and no advertising scripts, and has no account system, login or newsletter. Nothing you do here is tracked by us.
What we collect
Nothing directly. There is no contact form on this site — the contact page gives an email address, and if you email us we hold that message and your address for as long as it takes to answer it.
Our web host keeps standard server logs, which include IP addresses and requested URLs. Those are the host's records, kept for security and troubleshooting.
Third parties, and exactly when they are involved
Viator and GetYourGuide
When you click a tour link, you leave this site for Viator or GetYourGuide. The link carries a tracking code identifying this site as the referrer, and those platforms set their own cookies once you arrive. Their privacy policies govern what happens from that point.
Google Maps
The map on the homepage does not load until you click the button that loads it. Until that click, no request is made to Google and no Google cookie is set. This is deliberate: an embedded map that loads automatically contacts a third party before you have agreed to anything.
Search Console and Bing Webmaster Tools
This domain is verified with Google Search Console and Bing Webmaster Tools using a static verification file. Those services report aggregate search data about the site. They do not identify individual visitors to us.
Your rights
Under the UK GDPR and the EU GDPR you may request access to, correction of, or deletion of personal data we hold about you. In practice, the only personal data we are likely to hold is an email you sent us. Email the team and we will action the request.
Children
This site is aimed at adults planning travel. We do not knowingly collect any information from children.
Changes to this notice
If this site ever adds analytics, advertising or a form, this page will be updated before that change goes live, not after.