Cookie Policy
Last updated: April 2026
1. What are cookies?
Cookies are small text files placed on your device when you visit a website. They help the site remember your preferences, keep you signed in, and understand how you use the service. Some cookies are set by us (first-party) and some by services we use (third-party).
2. How we use cookies
When you first visit Clhub, only strictly necessary cookies are active. You choose which additional categories to allow via the consent banner. You can change your preferences at any time using the cookie settings button that appears in the bottom-left of every page.
We use Google Consent Mode v2 to ensure that analytics and advertising services respect your consent choices in real time. Tags loaded through Google Tag Manager only collect data matching the categories you have granted.
3. Cookie categories
Essential (strictly necessary)
These cookies are required for the site to function. They handle authentication, session management, security, and remembering your cookie consent choice. They cannot be switched off.
| Cookie | Purpose | Duration | Type |
|---|---|---|---|
| sb-*-auth-token | Supabase authentication session | Session | First-party |
| clhub_consent | Stores your cookie consent preferences | 1 year | First-party |
| clhub_anon_id | Anonymous visitor identifier for consent audit trail | 1 year | First-party |
Analytics
These cookies help us understand how visitors use Clhub so we can improve the service. Data is collected anonymously via Google Analytics (loaded through Google Tag Manager).
| Cookie | Purpose | Duration | Type |
|---|---|---|---|
| _ga | Distinguishes unique users | 2 years | Third-party (Google) |
| _ga_* | Maintains session state for Google Analytics 4 | 2 years | Third-party (Google) |
| _gid | Distinguishes users within a 24-hour window | 24 hours | Third-party (Google) |
Marketing
These cookies are used by Google Ads to measure conversions (e.g. completed bookings) and to build audience segments. They are only activated if you grant marketing consent.
| Cookie / Signal | Purpose | Duration | Type |
|---|---|---|---|
| _gcl_au | Google Ads conversion linker | 90 days | Third-party (Google) |
| Conversion pixels | Track booking and purchase completions for ad campaigns | Session | Third-party (Google) |
Personalisation
These cookies allow services to tailor content to your interests. At present, Clhub does not deploy personalisation cookies, but the category is included so that future features can be enabled transparently under your consent.
4. Google Tag Manager
Clhub uses Google Tag Manager (GTM) to manage analytics and marketing tags. GTM itself does not set cookies, but the tags it loads (Google Analytics, Google Ads) may set cookies as described above. Individual hubs may also have their own GTM container for hub-specific analytics.
We implement Google Consent Mode v2 (Advanced), which means GTM loads on every page but tags operate in a restricted, cookieless mode until you grant consent. This allows basic measurement (e.g. anonymised page-view counts) without storing cookies on your device.
5. Managing your preferences
You can control cookies in several ways:
- Consent banner: When you first visit Clhub, a banner lets you accept all, reject all, or customise by category.
- Cookie settings button: After your initial choice, a small cookie icon appears in the bottom-left corner of every page. Click it to re-open the preferences panel at any time.
- Browser settings: Most browsers let you block or delete cookies. Note that blocking essential cookies will prevent sign-in.
6. Consent record-keeping
Every time you make or update a consent choice, we store a consent receipt containing:
- Your consent categories (which you granted or denied)
- The decision type, including updates and later withdrawals
- The timestamp of the choice and the latest activity timestamp for the active consent window
- The consent policy version plus the exact banner text and banner version shown at that time
- The privacy policy version and cookie policy version in force at that time
- The site domain where the choice was made
- Your Clhub profile ID (if signed in) or an anonymous visitor identifier
These records are pseudonymous and minimal. We do not store IP addresses or user agent strings in the consent receipt. We keep only the data needed to evidence what was chosen, when it was chosen, and what disclosure version was presented under UK GDPR and PECR.
The active consent window rolls forward while you keep using Clhub within a 12-month period. Once a consent record becomes inactive or is later withdrawn, we retain the minimal receipt for up to 6 years after that active period ends so we can evidence compliance if needed.
7. Third-party services
The following third-party services are used by Clhub. Only Google (via GTM) sets cookies — the others do not place cookies on your device:
- Google Tag Manager / Google Analytics / Google Ads — analytics and conversion tracking (cookies listed above)
- Supabase — authentication and database (essential cookies only)
- Stripe — payment processing (no tracking cookies)
- Vercel — hosting and image optimisation (no tracking cookies)
- Mailgun — transactional email delivery (no client-side cookies)
8. Changes to this policy
If we add new cookie categories or change how existing cookies are used, we will update this page and, where appropriate, re-prompt you via the consent banner by incrementing the consent version.
9. Contact us
For questions about this cookie policy or your consent preferences, contact privacy@clhub.dev.