Cookies
To help improve this site we may place small data files, known as cookies, onto your computer, smartphone or other internet device. Cookies are used by most websites to help personalise your web experience.
We use two different types of cookie
- ‘necessary’ cookies which remember that you’ve logged in and what your cookie preferences are
- analytics cookies which measure how you use the website, without identifying you personally, so we can make sure it meets your needs. These are optional.
We also use Facebook’s Conversion Tracking Pixel – see below for more information.
You can opt out of our analytics cookies here
Necessary cookies
Our member login system sets a temporary ‘session cookie’ to allow it to run smoothly. This is classed as strictly necessary to the operation of our site, so you can’t opt out of it. You can disable it by changing your browser settings to not accept it, but this means that some parts of the site won’t work. We also use a cookie which records that you’ve accepted cookies. These are the necessary cookies:
| Name | Expiry | Application | Description |
| prs | End of session | Website | Session cookie to maintain your browsing session |
| TabViewSelectedTab | 1 year | Website | Records which tab you last viewed for tabbed content |
| analytics | 90 days | Website | Records whether you have opted to allow analytics cookies to be set |
| _hjClosedSurveyInvites | 365 days | Website | 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. |
| _hjDonePolls | 365 days | Website | 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. |
| _hjMinimizedPolls | 365 days | Website | 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. |
| _hjShownFeedbackMessage | 365 days | Website | 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. |
| _hjid | 365 days | Website | 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. |
| _hjRecordingLastActivity | Session | Website | 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). |
| _hjTLDTest | Session | Website | 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. |
| _hjUserAttributesHash | Session | Website | 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. |
| _hjCachedUserAttributes | Session | Website | 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. |
| _hjLocalStorageTest | Under 100ms | Website | 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. |
| _hjIncludedInPageviewSample | 30 minutes | Website | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site’s pageview limit. |
| _hjIncludedInSessionSample | 30 minutes | Website | 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. |
| _hjAbsoluteSessionInProgress | 30 Minutes | Website | This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
| _hjFirstSeen | Session | Website | 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. |
| hjViewportId | Session | Website | This stores information about the user viewport such as size and dimensions. |
| _hjRecordingEnabled | Session | Website | 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. |
Optional cookies
We use analytics to collect anonymous information about how people use our site. An analytics cookie records which pages you visit, how long you are on the site, how you got here and what you click on. It also records your general geographical vicinity, and information about your browser and operating system. It does not collect or store any personal information about you (eg your name or address) so it doesn’t identify who you are.
Find out how Google Analytics collects and processes data.
The optional cookies we use are shown below:
| Name | Expiry | Application | Description |
| _ga | 2 years | Google Analytics | Used to distinguish users |
| _gid | 24 hours | Google Analytics | Used to distinguish users |
| _gat | 1 minute | Google Analytics | Used to throttle request rate. This cookie will have a short string of letters and numbers after it. |
| _pk_id | 2 years after the latest page view | Piwik Analytics | For tracking goal conversions |
| _pk_ref | 6 months from the date of creation | Piwik Analytics | Contains the referrer URL for the entry point of this site visit session. |
| _pk_ses | 30 minutes after the latest page view | Piwik Analytics | Refers to a single site-visit session and allows all visited pages to be associated with this site-visit. Allows recording of the number of visits per page, rather than just the number of hits. |
| piwik_ignore | 2 years | Piwik Analytics | Records opt-out from Piwik analytics |
| uid | Vimeo videp player | Vimeo analytics tracking id | |
| vuid | Vimeo video player | Vimeo analytics unique id |
Facebook conversion tracking pixel
With your permission, our website uses Facebook’s Conversion Tracking Pixel. This enables us to find out how many people have visited our website after clicking on an advert they’ve seen on Facebook. We use this for statistical and marketing purposes, to help us assess the effectiveness of our Facebook ads. The collected data we receive is anonymous – Prospect cannot see the personal data of any individual user. However, Facebook also saves and processes the collected data. It can connect this with your Facebook account and use it for its own advertising purposes, in accordance with its own Data Use Policy. Facebook Conversion Tracking also allows Facebook and its partners to show you advertisements on and outside Facebook. A cookie will also be saved onto your computer for these purposes.
You can revoke your permission for Facebook to use its Conversion Tracking Pixel at https://www.facebook.com/ads/website_custom_audiences/.
Only users over 13 years of age can give their permission for the Facebook Conversion Tracking Pixel. If you are younger than 13, please consult your legal guardians.
Privacy policy
Prospect’s privacy policy sets out the terms on which we hold and process data.