Write your search here
  • FAQs
  • Claim Journey
  • Serious Injury
  • INK

Our cookie policy

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.

We use cookies, pixel tags or action tags for various purposes, including collating anonymous aggregated information that is used to manage and plan enhancements to our user experience, and statistic gathering of our user demographic. We are continually looking to adopt and implement new practices and technologies in order that we may improve your user experience. We may update this Cookie Policy from time to time with details of new cookies.

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. Hotjar cookies apply only to user of the INK customer portal. Details of the cookies we currently use on our website are shown below:-

Cookie Name Purpose More information
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
Minster Law Site Cookie Acceptance AllowCookies This cookie is used to store whether a user has accepted the use of cookies on the Minster Law website
Hotjar _hjSessionUser_{site_id}. Ensures data from subsequent visits to the same site are attributed to the same user ID. 365 days
Hotjar _hiFirstSeen Identifies a new user’s first session. 30 minutes
Hotjar _hjRecordingLastActivity Updated when a user recording starts and when data is sent to the server (the user performs an action that Hotjar records). Duration: session
Hotjar _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.

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 Enables us to know when any User Attribute has changed and needs to be updated. Duration: 2 minutes, extended every 30 seconds
Hotjar _hjHasCachedUserAttributes Enables us to know whether the data set in _hjUserAttributes Local Storage item is up to date or not. 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 _hjSessionStorageTest Checks if the Hotjar Tracking Code can use Session Storage. If it can, a value of 1 is set.

Data stored in _hjSessionStorageTest has no expiration time, but it is deleted almost immediately after it is created.

Duration: under 100 minutes
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: 2 minutes duration, extended every 30 seconds
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: 2 minutes duration, extended every 30 seconds
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 extended on user activity
Hotjar _hjUserAttributes Stores User Attributes sent through the Hotjar Identify API. No end
Hotjar hjViewportId Stores user viewport details such as size and dimensions. Duration: Session
Hotjar hjActiveViewportIds Stores user active viewports IDs.

Stores an expiration Timestamp that is used to validate active viewports on script initialization.

Hotjar _hjSession_{site_id} Holds current session data.

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

Duration: 30 minutes, extended on  user activity
Hotjar _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.

Duration: 1 hour
Hotjar _hjSessionResumed Set when a session/recording is reconnected to Hotjar servers after a break in connection. Duration: session
Hotjar _hjCookieTest Checks to see if the Hotjar Tracking Code can use cookies. If it can, a value of 1 is set.

Deleted almost immediately after it is created.

Duration: under 100 minutes
Hubspot hubspotutk

__hstc

__hssrc

__hssc

These cookies are used to monitor website traffic, including the number of visitors to the site, where visitors have come to the site from and the pages they visited. We use the information to compile reports and to help us improve the site.

Visitors will be tracked anonymously, unless:

A visitor fills out a form, in which case HubSpot will associate their previous page views based on the tracking cookie. If the email address filled in the form is associated with an existing contact, this visitor will be identified as the contact.

– HubSpot will attribute page views to a contact if the contact clicks a link in a tracked marketing email which directs to the website.

Click here for an overview of cookies.