Website cookies distinguish visitors and help improve the site
Last updated Dec 22, 2025, the notice says its website uses cookies to distinguish a visitor from other users, to provide a good browsing experience and to improve the site. The passage does not state a legal basis for cookies or say which cookies load before a visitor makes a choice.
Details not recorded for this card
Supporting quotations
Cookie Notice
Last Updated: Dec 22, 2025
Our website uses cookies to distinguish you from other users of our website. This helps us to provide you with a good experience when you browse our website and also allows us to improve our site.
Not stated here
The notice does not name the operator in this passage, state a legal basis for cookie use, or say which cookie categories load before a visitor chooses.
Data Access & Collection · Context
A cookie is a small file downloaded on a site visit
The notice defines a cookie as a small file of letters and numbers downloaded to a visitor's computer when visiting a website. It says cookies can remember preferences, record shopping-basket contents and count how many people view a site.
Details not recorded for this card
Supporting quotations
A cookie is a small file of letters and numbers that is downloaded on to your computer when you visit a website. Cookies are used by many websites and can do a number of things, e.g. remembering your preferences, recording what you have put in your shopping basket, and counting the number of people looking at a website.
Data Access & Collection · Company practice
Strictly necessary cookies are required and always enabled
The notice says strictly necessary cookies are required to operate the website and are always enabled because the site will not work properly without them. It gives logging into secure areas, using a shopping cart and using e-billing services as examples.
Details not recorded for this card
Supporting quotations
Strictly necessary cookies. These are cookies that are required for the operation of our website. These essential cookies are always enabled because our website won’t work properly without them. They include, for example, cookies that enable you to log into secure areas of our website, use a shopping cart or make use of e-billing services.
Qualifications & exceptions
The 'always enabled' statement is specific to the strictly necessary category.
Not stated here
The notice does not say whether any cookie in this category can be refused individually.
Cross-references
narrowed by (model-proposed): Cookie preferences can be changed in the Privacy Preference Center — The notice says preferences can be changed at any time, but separately says strictly necessary cookies are always enabled; the general preference control therefore does not extend to that category.
Data Access & Collection · Company practice
Performance cookies count visitors and show how they move
Performance cookies let the site recognise and count visitors and see how visitors move around it. The notice says this helps improve how the site works, including helping users find content, tracking errors and improving performance insights.
Details not recorded for this card
Supporting quotations
Performance cookies. These allow us to recognise and count the number of visitors and to see how visitors move around our website when they are using it. This helps us to improve the way our website works, for example, by ensuring that users are finding what they are looking for easily, track errors and improve insights into how the website is performing.
Not stated here
The notice does not name the analytics providers here or say whether performance cookies are optional.
Cross-references
contrast (model-proposed): Segment analytics cookies sit under Functionality — The performance category is defined as recognising and counting visitors and seeing how they move around the site, while the functional table lists Segment analytics cookies described as counting visits and tracking traffic metrics; the notice does not explain the different placement.
contrast (model-proposed): Fraud and security cookies are listed as performance cookies — The performance category is defined around visitor counting and movement, while the performance table lists fraud-detection and security cookies; the notice does not explain how they fit the category.
Data Access & Collection · Company practice
Functionality cookies remember visitors and personalise content
Functionality cookies recognise a visitor who returns to the site. The notice says they personalise content, greet the visitor by name, remember preferences such as language or region, and deliver content and features tailored to the visitor.
Details not recorded for this card
Supporting quotations
Functionality cookies. These are used to recognise you when you return to our website. This enables us to personalise our content for you, greet you by name and remember your preferences (for example, your choice of language or region) and deliver content and features tailored to you.
Not stated here
The notice does not say whether functionality cookies are optional or which preferences they store.
Data Access & Collection · User right or choice
Cookie preferences can be changed in the Privacy Preference Center
The notice says visitors can change cookie preferences at any time by managing privacy settings in the Privacy Preference Center. It also links to aboutcookies.org and allaboutcookies.org for information on cookies and how to see which ones are set.
Details not recorded for this card
Supporting quotations
Change your cookie preferences at any time by managing your privacy settings in the Privacy Preference Center. To find out more about cookies, including how to see what cookies have been set, visit www.aboutcookies.org or www.allaboutcookies.org.
Not stated here
The extracted text does not link to the Privacy Preference Center or say which categories it controls; strictly necessary cookies are separately described as always enabled.
Cross-references
narrows (model-proposed): Strictly necessary cookies are required and always enabled — The notice says preferences can be changed at any time, but separately says strictly necessary cookies are always enabled; the general preference control therefore does not extend to that category.
qualifies (model-proposed): Consent and opt-out choices are stored in strictly necessary cookies — The Privacy Preference Center statement is qualified by the table description of OneTrust consent records, which store the cookie categories and whether visitors gave or withdrew consent.
Data Access & Collection · Procedure
Browser help links and a Google Analytics opt-out are offered
The notice links to cookie-management instructions for Chrome, Edge, Firefox, Internet Explorer, Opera and Safari, and says information on other browsers is available from browser developers. It also links to Google's Analytics opt-out add-on for tracking across all websites.
Details not recorded for this card
Supporting quotations
Find out how to manage cookies on popular browsers:
The browser and analytics help pages are linked but their text is not part of this source, so the card does not describe their instructions.
Data Access & Collection · Context
Cookie list is presented as category tables with names, descriptions and terms
After the category descriptions, the notice sets out a Cookie List. The first table is captioned Strictly Necessary Cookies and the second Functional Cookies, each with columns for Cookie, Description and Term. This card describes the list's structure; the following cards describe the listed practices.
Details not recorded for this card
Supporting quotations
Cookie List
Strictly Necessary Cookies
Cookie
Description
Term
Functional Cookies
Cookie
Description
Term
Not stated here
The notice does not say whether the list is exhaustive or whether every cookie the site sets appears in it.
Data Access & Collection · Company practice
Consent and opt-out choices are stored in strictly necessary cookies
Four cookies in the strictly necessary table record consent or opt-out choices: CookieConsentPolicy and LSKey-c$CookieConsentPolicy apply end-user consent preferences, OptanonConsent stores the cookie categories and whether consent was given or withdrawn, and opt_out tracks a decision not to have data used for tracking and personalisation. The OptanonConsent description says its normal lifespan is one year, while its Term entry says Session.
Details not recorded for this card
Supporting quotations
CookieConsentPolicy
Used to apply end-user cookie consent preferences set by our client-side utility.
364 days
LSKey-c$CookieConsentPolicy
Used to apply end-user cookie consent preferences set by our client-side utility.
1 Years
OptanonConsent
This cookie is set by the cookie compliance solution from OneTrust. It stores information about the categories of cookies the site uses and whether visitors have given or withdrawn consent for the use of each category. This enables site owners to prevent cookies in each category from being set in the user’s browser, when consent is not given. The cookie has a normal lifespan of one year, so that returning visitors to the site will have their preferences remembered.
Session
opt_out
This cookie is used to track the user's decision to opt out of cookies on the website, indicating they have chosen not to have their data used for tracking and personalisation purposes.
1 Years
Qualifications & exceptions
All four cookies are placed in the strictly necessary category, which the notice says is always enabled.
Not stated here
The notice does not say which consent record governs which cookie category, or how a choice made in the Privacy Preference Center maps to these cookies.
Cross-references
qualified by (model-proposed): Cookie preferences can be changed in the Privacy Preference Center — The Privacy Preference Center statement is qualified by the table description of OneTrust consent records, which store the cookie categories and whether visitors gave or withdrew consent.
Data Access & Collection · Company practice
Page-view, Cloudflare and Salesforce cookies support site operation
Three strictly necessary cookies count page views by unauthenticated users against licence usage, identify trusted Cloudflare traffic, and route Salesforce requests for sticky sessions. Their listed terms are 364 days, Session and a few seconds respectively.
Details not recorded for this card
Supporting quotations
pctrk
Used to count page views by unauthenticated users against license usage.
364 days
__cfruid
Cookie associated with sites using CloudFlare, used to identify trusted web traffic.
Session
sfdc-stream
Used to properly route server requests within Salesforce infrastructure for sticky sessions.
A few seconds
Not stated here
The pctrk description refers to 'license usage' without saying whose licence or what it meters.
Data Access & Collection · Company practice
Anonymous-session and load-balancer cookies are strictly necessary
JSESSIONID maintains an anonymous server session, renderCtx stores site parameters in a client's session, and GAESA keeps session affinity with a Google Cloud Platform load balancer. Their listed terms are Session, Session and one month.
Details not recorded for this card
Supporting quotations
JSESSIONID
Used to maintain an anonymous user session by the server.
Session
renderCtx
Used to store site parameters in the session for reuse across requests by a single client for functionality and performance reasons.
Session
GAESA
Session affinity cookie set with Google Cloud Platform Load balancer.
1 Months
Data Access & Collection · Company practice
Mobile routing, cookie testing, localisation and analytics are strictly necessary
The remaining strictly necessary cookies route mobile visitors to a mobile version, test whether the browser blocks or allows cookies, maintain an anonymised server session, propagate localisation for logged-in users, and record an anonymous session for public visitor analytics. sb.anonymousId2 is described as analytics but sits in the always-enabled strictly necessary category.
Details not recorded for this card
Supporting quotations
DrupalVisitorMobile
Determines whether the visitor is originating from a mobile device and routes the user to a mobile version, if applicable.
Session
cookietest
Checks to see if the browser is set to block or allow cookies.
Session
session
This cookie is typically used to maintain an anonymized user session by the server.
A few seconds
Affirm-Locale
Strictly necessary cookie for logged in - used to propagate localization
1 Years
sb.anonymousId2
Anonymous session for public visitor analytics for data user is interacting with
1 Years
Not stated here
The notice does not explain why an anonymous-analytics session identifier is treated as strictly necessary.
Data Access & Collection · Company practice
Functional table begins with help-centre and bot-verification cookies
The functional table begins with a Zendesk help-centre session cookie and a Cloudflare clearance cookie used to verify that a visitor or system has solved a bot challenge. Their listed terms are Session and one year.
Details not recorded for this card
Supporting quotations
_help_center_session
This cookie aids in session for the Zendesk guide.
Session
cf_clearance
Used to verify user is not a bot; user/system has solved a challenge successfully
1 Years
Not stated here
The notice does not explain how bot verification counts as a functionality cookie rather than a strictly necessary one.
Data Access & Collection · Company practice
Segment analytics cookies sit under Functionality
Four Segment cookies appear under Functional: ajs_anonymous_id counts visits for analytics, __tld__ finds a visitor's top-level domain, ajs%3Atest counts visits and traffic metrics, and ajs%3Acookies supports site performance and functionality. The notice separately defines performance cookies as those that recognise and count visitors and show how they move around the site.
Details not recorded for this card
Supporting quotations
ajs_anonymous_id
These cookies are generally used for Analytics and help count how many people visit a certain site by tracking if you have visited before. This cookie has a lifespan of 1 year.
1 Years
__tld__
From Segment Analytics.js library; this cookie helps to figure out a top-level domain for a user.__tld__
Session
ajs%3Atest
This performance cookie counts visits and tracks other website traffic-related metrics. Cookies in this domain have a lifespan of 1 year.
1 Years
ajs%3Acookies
This cookie supports use, service performance, and functionality of websites. Cookies in this domain have a lifespan of 1 year.
1 Years
Performance cookies. These allow us to recognise and count the number of visitors and to see how visitors move around our website when they are using it. This helps us to improve the way our website works, for example, by ensuring that users are finding what they are looking for easily, track errors and improve insights into how the website is performing.
Qualifications & exceptions
The table places these analytics cookies in the functional category.
The descriptions give their terms as one year, Session, one year and one year.
Not stated here
The notice does not explain why these analytics cookies are grouped as functional rather than performance cookies.
Cross-references
contrast (model-proposed): Performance cookies count visitors and show how they move — The performance category is defined as recognising and counting visitors and seeing how they move around the site, while the functional table lists Segment analytics cookies described as counting visits and tracking traffic metrics; the notice does not explain the different placement.
Data Access & Collection · Company practice
Functional table lists marketing and testing cookies
The functional table includes _ssc, associated with TailTarget, a data management platform that provides customer data for targeted advertising; _pinterest_ct_ua, set for Pinterest Marketing; and chameleon-profile-id, used for testing. The listed terms are one day, one year and Session.
Details not recorded for this card
Supporting quotations
_ssc
This domain is associated with TailTarget, a Brazilian data management platform (DMP) that provides customer data to help in targeted advertising.
1 Days
_pinterest_ct_ua
This cookie is being set in relation to Pinterest Marketing
1 Years
chameleon-profile-id
This cookie is used for testing.
Session
Qualifications & exceptions
These rows sit under the Functional Cookies caption, not the Targeting Cookies caption.
Not stated here
The notice does not explain why marketing and testing cookies are grouped as functional.
Data Access & Collection · Company practice
Fingerprint and visitor-identification cookies appear under Functionality
The functional table includes two Fingerprint cookies that assist with device recognition and fraud prevention, with listed terms of 364 days, and visitorId, which identifies a unique visitor to personalise features and content from the visitor's preferences and browsing history, with a one-year term.
Details not recorded for this card
Supporting quotations
fpjs_group_id
Used by Fingerprint: assists with device recognition and fraud prevention.
364 days
fpjs_user_id
Used by Fingerprint: assists with device recognition and fraud prevention.
364 days
visitorId
This cookie is used to identify a unique visitor to enhance the user experience by enabling personalized features and content based on the visitor's preferences and browsing history.
1 Years
Qualifications & exceptions
These rows sit under the Functional Cookies caption.
Not stated here
The notice does not explain why device-recognition and fraud-prevention cookies are grouped as functional.
Data Access & Collection · Company practice
Internal analytics and rate-limiting cookies appear under Functionality
BrowserId_sec logs secure browser sessions and visits for internal-only product analytics, and _cfuvid lets Cloudflare distinguish users who share an IP address so it can enforce rate limits. Both rows are listed under Functional, with terms of one year and Session.
Details not recorded for this card
Supporting quotations
BrowserId_sec
Used to log secure browser sessions/visits for internal-only product analytics.
1 Years
_cfuvid
The _cfuvid cookie is used by Cloudflare to distinguish individual users who share the same IP address for the purpose of enforcing rate limiting rules.
Session
Not stated here
The notice does not say what 'internal-only product analytics' measures or who can see it.
Data Access & Collection · Company practice
Performance table starts with Mixpanel, Google Analytics and Datadog cookies
The performance table lists analytics and measurement cookies, including Mixpanel, Google Analytics' _gid and _gat, and Datadog's _dd_s. Their descriptions say they identify users and measure site performance and usage, distinguish visitors with a client identifier, throttle request rates, and group events from a user session. The listed terms are one year, a few seconds, 10 minutes and four hours.
Details not recorded for this card
Supporting quotations
Performance Cookies
Cookie
Description
Term
mp_xxxxxxx_mixpanel
Used to identify individual users. This tool is used to measure site performance and usage patterns
1 Years
_gid
This cookie name is associated with Google Universal Analytics. This appears to be a new cookie and as of Spring 2017 no information is available from Google. It appears to store and update a unique value for each page visited._gid
A few seconds
_gat
This cookie name is associated with Google Universal Analytics, according to documentation it is used to throttle the request rate - limiting the collection of data on high traffic sites. It expires after 10 minutes.
10 minutes
_dd_s
Datadog Cookie used to group all events generated from a unique user session across multiple pages. It contains the current session ID, whether the session is excluded due to sampling, and the expiration date of the session. The cookie is extended for an extra 15 minutes every time the user interacts with the website, up to the maximum user session duration (4 hours).
4 hours
Data Access & Collection · Company practice
Adobe and Piwik cookies measure visits and performance
The performance table also lists Adobe Site Catalyst's s_cc, which checks whether the browser enables cookies, and Piwik's _pk_ses* and _pk_id* pattern cookies, described as tracking visitor behaviour and measuring site performance. Their terms are Session, 30 minutes and one year.
Details not recorded for this card
Supporting quotations
s_cc
This cookie is associated with the Adobe Site Catalyst. It determines whether cookies are enabled in the web browser.
Session
_pk_ses*
This cookie name is associated with the Piwik open source web analytics platform. It is used to help website owners track visitor behaviour and measure site performance. It is a pattern type cookie, where the prefix _pk_ses is followed by a short series of numbers and letters, which is believed to be a reference code for the domain setting the cookie.
30 minutes
_pk_id*
This cookie name is associated with the Piwik open source web analytics platform. It is used to help website owners track visitor behaviour and measure site performance. It is a pattern type cookie, where the prefix _pk_id is followed by a short series of numbers and letters, which is believed to be a reference code for the domain setting the cookie.
1 Years
Data Access & Collection · Company practice
Google Analytics and Hotjar cookies sit in the performance table
Google Analytics' _ga distinguishes unique users by assigning a randomly generated client identifier. Hotjar's _hjSessionUser and _hjSession cookies persist a user ID and session data, and _hjTLDTest checks which cookie path to use across subdomains. The listed terms are Session, Session, a few seconds and Session.
Details not recorded for this card
Supporting quotations
_ga
This cookie name is associated with Google Universal Analytics. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the site's analytics reports.
Session
_hjSessionUser_xxxxxx
Hotjar cookie that is set when a user first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
Session
_hjSession_xxxxxx
A cookie that holds the current session data. This ensures that subsequent requests within the session window will be attributed to the same Hotjar session.
A few seconds
_hjTLDTest
When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.
Session
Data Access & Collection · Company practice
A second Mixpanel cookie measures site performance and usage
The performance table lists mp_5cb8cc91-e409-41c2-af0d-b337e1d966a7_perfalytics, described as identifying individual users to measure site performance and usage patterns, with a listed term of one year.
Used to identify individual users. This tool is used to measure site performance and usage patterns
1 Years
Data Access & Collection · Company practice
Shopify, session-tracking and Affirm analytics cookies end the performance table
The performance table ends with a Shopify analytics cookie whose term is 364 days, fs_lua and fs_uid for user session tracking and error debugging (one hour and one year), axp-override for Affirm analytics (Session), and Google Analytics' _ga_ cookie for identifying and tracking an individual session (one year).
Details not recorded for this card
Supporting quotations
This cookie is associated with Shopify's analytics suite.
364 days
fs_lua
Used for user session tracking and error debugging
1 hour
axp-override
Used for Affirm analytics purposes.
Session
_ga_xxxxxxxxxx
Used by Google Analytics to identify and track an individual session with your device.
1 Years
fs_uid
Used for user session tracking and error debugging