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:
SCVO uses the following types 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||To provide My SCVO account services||1 month|
|cookie_consent||A Boolean value used to remember if the user has dismissed the privacy information banner||No expiry|
We use Google Analytics to collect information about how you use SCVO services.
We store information about:
We do not:
All information we get through cookies and analytics will be treated in confidence.
We anonymise the last 3 digits of all user IP addresses for Google Analytics, so that we can ensure that you are protected (you can read more about how this works here). We can only see a general overview of which regions and cities you may come from, not where individuals access from.
You can opt out of Google Analytics cookies.
|_ga||This is used to understand and differentiate between different users.||13 Months|
|_ga_<container-id>||Used to persist session state. Container ID is the identifier for the Google Analytics account being used.||13 Months|
|_gid||_gid has a different ID for each page set on, and a timestamp. This assists with plotting user journeys.||24 Hours|
|Conversion||Help advertisers determine how many times people who click on their ads end up purchasing their products or performing a particular action (e.g. submitting a form, watching a video, downloading a PDF, etc). These cookies allow LinkedIn and the advertiser to determine that you clicked the ad and later visited the advertiser's site. Conversion cookies are not used by LinkedIn for personalised ad targeting and persist for a limited time only.||No expiry|
|JSESSIONID||General purpose platform session cookie. It is used to maintain an anonymous user session by the server.||Until end of session|
|lang||This cookie is used to set default locale/language.||Until end of session|
|lidc||This cookie is used for routing from Share buttons and ad tags||1 day|
|bcookie||This cookie is used by LinkedIn for identifying the Browser ID. It is set from LinkedIn share buttons and ad tags.||1 year|
|bscookie||This cookie is used by LinkedIn to recognize a secure Browser ID.||1 year|
Facebook pixel allows the website visitors’ behaviour to be tracked once they have been redirected to the provider’s website by clicking on a Facebook ad. This allows the efficacy of Facebook ads to be evaluated for statistical and market research purposes and future advertising measures to be optimised.
A randomly generated user ID and the time of the first visit are also recorded. This ID allows Facebook to recognise returning users on this website and compile data from previous visits.
|c_user; xs||We use these cookies to authenticate you and keep you logged in as you navigate between Facebook Pages.||365 days|
|sb; dbln||These cookies help us to identify your browser securely.||2 years|
|datr||This is a unique identifier for your browser that, amongst other things, helps us protect you from fraud. This cookie also helps us to identify browsers used by malicious actors and to prevent cyber security attacks.||2 years|
|csrf||This cookie helps us to keep your account secure.||Session|
|fr||Depending on your choices, this cookie is used to deliver, measure and improve the relevancy of ads.||90 days|
|_fbp; _fbc||These cookies identify browsers for businesses using our Meta Products for the purposes of providing advertising and site analytics services.||Session|
|oo||This cookie helps store your advertising preferences.||5 years|
|presence||This cookie supports your use of Messenger chat windows.||30 days|
|dpr; wd||These cookies help deliver an optimal experience for your device's screen.||7 days|
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|