Legal
Cookie policy
Two first-party cookies, analytics that works without cookies, and nothing third-party until you act. This page lists all of it — which is also why there’s no cookie banner.
Last reviewed 10 July 2026
The short version
This site sets two cookies, both first-party: a session cookie and an attribution cookie. Our analytics is configured to work without cookies. No third-party request leaves your browser on an ordinary page view — third-party services load only when you take an action that needs them, and that action is your consent.
Cookies we set
_jayex_session
Strictly necessary · Ends with your browsing session
Keeps your visit together: protects forms against forgery, holds the anonymous identifier our form measurement uses, and signs in administrators. The site cannot work safely without it.
jx_attrib
First-party attribution · 90 days
Records how you first arrived — campaign tags, referring site and landing page — so that if you send an enquiry we know which channel brought you. Written once on your first visit, read only if you enquire, and never sent to any other site.
Both are HttpOnly (scripts running in the page cannot read them) and restricted to this site.
Analytics without cookies
Page analytics run on Matomo, hosted on our own infrastructure and configured cookieless: it counts visits and pages in aggregate without setting any cookie or storing anything in your browser, and the data goes to no third-party analytics company. That configuration — not a banner — is how we keep analytics out of the consent problem.
Third-party services you trigger
Two things on this site involve a third party, and neither happens until you act:
- Spam protection on the enquiry form. When you begin filling in the form, Cloudflare Turnstile loads to tell people from bots. Until you start the form, no request is made to Cloudflare. Cloudflare’s handling of the technical signals Turnstile checks is described in its Turnstile Privacy Addendum.
- Embedded content you click to load. Where a page offers embedded third-party content — such as the demo-booking calendar — you see a placeholder first, and nothing loads from the third party until you choose to load it. That click is the consent act, and the third party’s own privacy terms apply from that point.
Why there’s no cookie banner
UK law (PECR) requires consent before storing things on your device that aren’t needed to provide the service you asked for. Our approach is to avoid needing that consent rather than to ask for it: analytics is cookieless, third-party content waits for your click, and what remains is the strictly necessary session cookie and the jx_attrib attribution cookie — first-party, holding no identity, used solely so an enquiry you choose to send carries its source. All of it is declared on this page.
Managing cookies
Your browser can refuse or delete cookies for this site at any time — the settings live under Privacy in every major browser. The site keeps working without them: forms still submit, and an enquiry sent without the attribution cookie simply attributes to the visit that sent it.
Questions about any of this? Ask us via the contact page — and see the privacy policy for what happens to enquiry data itself.