Privacy

What gets logged

Page counts, stripped of anything personal: which pages get opened, roughly which country the request came from, and how far down people read before giving up. I look at it for one reason, which is finding the pages where I have answered the question badly. It is not sold, it builds no profile, and it cannot be traced back to you.

What the booking platform sees

The tour cards and availability widgets are served from GetYourGuide, and they may set a cookie that tags a later booking as having come from here. The booking itself happens on their site, under their privacy policy, with the details you type into their form. None of that reaches me: not your name, not your card, not your dates. What eventually reaches me is a number.

The same is true of the operator. If you follow a link from here to the chapel’s own booking site — and on tickets and booking I suggest that you do — you are on their site under their terms, and I see nothing of it at all.

Typefaces, and where the pictures come from

Two typefaces load from Google Fonts, which means your browser asks Google for them each time a page opens. Nothing else is fetched from anywhere else: the pictures, the stylesheet and the markup all come from this domain. Who photographed the chapel, and under which licence, is set out on photo credits.

Turning it off

Block cookies in your browser settings and every page here behaves exactly as it does now. The one casualty is the booking tag, and losing that costs me rather than you. If you want to know what is held about you, or want something deleted, write to me.