What are cookies and how do we use them?
Our website uses cookies to distinguish you from other users of our website. This helps us to provide you with a good experience when you visit our website and also assists us in making improvements.
A cookie is a small file (consisting of letters and numbers) that we store on your browser or elsewhere on your device.
We use the following flavours of cookies:
- Functionality cookies. These are used to recognise you when you return to our website. This enables us to personalise our content for you, including (where applicable) greet you by name and remember your preferences (for example, content tailored for your region or choice of language).
You can find more information about the individual cookies we use and the purposes for which we use them in the table below:
Necessary Cookies |
|||
Cookie |
Description |
Expiry |
Provider |
|
|
|
|
|
|
|
|
Preference Cookies |
|||
lang |
Remembers the user’s selected language version of a website |
Session |
Ads.linkedin.com |
Statistics Cookies |
|||
dc_gtm_UA-# |
Used by Google Tag. Manager to control the loading of a Google Analytics script tag. |
Session |
lockncharge.com |
Cookie |
Description |
Expiry |
Provider |
_ga |
Registers a unique ID that is used to generate statistical data on how the visitor uses the website. |
2 years |
lockncharge.com |
_gid |
Registers a unique ID that is used to generate statistical data on how the visitor uses the website. |
Session |
lockncharge.com |
dtCookie |
Unclassified |
Session |
lockncharge.com |
vuid |
Collects data on the user’s visits to the website, such as which pages have been read |
2 years |
Vimeo.com |
Marketing Cookies |
|||
Cookie |
Description |
Expiry |
Provider |
_omappvp |
Used by the lead generation platform OptinMonster to determine if the visitor is returning and has visited the website before. |
11 years. |
lockncharge.com |
_omappvs |
Used by the lead generation platform OptinMonster to determine if the visitor is visiting the website for the first time. |
Session |
lockncharge.com |
ads/ga-audiences |
Used by Google AdWords to re-engage visitors that are likely to convert to customers based on the visitor’s online behaviour across websites. |
Session |
google.com |
bcookie |
Used by the social networking service LinkedIn for tracking the use of embedded services. |
2 years |
|
BizolID |
Unclassified. |
179 days |
ads.linkedin.com |
bscookie |
Used by the social networking service, LinkedIn, for tracking the use of embedded services. |
2 years |
linkedin.com |
Collect |
Used to send data to Google Analytics about the visitor’s device and behaviour. |
Session |
google-analytics.com |
fr |
Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers. |
3 months |
facebook.com |
Idc |
Used by the social networking service, LinkedIn, for tracking the use of embedded services. |
Session |
linkedin.com |
MUID |
Used widely by Microsoft as a unique user ID. The cookie enables user tracking by synchronising the ID across many Microsoft domains. |
1 year |
bing.com |
MUID8 |
Unclassified. |
1 year |
bing.com |
visitor_id<uniquestring> |
This visitor_id cookie includes the name “visitor_id” plus the unique identifier for your account which is derived from the tracking code placed on the Site. The value stored is the unique ID for the visitor. |
10 years |
pardot.com |
visitor_id<uniquestring>-hash |
This stores the domain name (hash code) of site, a unique visitor id … |
10 years |
Pardot.com |
Pardot |
This session cookie is set when a Pardot user is logged in. |
|
Pardot.com |
tr |
Unclassified. |
Session |
facebook.com |
UsedMatchHistory |
Unclassified |
179 days |
ads.linkedin.com |
_vis_opt_exp_EXPERIMENT_ID_goal_GOAL_ID |
VWO uses cookies to run tests and to track user information. The cookies keep track of the variation a user has viewed and help to serve the same variation to the user consistently; track goals completed by a user; and determine whether a user is a part of a test. |
100 days |
|
|
Drift uses cookies to enable chat on our website and help identify users to better provide customer engagement. |
|
Drift/drift.com |
_hjClosedSurveyInvites |
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. |
365 days |
Boolean true/false |
_hjDonePolls |
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. |
365 days |
Boolean true/false |
_hjMinimizedPolls |
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. |
365 days |
Boolean true/false |
_hjShownFeedbackMessage |
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. |
365 days |
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 visitor recording starts and when data is sent through the WebSocket (the visitor 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. These attributes will only be saved if the user interacts with a Hotjar Feedback tool. |
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 visitor 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 visitor 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 |
_ |
Used to determine a user’s inclusion in an experiment and the expiry of experiments a user has been included in. | Depends on the length of the experiment, but typically 90 days. | google.com |
_ |
Used for campaigns mapped to Google Ads Customer IDs. | 24 hours | google.com |
_ |
Used for campaigns mapped to Google Ads Campaign IDs. | 24 hours | google.com |
_ |
Used for campaigns mapped to Google Ads Ad Group IDs | 24 hours | google.com |
_ |
Used for campaigns mapped to Google Ads Criterion IDs | 24 hours | google.com |
_ |
Stores the last utm_ query parameter. |
24 hours | google.com |
_ |
This cookie is created when running a redirect experiment. It stores the experiment ID, the variant ID and the referrer to the page that’s being redirected. | 10 seconds | google.com |
Unclassified Cookies |
|||
Cookie |
Description |
Expiry |
Provider |
_uetsid |
Unclassified |
Session |
lockncharge.com |
gwcc |
Unclassified |
3 months |
lockncharge.com |
wfwaf-authcookie-<uniquestring> |
This cookie is set by the WordPress security plugin “Wordfence”. It is used to authenticate user’s login request. This cookie is persistent and expires in 1 day. |
24 Hours |
WordFence Security Plugin |
wordfence_verifiedHuman |
Cookie set by the Wordfence Security WordPress plugin to protect the site against malicious attacks. |
24 hours |
WordFence Security Plugin |
wfvt_<uniquestring> |
These contain information about your general geographic location (used to remember your time zone, for example). These are known as session cookies and are deleted when you leave the site. |
30 minutes |
WordPress Default |
wordpress_logged_in_<uniquestring> |
After login, wordpress sets the wordpress_logged_in_[hash] cookie, which indicates when you’re logged in, and who you are, for most interface use. |
When the browsing session ends |
WordPress Default |
wordpress_sec_<uniquestring> |
Execute for your security page is better |
When the browsing session ends |
WordPress Default |
wordpress_test_cookie |
Purpose: accepts wordpress cookies on the website |
When the browsing session ends |
WordPress Default |
wp-settings-8 |
Purpose: supports optimized display and use of the wordpress website by the Administrator |
8 years |
WordPress Default |
wp-settings-time-8 |
Purpose: allows optimized display and use of the wordpress website by the Administrator |
8 years |
WordPress Default |
How to control and delete cookies
The majority of web browsers accept cookies, but you can usually change the web browser’s settings to refuse new cookies, disable existing ones or simply let you know when new ones are sent to your device.
In order to do this, follow the instructions provided by your browser (usually located within the “Help”, “Tools” or “Edit” facility) or you can click on the links below to access instructions from some of the most popular browsers:
For more information on how to manage cookies, please visit http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm.
However, please be aware that, if you refuse or disable cookies, some of the website’s functionality may be lost.
In addition, disabling a cookie or category of cookie does not delete the cookie from your browser, you will need to do this yourself from within your browser.
Changes to our use of cookies
Any changes to our use of cookies for this website will be posted here and if appropriate, signposted from our web pages highlighting any changes.
Contact Information
If you have any queries in relation to this notice, please contact us at [email protected].