COOK and COOKies

 

COOKies (Cookie Policy)

Cookies are small text files saved on your device when you visit a website. We also use similar technologies (like tags/pixels and browser storage such as localStorage/sessionStorage) that can store or read information on your device in a similar way.

 

2) Why we use them

We use COOKies and similar technologies to:

• Keep the essentials working (session, login, basket, checkout)

• Remember your choices (like your cookie preferences)

• Power useful features (like address lookup and customer support chat)

• Protect the site (spam/abuse protection)

• Improve the experience (analytics, experience analytics, and A/B testing - only if you say yes)

 

3) Your choices (consent)

Strictly necessary COOKies

Some COOKies are strictly necessary - they’re needed to deliver the service you’re asking for (like holding your basket together while you browse). These are always on.

Optional COOKies

Everything else (analytics, experience analytics, experimentation, marketing) is optional and is only used if you consent in our cookie settings.

If you choose “no thanks” to optional COOKies:

• the site should still work

• but we’ll have less insight to help improve journeys and spot what’s not working as well as it could

 

4) How to manage your COOKies

• On-site cookie settings: use our cookie controls to accept, reject, or tailor optional cookies. We remember your preference using a cookie called CookieSettings.

• Browser settings: you can also block or delete cookies via your browser. (Blocking strictly necessary cookies may stop parts of the site - especially checkout - from working properly.)

 

5) Our COOKie menu (what we use)

Cookie names and what appears on your device can vary depending on:

• what you consent to

• which pages you visit (checkout, maps, support chat)

• vendor configuration and updates

Where we can be specific, we list cookie names below. Where a provider can use cookies and/or browser storage, we say so.

 

A) Strictly necessary (always on)

These keep the site running and shopping working:

• ASP.NET_SessionId (COOK)

Keeps your session working as you move around the site.

• Customer (COOK)

Helps with sign-in and account features (like order history).

• ShoppingBasketID (COOK)

Keeps your basket linked to you.

 

B) Security (always on when it runs)

• _GRECAPTCHA (Google reCAPTCHA) Set when reCAPTCHA runs to help protect the site from automated abuse.

 

C) Functional (helps key features)

• CookieSettings (COOK)

Stores your cookie preferences.

• pcaInstallationId (Loqate address lookup)

Used by our postcode/address lookup integration.

Note: The service is now Loqate (GBG). Some legacy scripts (and this cookie name) still use older “PCA/PostcodeAnywhere” naming.

• Zendesk (customer support widget)

If you use our support widget, Zendesk may use cookies and browser storage to keep it working (remembering settings, keeping the session stable, routing messages).

Depending on configuration, you may see cookies/storage keys such as:

• ZD-suid, ZD-buid (Zendesk identifiers used by Zendesk products)

• ZD-store, ZD-widgetOpen (widget settings/state - often browser storage)

• __zlcmid (used in some Zendesk Chat setups)

 

D) Third-party content (only when you use it)

• Google Maps (e.g. store finder)

When maps load, Google may set cookies such as:

PREF, NID, HSID, SSID, APISID, SAPISID, SID

• Facebook social sharing (Meta)

If you use sharing features on product pages, Meta may set cookies to enable that feature.

 

E) Analytics & experience analytics (optional - only if you consent)

These help us understand how the site is used and improve it.

Google Analytics 4 (GA4)

Common GA4 cookies include:

• _ga

• _ga_ (the suffix varies by GA4 property)

Microsoft Clarity

Clarity cookies can include:

• _clck (first-party)

• _clsk (first-party)

• and Microsoft cookies that may appear depending on configuration/context: CLID, ANONCHK, MR, MUID, SM

Contentsquare

Contentsquare cookies can include (among others):

• _cs_id (typically ~13 months)

• _cs_s (short-lived session cookie)

• _cs_c, _cs_cvars

• module/config-dependent cookies such as _cs_s_ctx, _cs_i, _cs_ex, _cs_optout, _cs_mk_*, _cs_rl_* Some Contentsquare capability-check cookies may be created and removed quickly during initialisation.

 

F) A/B testing & optimisation (optional - only if you consent)

Convert.com

Convert cookies used for experiments can include:

• _conv_v

• _conv_s

• _conv_r

• _conv_sptest (very short-lived, used for certain test types)

 

G) Personalisation / CRM (optional - only if you consent)

Optimove

Optimove’s Web SDK may store identifiers and session state using cookies and/or browser storage (often local storage) to recognise returning visitors and support personalisation and measurement.

Exact cookie/storage key names vary by configuration and modules enabled.

 

6) International transfers and privacy

Some of our providers may process data outside the UK. Where required, we use appropriate safeguards, and you can read more in our Privacy Notice.

 

7) Contact

If you have questions about our COOKies, please contact us using the details in our Privacy Notice.

 

8) Changes to this policy

We’ll update this page if we change the “COOKie recipe” - for example, if we add/remove tools or change how they’re configured.