Legal

Cookies & Embedded Content

What We Set

The Cookies We Actually Set

The short version: we set a handful of cookies to sign you in and keep the site secure, and Google Analytics sets two more only if you allow it. Nothing on this site follows you anywhere else.

A cookie is a small file a website asks your browser to keep. Ours do one job: they hold your sign-in together. They are all set by us, on our own domain, and none of them is read by anyone else.

While you are signed in

  • authjs.session-token — this is your sign-in. It tells us it is still you as you move from page to page. Lasts up to 30 days, or until you sign out. In your browser it will show a __Secure- prefix on the live site.
  • authjs.csrf-token — a one-use token that proves a form was submitted from our site and not from someone else's. It is what stops a hostile page from changing your details in the background. Disappears when you close the browser. Shows as __Host-authjs.csrf-token on the live site.
  • authjs.callback-url — remembers which page you were heading for, so signing in returns you there instead of dumping you on the dashboard. Disappears when you close the browser.
  • authjs.pkce.code_verifier and authjs.state — only if you choose to sign in with Google. They tie the start and the end of that handshake together so it cannot be hijacked. They last about fifteen minutes and are then gone.

All five are strictly necessary: they exist because you asked to sign in, they are not used to build a picture of you, and the site cannot work without them. Under the UK's cookie rules that means we do not need your permission for them — and we could not honour a refusal anyway without breaking sign-in.

Kept on your device, but not a cookie

  • clubgt.consent — your answer to the cookie question, stored in your browser's local storage rather than in a cookie, so it is never sent to us with a request. It stays until you change it, withdraw it, or clear your browser data.
  • clubgt-member-tour-v1 (and clubgt-operator-tour-v1 for our own team) — remembers that you have already seen the short welcome tour of the dashboard, so it does not reappear every time you sign in. Only ever set behind sign-in.
  • A service worker cache — a copy of pages and images so the site loads quickly and survives a patchy signal on tour. Personal documents are marked never-store and are not cached.

Only if you allow analytics

  • _ga — set by Google Analytics. A random number that lets it tell one visit from the next, so we count visitors rather than page loads. Lasts up to 2 years.
  • _ga_ followed by our property code — set by Google Analytics alongside it, holding the state of your current visit. Lasts up to 2 years.
  • _clck — set by Microsoft Clarity. A random number that ties your visits together, so our click and scroll maps count people rather than page loads. Lasts up to 1 year.
  • _clsk — set by Microsoft Clarity alongside it, joining the pages of one visit into a single recording. Lasts 1 day.

None of these is set, and neither script is even downloaded, until you switch on Analytics. Turn it off again and they are deleted. We see only totals (how many people read a page, from which country, on what kind of device) and anonymous click, scroll and recording data with anything typed into forms masked, never which person did what. Advertising features are switched off, and the signed-in areas of the site are never counted.

What we do not set

No advertising or retargeting pixel. No tag manager. No cross-site identifier of any kind.

Your Choices

The Four Categories

The banner offers four switches. One of them, Marketing, controls nothing today, and we would rather say so than let you assume otherwise.

  • Strictly necessary — the five cookies above. Always on, and the only ones we cannot turn off.
  • Embedded content — lets tour films load from YouTube and the moving route map load from Google Maps. These are other companies' players, so loading one shares your IP address with Google. Off until you say yes.
  • Analytics — lets Google Analytics count visits (which pages are read, roughly where visitors come from and what device they use) and Microsoft Clarity show where people click and how far they scroll. Off until you say yes; the cookies they set are listed above.
  • Marketing — would let advertising networks build a profile from your visit. We use nothing of the kind today, and have no plans to.

Refusing everything is a single click, from the same place and at the same size as accepting everything — we have not hidden it behind a settings screen. If you make no choice at all, everything except the strictly necessary cookies stays off.

Other Companies

Content We Borrow From Google

Two parts of this site are built from someone else's content. Both sit behind the embedded content switch, and neither loads until you allow it.

  • YouTube — the tour films and the film posters on the homepage. We use the youtube-nocookie.com address, which sets no cookies until playback begins, but the request still tells Google your IP address, your browser and which page you came from. Google is its own data controller for that; what it does with it is governed by Google's privacy policy.
  • Google Maps — the route map that moves alongside the day-by-day schedule on a tour page. Loading the map script shares the same details with Google. Decline it and the day-by-day route is still written out in full underneath; you lose the moving map, not the information.

If you have declined, each blocked film or map is replaced by a placeholder the same size as the thing it stands in for, carrying a button that loads that one item on its own. Using it loads that film, that map or that picture once, and leaves your standing answer exactly as it was.

A few other names appear on the site but send nothing until you choose to click them: the WhatsApp bubble, and the Instagram, YouTube, Facebook and LinkedIn links in the footer are ordinary links. Nothing is requested from those companies while you read the page.

Behind the scenes we also use mapping suppliers that never see you: tour route maps are drawn on our servers by Geoapify, in Germany, and served from our own address. The country flags on our forms are served by us. Neither involves a request from your browser to anyone else.

Changing Your Mind

Change or Withdraw Your Answer

Consent is only worth something if it is as easy to take back as it was to give.

  • The Cookie settings link at the foot of every page reopens the preferences panel, where you can change any switch — or withdraw your answer altogether, which wipes the record and puts the question back to you.
  • Withdrawing puts things back. A film or a map you loaded earlier returns to its placeholder — loading one item once never quietly becomes a permanent yes.
  • Your browser settings can block or clear cookies for this site at any time. Clearing site data also clears your saved cookie choice, so we will ask again on your next visit.
  • Signing out removes the session cookie.

Questions about any of this, or something here that does not match what you see in your browser? Write to [email protected] and we will look into it. How we handle personal data more generally is set out in our Privacy Policy.