What are cookies?
Cookies are text files containing small amounts of information which are downloaded to your device when you visit a website. Cookies are then sent back to that website on each subsequent visit, or to another website that recognises that cookie. Cookies are useful because they allow a website to recognise the device you are using and provide you with a better website experience. You can find more information about cookies at: www.allaboutcookies.org and www.youronlinechoices.eu.
Cookies do lots of different jobs, like letting you navigate between pages efficiently, remembering your preferences, and generally improving your user experience. They can also help to ensure that the adverts you see online are relevant to you and your interests.
The cookies used on this website have been categorised based on the categories found in the ICC UK Cookie guide (Nov 2012). A list of all the cookies used on this website by category is set out below.
Cookies are either:
Session cookies: these are only stored on your computer during your web session and automatically expire once you log off or close the browser. They usually store an anonymous session ID allowing you to browse a website without having to log in to each page, but they do not collect any personal data from your computer. They are only stored temporarily and are destroyed after leaving the page.
Persistent cookies: a persistent cookie is stored as a file on your computer and it remains there when you close your web browser. The cookie can be read by the website that created it when you visit that website again. They help remember information, settings, preferences, or sign-on credentials that a user has previously saved. This helps create a convenient and faster website experience.
Cookies can also be categorised as follows:
‘Strictly Necessary’ cookies: These cookies enable services you have specifically asked for. They are essential in order for you to move around our website and use its features, such as accessing secure areas of the website. Without these cookies the services available to you on our website cannot be provided. These cookies do not gather information about you that could be used for marketing or remember where you have been on the internet.
Performance cookies: These cookies collect anonymous information on the pages visited. They collect information about how visitors use our website, for instance which pages visitors go to most often, and if they get error messages. These cookies don’t collect information that identifies you. All information collected by these cookies is aggregated and therefore anonymous. They are only used to improve how our website works.
Functionality cookies: These cookies remember choices you make to improve your experience. They allow our website to remember your choices (such as your user name) and provide enhanced, more personal features. For instance, we may be able to provide you with news or updates relevant to the services you use. These cookies can also be used to provide services you have asked for such as watching a video or commenting on a blog. The information these cookies collect may be anonymised and they cannot track your browsing activity on other websites.
Targeting cookies or Advertising cookies: These cookies collect information about your browsing habits in order to make advertising relevant to you and your interests. They are also used to limit the number of times you see an advertisement, as well as help measure the effectiveness of advertising campaigns. They are usually placed by advertising networks with the website operator’s permission. They remember that you have visited a website and this information is shared with other organisations such as advertisers. Another purpose of targeting and advertising cookies is to build user profiles from visitors to the website to gather statistics on the performance of the advertisements that can carry across many websites. These cookies are almost always third party, persistent cookies. This means that the cookies can follow the user as they visit other websites. Sometimes, the site with the advertising cookies does not display the advertisements but it can target users with advertisements elsewhere even after they’ve left the site. Examples of targeting and advertising cookies include social media cookies that are placed on sites to track users around the web to provide ads to them on social media platforms.
You can 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.
To deactivate the use of third-party advertising cookies, you may visit the relevant consumer page. Alternatively, you can opt out of third-party cookies by visiting the Network Advertising Initiative opt-out page.
What cookies does Positive use?
You can read about the individual cookies we use and the purposes for which we use them in the table below:
|Cookie_notice_dismissed||This cookie ensures that the cookie notice des not reappear once it has been dismissed.||Session|
|_ga||This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the site’s analytics reports.||2 years|
|_gat||This cookie is used to throttle the request rate, limiting the collection of data on high traffic sites.||10 mins|
|_gat_gtag_UA_*||This cookie is used to store a unique user ID.||1 min|
|_gid||This cookie is used to distinguish unique users.||24 hours|
|_hjShownFeedbackMessage||This cookie is set when a visitor minimises or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimised immediately if the visitor navigates to another page where it is set to show.||365 days|
|_hjid||This cookie is set when a 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 behaviour in subsequent visits to the same site will be attributed to the same user ID.||365 days|
|_hjRecordingLastActivity||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||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||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||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||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||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 mins|
|_hjIncludedInSessionSample||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 mins|
|_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 mins|
|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|
|hjViewportId||This stores information about the user viewport such as size and dimensions.||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.|
|__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.||30 mins|
|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.||13 months|
|__hstc||The main cookie for Hubspot to track 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).||13 months|
|__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.||Session|
|__hs_do_not_track||This cookie can be set to prevent the tracking code from sending any information to HubSpot.It contains the string “yes”.||13 months|
|_hs_cookie_cat_pref||This cookie is used to record the categories a visitor consented to. It contains data on the consented categories.||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.|
|bcookie||This cookie is used to uniquely identify devices accessing LinkedIn to detect abuse on the platform.||2 years|
|bscookie||This cookie is a Secure Browser Cookie used by LinkedIn.||1 year|
|lang||This cookie is used to remember your selected language preference during your time on the site.||Session|
|lidc||This cookie is used to optimize data centre selection.||24 hours|
|UserMatchHistory||This cookie is used to identity you as a new or returning visitor.||30 days|
|BizoID||This cookie is used for LinkedIn Ad analytics.||6 months|
|BizoData||This cookie is used for LinkedIn Ad analytics.||6 months|
|BizoUserMatchHistory||This cookie is used for LinkedIn Ad analytics.||6 months|
|BizoNetworkPartnerIndex||This cookie is used for LinkedIn Ad analytics.||6 months|
|_atuvc||This cookie stores an updated page share count, making sure that the user sees the updated count if they share a page and then return to it.||13 months|
|uvc||This cookie is used by AddThis to measure frequency of visits by user.||13 months|
|_atuvs||This cookie holds the ID of a visit (a group of related views), and a counter for the number of views in the visit so far.||Session|
|loc||This is a geolocation cookie that helps publishers know approximately where people sharing information are located.||90 days|