Cookies

We make use of cookies when you visit our website.

What are cookies?

Cookies are small text files that are saved to your computer. We use  cookies to remember users during a visit, upon return to the site, and are required to enable certain functionality. In addition, cookies are used to help us understand how our customers use our websites and we use this information to help plan improvements 

How to control the use of cookies

If you wish to restrict or block the use of cookies on your computer when you visit our website, you can do this through the cookie preference centre or your browser settings. 

Some functionality on our website will not work if you disable ‘strictly necessary’ cookies in your browser.

How we use cookies

Both npower business solutions and third parties make use of cookies when you visit websites. The following is a description of the types of cookie that we use, why they are used and details of the individual cookies.

We use both session cookies and persistent cookies.

Session cookies are used by us to recognise a user throughout a visit. 

Persistent cookies allow us to retain information and settings about a user for more than one session. These cookies stay on a computer or a device until they expire or a user removes them. They enable us to recognise a user when they return to our site, identify their preferences.

Strictly necessary cookies

These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work.

Functional cookies

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

Performance cookies

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.

Targeting cookies

These cookies allow us to provide you with advertisements based on your past visits to, and use of, our website and may be set through our site by our advertising partners. These cookies may be set through our site by our advertising partners. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.

Strictly necessary cookies

_hs_opt_out

This Hubspot 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.It contains the string "yes" or "no".
It expires in 13 months.

_hs_do_not_track

This Hubspot cookie can be set to prevent the tracking code from sending any information to HubSpot. It contains the string "yes".
It expires in 13 months.

__hs_initial_opt_in

This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode. It contains the string "yes" or "no".
It expires in seven days.

__hs_cookie_cat_pref

This cookie is used to record the categories a visitor consented to. It contains data on the consented categories.
It expires in 13 months.

hs_ab_test

This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before. It contains the id of the A/B test page and the id of the variation that was chosen for the visitor.
It expires at the end of the session.

<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.It contains an encrypted version of the password so future visits to the page will not require the password again.
It expires in 14 days.

hs-messages-is-open

This cookie is used to determine and save whether the chat widget is open for future visits. It is set in your visitor's browser when they start a new chat, and resets to re-close the widget after 30 minutes of inactivity. It contains a boolean value of True if present.
It expires in 30 minutes.

hs-messages-hide-welcome-message

This cookie is used to prevent the chat widget welcome message from appearing again for one day after it is dismissed. It contains a boolean value of True or False.
It expires in one day.

__hsmem

This cookie is set when visitors log in to a HubSpot-hosted site. It contains encrypted data that identifies the membership user when they are currently logged in.
It expires in one year.

hs-membership-csrf

This cookie is used to ensure that content membership logins cannot be forged. It contains a random string of letters and numbers used to verify that a membership login is authentic.
It expires at the end of the session.

hs_langswitcher_choice

This Hubspot cookie is used to save the visitor’s selected language choice when viewing pages in multiple languages. It gets set when an end user selects a language from the language switcher and is used as a language preference to redirect them to sites in their chosen language in the future, if they are available. It contains a colon delimited string with the ISO639 language code choice on the left and the top level private domain it applies to on the right. An example will be "EN-US:hubspot.com".
It expires in two years.

__cfduid

This cookie is set by HubSpot’s CDN provider, Cloudflare. It helps Cloudflare detect malicious visitors to your website and minimizes blocking legitimate users. It may be placed on your visitors' devices to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It is necessary for supporting Cloudflare's security features.
It is a session cookie that lasts a maximum of 30 days.

__cfruid

This cookie is set by HubSpot’s CDN provider because of their rate limiting policies. Learn more about Cloudflare cookies. It expires at the end of the session.

These are non-essential cookies controlled by the cookie banner. If you're a visitor to a site supported by HubSpot, you can opt out of these cookies by not giving consent.

__hstc

The main Hubspot 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).
It expires in 13 months.

hubspotutk

This cookie keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts. It contains an opaque GUID to represent the current visitor.
It expires in 13 months.

