Cookies

Polaris.co.uk and imarket.co.uk puts small files (known as ‘cookies’) onto your computer to collect information about how you browse the site.

Cookies are used to:

  • measure how you use the website so it can be updated and improved based on your needs
  • remember the notifications you’ve seen so that we don’t show them to you again

Polaris cookies are not used to identify you personally.

How cookies are used on Polaris.co.uk

Necessary Cookies

Cookie Source Purpose Duration Party
XSRF-TOKEN Polaris.co.uk Security cookie used for cross site request forgery protection. 1 year First
polaris_session Polaris.co.uk Cookie set upon initiation of the user’s current session on the Polaris site. Session First
viewed_cookie_policy Polaris.co.uk Records that the user has viewed the site cookie banner 1 year First
cookielawinfo-checkbox-others Polaris.co.uk Records user response to the ‘others’ cookie category option presented in the site cookie banner. 1 year First
cookielawinfo-checkbox-advertisement Polaris.co.uk Records user response to the ‘advertisement’ cookie category option presented in the site cookie banner 1 year First
cookielawinfo-checkbox-analytics Polaris.co.uk Records user response to the ‘analytics’ cookie category option presented in the site cookie banner 1 year First
cookielawinfo-checkbox-functional Polaris.co.uk Records user response to the ‘functional’ cookie category option presented in the site cookie banner. First
cookielawinfo-checkbox-performance Polaris.co.uk Records user response to the ‘performance’ cookie category option presented in the site cookie banner. 1 year First
polaris_session Polaris.co.uk Cookie set upon initiation of the user’s current session on the Polaris site. Session First
CookieLawInfoConsent Polaris.co.uk Records user response to the cookie banner. 1 year First
cookielawinfo-checkbox-necessary Polaris.co.uk Records user response to the ‘necessary’ cookie category option presented in the site cookie banner. 1 year First
__cfduid Polaris.co.uk (Cloudflare) Used by the contentnetwork, Cloudflare, to identify trusted web traffic 29 days First
rc::a Google(Recaptcha) This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on its use. Persistent Third
rc::c Google(Recaptcha) This cookie is used to distinguish between humans and bots. Session Third
podaccesstoken Polaris.co.uk Records a logged in user’s access status to the POD system. Session First
wp-settings-time Polaris.co.uk Cookie set by the WordPress CMS. Used to customize user’s view of site interface. 363 days First


Measuring website usage (Google Analytics)
We use Google Analytics software to collect information about how you use Polaris.co.uk. We do this to help make sure the site is meeting the needs of its users and to help us make improvements.
Google Analytics stores information about:

  • the pages you visit on Polaris.co.uk – how long you spend on each Polaris.co.uk page
  • how you got to the site
  • what you click on while you’re visiting the site

We don’t collect or store your personal information (e.g. your name or address) so this information can’t be used to identify who you are. We don’t allow Google to use or share our analytics data.

Google Analytics (Site Statistics) sets the following cookies:

Cookie Source Purpose Duration
_ga Google Analytics Registers a unique ID that is used to generate statistical data on how the visitor uses the website 2 years
_gat_gtag Google Analytics Used by Google Analytics to track website visits. 1 minute
_gid Google Analytics Registers a unique ID that is used to generate statistical data on how the visitor uses the website 1 day

To opt out of being tracked by Google Analytics across all websites visit http://tools.google.com/dlpage/gaoptout.

How cookies are used on imarket.co.uk

imarket.co.uk uses “session” cookies on the website. We will use the session cookies to retain information about your current visit to assist your navigation around the website. Session cookies will be deleted from your computer when you close your browser.

The information we collect
We collect information from users when they register to use imarket. This information may include their company name, contact address, the name of the company representatives(s) utilising the services via imarket and their contact e-mail address(es).

How we use information
We will use the information provided to us to enable us to obtain an insurance company’s or Lloyd’s syndicate’s consent or other companies’ providing insurance related services consent to providing you with direct access to their extranet sites or websites. We do not use information provided to us for marketing purposes or share information with third parties.

We take reasonable care to keep any information provided to us secure and to prevent any unauthorised access or use of it. imarket will provide the facility for information to be submitted in structured e-mails for conversion and onward transmission as fax to numbers embedded within structured e-mail addresses. The security of the content of such transmissions cannot be guaranteed following conversion to fax. Users must therefore take particular care that fax numbers embedded in e-mail-for-fax addresses are correct.

How cookies are used on imarket Live-chat
Like many other services, the imarket Live-Chat solution provided by Click4Assistance uses cookies to function properly. Information on how these cookies are used can be found here.

Emails

Some of our emails may include tracking technologies (tiny graphic files) that contain unique identifiers allowing us to recognize if or when recipients have opened an email, how often this has happened (and for how long) and if any links have been clicked. These files will record the email address, IP address, and which email software and web browser were used.

Cookie Source Purpose Duration
lpv <accountid> pardot.com This LPV cookie is set to keep Pardot from tracking multiple page views on a single asset over a 30-minute session. For example, if a visitor reloads a landing page several times over a 30-minute period, this cookie keeps each reload from being tracked as a page view Session
visitor_id pardot.com The visitor cookie includes a unique visitor ID and the unique identifier for your account. For example, the cookie name visitor_id12345 stores the visitor ID 1010101010. The account identifier, 12345, makes sure that the visitor is
tracked on the correct Pardot account. The visitor value is the visitor_id in your Pardot account. This cookie is set for visitors by the Pardot tracking code
Session
visitor_id<accountid>-hash pardot.com The visitor hash cookie contains the account ID and stores a unique hash. For example, the cookie name visitor_id12345-hash stores the hash “855c3697d9979e78ac404c4ba2c66533”, and the account ID is 12345. This cookie is a security measure to make sure that a malicious user can’t fake a visitor from Pardot and access corresponding prospect information. Session
pardot pardot.com A session cookie named pardot is set in your browser while you’re logged in to Pardot as a user or when a visitor accesses a form, landing page, or page with Pardot tracking code. The cookie denotes an active session and isn’t used for tracking. Session

Surveys

Survey Monkey

We use SurveyMonkey to collect responses to our surveys. If you take part, SurveyMonkey will save extra cookies to your computer to track your progress through them.
SurveyMonkey sets the following cookies:

Name Purpose Expires
mbox This is used to keep your progress through the survey 30 minutes
SSOE This is used for testing different content and features on the survey website to help make it better When you close your browser
TS5159a2 and TSd0b041 These are used to manage survey traffic by sending your computer to a specific server When you close your browser
ep201 This is used to help us identify how you use the survey 30 minutes
ep202 This works with ep201 to help us identify how you use the survey 1 year


Hotjar

We use Hotjar to collect survey responses on the Polaris website. We currently have 2 Hotjar surveys live on the website, a general website survey located on each page, and a feedback survey located on the Resources section.

Heat Mapping
We also use Hotjar Heatmaps to collect anonymized user behavior on our webpages to help us to get an overview of our visitor behavior while protecting end-user privacy.

Hotjar sets the following cookies:

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

How can I control cookies?

Web browser cookies
If you don’t want to receive cookies, you can modify your browser so that it notifies you when cookies are sent to it or you can refuse cookies altogether. You can also delete cookies that have already been set. If you wish to restrict or block web browser cookies which are set on your device then you can do this through your browser settings; the Help function within your browser should tell you how. Alternatively, you may wish to visit www.aboutcookies.org, which contains information on how to do this on a wide variety of desktop browsers.