Cookies are small pieces of information stored by your browser. This site uses storage for requested features such as secure booking access and event checkout. You can remove cookies in your browser, although doing so may end a booking session.
Booking and website operation
- cbs_booking_access: a secure, HTTP-only identifier created after you verify your emailed code. It gives access to bookings for that email address for up to 30 minutes. It contains no booking details and is removed when you finish viewing bookings.
- wp_woocommerce_session_…: remembers the event booking session when you begin checkout. WooCommerce normally keeps this session for up to two days. Booking selection cookies such as woocommerce_items_in_cart and woocommerce_cart_hash may also be used during a checkout session.
- WordPress login cookies: used when an authorised user signs in to administer the site. Customers do not need a WordPress account to view bookings. Login duration depends on the sign-in and “remember me” choice.
Other services
When you choose online payment, checkout loads WooPayments and Stripe payment features. Observed payment security cookies include __stripe_mid, __stripe_sid and m. Stripe may also load hCaptcha security checks, which can use cookies such as __cf_bm, __cflb and hmt_id. Availability and duration vary with the payment method and security checks; see Stripe’s cookie information and hCaptcha’s privacy information. Apple Pay and Google Pay may load their own payment features where supported. These services are used for the requested payment and fraud prevention.
MailPoet provides the newsletter form. Optional subscriber engagement and sales tracking are disabled. Ordinary browsing and the newsletter form did not set optional tracking cookies during our checks.
The custom theme hosts its fonts locally; payment-provider interfaces may request their own assets. Social buttons are ordinary links, rather than embedded social feeds. Google Calendar synchronisation takes place between the website server and Google and does not add a visitor calendar cookie. Optional WooCommerce sales attribution and the public Jetpack tracking script are disabled by the new events plugin.
If optional tracking is added later, we will explain it here and provide the required choices before it runs. For questions about your information, read our Privacy Policy or contact Steph.