Cookie Policy
Cookies are small amounts of information which are stored on a user’s computer to help the website remember specific things or actions.
Cookies are commonly used and are intended to record small amounts of data specific to a particular website user, and can be accessed either by the web server or on the client computer. Consequently, web pages can be tailored to enhance the user experience, the web page may perform different actions depending on the value of the ‘cookie’ or the cookie can help report on the usage of the website in the form of website analytics such as Google analytics.
Analytics helps us understand where the website is working well and where there are potential issues for the user on specific pages so we can improve the user experience. For more information on cookies, please click here.
How Can I Disable Cookies?
Cookies can be disabled on your site. To understand how, please click here.
What Does Monkey Puzzle Use Cookies For?
Our website uses cookies for the following:
- To record website usage and initiate analytics. This does not record specific details such as name and address details, but instead focuses on how the website is being used i.e. which pages were visited, how long were they viewed, where do web users leave our site. This is intended to helps us understand where our website is working well and where there are opportunities for improvement
- Within our admin system, cookies are also used, but this is used internally only and not available to the wider community
Hubspot
HubSpot is committed to privacy and protecting individual rights on the internet. Learn about cookies used on HubSpot websites including: www.hubspot.com, www.hubspot.de, www.hubspot.fr, www.hubspot.es, www.hubspot.jp, br.hubspot.com, and www.inbound.com. These cookies are also used in the HubSpot product (app.hubspot.com). Cookies used by HubSpot on www.seismic.com are also listed.
Cookie Name | Domain | Vendor | Purpose | Category |
AWSELB | app.hubspot.com | Amazon | AWS Elastic Load Balancer | Performance |
__utma | hubspot.com | Google Analytics | Targeting | |
__utmb | hubspot.com | Google Analytics | Targeting | |
__utmc | hubspot.com | Google Analytics | Targeting | |
__utmz | hubspot.com | Google Analytics | Targeting | |
_gauges_unique_hour | hubspot.com | Gauges | Gauges Analytics | Performance |
_gauges_unique_day | hubspot.com | Gauges | Gauges Analytics | Performance |
_gauges_unique_month | hubspot.com | Gauges | Gauges Analytics | Performance |
_gauges_unique_year | hubspot.com | Gauges | Gauges Analytics | Performance |
_gauges_unique | hubspot.com | Gauges | Gauges Analytics | Performance |
apex__product | hubspot.com | Salesforce | Salesforce Analytics | Strictly Necessary |
__hstc | hubspot.com | HubSpot | HubSpot Analytics | Targeting |
__hssrc | hubspot.com | HubSpot | HubSpot Analytics | Targeting |
__hssc | hubspot.com | HubSpot | HubSpot Analytics | Targeting |
hsPagesViewedThisSession | hubspot.com | HubSpot | HubSpot Analytics | Strictly Necessary |
__hs_preview_auth | preview.hs-sites.com | HubSpot | Memberships Authentication | Strictly Necessary |
hubspotutk | hubspot.com | HubSpot | HubSpot Analytics | Targeting |
hubspot.hub.id | hubspot.com | HubSpot | HubSpot Authentication | Strictly Necessary |
hubspotauth | hubspot.com | HubSpot | HubSpot Authentication | Strictly Necessary |
hubspotauthcms | hubspot.com | HubSpot | HubSpot Authentication | Strictly Necessary |
hubspotauthremember | hubspot.com | HubSpot | HubSpot Authentication | Functionality |
_hs_opt_out | hubspot.com | HubSpot | Opt out of HubSpot tracking | Strictly Necessary |
hs_c2l | hubspot.com | HubSpot | HubSpot Authentication | Functionality |
hubspotutktzo | academy.hubspot.com | HubSpot | Time Zone Offset | Functionality |
__hluid | hubspot.com | HubSpot | In-app usage tracking | Targeting |
mp_id_mixpanel | hubspot.com | Mixpanel | In-app usage tracking | Targeting |
__cfduid | hubspot.com | Cloudflare | Detection of malicious actors | Strictly Necessary |
__cfruid | hubspot.com | Cloudflare | Rate limiting policies | Strictly Necessary |
ConsentGDPR-{tenant} | seismic.com | Seismic | GDPR consent status | Functionality |
SeismicPreferences | seismic.com | Seismic | Link preferences | Functionality |
{linkToken} | seismic.com | Seismic | Link preferences in Internet Explorer | Functionality |
SeismicCompliancePreferences- {tenant} |
seismic.com | Seismic | Compliance preferences | Functionality |
UniqueInteractionProof | seismic.com | Seismic | Robot check | Functionality |
quickShareTrackRecipientTip | seismic.com | Seismic | Usage tips | Functionality |
Hotjar Cookies & Scripts
We use the following scripts and cookies to help us improve our website and your experience.
Name of Cookie | First / Third Party | Provider | Purpose | Duration |
_hjClosedSurveyInvites | First | HotJar | Hotjar cookie that is set once a visitor interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown. | 365 days |
_hjDonePolls | First | HotJar | Hotjar cookie that is set once a visitor completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in. | 365 days |
_hjMinimizedPolls | First | HotJar | Hotjar cookie that is set once a visitor minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site. | 365 days |
_hjShownFeedbackMessage | First | HotJar | 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. | 365 days |
_hjid | First | HotJar | 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. | 365 days |
_hjRecordingLastActivity | First | HotJar | 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). | Session |
_hjTLDTest | First | HotJar | 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. | Session |
_hjUserAttributesHash | First | HotJar | 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. | Session |
_hjCachedUserAttributes | First | HotJar | 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. | Session |
_hjLocalStorageTest | First | HotJar | 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. | Under 100ms |
_hjIncludedInPageviewSample | First | HotJar | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site’s pageview limit. | 30 minutes |
_hjIncludedInSessionSample | First | HotJar | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site’s daily session limit. | 30 minutes |
_hjAbsoluteSessionInProgress | First | HotJar | This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. | 30 Minutes |
_hjFirstSeen | First | HotJar | This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. | Session |
hjViewportId | First | HotJar | This stores information about the user viewport such as size and dimensions. | Session |
_hjRecordingEnabled | First | HotJar | This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session. | Session |
Do you want to tell Hotjar not to collect your data?
Hotjar’s behavior analytics software is designed to give website owners an aggregated view of their users’ behavior while browsing their site. This provides website owners with the insights needed to improve the overall experience for their users. Hotjar is not designed to track individual users.
At Hotjar we take privacy rights seriously. Any data our service captures about you is processed and stored in a way that is designed to protect you and your information.
It is the responsibility of the website owner to obtain consent to collect and/or process your data when browsing on their site and to allow you to withdraw that consent in accordance with data privacy laws.
That said, we know and respect that some people might prefer to have Hotjar not process their information across any site on the web and we want to make it as easy as possible for you to make a ‘Do Not Track’ or ‘Block’ request to our servers. We offer two methods to do this.
However, due to the constantly changing nature of browsers, both methods do have limitations and might not be available on all platforms and browsers.
Option 1: Block
The block method works with just one click by installing a cookie on your browser that prevents Hotjar from collecting your data in the future when using your current browser.
Important to note:
- You will need to take this same action for all browsers that you use where you do not want Hotjar to collect your data.
- The block will no longer be effective if you clear cookies in your browser or browse in incognito/private mode.
- The block request is only recognized by Hotjar and will not prevent other, similar services from collecting your data.
- The block may be impacted by future browser updates. If in doubt, check back here for updates. You can always install the do not track cookie again to be sure.
Your browser does not currently support one-click block. To let Hotjar know not to collect your data, please follow the instructions below to enable “Do Not Track” in your browser. Note that this will also block similar services which use the “Do Not Track” setting to disable tracking.
One-click block is currently supported by the following browsers:
MacOS
- Firefox (up to version 64)
- Chrome
- Opera
Windows
- Firefox (up to version 64)
- Chrome
- Opera
- Internet Explorer
- Microsoft Edge
iOS
- Firefox
- Chrome
Android
- Firefox
- Chrome
Windows Mobile
- Internet Explorer
Option 2: ‘Do Not Track’ Browser Setting
The block method outlined above is specific to Hotjar and will not prevent other similar services from collecting your data. It can also be rendered ineffective if you clear cookies in your browser. This second method involves changing a setting in your browser. This means it is not specific to Hotjar and will not be undone when you clear cookies.
Before collecting your data, Hotjar always checks to see if you have enabled the ‘Do Not Track’ setting in your browser. If you wish to prevent Hotjar from collecting your data, as well as other services that check for this setting in advance, you can do so by following the instructions below.
Important to note:
- You will need to take this same action for all browsers that you use where you do not want Hotjar or similar services to collect your data.
- The do not track setting is respected by Hotjar but not all other tracking services do the same.
- Enabling the do not track browser setting may also block some other non-similar services.
- This setting will not be affected by deleting cookies.
- The do not track setting does not work in all browsers and may be impacted by future browser updates. If in doubt, check back here for updates.
How to install the Do Not Track header
- To update your settings, please go to Firefox “Options” from the menu button.
- Click on “Privacy & Security”.
- In the “Content Blocking” section under Send websites a “Do Not Track” signal that you don’t want to be tracked, choose “Always”.
For more information, please visit the documentation.
Please note, all cookie data is intended for use by Monkey Puzzle only and is not shared with any third parties.