Cookie policy

What are cookies?

Cookies are small text files containing a string of characters that can be placed on your computer or mobile device that uniquely identify your browser or device.

What sort of cookies does our Site use?

Like most websites on the internet, we also use cookies. Each cookie or online identifier has its own unique role, but in general they can be divided into some main categories: necessary, performance, preference and marketing cookies.

We use performance cookies, but they don’t identify you, therefore do not fall under the scope of personal data. These cookies collect information about how you use a website, for instance which pages visitors go to most often, which we manage with the help of Google Analytics. This is used to improve our website and therefore overall business practices.

Necessary cookies are the ones that enable you to move around the website and use its features, such as accessing secure areas of the website. As the name suggests, these are the cookies that enable you to even use our site, since without them we cannot properly display you our website content.

Preference cookies are the ones that can adjust the content of the website based on parameters like your location. We don’t customize our website content and therefore do not use such cookies.

Marketing cookies are the ones we use to optimize our business processes. For example, these are the cookies that track which blog posts you read while on our website.
We ask your consent to use such cookies and additionally you can manage your preference at any later time as well.

Description

This cookie is used for to keep track of a visitor’s identity. This cookie is passed to HubSpot on form submission and used when de-duplicating contacts.

This cookie is used to recognize visitors who chat with you via the messages tool. If the visitor leaves your site before they’re added as a contact, they will have this cookie associated with their browser. If you have a history of chatting with a visitor and they return to your site later in the same cookie browser, the messages tool will load your conversation history with that visitor.

Whenever HubSpot changes the session cookie, this cookie is also set. We set it to 1 and use it to determine if the user has restarted their browser. If this cookie does not exist when we manage cookies, we assume it is a new session.

The main cookie for tracking visitors. 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).

This cookie keeps track of sessions. This is used to determine if we should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp.

Used to distinguish users.

Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>.

Used to distinguish users.

The __cfduid cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. For example, if the visitor is in a coffee shop where there are a bunch of infected machines, but the specific visitor’s machine is trusted (e.g. because they’ve completed a challenge within your Challenge Passage period), the cookie allows us to identify that client and not challenge them again. It does not correspond to any user ID in your web application, and does not store any personally identifiable information.

Stores ‘yes’ if you already closed our newsletter popup.

Stores ‘yes’ if you already accepted our cookie policy.