This site uses cookies – small text files that are placed on your machine to help the site provide a better user experience. In general, cookies are used to retain user preferences, store information for things like shopping carts, and provide anonymised tracking data to third party applications like Google Analytics. As a rule, cookies will make your browsing experience better. However, you may prefer to disable cookies on this site and on others. The most effective way to do this is to disable cookies in your browser. We suggest consulting the Help section of your browser or taking a look at the About Cookies website which offers guidance for all modern browsers.

View our Terms & Conditions and our privacy policy here. If you choose “Don’t track my usage” we will disable google analytics tracking for your session however other cookies outlined below will still be installed as they are integral to some of the basic functions and security of this website. If you do not wish for this website to install any cookies then please close the session by either visiting another website or closing your browser.

Here is more information on the cookies we use

Blog Comments

When you comment on the blog (NEWS section), cookies are stored on your computer. This is purely a convenience, so that you don’t need to re-type all your information again when you want to leave another comment. Three cookies are set for comments:

  • comment_author
  • comment_author_email
  • comment_author_url

The commenter cookies are set to expire a little under one year from the time they’re set.

Ecommerce/Shop

When using our “Shop” a number of different cookies are used for convenience. Here are the details of the cookies in full.

  • woocommerce_cart_hash
  • woocommerce_items_in_cart
  • wp_woocommerce_session_

The first two cookies contain information about the cart as a whole and helps WooCommerce know when the cart data changes. The final cookie (wp_woocommerce_session_) contains a unique code for each customer so that it knows where to find the cart data in the database for each customer. No personal information is stored within these cookies.

Cloudflare

We use cloudflare to serve content to your location in the most efficient way possible. Cloudflare speeds up the website while also offering protection from malicious attacks. Cloudflare stores one cookie on your machine

  • _cfuid

The _cfduid cookie is used by Cloudflare to override any security restrictions based on the IP address the visitor is coming from. For example, if the visitor is in a coffee shop where there are a bunch of infected machines, but the visitor’s machine is known trusted, then the cookie can override the security setting. It does not correspond to any userid in the web application, nor does the cookie store any personally identifiable information.

Google Analytics

Google Analytics supports two JavaScript libraries (tags) for measuring website usage: analytics.js and ga.js. The following sections describe how each use cookies.

analytics.js – Cookie Usage

The analytics.js JavaScript library is part of Universal Analytics and uses first-party cookies to:

  • Distinguish unique users
  • Throttle the request rate

By default, this library sets cookies on the top level domain, excluding the leading dot, and sets the cookie path to the root level (/).
Note: The analytics.js library does not require setting cookies to transmit data to Google Analytics.

This library sets the following cookies:

Cookie Name: _ga Expiration Time: 2 years – Description: Used to distinguish users.
Cookie Name:_gat Expiration Time: 10 minutes – Description: Used to throttle request rate.

ga.js – Cookie Usage

The ga.js JavaScript library uses first-party cookies to:

  • Determine which domain to measure
  • Distinguish unique users
  • Throttle the request rate
  • Remember the number and time of previous visits
  • Remember traffic source information
  • Determine the start and end of a session
  • Remember the value of visitor-level custom variables

By default, this library sets cookies on the domain specified in the document.host browser property and sets the cookie path to the root level (/).

This library sets the following cookies: 

Cookie Name: __utma,  Expiration Time: 2 years from set/update
Description: Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics.

Cookie Name: __utmt,  Expiration Time: 10 minutes
Description: Used to throttle request rate.

Cookie Name:__utmb, Expiration Time: 30 mins from set/update
Description:Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.

Cookie Name: __utmc, Expiration Time: End of browser session
Description: Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit.

Cookie Name: __utmz, Expiration Time: 6 months from set/update
Description: Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.

Cookie Name: __utmv, Expiration Time: 2 years from set/update
Description: Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics.

Miscellaneous

Here is a list of miscellaneous cookies that are stored against your session. These cookies are generated by 1. The server (our host provider), 2. specific plugins or widgets,

  • _distillery:  Used for measuring video views – Expires a the end of the browsing session
Cookie NameCookie CategoryDescriptionDuration
wordpress_2WordPress cookie for a logged in user.session
wordpress_logged_in_2WordPress cookie for a logged in usersession
wordpress_test_2WordPress cookie for a logged in usersession
wordpress_test_cookie2WordPress test cookiesession
wp-settings-1Wordpress also sets a few wp-settings-[UID] cookies. The number on the end is your individual user ID from the users database table. This is used to customize your view of admin interface, and possibly also the main site interface. 1 year
wp-settings-time-2Wordpress also sets a few wp-settings-{time}-[UID] cookies. The number on the end is your individual user ID from the users database table. This is used to customize your view of admin interface, and possibly also the main site interface. 1 year
PHPSESSID1To identify your unique session on the websitesession
SESS1To ensure that you are recognised when you move from page to page within the site and that any information you have entered is remembered.session
vc_widget_generic-expert2Cookie created by vCita - part of Fast Secure Contact form admin page1 year