Cookie Policy

The Open ECX website uses cookies to help improve the experience for our visitors and give us information about how people interact with the site.

For information on how we use any information gathered through the website, please read our privacy policy.

You can control the cookies that our website adds to your browser at any time by clicking the ‘cookie settings’ button on this page. Below, you can find out more about cookies, how we use them and how to remove them if you wish.

About Cookies

A cookie is a file containing an identifier (a string of letters and numbers) that is sent by web server to a web browser and is stored by the browser. The identifier is then sent back to the server each time the browser requests a page from the server.

Cookies may be either “persistent” cookies or “session” cookies: a persistent cookie will be stored by a web browser and will remain valid until its set expiry date unless deleted by the user before the expiry date; a session cookie, on the other hand, will expire at the end of the user session, when the web browser is closed.

Cookies may not contain any information that personally identifies a user, but personal data that we store about you may be linked to the information stored in and obtained from cookies.

Cookie Settings

When you visit our website for the first time, you are given the option to review and control the cookies that we set on your browser. You can manage your preferences relating to the use of cookies on our website by clicking on the button displayed below and then ‘Cookie Settings’ link in the pop-up.

Necessary Cookies

HubSpot & Cloudflare

We use HubSpot to control the use of cookies on our website and to provide analytics about how visitors use the site and the information they view. For more information on HubSpot cookies, read their cookie information here and below.

__cf_bm

Cloudflare’s bot products identify and mitigate automated traffic to protect our site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions. This cookie appears twice, once from HubSpot and once from monacosol.com.

Expires: After 30 minutes.

For more information on Cloudflare cookies, visit their website here: https://developers.cloudflare.com/fundamentals/reference/policies-compliances/cloudflare-cookies/

__hs_do_not_track

This cookie prevents the tracking code from sending any information to HubSpot. It contains the string “yes”.

Expires: After 6 months.

__hs_initial_opt_in

This cookie prevents the cookie banner from displaying when visitors are browsing in strict mode. It contains the string “yes” or “no”.

Expires: After 6 days.

__hs_opt_out

This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again. This cookie is set when you give visitors the choice to opt out of cookies. It contains the string “yes” or “no”.

Expires: After 6 months.

__hs_cookie_cat_pref

The HubSpot Cookie Banner’s consent preferences cookie.

Expires: After 6 months.

Functionality Cookies

LinkedIn

li_gc

A LinkedIn cookie used to store guest consent to the use of cookies for non-essential purposes.

Expires: After 6 months.

For more information on LinkedIn cookies, visit the cookie page on their website.

Google

test_cookie

This cookie is set by DoubleClick (which is owned by Google) to determine if the website visitor’s browser supports cookies.

Expires: After 15 minutes.

Tawk

twk_idm_key

A Tawk cookie that enables website visitor connection management for the chat widget.

Expires: After the session.

tawk_uuid_*

A Tawk cookie that enables unique visitor tracking for the website, it does not store any personal details.

Expires: After 6 months

TawkConnectionTime

This cookie is used to determine the connection duration of Tawk sessions and load the widget across multiple pages.

Expires: After the session.

for more information on Tawk cookies, visit the cookie section on their website.

Analytics Cookies

Google Analytics

We use Google Analytics, which gathers information about the use of our website and uses cookies for this purpose.

We use the information gathered by Google Analytics to create reports about the use of our website. You can find out more about Google’s use of information by visiting https://policies.google.com/technologies/partner-sites and you can review Google’s privacy policy at https://policies.google.com/privacy.

The cookies used by Google Analytics are detailed in the cookie list below.

_ga_UA-*

A Google Analytics cookie used to limit the number of requests made to doubleclick.net. It does not store any user information.

Expires: After a minute.

_ga_*

A Google Analytics cookie is used to persist the session state.

Expires: After a year.

_ga

A Google Analytics cookie ID used to store and count pageviews.

Expires: After a year.

_gat_gtag_UA_*

A Google Analytics cookie used to store a unique user ID.

Expires: After a year.

_gid

A Google Analytics cookie used to identify users for 24 hours after the last activity.

Expires: After a day.

HubSpot

__hssrc

When HubSpot changes the session cookie, the _hssrc cookie is set to determine if the visitor restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session. It contains the value “1” when it is present.

Expires: At the end of the session.

__hstc

A HubSpot analytics session tracking cookie. It is the main cookie for tracking visitors.

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

Expires: After 6 months.

__hssc

A HubSpot analytics session cookie. It determines if HubSpot should increment the session number and timestamps in the __hstc cookie. It contains the domain, view count (increments each page view in a session), and session start timestamp.

Expires: After 30 minutes.

hubspotutk

A HubSpot cookie that contains the domain, hubspotutk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).

Expires: After 6 months.

LinkedIn

li_sugr

Used by LinkedIn to make a probabilistic match of a user’s identity outside the Designated Countries.

Expires: After 3 months.

AnalyticsSyncHistory

A LinkedIn cookie used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries.

Expires: After a month.

Vimeo

vuid

This first party cookie created by Vimeo is used to assign a Vimeo Analytics unique ID.

Expires: After a year.

Marketing Cookies

Google

IDE

This cookie is used for targeting, analysing and optimisation of ad campaigns in the DoubleClick/Google Marketing Suite.

Expires: After a year.

_gcl_au

Used by Google AdSense for experimenting with advertisement efficiency across websites using their services.

Expires: After 3 months.

LinkedIn

UserMatchHistory

These cookies are set by LinkedIn for advertising purposes, including tracking visitors so that more relevant ads can be presented, allowing users to use the ‘Apply with LinkedIn’ or the ‘Sign-in with LinkedIn’ functions, and collecting information about how visitors use the site.

Expires: After a month.

bscookie

A LinkedIn cookie used for remembering that a logged in user is verified by two factor authentication and has previously logged in.

Expires: After a year.

bcookie

A LinkedIn browser Identifier cookie to uniquely identify devices accessing LinkedIn to detect abuse on the platform and for diagnostic purposes.

Expires: After a year.

lidc

Used by LinkedIn to facilitate data centre selection.

Expires: After a day.

Leadfeeder

_lfa

A Leadfeeder cookie collects behavioural data of website visitors. This includes pages viewed, visitor source and time spent on the site.

Expires: After a year.

Managing Cookies in Your Browser

Most browsers allow you to refuse to accept cookies and delete cookies. The methods for doing so vary from browser to browser, and from version to version.

If you have accepted cookies initially but then decline them, this will stop our website adding them in your browser in future, but you will need to manually delete any that have already been dropped.

You can obtain up-to-date information about blocking and deleting cookies via these links:

Blocking all cookies will have a negative impact on the usability of many websites.

If you block cookies, you may not be able to use all the features on our website.