Cookie Policy

Last updated: (27 October 2021)

The Growth Hub ("us", "we", or "our") uses cookies on thegrowthhub.biz (the “Service”). By using the Service, you consent to the use of cookies.

Our cookie policy explains what cookies are, how we use cookies, how third-parties we may partner with may use cookies on the Service, your choices regarding cookies and further information about cookies.

(And if you want a real cookie, and a cup of coffee, our Growth Hub spaces across the county are ready and waiting! Or if you want to make sure your website is compliant with regulations and cyber security then check our events. If you have any questions you can contact us on talktous@thegrowthhub.biz)

 

What are cookies

Cookies are small pieces of text sent by your web browser by a website you visit. A cookie file is stored in your web browser and allows the Service or a third-party to recognise you and make your next visit easier and the Service more useful to you.

Cookies can be “persistent” or “session” cookies.

 

How The Growth Hub uses cookies

When you use and access the Service, we may place a number of cookies files in your web browser.  We use cookies for the following purposes: to enable certain functions of the Service, to provide analytics, to store your preferences, to enable advertisements delivery, including behavioural advertising. 

Some cookies are always on when you visit us, and you can’t turn them off unless you change your browser settings. We call these essential cookies. We use them to make sure our digital services work correctly and are meeting audience needs and interests.

We also use functional, performance and marketing cookies to make your experience more enjoyable. You can switch these on or off at any time and you can always change your mind. We’ll only use them if you’ve agreed.

The different types of cookies we use are as follows: ­ 

  • Essential cookies. These cookies are essential for you to browse the website and use its features, such as accessing secure areas of the site.
  • Functional cookies. Also known as “preferences cookies,” these cookies allow a website to remember choices you have made in the past.
  • Performance cookies. These cookies collect information about how you use a website, like which pages you visited and which links you clicked on. None of this information can be used to identify you. It is all aggregated and, therefore, anonymised.
  • Marketing cookies. These cookies track your online activity to help advertisers deliver more relevant advertising or to limit how many times you see an ad. These cookies can share that information with other organisations or advertisers.

 

List of essential cookies

Cookie Name What it's for
SSES*

Identifies your session

 

List of functional cookies

Cookie Name What it's for
CONSENT

Stores cookie consent preferences

 

List of performance cookies

Cookie Name What it's for

_gi

Used to count page views

_ga

Used to count page views

 

List of marketing cookies

Cookie Name What it's for
_gcl_au

Store and track Google Adsense conversions

gat_gtag_UA_*_1

Store and track Google Adsense conversions

 

Hotjar Cookie Information

Name

Description

Duration

Data type

_hjSessionUser{site_id}

Hotjar cookie that is set when a user 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

JSON

_hjSession{site_id}

A cookie that holds the current session data. This ensues that subsequent requests within the session window will be attributed to the same Hotjar session.

30 minutes

JSON

_hjClosedSurveyInvites

Hotjar cookie that is set once a user 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

Boolean true/false

_hjDonePolls

Hotjar cookie that is set once a user 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

Boolean true/false

_hjMinimizedPolls

Hotjar cookie that is set once a user minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site.

365 days

Boolean true/false

_hjShownFeedbackMessage

Hotjar cookie that is set when a user minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the user navigates to another page where it is set to show.

365 days

Boolean true/false

_hjSessionTooLarge

Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit.

Session

Boolean true/false

_hjSessionRejected

If present, this cookie will be set to '1' for the duration of a user's session, if Hotjar rejected the session from connecting to our WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues.

Session

Boolean true/false

_hjSessionResumed

A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection.

Session

Boolean true/false

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

365 days

UUID

_hjRecordingLastActivity

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

Session

Numerical Value (Timestamp)

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

Session

Boolean true/false

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

Session

Hash

_hjCachedUserAttributes

This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. Collected attributes will only be saved to Hotjar servers if the user interacts with a Hotjar Feedback tool, but the cookie will be used regardless of whether a Feedback tool is present.

Session

JSON

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

Under 100ms

Boolean true/false

_hjIncludedInPageviewSample

This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit.

30 minutes

Boolean true/false

_hjIncludedInSessionSample

This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's daily session limit.

30 minutes

Boolean true/false

_hjAbsoluteSessionInProgress

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

Boolean true/false

_hjFirstSeen

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

Boolean true/false

_hjViewportId

This stores information about the user viewport such as size and dimensions.

Session

UUID

_hjRecordingEnabled

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

Boolean true/false

Get in touch with the Growth Hub

If your business has the potential to grow, get in touch

talktous@thegrowthhub.biz

Mon to Fri - 8:30 – 17:30

Specialist Advice

Create a tailored growth plan with one of our Business Navigators