Cookies used by this website
What are Cookies?
Cookies are small pieces of data, stored in text files, that are stored on your computer or other device when a website is loaded within your chosen browser. They are widely used to ‘remember’ you and your preferences, either for a single visit (through a ’session cookie’) or for multiple repeat visits (using a ‘persistent cookie’). They ensure a consistent and efficient experience for visitors, and perform essential functions such as allowing users to register and remain logged in. Cookies may be set by the site that you are visiting (known as ‘first party cookies’), or by other websites who serve up content on that site (‘third party cookies’).
What is Cookie Control?
When (as the user) you consent to one of the optional cookie categories, Cookie Control will place a cookie to remember that decision. The name of the cookie will be the name of the category specified within the Cookie Control widget itself. That cookie will be removed when you (the user) revokes consent to that category.
What are ‘Strictly Necessary Cookies’?
These are the cookies that are essential for this website to perform its basic functions. These include those required to allow registered users to authenticate and perform account related functions, as well as to save the contents of virtual ‘carts’ on sites that have an e-commerce functionality.
Strictly Necessary Cookies are highlighted with a double asterisk (**) in the tables below:
Cookies set by WordPress
| Cookie Name | Description | Duration |
| wordpress_<hash> ** | On login, wordpress uses the wordpress_[hash] cookie to store your authentication details. Its use is limited to the admin console area, /wp-admin/ | 2 years |
| wordpress_logged_in_<hash> ** | After login, wordpress sets the wordpress_logged_in_<hash> cookie, which indicates when you’re logged in, and who you are, for most interface use. | Session |
| wp-settings-<time>-<UID> ** | WordPress 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. | Session |
| WordPress_google_apps_login ** | This cookie is set by the plugin ‘Google Apps Login for WordPress’ and may be present for users who login to WordPress via their Google or GSuite account. | Session |
| wordpress_test_cookie | Used to check whether your web browser is set to allow, or reject cookies. | Session |
| wpe-auth |
Cookies set by Google Analytics
| Cookie Name | Description | Duration |
| _ga | Used to distinguish users. | 2 years |
| _gid | Used to distinguish users. | 24 hours |
| _gat | Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>. | 1 minute |
| AMP_TOKEN | Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service. | 30 seconds to 1 year |
| _gac_<property-id> | Contains campaign related information for the user. If you have linked your Google Analytics and AdWords accounts, AdWords website conversion tags will read this cookie unless you opt-out. Learn more. | 90 days |
| _gaexp | Optimize 360 – Used to determine a user’s inclusion in an experiment and the expiry of experiments a user has been included in. | 90 days |
Cookies set by CloudFlare
| Cookie Name | Description | Duration |
| __cfduid ** | The __cfduid cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. | 1 years |
Cookies set by Hubspot
| Cookie Name | Description | Duration |
| _hs_opt_out | This cookie is used by the opt-in privacy policy to remember not to ask the user to accept cookies again. This cookie is set when you give users the choice to opt out of cookies. | 2 years |
| __hs_do_not_track | This cookie can be set to prevent the tracking code from sending any information to HubSpot. Setting this cookie is different from opting out of cookies, which still allows anonymized information to be sent to HubSpot. | 2 years |
| __hs_testcookie | This cookie is used to test whether the visitor has support for cookies enabled. | Session cookie |
| hs_ab_test | This cookie is used to consistently serve visitors the same version of an A/B test page that they’ve seen before. | Session cookie |
| hs_lang_switcher_choice | This cookie is used to consistently redirect visitors to the language version of a page in the language they’ve selected on this top-level private domain in the past (if such a language version exists). | |
| <id>_key | When visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login. The cookie name is unique for each password-protected page. | |
| Hs-messages-is-openhs-messages-hide-welcome-message | This cookie is used on the visitor UI side so HubSpot can determine/save whether the chat widget is open for future visits. It resets after 30 minutes to re-close the widget after 30 minutes of inactivity | (TTL 30 minutes) |
| __hstc | The main cookie for tracking visitors. It contains the domain, utk (see below), initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). | 2 years |
| hubspotutk | This cookie is used for to keep track of a visitor’s identity. This cookie is passed to HubSpot on form submission and used when de-duplicating contacts. | 10 years |
| __hssc | This cookie keeps track of sessions. This is used to determine if we should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp. | 30 min |
| __hssrc | Whenever HubSpot changes the session cookie, this cookie is also set. We set it to 1 and use it to determine if the user has restarted their browser. If this cookie does not exist when we manage cookies, we assume it is a new session. | None. Session cookie |
| messagesUtk | This cookie is used to recognize visitors who chat with you via the messages tool. If the visitor leaves your site before they’re added as a contact, they will have this cookie associated with their browser. If you have a history of chatting with a visitor and they return to your site later in the same cookied browser, the messages tool will load your conversation history with that visitor. |
Miscellaneous Cookies
| Cookie Name | Description | Duration |
| complianceCookie | Used to distinguish your acknowledgement of our website’s Cookie Banner and subsequent policy (this document). | 14 days |
How to change your Cookie preferences
The most popular web browsers typically provide additional tools to users for controlling or restricting cookies on their device. To find out more about cookies, including how to see what cookies have been set, you can visit www.aboutcookies.org.