Sign up for a personal SCVO account.
After verifying your email address, you can link your account to an organisation. If your organisation is an SCVO member or supporter you will be able to access exclusive content. Find out more
A cookie is a small file of letters and numbers that we may store on your browser or the hard drive of your computer or device. They cannot be used to identify you personally.
Cookies are used to improve services for you through, for example:
The Site uses the following categories of cookies:
You can find more detailed information about the individual cookies we use and the purposes for which we use them in the tables below:
|scvo_account||Unique token||To provide SCVO Account services||1 month|
|CookieInfoScript||1||A Boolean value used to remember if the user has dismissed the privacy information banner||No expiry|
|cjs_token||Randomly generated number||Used to allow a CJS user to sign in||1 month|
|cjs_cookie||Randomly generated number||Used to allow a CJS user to sign in||1 month|
|_utma||Randomly generated number||This cookie is typically written to the browser upon the first visit to our site from that web browser. This cookie is used to determine unique visitors to our site and it is updated with each page view. Additionally, this cookie is provided with a unique ID that Google Analytics uses to ensure both the validity and accessibility of the cookie as an extra security measure.||2 years|
|_utmb||Randomly generated number||This cookie is used to establish and continue a user session with our site. Each time a user visits a different page on our site, this cookie is updated to expire in 30 minutes, continuing a single session for as long as user activity continues within 30 minute intervals. This cookie expires when a user pauses on a page on our site for longer than 30 minutes.||30 minutes|
|_utmc||Randomly generated number||This cookie operates in conjunction with the utmb cookie to determine whether or not to establish a new session for the user. Should a user visit our site, exit the browser and then return to our website within 30 minutes, the absence of the utmc cookie indicates that a new session needs to be established.||End of session|
|_utmz||Randomly generated number + info on how the site was reached (e.g. directly or via a link, organic search or paid search)||This cookie stores the type of referral used by the visitor to reach our site, whether via a direct method, a referring link, a website search, or a campaign such as an ad or an email link. It is used to calculate search engine traffic, ad campaigns and page navigation within our own site. The cookie is updated with each page view to our site.||6 months|
For further details, please see the ‘about Hotjar’ section of Hotjar’s support site.
|_hjClosedSurveyInvites||Hotjar cookie. This cookie is set once a visitor interacts with a Survey invitation modal popup. It is used to ensure that the same invite does not re-appear if it has already been shown.||365 days|
|_hjDonePolls||Hotjar cookie. This cookie is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not re-appear if it has already been filled in.||365 days|
|_hjMinimizedPolls||Hotjar cookie. This cookie is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site.||365 days|
|_hjDoneTestersWidgets||Hotjar cookie. This cookie is set once a visitor submits their information in the Recruit User Testers widget. It is used to ensure that the same form does not re-appear if it has already been filled in.||365 days|
|_hjIncludedInSample||Hotjar cookie. This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels.||365 days|
|_hjShownFeedbackMessage||This cookie is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if they navigate to another page where it is set to show.||365 days|
|_hjid||Hotjar cookie. This cookie 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|
|_hjRecordingLastActivity||This should be found in sessionStorage (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 ||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 immediately after creating it so the expected storage time is under 100ms.||N/A|
|_hjptid||This cookie is set for logged in users of Hotjar, who have Admin Team Member permissions. It is used during pricing experiments to show the Admin consistent pricing across the site.||Session|
|_hjAbsoluteSessionInProgress||The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information.||30 minutes|
We use Pardot for email campaign and bulletin usage tracking.
For further details, please see this page about Pardot cookies on the Salesforce support site.
|visitor_id<accountid>||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.||365 days|
|pi_opt_in<accountid>||If Tracking Opt-in preferences is enabled, the pi_opt_in cookie is set with a ||365 days|
|visitor_id<accountid>-hash||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.||365 days|
|lpv<accountid>||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.||30 minutes|
|pardot||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|