Cookie Policy

Cookie policy

Our website (https://www.asolvi.com/) uses cookies to distinguish you from other users of our website. This helps us to provide you with a good experience when you browse our website and also allows us to improve our site.

A cookie is a small file of letters and numbers that we store on your browser or the hard drive of your computer if you agree. Cookies contain information that is transferred to your computer’s hard drive.

A cookie will typically contain a record of the website which issued it, its own name, and a value which is often a randomly generated unique number. A cookie will have a ‘lifetime’, which tells your browser when to delete it.

Types of Cookies

Different cookies are used for different purposes. The most common ones are as follows:

  • Strictly necessary cookies. These are cookies that are required for the operation of our website. They include, for example, cookies that enable you to log into secure areas of our website.
  • Analytical/performance cookies. They allow us to recognise and count the number of visitors and to see how visitors move around our website when they are using it. This helps us to improve the way our website works, for example, by ensuring that users are finding what they are looking for easily.
  • Functionality cookies. These are used to recognise you when you return to our website. This enables us to personalise our content for you, greet you by name and remember your preferences (for example, your choice of language or region).
  • Targeting cookies. These cookies record your visit to our website, the pages you have visited and the links you have followed. We will use this information to make our website more relevant to your interests. We may also share this information with third parties for this purpose.

There are also several different types of cookie. These are the most common ones:

  • Session cookies. Session cookies only last for the duration of your website visit. A web browser normally deletes session cookies when it quits.
  • Persistent cookies. Persistent cookies will outlast user sessions. If a persistent cookie has its maximum age set to 1 year, then, within the year, the initial value set in that cookie would be sent back to the server every time the user visited the server. This could be used to record a piece of information such as how the user initially came to this website. For this reason persistent cookies are also called tracking cookies.
  • Secure cookies. Secure cookies are only used when a browser is visiting a server via HTTPS, ensuring that the cookie is always encrypted when transmitting from client to server.
  • First-party cookies. First-party cookies are cookies set with the same domain (or its subdomain) in the browser's address bar.
  • Third-party cookies. Third-party cookies are cookies set with different domains from the one shown on the address bar (i.e. the web pages on that domain may feature content from a third-party domain - e.g. Google Maps or YouTube). Privacy setting options in most modern web browsers allow you to block third-party tracking cookies.

The Cookies We Use

The table below provides an overview of the cookies used on our website, their purpose and when they expire.

Cookie Name Purpose Expiration
_hjClosedSurveyInvites _hjClosedSurveyInvites Hotjar cookie that is set once a visitor interacts with an external link survey invitation. It is used to ensure that the same invite does not reappear if it has already been shown. 365 days
_hjDonePolls Hotjar cookie that is set once a visitor 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. 365 days
_hjMinimizedPolls _Hotjar cookie that is set once a visitor minimizes an on-site survey widget. It is used to ensure that the widget stays minimized when the visitor navigates through our site. 365 days
_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. 365 days
_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 our site on the browser. This ensures that behaviour in subsequent visits to our site will be attributed to the same user ID. 365 days
_hjRecordingLastActivity This should be found in session storage (as opposed to cookies). This gets updated when a visitor recording starts and the visitor performs an action that Hotjar records. Session
_hjTLDTest This Hotjar script is used to determine the most generic cookie path that can be used so that cookies can be shared across subdomains (where applicable). Session
_hjUserAttributesHash This Hotjar cookie is cached for the duration of the session in order to know when a user attribute has changed and needs to be updated. Session
_hjCachedUserAttributes This cookie stores user attributes which are sent through the Hotjar, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar feedback tool. Session
_hjLocalStorageTest This cookie is used to check if the Hotjar tracking script can use local storage. The data stored by this cookie is deleted almost immediately after it is created. Under 100ms
_hjIncludedInPageviewSample This cookie is set to let Hotjar know whether a visitor is included in the data sampling defined by our site's pageview limit. 30 minutes
_hjIncludedInSessionSample This cookie is set to let Hotjar know whether a visitor is included in the data sampling defined by our site's daily session limit. 30 minutes
_hjAbsoluteSessionInProgress This cookie is used to detect the first pageview session of a visitor. 30 minutes
_ga Used to distinguish users 2 years
_gid Used to distinguish users 24 hours
_gat Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>. 1 minute
AMP_TOKEN Contains a token that can be used to retrieve a client ID. Other possible values indicate opt-out, inflight request or an error retrieving a client ID. 0 seconds to 1 year
_gac_<property-id> Contains campaign related information for the user, and can be used (unless you opt out) to link your Google Analytics and Google Ads accounts. Google Ads website conversion tags will read this cookie unless you opt-out. 90 days
__utma Used to distinguish users and sessions. The cookie is updated every time data is sent to Google Analytics. 2 years
__utmt Used to throttle request rate. 10 minutes
__utmb Used to determine new sessions/visits. The cookie is updated every time data is sent to Google Analytics. 30 minutes
__utmc This cookie operated in conjunction with the __utmb cookie to determine whether a visitor is in a new session/visit. Session
__utmz Stores the traffic source or campaign that explains how the user reached our site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics. 6 months
__utmv Used to store visitor-level custom variable data. The cookie is updated every time data is sent to Google Analytics. 2 years
F24_autoID This is a temporary identifier on a local machine or phone browser that helps us track anonymous information to be later married up with other cookie data. 6 months - 10 years
F24_personID This is an ID generated per individual contact in the Force24 system to be able to track behaviour and form submissions into the Force24 system from outside sources per user. This is used for personalisation and ability to segment decisions for further communications. 10 years
ASP.NET_SessionId Used to track a user through the website. Session
UMB_MCULTURE Used by the Umbraco CMS to track the language variant of the website. Session

 

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 are likely to be analytical/performance cookies or targeting cookies.

Declining Cookies - Your Choice

You can choose to accept or decline cookies. Most web browsers automatically accept cookies, but 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 site.