Cookies

CookieControl is the widget on this site that enables you to make choices about cookies (it’s the same one that the ICO use). Any cookie they use is used to remember your choice about cookies on this site, and if you have previously indicated a preference it will be stored in this cookie.

You can change your cookie preferences at any time by clicking on the ‘C’ icon. You can then adjust the available sliders to ‘On’ or ‘Off’. You may need to refresh your page for your settings to take effect.

Alternatively, most web browsers allow some control of most cookies through the browser settings. To find out more about cookies, including how to see what cookies have been set, visit www.aboutcookies.org or www.allaboutcookies.org.

Functional cookies are cookies that ensure the proper functioning of the Website (e.g. cookies for login or registration, language preferences) and their installation does not require your permission.

SIDCC to provide the identification of trusted web traffic.(source)

HSID to provide fraud prevention expires in 2 years (source)

wordpress_test_cookie is a functional, session cookie (source) to read if cookies can be replaced

woocommerce_items_in_cart is a functional, session cookie (source)

Woocommerce_cart_hash is a functional, session cookie to store items in the shopping cart (source)

wp_lang WordPress cookie to store language settings, and lasts for the session (source)

WordPress_test_cookie WordPress cookie to read if cookies can be placed, and lasts for the session (source)

cookie_notice_accepted to read if cookies can be placed – functional and persistent (source)

wp_woocommerce_session_[hash] Contains a unique code for each customer so that it knows where to find the cart data in the database for each customer.

In an effort to future-proof, we have listed far more cookies here than are found on this site, and you can find out what cookies are used by clicking on the padlock in the address bar. This is because 3rd party cookie, e.g., Google Analytics, YouTube, Etc. may change because the web developers are not in control of them.

• _ga to distinguish unique users by assigning a randomly generated number as a client identifier, and expires in 2 years (source)
• _ga_<container-id> Used to persist session state and expires in 2 years (source)
• _gali is used by Google Analytics to determine which links on a page are being clicked (source)
• _gat_* is used to limit the number of user requests in order to maintain a website’s performance, and it expires after 1 day. It does not store any user information (source)
• _gid to store and update a unique value for each page visited, and expires after 1 day (source)
• __utma This cookie is what’s called a “persistent” cookie, as it never expires. This cookie keeps track of the number of times a visitor has been to the site pertaining to the cookie, when their first visit was, and when their last visit occurred. Google Analytics uses the information from this cookie to calculate things like Days and Visits to purchase.
• __utmb and __utmc working together to calculate how long a visit takes.
• __utmb takes a timestamp of the exact moment in time when a visitor enters a site, and expires at the end of a session.
• __utmc takes a timestamp of the exact moment in time when a visitor leaves a site (it doesn’t know when a user closes their browser or leaves a website, so it waits 30 minutes for another pageview to happen, and if it doesn’t, it expires).
• _utmt stores the number of requests, and expires after 10 minutes.
• __utmz  This keeps track of where the visitor came from (e.g., what search engine you used, or link you clicked, or what keyword you used, and, where they were in the world when they accessed a website). It expires in 6 months. (source)

These cookies are used to collect information about how visitors use our website. We use the information to compile reports and to help us improve the website. The cookies collect information in a way that does not directly identify anyone. Read Google’s overview of privacy and safeguarding data and Google’s advertising and measurement cookies

__Secure-3PAPISID shows personalised adverts, duration 2 years (source)

__Secure-1PSIDCC shows personalised adverts, duration 2 years

SSID Google ads optimisation – duration 2 years (source)

SID Google ads optimisation – duration 2 years (source)

APISID Google ads optimisation – duration 2 years (source)

SAPISID Google ads optimisation – duration 2 years (source)

__Secure-1PAPISID Used by Google for targeting purposes to build a profile of the website visitor’s interests in order to show relevant & personalised Google advertising – duration 2 years (source)

__Secure-3PSIDCC Google cookie required to use website options and services – duration 1 year (source)

UULE Google – shows you results that are relevant to your location – expires in 6 months (source)

1P_JAR Google ads duration one month (source)

OGPC Google maps – duration 1 month (source)

SOCS – Google consent cookie – to store a user’s state regarding their cookies choices – duration 2 years (source)

AEC ensure that requests within a browsing session are made by the user, and not by other sites. Duration 6 months (source)

OGP = activate and track Google Maps functionality (source)

SEARCH_SAMESITE SameSite cookie attribute is used by browsers to identify how first- and Third-Party Cookies should be handled. Browsers can either allow or block such cookies depending on attribute and scenario.

Tk_tc by Jetpack to store the user’s usage history (source)

Tk_r3d by Jetpack for statistics, duration 3 days (source)

Tk_or by Jetpack for WooCommerce, duration 5 years (source)

These cookies remember your activities on a website, and they last for a session. A session starts when you launch a website or web app and ends when you leave the website or close your browser window). They contain information which is deleted after the session ends. Unlike other cookies, session cookies are never stored on your device, so they are also known as transient cookies, non-persistent cookies, or temporary cookies.

UserWay Accessibility tool (found in the bottom right corner on all pages)

_cq_duid

_cq_suid
They said “In regards to cookies, we don’t store any personal data, the widget only saves the session information from the user’s preferences e.g. A blind person who had the screen reader active. Someone with visual issues who set the font to be bigger.”

PHPSESSID
The PHPSESSID cookie is native to PHP and enables websites to provide functions across pages. It is used to establish a user session and to pass state data via a temporary cookie, which is commonly referred to as a session cookie (expires when you close your browser). (source)

wordpress_sec_ Is to provide protect against hackers and store account details (source)

WooCommerce: Cookies from WooCommece such as woocommerce_cart_hash and woocommerce_items_in_cart are linked to the items in your basket, so removing/declining them means that any purchases (free or paid) may not get to the checkout.

pmpro_visit Cookies from pmpro are linked to your membership to this site.

_grecaptcha to provide spam protection (source)

wordpress_[hash] This cookie is used to store your authentication details upon login and is limited to the admin area (source)

wp-settings-1 and wp-settings-time-1 are used to customize your view of admin interface, and possibly also the main site interface.

wordpress_logged_in_[hash] This cookie enables the interface to recognize you as a logged-in user and determine which account and preferences to use for various features (source)

wordpress_sec_[hash] used to store your authentication details (source)

tk_ai from Jetpack, stores a randomly-generated anonymous ID. This is only used within the admin area and is used for general analytics tracking (source)