legal
Cookie Policy

Our Cookie Policy

Cloud.IQ Limited ("we/us/our") are the owner and operator if www.cloudiq.com (the "Website") and our services platform (the "Platform") which use cookies.

This Cookie Policy describes;

  • what cookies are;
  • our use of cookies;
  • how you can manage cookies used on the Website and the Platform;
  • privacy;
  • further information; and
  • changes to this Cookie Policy.

What are cookies?

Cookies are small text files which are placed on your device when you visit the Website and the Platform. Some cookies may collect personal data about you. You can find more general information about cookies at: www.allaboutcookies.org.

Our use of cookies

Cookies do lots of different jobs, but we want you to understand the different types of cookies that are typically used on websites and apps. We use a variety of types of cookies and other tracking technologies for the following purposes:

  • Strictly necessary cookies: these are cookies which are strictly necessary for the performance of our Website and Platform, for example, cookies that enable you to log into secure areas of our Platform.
  • Performance cookies: these cookies collect information about the pages or screens you visit, and other performance metrics. This helps us to improve the way our Website and Platform works, for example, by ensuring that users are finding what they are looking for easily.
  • Functionality cookies: these cookies remember your choices to improve your experience, for example, remembering your username, your language, the region you are in. the aim of these cookies is to provide you with a more personal experience so that you don't have to reset your preferences each time you visit our Website or login to our Platform.
  • Targeting and advertising cookies: these cookies are often placed by re-targeting and advertising partners, to track your browsing habits so that you can later be shown targeted ads on other websites and apps. We use this information to make our Website and Platform and the advertising displayed on them more relevant to your interests. We may also share this information with third parties for this purpose.

You can find more information about the individual cookies we use on our Website and Platforms and the purposes for which we use them in the tables below:

Website

First party cookies (the cookies we use):

Cookie Name

Purpose

More Info

SnapABugHistory

This cookie keeps track of the user visits and previous chats to present history to agent.

We use this cookie when a visitor engages in web chat with a chat operator at Source.
‍
This data is used to provide a better user experience as we will be able to review your chat history and previous visits to our website.

SnapABugRef

This cookie tracks the country the user is from (best prediction) and also what page on our website the user hits the chat button.
‍
We only collect data using this cookie when a user who has stated that they are a Professional Investor clicks the "online chat" button.

We use this data to enable web chat to function - This helps us route the chat to the right chat operator with the correct language skills. For example we route French visitors to a chat operator fluent in French. This cookie is also used for regulatory compliance purposes as it allows the chat operator to ensure we are not selling to an investor claiming to be in Europe that is actually based in, for example, the USA.

SnapABugVisit

This cookie detects the start of a new session

We use this cookie when a user engages in web chat with a chat operator at Source.

This data enables web chat to function.

__cfduid

Used by the content network, Cloudflare, to identify trusted web traffic.

__cfruid

Unclassified

__hssc

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.

__hssrc

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.

__hstc

The main cookie for tracking visitors. It contains the domain, utk (see below), initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).

hubspotutk

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.

_hjClosedSurveyInvites

This Hotjar cookie that is set once a visitor interacts with a Survey invitation modal pop-up. It is used to ensure that the same invite does not reappear if it has already been shown.

_hjDonePolls

Hotjar cookie that is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not reappear if it has already been filled in.

_hjMinimizedPolls

Hotjar cookie that is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site.

_hjIncludedInSample

Hotjar cookie that is set to let Hotjar know whether that visitor is included in the sample which is used to generate Funnels.

_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.

_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 behavior in subsequent visits to the same site will be attributed to the same user ID.

_hjRecordingLastActivity

This should be found in Session storage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records).

_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.

_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.

_hjCachedUserAttributes

This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool.

_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.

_hjIncludedInSample

Session cookie which is destroyed when user leaves the Hotjar site.

_gat

Set by Google Analytics to collect anonymous information about users and how they use our website. Typical information it collects would include how many visitors we get to the website and how long visitors stay on our website.

_gid

Set by Google Analytics to collect anonymous information about users and how they use our website. Typical information it collects would include how many visitors we get to the website and how long visitors stay on our website.

_ga

Set by Google Analytics to collect anonymous information about users and how they use our website. Typical information it collects would include how many visitors we get to the website and how long visitors stay on our website.

Platform (accessible on paypal.cloudiq.com domain)

Cookies we use:

Cookie Name

Purpose

More Info

CGISESSID

Used for timeout from secure section.

cloudiq_platform_url

Cookie used to capture the URL of the Platform.

__hssc

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.

__hssrc

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.

__hstc

The main cookie for tracking visitors. It contains the domain, utk (see below), initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).

https://knowledge.hubspot.com/articles/kcs_article/reports/what-cookies-does-hubspot-set-in-a-visitor-s-browser