__hssc

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.
It expires in 30 minutes.

__hssrc

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. It contains the value "1" when present.
It expires at the end of the session.

Functional cookies

Chatflow cookie

This is the Hubspot cookie used for the chatflows tool. If you're a visitor, this allows you to chat with a representative on the site.

messagesUtk

This cookie is used to recognize visitors who chat with you via the chatflows 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 chatflows tool will load their conversation history. The cookie is controlled by the Consent to collect chat cookies setting in your chatflow.
If this setting is disabled, the cookie is controlled by the Consent to process setting in your chatflow.


HubSpot will not drop the messagesUtk cookie for visitors who have been identified through the Visitor Identification API. The analytics cookie banner will not be impacted.
This cookie will be specific to a subdomain and will not carry over to other subdomains. For example, the cookie dropped for info.example.com will not apply to the visitor when they visit www.example.com, and vice versa. It contains an opaque GUID to represent the current chat user.
It expires in 13 months.

Chatflow cookie consent text

With the Consent to collect chat cookies setting enabled, HubSpot will prompt visitors for consent to drop a cookie in their browser before the start a chat or when they attempt to the leave the page during a chat conversation. This cookie is used to interact with website visitors and provide a visitor's chat history. If you choose to display the banner before the visitor starts a chat and the visitor does not give consent, they will not be able to start the chat.

If you choose to display the banner upon exit intent, however, the visitor can start the chat, but if they don't consent to cookies before navigating away from the page, the chat widget will reset and the conversation will end. With this setting disabled, a visitor can start a chat and give consent to process their information via the Consent to process setting. Visitors can also accept or decline cookies on the HubSpot cookie banner if it is enabled on your pages. If a visitor accepts the cookie when they start a chat, but then clicks Decline on the HubSpot cookie banner, the cookie will be removed.

If a visitor clicks Decline on the HubSpot cookie banner before starting a chat, HubSpot will not drop a cookie or prompt them to consent to cookies in the chat widget.

Analytics cookies

__hstc

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).
It expires in 13 months.

hubspotutk

This cookie keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts.
It contains an opaque GUID to represent the current visitor.
It expires in 13 months.

__hssc

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.
It expires in 30 minutes.

__hssrc

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.
It contains the value "1" when present.
It expires at the end of the session.

Google analytics cookies

_ga

Used to distinguish users. Duration 2 years.

_gid

Used to distinguish users. Duration 24 hours.

_ga_<container-id>

Used to persist session state. Duration 2 years.

_gac_gb_<container-id>

Contains campaign related information. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Duration 90 days.

Hotjar cookies

_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. Duration 365 days.

_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. Duration 30 minutes.

_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. Duration 365 days

_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. Duration 365 days

_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. Duration 365 days.

_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. Duration 365 days.

_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. Duration: session.

_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. Duration: session.

_hjSessionResumed

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

_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. Duration 365 days.

_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). Duration: session.

_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. Duration: session.

_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. Duration: session.

_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. Duration: session.

_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. Duration under 100ms.

_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. Duration: 30 minutes.

_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. Duration: 30 minutes.

_hjAbsoluteSessionInProgress

This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.

_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. Duration: session

_hjViewportId

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

_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. Duration: session.

Contact us

For a new quote or a renewal please call:

Show Phone Number 0800 644 6135

We're open:
Monday-Friday 9am-5pm.
Excluding public holidays.

Request a call back

Request a call back

Contact us

For a new quote or a renewal please call:

Show Phone Number 0800 644 6135

We're open:
Monday-Friday 9am-5pm.
Excluding public holidays.

Request a call back

Request a call back

Contact us

For a new quote or a renewal please call:

Show Phone Number 0800 669 6443

We’re open:
Monday-Friday 9am-5pm.
Excluding public holidays.

Request a call back

Request a call back

Contact us

To discuss a quote or a renewal for one of your clients please call:

Show Phone Number 0800 193 6866

We’re open:
Monday-Friday 9am-5pm.
Excluding public holidays.

Request a call back

Request a call back