Cookies

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.

A cookie is a small file of letters and numbers that we store on your browser or the hard drive of your computer if you agree. Cookies contain information that is transferred to your computer's hard drive. Once you agree, the file is added and the cookie can help us to analyse web traffic, let you know when you visit a particular site or store details of your preferences for when you visit a site.

Cookies allow web applications to respond to you as an individual. The web application can tailor its operations to your needs, likes and dislikes by gathering and remembering information about your preferences.

We use the following cookies:

Strictly necessary cookies. These are cookies that are required for the operation of our website. 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.
Analytical or 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.
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).
Targeting cookies. These cookies record your visit to our website, the pages you have visited and the links you have followed. We will use this information to make our website and the advertising displayed on it more relevant to your interests.

You can find more information about the individual cookies we use and the purposes for which we use them in the table below:

Cookie Name	Purpose	More information
Google Analytics	Analytical or performance	This website uses a statistical analytics tool called 'Google Analytics'. Using statistical analytics tools such as this helps us to anonymously identify how our website is being used by our visitors; we can then use this information to make decisions on how we can improve the usability of our site. Ultimately leading to a better experience for our visitors. The code behind the Google Analytics tool is owned and maintained by Google Inc. Google Analytics uses 'cookies', which are text files placed and stored on your computer to collect standard internet log information and visitor behaviour information in an anonymous form. The information generated by the cookie about your use of the website (including your IP address) is transmitted to Google. This information is then used to evaluate visitors' use of the website and to compile statistical reports on website activity for us. Google Analytics does not track or store any personally identifiable information of this site's visitors nor does it allow any third party to use collected data for this purpose. No data gathered from the site will be associated with any personally identifying information from any source as part of our use of the Google statistical analytics tools. Google will not associate your IP address with any other data held by Google. Neither us nor Google will link IP addresses with the identity of the computer user. To find out more about Google Analytics and the information we receive from it please visit: http://www.google.com/analytics/ https://support.google.com/analytics/answer/6004245 and refer to the section "Information for Visitors of Sites and Apps Using Google Analytics". To opt out of being tracked by Google Analytics across all websites please visit: http://tools.google.com/dlpage/gaoptout.
form_key	Necessary	Ensures visitor browsing security by preventing cross site request forgery. This cookie is essential for the security of the website an d visitor.
mage-banners-cache-storage	Necessary	This cookie is necessary for the cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser.
mage-banners-cache-storage	Necessary	This cookie is necessary for the cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser.
mage-banners-cache-timeout	Necessary	This cookie is necessary for the cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser.
mage-banners-storeId	Necessary	This cookie is necessary for the cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser.
mage-cache-sessid	Necessary	This cookie is used in context with load balancing - This optimizes the response rate between the visitor and the site, by distributing the traffic load on multiple network links or servers.
mage-cache-storage	Necessary	This cookie is used in context with load balancing - This optimizes the response rate between the visitor and the site, by distributing the traffic load on multiple network links or servers.
mage-cache-storage-section-invalidation	Necessary	This cookie is used in context with load balancing - This optimizes the response rate between the visitor and the site, by distributing the traffic load on multiple network links or servers.
mage-cache-timeout	Necessary	This cookie is necessary for the cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser.
rc::a	Necessary	This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website.
magepal-enhanced-ecommerce	Necessary	This cookie is necessary for the cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser.

Please note that the following third parties may also use cookies, over which we have no control. These named third parties may include, for example, advertising networks and providers of external services like web traffic analysis services. These third party cookies are likely to be analytical cookies or performance cookies or targeting cookies:

Google Analytics

Hotjar

We use Hotjar in order to better understand our users’ needs and to optimize this service and experience. Full details can be found on our Privacy Policy page.

To function properly, Hotjar stores first-party cookies on your user's browser. Cookies set by the Hotjar script are as follows:

Name	Description	Duration	Data type
_hjClosedSurveyInvites	Hotjar cookie that is set once a user interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown.	365 days	Boolean true/false
_hjDonePolls	Hotjar cookie that is set once a user completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in.	365 days	Boolean true/false
_hjMinimizedPolls	Hotjar cookie that is set once a user minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site.	365 days	Boolean true/false
_hjShownFeedbackMessage	Hotjar cookie that is set when a user minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the user navigates to another page where it is set to show.	365 days	Boolean true/false
_hjSessionTooLarge	Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit.	Session	Boolean true/false
_hjSessionRejected	If present, this cookie will be set to '1' for the duration of a user's session, if Hotjar rejected the session from connecting to our WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues.	Session	Boolean true/false
_hjSessionResumed	A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection.	Session	Boolean true/false
_hjid	Hotjar cookie that is set when the customer 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.	365 days	UUID
_hjRecordingLastActivity	This should be found in Session storage (as opposed to cookies). This gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records).	Session	Numerical Value (Timestamp)
_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	Boolean true/false
_hjUserAttributesHash	User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated.	Session	Hash
_hjCachedUserAttributes	This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. Collected attributes will only be saved to Hotjar servers if the user interacts with a Hotjar Feedback tool, but the cookie will be used regardless of whether a Feedback tool is present.	Session	JSON
_hjLocalStorageTest	This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created.	Under 100ms	Boolean true/false
_hjIncludedInPageviewSample	This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit.	30 minutes	Boolean true/false
_hjIncludedInSessionSample	This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's daily session limit.	30 minutes	Boolean true/false
_hjAbsoluteSessionInProgress	This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.	30 Minutes	Boolean true/false
_hjFirstSeen	This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.	Session	Boolean true/false
_hjViewportId	This stores information about the user viewport such as size and dimensions.	Session	UUID
_hjRecordingEnabled	This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session.	Session	Boolean true/false

If you wish to tell Hotjar to not collect your data, instructions can be found on the Do Not Track page of Hotjar's website.

Cookies

Cookies

Hotjar

Important information