Cookie Policy
Last updated: 11 August 2026
1. What are cookies?
Cookies are small text files a website saves on your device when you visit it. They're used to remember things like whether you're signed in, your theme preference, and to keep the platform secure. Similar technologies (local storage, session storage) work in much the same way and are covered by this policy.
2. Strictly necessary cookies
CHAIR SOFTWARE LTD(“CHAIR”) sets the cookies below to keep the platform running: sign-in, security, your theme preference. Under UK PECR Regulation 6, strictly necessary cookies do not require prior consent and you cannot opt out of them while using the platform.
| Name | Purpose | Lifetime |
|---|---|---|
chair_session | Keeps you signed in. HttpOnly, Secure, SameSite=Lax. Without it you have to log in on every page load. | 30 days |
chair_theme | Stores your light / dark mode preference so the platform doesn't flash the wrong theme on load. | 1 year |
3. Analytics cookies (with your consent)
We use Google Analytics 4 to understand which pages and features visitors actually use, so we can prioritise what to improve. These cookies are only set if you tap Accepton the cookie banner. If you reject (or don't respond), GA still receives anonymised pageviews from your browser but does not set any cookies and cannot link visits together across sessions. You can change your mind at any time via the Cookie settings link in our footer.
| Name | Purpose | Lifetime |
|---|---|---|
_ga | Google Analytics: distinguishes unique visitors. Anonymised IP. Set only after you accept analytics cookies. | 2 years |
_ga_3JTFCSNH5L | Google Analytics 4: per-property session state. Anonymised IP. Set only after you accept analytics cookies. | 2 years |
chair_cookie_consent_v1 | Local storage entry recording your consent choice so we don't re-ask on every page load. | 12 months |
We use Google Consent Mode v2, which means GA tags respect your choice in real time; there's no delay between you rejecting and the cookies stopping.
4. Advertising cookies (with your consent)
We run ads to reach professionals looking for booking software. With your consent we use Google Ads cookies, and on our pre-launch page the Meta pixel, to work out which of those ads actually led to someone signing up, so we can stop paying for the ones that don't. These are set only if you accept advertising cookies. If you reject (or don't respond), our Google Ads tags still run in cookieless mode and report an estimated conversion count to Google, but nothing is stored on your device and you are not added to any remarketing audience. We do not sell your personal data.
| Name | Purpose | Lifetime |
|---|---|---|
_gcl_aw | Google Ads: stores the click identifier from an ad you clicked, so a later sign-up can be attributed to that ad. Set only after you accept advertising cookies. | 90 days |
_gcl_ls | Google Ads: local storage entry used by the same conversion linker when a cookie cannot be set. | 90 days |
_fbp | Meta pixel: a random browser identifier used to match a waitlist sign-up back to the Facebook or Instagram ad that brought you here. Set only on our pre-launch page, and only after you accept advertising cookies. | 90 days |
_fbc | Meta pixel: stores the click identifier Meta appends to an ad link (fbclid) for the same purpose. Set only if you arrived from a Meta ad, on the same terms as above. | 90 days |
The Meta pixel is handled more strictly than the Google tags: unlike Google Ads it has no cookieless mode, so we do not load it at all until you accept advertising cookies. Reject, or ignore the banner, and nothing is requested from Meta and nothing about your visit reaches them. If you accept and later change your mind, we stop sending events and delete the two cookies above.
Separately, and regardless of your cookie choice, we record the ad click identifier against your account when you sign up as a professional through one of our ads. That is first-party data we hold under legitimate interests to measure our own marketing spend, not a cookie, and it is covered by our privacy policy.
5. Third-party cookies
When you interact with certain features, third parties we use may set their own cookies. We do not control these; they're governed by each provider's privacy policy.
- Stripe: payment processing and fraud prevention on pages that show a checkout or card form. See stripe.com/cookie-settings.
- Cloudflare: security cookie (
__cf_bm) used to distinguish humans from bots and protect the platform from abuse. See cloudflare.com/privacypolicy. - Google: only if you choose to sign in with Google OAuth, Google may set cookies during the sign-in flow. See policies.google.com/technologies/cookies.
- Meta (Facebook / Instagram): only on our pre-launch page, and only if you accept advertising cookies, the Meta pixel described in section 4. See facebook.com/policies/cookies.
6. What we do NOT use
- No advertising cookies at all unless you accept them. If you reject advertising, Google Ads runs in cookieless mode via Consent Mode v2: it reports an estimated conversion to Google but sets nothing on your device.
- No tracking pixel anywhere on the platform itself. The one exception is the Meta pixel on our pre-launch page (section 4), which is not loaded unless you accept advertising cookies. No TikTok, X, LinkedIn, Pinterest or Reddit pixel, anywhere, ever.
- No social-media tracking widgets embedded in the site.
- No Google Signals (the cross-device user-graph that GA4 offers as opt-in).
7. Managing your choice
You can change or withdraw your consent to analytics or advertising cookies at any time by clicking Cookie settings in the footer. Doing so will re-open the banner with your current choice pre-filled, and the change takes effect immediately: no page reload is needed for the tags to stop.
You can also block or delete cookies in your browser settings:
- Chrome: Settings → Privacy and security → Cookies and other site data
- Safari: Settings → Privacy
- Firefox: Settings → Privacy & Security → Cookies and Site Data
- Edge: Settings → Cookies and site permissions
Blocking the chair_session cookie will prevent you from signing in. Blocking chair_thememeans the platform will default to your system theme each load. Blocking analytics cookies has no effect on the platform's functionality.
8. Changes to this policy
If we change which cookies we use, we'll update this page and bump the “Last updated” date above. Material changes will be communicated by email or a banner on the platform.
9. Contact
Questions about cookies or this policy: support@getchair.co.uk.
See also our Privacy Policy for details on how we handle personal data more broadly.