Last updated January 12, 2023
Conductor LLC and its affiliates, including without limitation ContentKing Group B.V. (collectively, “Conductor” “we”, “us”, or “our
”) care about your privacy. We, as well as third parties that provide content and other functionality on our websites, currently available at www.conductor.com and www.contentkingapp.com (collectively, the “Websites
”) and the platforms available at app.conductor.com and app.contentking.com (collectively, the “Conductor Platform
WHAT ARE COOKIES AND OTHER TRACKING TECHNOLOGIES?
A cookie is a small file stored on your computer or other device that enables the entity that put the cookie on your computer or device to recognize it across different websites, services, devices, and browsing sessions. By storing such information, cookies can, among other things, remember your preferences and settings for the Services and help us understand how our users use the Services. To see the categories of Cookies that we use, please see Section 3 below. We also use third-party cookies – which are cookies from a domain different than the domain of the websites you are visiting – for our advertising and marketing efforts. Cookies can also be categorized as either (i) session cookies that do not retain any information and are deleted when the browsing session is ended or (ii) persistent cookies that remain on your device between sessions until they expire. WEB BEACONS / PIXEL TAGS
Web beacons or pixel tags and similar technologies are small bits of code, which are embedded in web pages, ads, and email, that communicate with third parties. Pixel tags can collect information such as the Internet Protocol (“IP”) address of the computer that downloaded the page on which the web beacon appears; the URL of the page on which the pixel tag appears; the time the page containing the pixel tag was viewed; the type of browser that fetched the pixel tag; and the identification number of any cookie on the computer previously placed by that server. We may use web beacons, for example, to count the number of users who have visited a particular web page, to deliver or communicate with cookies, and to understand usage patterns. We also may include web beacons in emails to understand whether messages have been opened, acted on, or forwarded.
Cookies help us to improve the Services and your experience thereon by customizing your experience and helping us analyze usage, technical and browsing metrics.
THE COOKIES WE USE
We use the following types of cookies on the Services and for the purposes described in the overview below:
- Essential Cookies: These Cookies are necessary for the functionality of the Services. These Cookies can be disabled in your browser but may prevent certain aspects of the Services from functioning.
- Performance or Enhanced functionality cookies: These Cookies allow us to improve the Website’s functionality by tracking usage on our Websites. In some cases, these Cookies can improve the speed with which we can process your request as they allow us to remember preferences that you’ve selected. De-selecting these Cookies may result in poorly tailored recommendations and slow site performance.
- Analytics Cookies: These Cookies may be set by third parties and help us to determine the source and amount of traffic to the Services and to better understand how our users use the Services. If you choose to disable these cookies, it will impact our ability to measure the performance of the Services.
- Advertising/Marketing/targeting Cookies: Advertising or targeting Cookies may be set by third parties to facilitate the delivery of targeted advertising, including through the delivery of interest-based advertising. We may use advertising or targeting Cookies on the Services.
Cookies and other techniques that are used on the Services
|# ||Cookie name ||Cookie Purpose ||Collected personal data ||Retention period ||Cookie host (including domain, if possible) ||Full legal name of third party with access |
|1.||JSESSIONID||User's session identifier. Used for session management in the Conductor Platform||None||Session||.conductor.com||Conductor|
|2||INGRESSCOOKIE||Used for load balancing||None||Session||.app.conductor.com||Conductor|
|3||accessToken||Holds the bearer JWT token from OIDC. Used for authentication||None||Session||.app.conductor.com||Conductor|
|4||accessToken-ck||Holds the bearer JWT token from OIDC. Used for cross domain authentication with the ContentKing platform||None||Session||.app.conductor.com||Conductor|
|5||fs_uid||Cookie set by FullStory. On page tracking||None||Year||.conductor.com||FullStory|
|6||__zlcmid||Cookie set by Zopim (Zendesk). Holds unique user id||None||Year||.conductor.com||Zendesk|
|7||searchlightAccountId||Cookie set by Conductor app for internal purpose. Holds an id of the current Account||None||Session||.app.conductor.com||Conductor|
|8||__utmt||Set by Google Analytics to store number of service requests||None||1 Minute||.app.conductor.com||Google|
|9||viewed0uibounceModal||Store state of having closed the exit intent modal||None||1 Month||.app.contentkingapp.com||ContentKing|
|10||nette-samesite||Communication with account service||None||session||.app.contentkingapp.com||ContentKing|
|11||session-timestamp||Utility for tracking of session start time||None||session||.app.contentkingapp.com||ContentKing|
|12||what-intent||Utility for tracking current input method||None||session||.app.contentkingapp.com||ContentKing|
|13||contentking||Store state for Website functioning||None||1 day||.app.contentkingapp.com||ContentKing|
Performance and functionality Cookies
|14 ||_hp2_id.*||Set by Heap Analytics to store and track user interaction with the Websites||None||14 months||.conductor.com||Heap|
|15||_hp2_ses_props.*||Set by Heap Analytics to store and track user interaction with the Websites||None||14 months||.conductor.com||Heap|
|16||_hp2_props.*||Set by Heap Analytics to store and track user interaction with the Websites||None||30 minutes||.conductor.com||Heap|
|17||__utmb||Set by Google Analytics to store time of visit||Unique user identifier||1 hour||.app.conductor.com||Google|
|18||__utmz||Set by Google Analytics to store used keyword and search engine||Unique user identifier||6 months||.app.conductor.com||Google|
|19||__utmc||Set by Google Analytics to store time of visit||Unique user identifier||Session||.app.conductor.com||Google|
|20||__utma||Set by Google Analytics to Store the calculation of days and time to purchase||Unique user identifier||2 Years||.app.conductor.com||Google|
|21||_pendo_visitorId.* ||Set by Pendo to store and track user to provide guided user recommendations||None||100 days||.conductor.com||Pendo|
|22||_pendo_launcher-closed.*||Set by Pendo to store and track user to provide guided user recommendations||None||10 days||.conductor.com||Pendo|
|23||_pendo_meta.*||Set by Pendo to store and track user to provide guided user recommendations||None||100 days||.conductor.com||Pendo|
|24||_pendo_lastStepAdvanced.* ||Set by Pendo to store and track user to provide guided user recommendations||None||10 seconds||.conductor.com||Pendo|
|25||_pendo_latestDismissedAutoAt.*||Set by Pendo to store and track user to provide guided user recommendations||None||10 seconds||.conductor.com||Pendo|
|26||_pendo_finalDismissedAutoAt.*||Set by Pendo to store and track user to provide guided user recommendations||None||10 seconds||.conductor.com||Pendo|
|27||_ga*||Store and count pageviews||None||2 years||.contentkingapp.com||Google Analytics|
|28||_gcl_au||Store and track conversions||None||3 months||.contentkingapp.com||Google AdSense|
|29||_gid||Store and count pageviews||None||1 day||.contentkingapp.com||Google Analytics|
|30||_dc_gtm_*||Store number of service requests||None||1 minute||.contentkingapp.com||Google Analytics|
|31||wd||Browser information & window dimensions||None||1 day||.contentkingapp.com||Facebook|
|32 ||intercom-session-*||Contact, communication and support||None||1 week||.app.contenking.com||Intercom|
|33||intercom-id-*||Contact, communication and support||None||9 months||.app.contenking.com||Intercom|
|39||tap_vid||Affiliate Marketing||None||1 year||.app.contenking.com||Tapfiliate|
|46||sb||Marketing||None||1 year, 1 month, 14 days||.app.contenking.com||Facebook|
|47||datr||Marketing||None||1 year, 1 month, 14 days||.app.contenking.com||Facebook|
|48||muc||Marketing||None||1 year, 10 months, 3 days||.app.contenking.com||Twitter|
|49||muc-ads||Marketing||None||1 year, 10 months, 3 days||.app.contenking.com||Twitter|
TRANSFER OF PERSONAL DATA OF EEA RESIDENTS
We transfer personal data to countries with data protection laws that are considered inadequate by the European Commission. When we do so, we have taken appropriate (supplemental) safeguards to ensuring an equivalent level of data protection by concluding Standard Contractual Clauses approved by the European Commission
with the receiving party located in such third country (in accordance with article 46.2(c) of the General Data Protection Regulation). Transfers to adequate countries
Depending on your location and the services you use, we also transfer personal data recognized by the European Commission as providing an appropriate level of data protection, such as the United Kingdom (see here
a list of adequacy decisions taken by the European Commission). You can contact us using the contact details below, if you would like to receive more information on the measures taken to safeguard your information to the extent they are transferred outside the EEA.
. To opt-out of internet-based advertising by all companies which participate in the self-regulatory Digital Advertising Alliance (“DAA”), please visit http://www.aboutads.info/choices/
. If you are located in the EU, you can find out about cookies and opt out of interest-based advertising by visiting youronlinechoices.com
. To limit interest-based advertising on your mobile device, you can review and adjust the settings provided by your device manufacturer, such as “Limit Ad Tracking” for iOS or “Opt-out of interest-based ads” for Android. Please note that it is not possible for us to allow you to carry your cookie settings with you between your browsers and devices, so you will need to change these cookie settings on each browser and or device that you use.