What Cookies we and third parties use, why are they used, and how they impact you
A cookie is a small text file, typically of letters and numbers (with an ID tag), which may be placed on your computer or mobile when you access our Platforms. Cookies generally allow a website to recognise your device and browsing activity if you return to it, or if you visit another website which recognises the same cookies.
Different cookies perform different functions. Necessary cookies help you navigate through pages, “storing preferences” information and functionality cookies generally make the website easier to use. They exist just for the life of your current visit whilst you have your browser open. They are not stored on your hard disk and are erased when you exit your web browser.
Others, such as targeting and advertising cookies, identify products, goods or services you may be interested in and are used to provide you with tailored advertising and performance cookies help us collect aggregated information on how people use our Platforms.
When you visit our Platforms we request your consent for the non-necessary cookies to be placed on your device. To opt out of cookies, please see details below.
The table below explains the cookies we use and their purpose:
|Cookies allowed||exp_cookies_allowed||This cookie is necessary and is used to remember a user’s choice about cookies on our site. This cookie is, by default, set on arrival to the site with a value of ‘y’.||Persistent|
|Cookies declined||exp_cookies_declined||This cookie is necessary and is used to remember a user’s choice about cookies on our site. This cookie is set after a visitor chooses to opt out of receiving cookies, replacing the exp_cookies_allowed cookie.||Persistent|
|Cookies notice hidden||exp_cookie_notice_hidden||This cookie is necessary and is used to remember whether a visitor has previously been notified about cookie use on our site. It is set with a value of ‘y’, when the visitor dismisses the cookie information notice.||Persistent|
|Content management system||exp_last_visit exp_tracker exp_last_activity exp_stashid||These cookies are first party analytics cookies set by our content management system upon arrival to our site. Some of these cookies are deleted when a user closes their browser, the others have a variable expiry date.||Persistent: exp_last_visit exp_last_ activity Session: exp_tracker exp_stashid|
|Google Analytics||__utma __utmb __utmc __utmt __utmz||These cookies are analytics cookies and are used to collect information about how visitors use our site. We use the information to compile reports and to help us improve the site. The cookies collect information in an anonymous form, including the number of visitors to the site, where visitors have come to the site from and the pages they visited. Click here for an overview of privacy at Google.||Persistent: __utma __utmb __utmt __utmz Session: __utmc|
|Lead Forensics||_lfuuid||“The _lfuuid cookie allows a website to track visitor behavior on the sites on which the cookie is installed. Tracking is performed anonymously until a user identifies himself by submitting a form.”||Persistent|
|Hotjar||edSurveyInvites||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|
|Hotjar||_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|
|Hotjar||_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|
|Hotjar||_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|
|Hotjar||_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|
|Hotjar||_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|
|Hotjar||_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|
|Hotjar||_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|
|Hotjar||_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|
|Hotjar||_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|
|Hotjar||_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|
|Hotjar||_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|
|Hotjar||_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|
|Hotjar||_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|
|Hotjar||hjViewportId||This stores information about the user viewport such as size and dimensions.||Session|
|Hotjar||_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|
|Ads.LinkedIn||lang||Used to remember a user’s language setting||When session ends|
|UserMatchHistory||LinkedIn Ads ID syncing||1 month|
|bcookie||Browser Identifier cookie to uniquely identify devices accessing LinkedIn to detect abuse on the platform||2 years|
|lang||Used to remember a user’s language setting||When session ends|
|lidc||To optimize data center selection||1 day|
|lissc||Used to ensure there is correct SameSite attribute for all cookies in that browser||1 year|
|bscookie||Used for saving the state of 2FA of a logged in user||2 years|
Persistent cookies allow our website to recognise you when you return to our site another time. This provides us with useful analytics that help us optimise our website and your visits.
Session cookies exist just for the life of your current visit whilst you have your browser open. They are not stored on your hard disk and are erased when you exit your web browser.
Our websites also use the Facebook Pixel provided by Facebook Inc. (“Facebook”). We use the Facebook Pixel to track user behaviour, which enables us to send you relevant, targeted advertising on Facebook. It’s a tracking pixel that collects information about you, which is used to build and optimize target audiences for Facebook ads. For example, it collects and sends data, which is connected to an identifier such as your name or IP-address, to Facebook regarding that you have visited our site and what you clicked on. The pixel sends this data to Facebook where it’s matched with your user profile if you have one. So, when we create an ad on Facebook, we can ask Facebook to target the ad to people having visited our site and then it might pop up in your feed. We do not collect or store any personal data about you through the Pixel, but Facebook does. If you would like to opt out of this data processing, you can use the settings and opt out options provided by Facebook under facebook.com/ads/preferences/edit.
The LinkedIn Insight Tag is a piece of code that we have added to our websites to enable in-depth campaign reporting and to help us unlock valuable insights about our website visitors. We use the LinkedIn Insight Tag to track conversions, retarget website visitors, and unlock additional insights about members interacting with our LinkedIn adverts.
The LinkedIn Insight Tag enables the collection of metadata such as IP address information, timestamp, and events such as page views. All data is encrypted. The LinkedIn browser cookie is stored in a visitor’s browser until they delete the cookie or the cookie expires (there’s a rolling six-month expiration from the last time the visitor’s browser loaded the Insight Tag).
On many of the pages of our website you will see ‘social buttons’. These allow you to share or bookmark pages on our site.
Social media sites such as Twitter, Google, Facebook, and LinkedIn may collect information about your internet activity. They may record if you visit our Platforms and the specific pages you are on if you are logged into their services, even if you don’t click on the button. Where this happens, we may be joint controllers with the social media site over the data transmitted to them from our website. However they will be a separate controller for any subsequent use of your data. You can exercise your rights in relation to jointly controlled data against either us or the social media partner.
For their subsequent use, you should check the privacy and cookies policies of each of these sites to see how exactly they use your information and to find out how to opt out, or delete, such information.
1. Facebook cookies
2. Twitter cookies
3. Google cookies
4. LinkedIn cookies
Manually managing cookies
There are a number of ways you can manually manage cookies on your computer/device. Read more on the About Cookies website.
If you access the Internet from more than one computer/device it is important to ensure each browser is configured to suit your cookie preferences.
Do Not Track
If you wish to block all cookies all the time you can set your browser to do this. It is important to note that blocking cookies may result in some parts of our site not working properly. This may affect your browsing experience.
Our Platforms respect a DNT:1 signal as a valid browser setting communicating your preference.
You can object to the registration of cookies by configuring your browser settings as follows:
For Mozilla Firefox:
- Select the “Tools” menu, then go to “Options”
- Click on the “Privacy” icon
- Go to the “cookie” menu and select the options that suit you
For Microsoft Internet Explorer:
- Select the “Tools” menu, then go to “Internet Options”
- Click on the “Confidentiality” tab
- Select the desired level using the cursor (moving the slider to the top to block all cookies)
- In the menu bar, select “Edit”
- In the dropdown menu, select “Preferences”
- Select the “Security” icon
- To block cookies, choose the “Always” option. On this browser it is not possible to block cookies on a case-by-case basis.
- Click on the Google Chrome menu in the browser’s toolbar
- Click on “Settings”
- Click on “Show advanced settings”
- In the “Privacy” section, click on the button “Content settings”
- In the “Cookies” section, you can change the following settings: Block all cookies: select the option “Block sites from setting any data”.
How does Konex Media ask for Cookies consent?
Konex Media complies with applicable legislation on cookies. Where we need your consent a popup box will appear when you first access our Platform. This will ask you whether you consent to our use of not necessary cookies. If you do not consent to cookies, they will be disabled on your behalf. You are also free to disable cookies at any time through your browser’s settings, (for more information on how to do this please see the “how to delete cookies” tab at aboutcookies.org).
If you choose to disable cookies, please be aware that some parts of our Platforms may not work properly and it is likely that your Platform usage won’t be counted and measured as described above, so we won’t be able to take your actions into account when analysing data or when seeking to improve our service based on that analysis.