Cookie Policy

 

 

What are cookies?

A cookie is a small, often encrypted text file, located in browser directories (they can also be known as browser cookies or tracking cookies). They are placed on the computer or other device by the website that is being viewed in order to improve the ease of access to and use of that site. 

 

How we use cookies

They are used by us to help our website users navigate our website efficiently and like most websites we use cookies to capture certain information about our site’s users.  

These are cookies you might come across on our website: 

  • Necessary cookies - We operate our website through HubSpot, who use cookies that help us with the day to day running of our website. These help from remembering your cookie preferences to protecting us from malicious users! These cookies are strictly necessary and do not require consent.  

  • Analytical cookies - When you visit our website, as well as HubSpot cookies, we set Google Analytics cookies which help measure the number of visitors to the site, see how they navigate and which areas they access. We also use Hotjar cookies, which records and stores anonymised data and helps us understand how our users interact with our site, how much time they spend on pages, what they interact with, device profile and geographic location. For more information please see the Hotjar documentation.

    We use this information to help us to develop new content and to improve the way our website works. These cookies are optional, and they can be blocked. 

  • Functionality cookies - Ever wondered how websites remember your language, where you’re from or maybe even your name? This is down to functionality cookies that help our website remember who you are. We don’t really use these cookies often on our website, but they can be useful for creating a more personalised experience. Again, these can be blocked. 

  • Targeting cookie - These are commonly used for advertising purposes. We don’t really use them here at Law 365; however, these are the reasons you might see Ads on Facebook for holiday homes when you’ve just been on EasyJet.com searching for Portugal flights! 

  • Third-Party cookies- Other third-party sites which are linked to and can be accessed from our site such as You Tube, Twitter and LinkedIn also set a variety of cookies over which we have no control. 

 

You can find more information about the individual cookies we use and the purposes for which we use them in the table below:


Name 

Typical Content 

Description 

Expires  

HubSpot cookies

 

 

 

__hs_opt_out 

It contains the string "yes" or "no". 

  • Necessary cookie 
  • HubSpot 
  • This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again. 

13 months 

__hs_do_not_track 

It contains the string "yes". 

  • Necessary cookie 
  • HubSpot 
  • This cookie can be set to prevent the tracking code from sending any information to HubSpot. 

13 months  

__hs_initial_opt_in 

It contains the string "yes" or "no". 

  • Necessary cookie 
  • HubSpot 
  • This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode. 

7 days 

__hs_cookie_cat_pref 

It contains data on the consented categories. 

  • Necessary cookie 
  • HubSpot 
  • This cookie is used to record the categories a visitor consented to. 

13 months  

hs_ab_test 

It contains the id of the A/B test page and the id of the variation that was chosen for the visitor. 

  • Necessary cookie 
  • HubSpot 
  • This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before. 

It expires at the end of the session. 

__cfruid 

It contains a randomly generated number 

It expires at the end of the session. 

__hstc 

It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). 

  • Analytical cookie 
  • HubSpot 
  • The main cookie for tracking visitors. 

13 months  

Hubspotutk 

It contains an opaque GUID to represent the current visitor. 

  • Analytical cookie 
  • HubSpot 
  • This cookie keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts. 

13 months 

__hssc 

It contains the domain, view count (increments each pageview in a session), and session start timestamp. 

  • Analytical cookie 
  • HubSpot 
  • This cookie keeps track of sessions. 

30 minutes 

__hssrc 

It contains the value "1" when present. 

  • Analytical cookie 
  • HubSpot 
  • Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. 

It expires at the end of the session. 

Google Analytics cookies

 

 

 

_ga 

It contains pageviews and a randomly generated number 

  • Analytical cookie 
  • Google Analytics 
  • To count and track pageviews. 

2 years 

_gid 

It contains pageviews and a randomly generated number 

  • Analytical cookie 
  • Google Analytics 
  • To count and track pageviews. 

24 hours 

Hotjar cookies

 

 

 

hjSessionUser{site_id} 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.
  • Analytical cookie 
365 days
_hjSession{site_id} 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.
  • Analytical cookie 
30 minutes
_hjClosedSurveyInvites 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.
  • Analytical cookie 
365 days
_hjDonePolls 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.
  • Analytical cookie 
365 days
_hjMinimizedPolls 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.
  • Analytical cookie 
365 days
_hjShownFeedbackMessage 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.
  • Analytical cookie 
365 days
_hjSessionTooLarge 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.
  • Analytical cookie 
Session
_hjSessionRejected 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.
  • Analytical cookie 
Session
_hjSessionResumed A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection.
  • Analytical cookie 
Session
_hjid 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 behaviour in subsequent visits to the same site will be attributed to the same user ID.
  • Analytical cookie 
365 days
_hjRecordingLastActivity 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).
  • Analytical cookie 
Session
_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.
  • Analytical cookie 
Session
_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.
  • Analytical cookie 
Session
_hjCachedUserAttributes 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.
  • Analytical cookie 
Session
_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.
  • Analytical cookie 
Under 100ms
_hjIncludedInPageviewSample This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit.
  • Analytical cookie 
30 minutes
_hjIncludedInSessionSample 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.
  • Analytical cookie 
30 minutes
_hjAbsoluteSessionInProgress This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.
  • Analytical cookie 
30 Minutes
_hjFirstSeen 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.
  • Analytical cookie 
Session
_hjViewportId This stores information about the user viewport such as size and dimensions.
  • Analytical cookie 
Session
_hjRecordingEnabled 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.
  • Analytical cookie
Session

 


OK with this?

We hope that this information gives you confidence about our use of cookies. By selecting the button below, you can reconfigure your use of analytics, advertisement and functionality cookies.

 

 

To deactivate the use of third-party advertising cookies, you may visit the relevant consumer page to manage the use of these types of cookies.

If you want to prevent Google Analytics cookies being set, you may install the Google Analytics Opt-Out Browser Add-On.

You can block cookies by activating the setting on your browser that allows you to refuse the setting of all or some cookies. Alternatively, you can adjust your cookie preferences for our website by clicking above. 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.

For more information about cookies and how to disable them, please visit www.allaboutcookies.org or https://www.youronlinechoices.com/ 

 

Also see our: