Our Cookie Policy

Our Cookie Policy

Version 1.1 – 28th November 2023

What are cookies?

Cookies are small text files that are stored on your computer or mobile device.

Why we use cookies

We use cookies principally because we want to make our websites and mobile applications user-friendly, and we are interested in anonymous user behaviour.

The www.ilivestock.co.uk website uses a number of suppliers who set cookies on its behalf in order to deliver various services.

Listed below is information about the cookies used, as well as information on how to opt-out.

How to control and delete cookies

Duradiamond Software Ltd will not use cookies to collect personal information about you.

To limit or block the cookies which are set by Duradiamond Software Ltd, you can amend your browser's privacy settings.

The Help function within your web browser will explain how this is done.

Please note that if you disable cookies you will be unable to use some or all of our services and the functionality of the website may degrade.

Visit About Cookies to find out how to limit or block cookies on an array of different browsers.

There are details on how to delete cookies as well as general information about them.

For information on how to do this on your mobile phone you will need to refer to the manufacturer's guide.

List of Duradiamond Software Ltd cookies

  • Google cookie descriptions from Google Analytics

    device-uuid

    A token set by the iLivestock portal as part of its user authentication system

    COOKIECONSENT_STATUS

    This cookie keeps track of users choice to accept cookies or not via the pop-up

    _gid

    This cookie from Google Analytics is used to distiguish site visitors

    _ga

    This cookie from Google Analytics is used to distiguish site visitors

    _gat

    Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm <property-id>

    Intercom cookie descriptions from Intercom

    intercom-session-t8qfmn5l

    Allows visitors to see any conversations they've had on Intercom websites.

    intercom-device-id-t8qfmn5l

    Allows users to access their conversations and have data communicated on logged out pages for 1 week.

    intercom-id-t8qfmn5l

    Used to identify the device interacting with the Messenger in order to improve security.

    Hotjar cookie descriptions from Hotjar cookies help page

    _hjSessionUser_3618840

    Set when a user first lands on a page. Persists the Hotjar User ID which is unique to that site. Hotjar does not track users across different sites. Ensures data from subsequent visits to the same site are attributed to the same user ID.

    _hjFirstSeen

    Identifies a new user’s first session. Used by Recording filters to identify new user sessions.

    _hjSession_3618840

    Holds current session data. Ensures subsequent requests in the session window are attributed to the same session.

    _hjIncludedInSessionSample_3618840

    Set to determine if a user is included in the data sampling defined by your site's daily session limit.

    _hjAbsoluteSessionInProgress

    Used to detect the first pageview session of a user. 30 minutes duration, extended on user activity. Boolean true/false data type.

    _hjIncludedInPageviewSample

    Set to determine if a user is included in the data sampling defined by your site's pageview limit.

    _hjHasCachedUserAttributes

    Enables us to know whether the data set in _hjUserAttributes Local Storage item is up to date or not.

    _hjUserAttributesHash

    Enables us to know when any User Attribute has changed and needs to be updated.

    _hjUserAttributes

    Stores User Attributes sent through the Hotjar Identify API.

    hjViewportId

    hjActiveViewportIds

    Stores user active viewports IDs. Stores an expirationTimestamp that is used to validate active viewports on script initialization.

    _hjSessionTooLarge

    Causes Hotjar to stop collecting data if a session becomes too large. Determined automatically by a signal from the server if the session size exceeds the limit.

    _hjSessionResumed

    Set when a session/recording is reconnected to Hotjar servers after a break in connection.

    _hjCookieTest

    Checks to see if the Hotjar Tracking Code can use cookies. If it can, a value of 1 is set.

    _hjLocalStorageTest

    Checks if the Hotjar Tracking Code can use Local Storage.

    _hjSessionStorageTest

    Checks if the Hotjar Tracking Code can use Session Storage. If it can, a value of 1 is set.

    _hjTLDTest

    We try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. Enables us to try to determine the most generic cookie path to use, instead of page hostname.

    _hjRecordingEnabled

    Set when a Recording starts. Read when the Recording module is initialized to see if the user is already in a recording in a particular session.

    _hjClosedSurveyInvites

    Set when a user interacts with a Link Survey invitation modal. Ensures the same invite does not reappear if it has already been shown.

    _hjDonePolls

    Set when a user completes an on-site Survey. Ensures the same Survey does not reappear if it has already been filled in.

    _hjMinimizedPolls

    Set when a user minimizes an on-site Survey. Ensures that the Survey stays minimized when the user navigates through your site.

    _hjShownFeedbackMessage

    Set when a user minimizes or completes a Feedback widget. Ensures the Feedback widget will load as minimized if the user navigates to another page where it is set to show.

Third-party cookies on our website

These are from the various suppliers whose services we use to deliver services on our website.

  • Intercom

    Intercom powers our contact form, help centre, and live chat functionality.

    Cookie definitions and how to opt out of Intercom cookies can be found at the Intercom's cookie page.

  • Google

    Google cookies involve monitoring site performance and advertising.

    Further information about Google cookies and how to opt out can be found here

  • Shopify

    Shopify powers our shop and checkout functionality.

    Cookie definitions and how to opt out of Shopify cookies can be found at the Shopify cookie page.

  • Stripe

    We use Stripe to process the transactions through which we take payment for the plan you purchase

    Cookie definitions and how to opt out of Stripe cookies can be found at the Stripe cookie page.

  • Hotjar

    We use Hotjar in order to better understand our users’ needs and to optimize this service and experience. Hotjar is a technology service that helps us better understand our users’ experience (e.g. how much time they spend on which pages, which links they choose to click, what users do and don’t like, etc.) and this enables us to build and maintain our service with user feedback. Hotjar uses cookies and other technologies to collect data on our users’ behavior and their devices. This includes a device's IP address (processed during your session and stored in a de-identified form), device screen size, device type (unique device identifiers), browser information, geographic location (country only), and the preferred language used to display our website. Hotjar stores this information on our behalf in a pseudonymized user profile. Hotjar is contractually forbidden to sell any of the data collected on our behalf. For further details, please see the ‘about Hotjar’ section of (https://help.hotjar.com/hc/en-us/categories/115001323967-About-Hotjar)[Hotjar’s support site].

    Cookie definitions and how to opt out of Hotjar cookies can be found at the Hotjar cookie page.