Cookies policy
You can browse our site without identifying yourself.
We use cookies set by both Google Analytics & HubSpot.
Google Analytics is the third-party software library we use to track visitor statistics. HubSpot uses cookies to help us identify and track visitors, their usage of our website, and their website access preferences.
The Google Analytics library sets the following cookies:
Cookie Name | Default Expiration Time | Description |
_utma | 2 years from set/update | Used to distinguish user 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 |
__utmb | 30 minutes 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 within 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 the site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics. |
__utmv | 2 years from set/update | Used to store visitor- level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated_setVar method. The cookie is updated everytime data is sent to Google Analytics. |
HubSpot sets the following cookies:
Cookie Name | Default Expiration Time | Description |
__hs_opt_out | 13 months | 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. |
__hs_do_not_track | 13 months | This cookie can be set to prevent the tracking code from sending any information to HubSpot. Setting this cookie is different from opting out of cookies, as it still allows anonymized information to be sent to HubSpot. |
hs_ab_test | end of session | This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before. |
id_key | When visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login again. The cookie name is unique for each password-protected page. | |
hs-messages-is-open | 30 minutes | This cookie is used to determine and save whether the chat widget is open for future visits. It resets to re-close the widget after 30 minutes of inactivity. |
hs-messages-hide-welcome-message | 1 day | This cookie is used to prevent the welcome message from appearing again for one day after it is dismissed. |
__hsmem | 1 year | This cookie is set when visitors log in to a HubSpot-hosted site. |
__hstc | 13 months | 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). |
hubspotutk | 13 months | This cookie is used to keep track of a visitor’s identity. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
__hssc | 30 min | This cookie keeps track of sessions. This is used to determine if HubSpot 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 | end of session | Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session. |
messagesUtk | 13 months | 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 chat with a visitor who later returns to your site in the same cookied browser, the messages tool will load their conversation history. |
If you would prefer these cookies not to be set, simply disable cookies in your browser for this site.