Cookie policy
Cookies in use on this site
Like most websites, Idox plc and all its group companies (the "Idox Group") collects certain information automatically when you visit our websites, read our emails, or interact with us. We typically collect this information through a variety of tracking technologies, including cookies, beacons, and similar technology (which we'll refer to collectively as 'cookies').
Throughout this Cookie Policy we'll refer to our corporate website and any other Idox Group brand websites or subdomains and country-level domain variants that link to this Cookie Policy collectively as our "Site".
This statement explains what these technologies are and why we use them, as well as your rights to control our use of them.
If you would like to know what cookies are, or how to control or delete them, please visit: www.allaboutcookies.org for detailed guidance.
What are cookies?
Cookies are text files containing small amounts of information which are downloaded to your device when you visit a website. Cookies are then sent back to the originating website on each subsequent visit, or to another website that recognises that cookie. Cookies are useful because they allow a website to recognise a user's device. You can find more information about cookies at: www.allaboutcookies.org and www.youronlinechoices.com.
Why do we use cookies?
Cookies do lots of different jobs, like letting you navigate between pages efficiently, remembering your preferences, and generally improving the user experience.
We also use cookies to collect information about the way you use the website, for example: the site from which you came, the pages you visit, the links you click, how frequently you access the website, whether you open emails or click the links contained in emails, whether you access the website from multiple devices, etc. We also gather statistics around email opening and clicks using industry standard technologies including clear gifs to help us monitor and improve our emails.
There are different types of cookies and they all work in the same way. The list below describes the cookies we use on our site and why.
Strictly Necessary Cookies
These cookies enable core functionality of our website and cannot be disabled. These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
| Cookie name | Expiry | Purpose |
|---|---|---|
| .ASPXAUTH | Cookie expires after session. | This cookie is used to help website owners track visitor behaviour and measure site performance. |
| ASP.Net_SessionId | Cookie expires after session. Cookie can be persistent if the user ticks "Remember me?" option on log in screen. | This cookie is used to identify your unique session on the website. Typically used to maintain the integrity of your session while transacting. |
| CookieControl | 90 days | Cookie Control cookies. This cookie is set in order to remember the user's preferences in regards to cookies. |
| IDOX | Cookie expires after session. | We use this cookie so that we can display usage within our product and report this on request. |
| _idck | Cookie expires after session. | This cookie is used to help website owners track visitor behaviour and measure site performance. |
| _pk_ses.* | Cookie expires after session. | This cookie is used to identify your unique session on the website. |
| _Unique id | Cookie expires after session. | This cookie is used to help website owners track visitor behaviour and measure site performance. |
| __RequestVerificationToken | Cookie expires after session. | This cookie is used to help website owners track visitor behaviour and measure site performance. |
| __zlcmid | Cookie expires after session. | This cookie is used to enable the customer chat and messaging facility to function. |
Analytic Cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site and will not be able to monitor its performance.
Google Analytics
| Cookie name | Expiry | Purpose |
|---|---|---|
| _ga | 2 years | A unique ID is registered to generate statistical data on how user uses the product. |
| _gid | 24 hours | A unique ID is registered to generate statistical data on how user uses the product. |
| _gat | 1 minute | Google Analytics throttle request rate. |
Hotjar
| Cookie name | Expiry | Purpose |
|---|---|---|
| _hjSessionUser{site_id} | 365 days | Hotjar cookie that is set when a user 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. |
| _hjSession{site_id} | 30 minutes | A cookie that holds the current session data. This ensues that subsequent requests within the session window will be attributed to the same Hotjar session. |
| _hjClosedSurveyInvites | 365 days | 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. |
| _hjDonePolls | 365 days | 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. |
| _hjMinimizedPolls | 365 days | 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. |
| _hjShownFeedbackMessage | 365 days | 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. |
| _hjSessionTooLarge | Cookie expires after session | 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. |
| _hjSessionRejected | Cookie expires after session | 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. |
| _hjSessionResumed | Cookie expires after session | A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection. |
| _hjid | 365 days | 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. |
| _hjRecordingLastActivity | Cookie expires after session | 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). |
| _hjTLDTest | Cookie expires after session | 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. |
| _hjUserAttributesHash | Cookie expires after session | 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. |
| _hjCachedUserAttributes | Cookie expires after session | 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. |
| _hjLocalStorageTest | Under 100ms | 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. |
| _hjIncludedInPageviewSample | 30 minutes | This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit. |
| _hjIncludedInSessionSample | 30 minutes | 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. |
| _hjAbsoluteSessionInProgress | 30 Minutes | This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
| _hjFirstSeen | Cookie expires after session | 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. |
| _hjViewportId | Cookie expires after session | This stores information about the user viewport such as size and dimensions. |
| _hjRecordingEnabled | Cookie expires after session | 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. |
Heap
| Cookie name | Expiry | Purpose |
|---|---|---|
| _hp2_id.APP_ID | 13 months | User cookie (stores user_id, identity, other ids). |
| _hp2_ses_props.APP_ID | 30 minutes | Session properties cookie (stores timestamp and cookie domain/path). |
| _hp2_props.APP_ID | 13 months | Event properties cookie (stores properties set by addEventProperties API). |
| _hp2_hld.* | Cookie expires after session | Used to determine which domain a cookie can be set on (since public suffix domains block setting cookies on the top level). |
Other analytics
| Cookie name | Expiry | Purpose |
|---|---|---|
| _pk_id.* | 13 months | This cookie is used to help website owners track visitor behaviour and measure site performance. |
Marketing Cookies
There are no marketing cookies in use on this site.
Advertising cookies
There are no advertising cookies in use on this site.
What about other tracking technologies, like web beacons?
Cookies are not the only way to recognise or track visitors to a website. We may use other, similar technologies from time to time, like web beacons (sometimes called 'tracking pixels' or 'clear gifs').
Web beacons are tiny graphic files that contain a unique identifier that enables us to track the activity of anonymous and known prospects to our website, landing pages and web forms.
It helps us to monitor the traffic patterns of visitors from one page within our sites to another, to understand whether you have come to our sites from an online advertisement displayed on a third-party website, to improve site performance, and to measure the success of e-mail marketing campaigns.
Web Beacons used:
- /acton/bn/tracker
- ?vyemail=
How can I control cookies?
You can change your cookie preferences at any time here. 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.
Find out how to manage cookies on popular browsers:
To find information relating to other browsers, visit the browser developer's website.
To opt out of being tracked by Google Analytics across all websites, visit http://tools.google.com/dlpage/gaoptout.
How often will you update this Cookie Statement?
We may update this Cookie Statement from time to time in order to reflect, for example, changes to the cookies we use or for other operational, legal or regulatory reasons. Please therefore re-visit this Cookie Statement regularly to stay informed about our use of cookies and related technologies.
By using this website (through any device) you agree that this Cookie Policy applies to that use in addition to any other terms and conditions which may apply.
Where can I get further information?
If you have any questions about our use of cookies or other tracking technologies, please e-mail: privacy@idoxgroup.com.
Cookie Statement
Last updated: June 2022.