Cookies & technologies

Netlify Web Analytics

Netlify derives page views, broad location information and visitor counts from requests made to its content-delivery network. Its Web Analytics feature does not add client-side code or cookies. Normal web-server requests still involve technical information, which is explained in our privacy notice.

Functional services

If you choose a language, we store a functional chw_language cookie for one year so the website remembers that choice. It does not track you across websites. If you have not chosen a language, the site may use your browser language and an approximate country inferred from the request to suggest a language; that automatic choice is not stored in a cookie.

If you choose a price currency, we store a functional chw_currency cookie for one year to remember your choice across pages and visits. It contains only GBP, EUR or USD and is not used for tracking. The currency you select is shown again at order review and sent to Stripe Checkout.

The public website does not currently load advertising pixels or a separate browser-based analytics service. The administration area uses Netlify Identity for authorised editors; authentication may need functional storage when an editor signs in. Our public pages no longer initialise that identity widget.

Forms send the details you choose to provide to Formspree when you submit them. Paid checkout opens Stripe's hosted website after you choose to continue, where Stripe's own privacy and cookie information applies. External destinations may use their own technologies.

Booking calendars

We offer two Cal.com booking calendars in popups on this website. Neither is loaded when you first open a page. Choosing a call opens the calendar and connects your browser to Cal.com, which may use its own cookies and technologies. If the popup cannot load, you can use the direct booking link instead. We review the booking provider's behaviour as part of our regular privacy checks.

If our technology changes

We will review this notice and the need for consent before introducing non-essential cookies, pixels or similar technologies. Where consent is required, we will not load those technologies before a visitor has chosen to allow them, and we will provide a way to change that choice.