Cookie Policy

Last updated 10/01/2020

Our website (https://cloudofficer.co) uses cookies to distinguish you from other users of our website (our Website). This helps us to provide you with a good experience when you browse the Cloud Officer Website and also allows us to improve our Website. By continuing to browse our Website, you are agreeing to our use of cookies. A cookie is a small file of letters and numbers that we store on your browser, device or the hard drive of your computer if you agree. Cookies contain information that is transferred to your device’s hard drive. More information on cookies (including how to disable them) is available at www.allaboutcookies.org.

We use the following cookies:

1. Google Analytics

We use ga.js (cookie usage – First-Party Cookies). We do not use Google Analytics’ Display Advertising features. The ga.js JavaScript library uses first-party cookies to:

  • Determine which domain to measure
  • Distinguish unique users
  • Throttle the request rate
  • Remember the number and time of previous visits
  • Remember traffic source information
  • Determine the start and end of a session
  • Remember the value of visitor-level custom variable

By default, this library sets cookies on the domain specified in the document.host browser property and sets the cookie path to the root level (/).

Google Analytics sets the following cookies:

Cookie name Expiration time Description
__utma 2 years from set/update Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics.
__utmt 10 minutes Used to throttle request rate. This is a limit on how often you can submit requests.
__utmb 30 mins from set/update Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.
__utmc End of browser session Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit.
__utmz 6 months from set/update Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.
_ga 2 years Used to distinguish users.
_gid 24 hours Used to distinguish users.
_gat 1 minute Used to throttle request rate.
_gac_property-id 90 days Contains campaign related information for the user. If you have linked your Google Analytics and AdWords accounts, AdWords website conversion tags will read this cookie unless you opt-out.

A copy of Google’s Privacy Policy can be found here.

2. Hubspot

Hubspot sets the following cookies:

Cookie name Expiration time Description
hubspotutk 10 years 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.
__hstc 2 years 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).
__hssc 30 minutes 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 None (session cookie) 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.
hsPagesViewed None (session cookie) This cookie is used to keep track of page views in a session.

A copy of Hubspot's Privacy Policy can be found here.

Further information

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.

You 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 Website.


© Cloud Officer Limited. All rights reserved.