What is a Cookie?
A cookie identifies your computer to a server that then enables information to be stored on the hard drive of your computer. Cookies allow a computer to be identified as corresponding to one that has accessed another website or visited a website previously. Cookies are commonly used on the Internet and do not harm your computer system.
What Cookies do we use?
There are two main types of cookies we use:-
- Session Cookies – these only exist for the duration of your visit to our website and are deleted when you leave the Website.
- Persistent Cookies – these stay on your computer until they expire or are deleted.
In addition to this, if you use any Minster Law mobile applications to access your claim information, these applications capture information such as your IP address, gender, browser type and device type. We capture this information as part of our data security measure, but also to ensure that we test our applications to cover all browsers/ devices being used, and to pinpoint user interface errors. More information about how we use your data can be found within our Privacy Notice.
How can I stop cookies and what effect will this have?
You can stop cookies from being deployed on your computer by configuring your browser not to accept them or opt-out. Please refer to your browser’s ‘help’ facility. If cookies are already on your system, you can delete them – For more information on cookies and deletion of cookies please visit: www.allaboutcookies.org/manage-cookies/
Please be aware that restricting or deleting certain cookies can result in difficulties when navigating around websites. Details of the cookies we currently use on our website are shown below:-
|Google Analytics||_utma _utmb _utmc _utmz||These cookies are used to collect information about how visitors use our site. We use the information to compile reports and to help us improve the site. The cookies collect information in an anonymous form, including the number of visitors to the site, where visitors have come to the site from and the pages they visited.||Click here for an overview of privacy at Google|
|Hotjar||_hjClosedSurveyInvites||Hotjar cookie is set once a visitor interacts with a survey invitation modal pop-up. It is used to ensure that the same invite does not reappear if it has already been shown.||Duration: 365 days|
|Hotjar||_hjDonePolls||Hotjar cookie that is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not reappear if it has already been filled in.||Duration: 365 days|
|Hotjar||_hjMinimizedPolls||Hotjar cookie that is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site.||Duration: 365 days|
|Hotjar||_hjShownFeedbackMessage||Hotjar cookie that is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the visitor navigates to another page where it is set to show.||Duration: 365 days|
|Hotjar||_hjid||Hotjar cookie 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 behaviour in subsequent visits to the same site will be attributed to the same user ID.||Duration: 365 days|
|Hotjar||_hjRecordingLastActivity||This should be found in Session storage (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).||Duration: session|
|Hotjar||_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.||Duration: session|
|Hotjar||_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.||Duration: session|
|Hotjar||_hjCachedUserAttributes||This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool.||Duration: session|
|Hotjar||_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.||Duration: under 100 mins|
|Hotjar||_hjIncludedInPageviewSample||This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site’s pageview limit.||Duration: 30 mins|
|Hotjar||_hjIncludedInSessionSample||This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site’s daily session limit.||Duration: 30 mins|
|Hotjar||_hjAbsoluteSessionInProgress||This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.||Duration: 30 mins|