hubspotutk

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.

https://knowledge.hubspot.com/articles/kcs_article/reports/what-cookies-does-hubspot-set-in-a-visitor-s-browser

_gat

Set by Google Analytics to collect anonymous information about users and how they use our website. Typical information it collects would include how many visitors we get to the website and how long visitors stay on our website.

https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage

_gid

Set by Google Analytics to collect anonymous information about users and how they use our website. Typical information it collects would include how many visitors we get to the website and how long visitors stay on our website.

https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage

_ga

Set by Google Analytics to collect anonymous information about users and how they use our website. Typical information it collects would include how many visitors we get to the website and how long visitors stay on our website.

https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage

_hjClosedSurveyInvites

This Hotjar cookie that is set once a visitor interacts with a Survey invitation modal pop-up. It is used to ensure that the same invite does not reappear if it has already been shown.

https://help.hotjar.com/hc/en-us/articles/115011789248-Hotjar-Cookies

_hjDonePolls

Hotjar cookie that is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not reappear if it has already been filled in.

https://help.hotjar.com/hc/en-us/articles/115011789248-Hotjar-Cookies

_hjMinimizedPolls

Hotjar cookie that is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site.

https://help.hotjar.com/hc/en-us/articles/115011789248-Hotjar-Cookies

_hjIncludedInSample

Hotjar cookie that is set to let Hotjar know whether that visitor is included in the sample which is used to generate Funnels.

https://help.hotjar.com/hc/en-us/articles/115011789248-Hotjar-Cookies

_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.

https://help.hotjar.com/hc/en-us/articles/115011789248-Hotjar-Cookies

_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 behavior in subsequent visits to the same site will be attributed to the same user ID.

https://help.hotjar.com/hc/en-us/articles/115011789248-Hotjar-Cookies

_hjRecordingLastActivity

This should be found in Session storage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records).

https://help.hotjar.com/hc/en-us/articles/115011789248-Hotjar-Cookies

_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.

https://help.hotjar.com/hc/en-us/articles/115011789248-Hotjar-Cookies

_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.

https://help.hotjar.com/hc/en-us/articles/115011789248-Hotjar-Cookies

_hjCachedUserAttributes

This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool.

https://help.hotjar.com/hc/en-us/articles/115011789248-Hotjar-Cookies

_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.

https://help.hotjar.com/hc/en-us/articles/115011789248-Hotjar-Cookies

_hjIncludedInSample

Session cookie which is destroyed when user leaves the Hotjar site.

https://help.hotjar.com/hc/en-us/articles/115011789248-Hotjar-Cookies

Platform (accessible on the platform.cloud-iq.com domain)

Cookies we use:

Cookie Name

Purpose

More Info

_gat

Set by Google Analytics to collect anonymous information about users and how they use our website. Typical information it collects would include how many visitors we get to the website and how long visitors stay on our website.

https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage

_gid

Set by Google Analytics to collect anonymous information about users and how they use our website. Typical information it collects would include how many visitors we get to the website and how long visitors stay on our website.

https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage

_ga

Set by Google Analytics to collect anonymous information about users and how they use our website. Typical information it collects would include how many visitors we get to the website and how long visitors stay on our website.

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.

How to manage cookies on our Website and Platform

Cookies do lots of jobs on the Website and Platform. However, you may be able to disable them if you would like to if the relevant third party allows you to. If you do this, you may find that certain parts of the Website and Platform do not work at all, or do not work correctly.

Except for essential cookies, our session cookie will expire after the browsing session.
‍
Each browser is configured differently. You should follow the instructions given by the publisher of your browser. As of the date of this Cookie Policy, these instructions are available for commonly used browsers through the following links:

If you use Microsoft Edge:
https://privacy.microsoft.com/en-us/windows-10-microsoft-edge-and-privacy

If you use Internet Explorer:
http://windows.microsoft.com/en-GB/windows-vista/Block-or-allow-cookies

If you use Safari:
https://support.apple.com/kb/ph21447?locale=en_US

If you use Firefox:
https://support.mozilla.org/en-US/kb/enable-and-disable-cookies-website-preferences

If you use Chrome:
https://support.google.com/chrome/answer/95647?hl=en&hlrm=en

If you use different devices, make sure you configure the settings of the corresponding browser according to your preferences.

Privacy

We are committed to using cookies and tracking technologies fairly and in accordance with applicable privacy rights. Our Privacy Policy can be accessed here.

Further information

If you have any queries relating to this Cookie Policy please contact our Data Protection Officer at helpdesk@cloudiq.com.

Changes to this Cookie Policy

If this Cookie Policy changes, the revised policy will include a new effective date and will be posted on this page. Please check back regularly to keep informed of updates. The effective date of this Cookie Policy is 24th June, 2020.
‍
Previous Version