Cookie policy
How HALO ("we", "us" or "our") uses cookies and similar technologies on our website. This policy applies to all visitors and users who access our website, www.halotrust.org.
What are cookies?
Cookies are small pieces of information stored on the hard drive of a user's computer or internet-enabled device that contain information about the user.
A website can retrieve only the information that it has placed on your browser. It cannot retrieve information from other cookie files or any other information from your machine. Once the cookie is on your device, the site 'knows' that you've been there before and can then use that knowledge to tailor the experience that you have. The vast majority of websites use cookies.
What are they used for?
Cookies are used for many different functions including auto-filling forms, counting visitors, personalizing content, targeting advertising, recording user preferences (eg preferred text size) and for authentication and security.
Cookies help us provide you with a good experience when you browse our website and also allow us to improve our site.
Your rights
You have the right to choose whether or not to accept cookies. When you first use our website, we will ask you to consent to our use of cookies.
If you want to delete any cookies that are already on your device, please refer to instructions for your file management software to locate the file or directory that stores cookies.
You can block cookies by activating the setting on your browser that allows you to refuse the setting of all or some cookies. However, if you use your browser settings to block all cookies (including essential cookies) you may not be able to access all or parts of our website.
Please note that third parties (including, for example, advertising networks and providers of external services like web traffic analysis services) may also use cookies, over which we have no control. These cookies may include analytical/performance cookies or targeting cookies. We recommend that you check the relevant third party's cookie policy for information about any cookies that may be used.
To find out more about cookies, including how to see what cookies have been set and how to manage and delete them, visit All About Cookies.
Changes
We may need to update this cookie policy in the future and so encourage you to review this policy periodically to stay informed about how we are using cookies. This cookie policy was last updated in June 2025.
This policy should be read alongside, and in addition to, our terms of use and our privacy policy.
Cookies we use and what they do
Hotjar
These cookies enable us to run website surveys using Hotjar (an insights platform that helps organisations understand user behaviour on their websites).
|
Name |
Description |
|
|---|---|---|
|
_hjClosedSurveyInvites |
This cookie is set once a visitor interacts with a Survey invitation modal popup. It is used to ensure that the same invite does not re-appear if it has already been shown. |
|
|
_hjDonePolls |
This cookie is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not re-appear if it has already been filled in. |
|
|
_hjMinimizedPolls |
This cookie is set once a visitor minimises a Feedback Poll widget. It is used to ensure that the widget stays minimises when the visitor navigates through your site. |
|
|
_hjDoneTestersWidgets |
This cookie is set once a visitor submits their information in the Recruit User Testers widget. It is used to ensure that the same form does not re-appear if it has already been filled in. |
|
|
hjIncludedInSample |
This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels. |
|
|
_hjShownFeedbackMessage |
This cookie is set when a visitor minimises or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimised immediately if they navigate to another page where it is set to show. |
|
|
_hjid |
This cookie is set when the customer first lands on a page with the Hotjar script. |
|
|
_hjRecordingLastActivity |
This should be found in sessionStorage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records). |
|
|
_hjTLDTest |
When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. |
|
|
_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. |
|
|
_hjCachedUserAttributes |
This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. |
|
|
_hjLocalStorageTest |
This cookie is used to check if the Hotjar Tracking Script can use local storage. |