www.leadforensics.com
Open in
urlscan Pro
2606:4700::6812:1e3c
Public Scan
Submitted URL: https://email.martechuk.co.uk/c/1pqHODctP9Ocv1bXv5zEcZM0fJf
Effective URL: https://www.leadforensics.com/privacy-policy/
Submission Tags: falconsandbox
Submission: On September 24 via api from US — Scanned from DE
Effective URL: https://www.leadforensics.com/privacy-policy/
Submission Tags: falconsandbox
Submission: On September 24 via api from US — Scanned from DE
Form analysis 2 forms found in the DOM
GET /
<form role="search" method="get" class="et_pb_searchform" action="/" data-hs-cf-bound="true">
<div>
<label class="screen-reader-text" for="s">Search for:</label>
<input type="text" name="s" placeholder="Search website" class="et_pb_s" style="padding-right: 44px;">
<input type="hidden" name="et_pb_searchform_submit" value="et_search_proccess">
<input type="hidden" name="et_pb_include_posts" value="yes">
<input type="hidden" name="et_pb_include_pages" value="yes">
<input type="submit" value="⚲" class="et_pb_searchsubmit" style="">
</div>
</form>POST /privacy-policy/#gf_21
<form method="post" enctype="multipart/form-data" target="gform_ajax_frame_21" id="gform_21" action="/privacy-policy/#gf_21" data-formid="21" novalidate="" data-hs-cf-bound="true">
<div class="gform-body gform_body">
<div id="gform_fields_21" class="gform_fields top_label form_sublabel_below description_below validation_below">
<fieldset id="field_21_2" class="gfield gfield--type-name gfield--width-full gfield_contains_required field_sublabel_hidden_label gfield--no-description field_description_below hidden_label field_validation_below gfield_visibility_visible"
data-js-reload="field_21_2">
<legend class="gfield_label gform-field-label gfield_label_before_complex">Name<span class="gfield_required"><span class="gfield_required gfield_required_text">(Required)</span></span></legend>
<div class="ginput_complex ginput_container ginput_container--name no_prefix has_first_name no_middle_name no_last_name no_suffix gf_name_has_1 ginput_container_name gform-grid-row" id="input_21_2">
<span id="input_21_2_3_container" class="name_first gform-grid-col gform-grid-col--size-auto">
<input type="text" name="input_2.3" id="input_21_2_3" value="" aria-required="true" placeholder="Full name">
<label for="input_21_2_3" class="gform-field-label gform-field-label--type-sub hidden_sub_label screen-reader-text">Full Name</label>
</span>
</div>
</fieldset>
<div id="field_21_3" class="gfield gfield--type-email gfield--width-full gfield_contains_required field_sublabel_below gfield--no-description field_description_below hidden_label field_validation_below gfield_visibility_visible"
data-js-reload="field_21_3"><label class="gfield_label gform-field-label" for="input_21_3">Email<span class="gfield_required"><span class="gfield_required gfield_required_text">(Required)</span></span></label>
<div class="ginput_container ginput_container_email">
<input name="input_3" id="input_21_3" type="email" value="" class="large" placeholder="Business email" aria-required="true" aria-invalid="false">
</div>
</div>
<div id="field_21_18" class="gfield gfield--type-phone gfield--width-full gfield_contains_required field_sublabel_below gfield--no-description field_description_below field_validation_below gfield_visibility_visible"
data-js-reload="field_21_18"><label class="gfield_label gform-field-label screen-reader-text" for="input_21_18">Direct dial<span class="gfield_required"><span class="gfield_required gfield_required_text">(Required)</span></span></label>
<div class="ginput_container ginput_container_phone"><input name="input_18" id="input_21_18" type="tel" value="" class="large" placeholder="Direct dial" aria-required="true" aria-invalid="false"></div>
</div>
<div id="field_21_5" class="gfield gfield--type-text gfield--width-full gfield_contains_required field_sublabel_below gfield--no-description field_description_below hidden_label field_validation_below gfield_visibility_visible"
data-js-reload="field_21_5"><label class="gfield_label gform-field-label" for="input_21_5">Website<span class="gfield_required"><span class="gfield_required gfield_required_text">(Required)</span></span></label>
<div class="ginput_container ginput_container_text"><input name="input_5" id="input_21_5" type="text" value="" class="large" placeholder="Website URL" aria-required="true" aria-invalid="false"> </div>
</div>
<div id="field_21_11" class="gfield gfield--type-hidden gform_hidden field_sublabel_below gfield--no-description field_description_below field_validation_below gfield_visibility_visible" data-js-reload="field_21_11">
<div class="ginput_container ginput_container_text"><input name="input_11" id="input_21_11" type="hidden" class="gform_hidden" aria-invalid="false" value=""></div>
</div>
<div id="field_21_12" class="gfield gfield--type-hidden gform_hidden field_sublabel_below gfield--no-description field_description_below field_validation_below gfield_visibility_visible" data-js-reload="field_21_12">
<div class="ginput_container ginput_container_text"><input name="input_12" id="input_21_12" type="hidden" class="gform_hidden" aria-invalid="false" value=""></div>
</div>
<div id="field_21_13" class="gfield gfield--type-hidden gform_hidden field_sublabel_below gfield--no-description field_description_below field_validation_below gfield_visibility_visible" data-js-reload="field_21_13">
<div class="ginput_container ginput_container_text"><input name="input_13" id="input_21_13" type="hidden" class="gform_hidden" aria-invalid="false" value=""></div>
</div>
<div id="field_21_14" class="gfield gfield--type-hidden gform_hidden field_sublabel_below gfield--no-description field_description_below field_validation_below gfield_visibility_visible" data-js-reload="field_21_14">
<div class="ginput_container ginput_container_text"><input name="input_14" id="input_21_14" type="hidden" class="gform_hidden" aria-invalid="false" value=""></div>
</div>
<div id="field_21_15" class="gfield gfield--type-hidden gform_hidden field_sublabel_below gfield--no-description field_description_below field_validation_below gfield_visibility_visible" data-js-reload="field_21_15">
<div class="ginput_container ginput_container_text"><input name="input_15" id="input_21_15" type="hidden" class="gform_hidden" aria-invalid="false" value=""></div>
</div>
<div id="field_21_16" class="gfield gfield--type-hidden gform_hidden field_sublabel_below gfield--no-description field_description_below field_validation_below gfield_visibility_visible" data-js-reload="field_21_16">
<div class="ginput_container ginput_container_text"><input name="input_16" id="input_21_16" type="hidden" class="gform_hidden" aria-invalid="false" value=""></div>
</div>
<div id="field_21_17" class="gfield gfield--type-hidden gform_hidden field_sublabel_below gfield--no-description field_description_below field_validation_below gfield_visibility_visible" data-js-reload="field_21_17">
<div class="ginput_container ginput_container_text"><input name="input_17" id="input_21_17" type="hidden" class="gform_hidden" aria-invalid="false" value=""></div>
</div>
<div id="field_21_19" class="gfield gfield--type-hidden gform_hidden field_sublabel_below gfield--no-description field_description_below field_validation_below gfield_visibility_visible" data-js-reload="field_21_19">
<div class="ginput_container ginput_container_text"><input name="input_19" id="input_21_19" type="hidden" class="gform_hidden" aria-invalid="false" value="e1f289d1-b461-41c6-a2bf-3fec90094c6e"></div>
</div>
<div id="field_21_20" class="gfield gfield--type-hidden gform_hidden field_sublabel_below gfield--no-description field_description_below field_validation_below gfield_visibility_visible" data-js-reload="field_21_20">
<div class="ginput_container ginput_container_text"><input name="input_20" id="input_21_20" type="hidden" class="gform_hidden" aria-invalid="false" value="643c570e-df06-4d5b-baf6-3804588f6f6d"></div>
</div>
<div id="field_21_21" class="gfield gfield--type-hidden gform_hidden field_sublabel_below gfield--no-description field_description_below field_validation_below gfield_visibility_visible" data-js-reload="field_21_21">
<div class="ginput_container ginput_container_text"><input name="input_21" id="input_21_21" type="hidden" class="gform_hidden" aria-invalid="false" value="whizeo_campaign_id"></div>
</div>
<div id="field_21_22" class="gfield gfield--type-hidden gform_hidden field_sublabel_below gfield--no-description field_description_below field_validation_below gfield_visibility_visible" data-js-reload="field_21_22">
<div class="ginput_container ginput_container_text"><input name="input_22" id="input_21_22" type="hidden" class="gform_hidden" aria-invalid="false" value="1865679250.1727192988"></div>
</div>
<div id="field_21_23" class="gfield gfield--type-hidden gform_hidden field_sublabel_below gfield--no-description field_description_below field_validation_below gfield_visibility_visible" data-js-reload="field_21_23">
<div class="ginput_container ginput_container_text"><input name="input_23" id="input_21_23" type="hidden" class="gform_hidden" aria-invalid="false" value="1865679250.1727192988"></div>
</div>
<div id="field_21_24" class="gfield gfield--type-honeypot gform_validation_container field_sublabel_below gfield--has-description field_description_below field_validation_below gfield_visibility_visible" data-js-reload="field_21_24"><label
class="gfield_label gform-field-label" for="input_21_24">Email</label>
<div class="ginput_container"><input name="input_24" id="input_21_24" type="text" value="" autocomplete="new-password"></div>
<div class="gfield_description" id="gfield_description_21_24">This field is for validation purposes and should be left unchanged.</div>
</div>
</div>
</div>
<div class="gform_footer top_label"> <input type="submit" id="gform_submit_button_21" class="gform_button button" value="Try For Free"
onclick="if(window["gf_submitting_21"]){return false;} if( !jQuery("#gform_21")[0].checkValidity || jQuery("#gform_21")[0].checkValidity()){window["gf_submitting_21"]=true;} "
onkeypress="if( event.keyCode == 13 ){ if(window["gf_submitting_21"]){return false;} if( !jQuery("#gform_21")[0].checkValidity || jQuery("#gform_21")[0].checkValidity()){window["gf_submitting_21"]=true;} jQuery("#gform_21").trigger("submit",[true]); }"><span
aria-hidden="true"></span> <input type="hidden" name="gform_ajax" value="form_id=21&title=&description=&tabindex=0&theme=gravity-theme">
<input type="hidden" class="gform_hidden" name="is_submit_21" value="1">
<input type="hidden" class="gform_hidden" name="gform_submit" value="21">
<input type="hidden" class="gform_hidden" name="gform_unique_id" value="">
<input type="hidden" class="gform_hidden" name="state_21" value="WyJbXSIsIjFkZDNjN2FkOGIzMmI1YzNjZDAxN2E3NTdiOTE1ZWQwIl0=">
<input type="hidden" class="gform_hidden" name="gform_target_page_number_21" id="gform_target_page_number_21" value="0">
<input type="hidden" class="gform_hidden" name="gform_source_page_number_21" id="gform_source_page_number_21" value="1">
<input type="hidden" name="gform_field_values" value="">
</div>
</form>Text Content
* Plans * Pricing * Solutions * For Sales * For Marketing * For Account Management * For Agencies * Products * Product Features * Integrations * How it Works * Customers * Case Studies * Resources * Webinars & Events * Blog * Podcasts * News * Revenue Calculator * About * Contact Us * Careers & * Customer Login * USA: 720 362 5033 * UK: 0207 206 7293 * Login Try for free5 * Plans * Pricing * Solutions * For Sales * For Marketing * For Account Management * For Agencies * Products * Product Features * Integrations * How it Works * Customers * Case Studies * Resources * Webinars & Events * Blog * Podcasts * News * Revenue Calculator * About * Contact Us * Careers & * Customer Login Try for free5 PRIVACY POLICY https://www.leadforensics.com/call-recording-policy/Lead Forensics is software that reveals the identity of your anonymous website traffic and turns them into actionable leads within a business-to-business environment. As a leading provider of SaaS solutions, we are committed to providing a high calibre data-led solution for all of our clients; as part of that, we take data compliance extremely seriously and are proactive in ensuring the compliance of both the SaaS solutions we provide to our customers as well as ensuring compliance as a business entity in our own right. The purpose of this statement is to provide information regarding how and why Lead Forensics collect, process and store data, as well as provide the appropriate contact information should you wish to request the information we hold about you, withdraw from processing or request deletion of any data we hold about you. LEAD FORENSICS MARKETING AND SALES DATA As an organisation that processes business-related data, Lead Forensics has assessed all six grounds for lawful processing of personal data. It has selected ‘Legitimate Interests’ as the most suitable legal ground for processing Lead Forensics marketing and sales data. Lead Forensics collects, processes and stores data relating to businesses and decision-makers. We believe we process data about individuals likely to be interested in the Lead Forensics product. Considered ‘Legitimate Interest’, this is based upon specific criteria, including the business industry sector, size of the organisation, and the individual’s job function within the organisation. Our typical segmentation includes marketing, sales, business development, Managing Director and owner-related job functions. This list is not exhaustive, and other variables may apply. We will only collect, process, and store the essential information required to contact the data subjects within a business environment. The personal data we collect is limited to: * First name * Last name * Email address * Social profiles (limited to LinkedIn) * The business IP address * Other business-related data may also be processed, including business name, job function, turnover and business address; however, we will never collect sensitive personal data. The data collected will be used to communicate marketing and sales messages relating to the Lead Forensics product, based on the data subject’s job function. Lead Forensics specifically only sends messages to those we believe are likely to be interested in the Lead Forensics product based upon the organisation they are employed by and their job function within that organisation. Messages from Lead Forensics could be delivered via email, social media, telephone or any other business-to-business (B2B) marketing methods that may be relevant. When you send Lead Forensics an enquiry or booking form via our website or one of our microsites, you will be asked to provide your contact details. We will use the data you provide to process your request and may use it to inform you by email, telephone or mail about other Lead Forensics products and services that we feel may be of interest to you; it is deemed that as you have visited the Lead Forensics website and provided us with your contact information that you are legitimately interested in our products and services. You have the right to object from any method of correspondence, using the unsubscribe button on an email, by informing the telephone operator or contacting us via any of the methods below. All collected phone numbers are checked against the TPS (Telephone Preference Service), and CTPS (Corporate Telephone Preference Service) lists daily. This ensures our team does not contact any individual or business that has registered their phone number on either of these lists. HOW WE PROCURE DATA At Lead Forensics, we procure data in various ways, according to the lawful basis of ‘Legitimate Interests’. If you have received correspondence from us, we will have procured your data in one of the following ways: You have requested information from Lead Forensics on a previous occasion. Someone has sent us your e-mail address requesting information about our articles and services be sent to you. You or someone else has expressly shared your contact details to receive information now and in the future. We have previously met at an event, and your business card or contact details were handed to us willingly. You or a business colleague has visited our website, and we believe there is a genuine legitimate interest in our services. You have previously connected with a team member via LinkedIn and discussed our services. During our communications with you, including via email, we may collect information such as your IP address. We may use this information to improve our responsiveness to our prospects and customers, for example by being able to engage when an action has been taken upon an email we have sent. In addition, we may use non-personally identifiable attributes from the communication, such as the business name. A team member has found your business and your contact details online, believing that your business would genuinely be interested in the Lead Forensics product. Based upon your job function aligning with our typical customer profiles, they have made contact to introduce you to our product. Your data has been purchased by a registered third-party data supplier, which will have been segmented by industry, organisation size and job function based on our typical customer profiles. (Due diligence checks around UK GDPR compliance will have been conducted accordingly). LEGITIMATE INTEREST ASSESSMENT (LIA) Lead Forensics has carried out a Legitimate Interest Assessment (LIA). Based upon that assessment, it is deemed that the rights and freedoms of the data subjects would not be overridden in our correspondence regarding Lead Forensics. In no way would a data subject be caused harm by our post. Based upon our segmentation by an organisation and by specific job function, coupled with our processing of personal data within a business environment, we believe that any individual that receives correspondence from Lead Forensics in direct marketing or sales capacity could be legitimately interested in the Lead Forensics solution. It is also deemed that direct marketing and sales are necessary for promoting Lead Forensics to professionals in the business to increase awareness of our SaaS solution in the marketplace. Per the ICO guidance, Lead Forensics can confirm: * We have checked that legitimate interests are the most appropriate basis * We understand our responsibility to protect the individual’s interests * We have conducted a Legitimate Interests Assessment (LIA) and kept a record of it to ensure that we can justify our decision * We have identified the relevant legitimate interests * We have checked that the processing is necessary and there is no less intrusive way to achieve the same result * We have done a balancing test and are confident that the individual’s interests do not override those legitimate interests * We only use individual’s data in ways they would reasonably expect * We are not using people’s data in ways they would find intrusive or which could cause them harm * We do not process the data of children * We have considered safeguards to reduce the impact where possible * We will always ensure there is an opt-out/ability to object * Our LIA did not identify a significant privacy impact, and therefore we do not require a DPIA * We keep our LIA under review every six months and will repeat it if circumstances change * We include information about our legitimate interests in our privacy notice DATA STORAGE AND RETENTION The data held within the Lead Forensics CRM system is processed and stored in the UK within a secure environment. Lead Forensics has an in-house data verification team responsible for ensuring the validity and quality of the data contained within the Lead Forensics CRM system ‘Cyclone’. The team continually cleanse the data held within the CRM system, completing an entire cleanse cycle at least once every 12 months. Any out-of-date records are placed into a deletion queue securely purged four times in 12 months. CALL RECORDINGS All calls are recorded for training and monitoring purposes in the interest of our employees, customers, and prospective customers. Please see our Call Recording Policy for more information RECORDING OF WEBINARS Please note that we may record our webinar sessions. The presenter represents a data controller of personal data recorded in this webinar. The purpose of recording webinars is to provide a referenceable resource for ourselves, our customers and others, allowing people to listen to the webinar recording in the future. The lawful basis for processing is our legitimate interests: to use recordings of webinars to promote our business and provide a valuable resource to interested parties. We recognise that it might also be in the interests of third parties such as the participants in this session or those who wish to review the recording. You have the right to object to processing based on a legitimate interest, and we would ask you to inform us if you wish to raise such an objection. If you would like us to pause the recording during a session, please let us know, and we will endeavour to respect your wishes. If you subsequently listen to a recording and wish to object to any personal data about you being included in it, please let us know. We will endeavour to edit or erase the recording. You also have the right to request access to and rectify or personal erasure data contained in recordings and the right to restrict processing and data portability in certain circumstances. You have the right to complain to the supervisory authority in the UK, the Information Commissioner’s Office. Please see the section ‘Your Rights as a Data Subject’ for more information. We have chosen to deliver our sessions through a video conference platform (e.g. Teams or Zoom), making the platform’s provider a data processor. The processor’s identity will be available when you log into a session. If you are in any doubt, please ask. If we make the recording available on our website, social media, or YouTube channel, other recipients may access it: people we do not know and have no control over. If we transfer the recordings to a third country (e.g. the USA), we will ensure that a lawful mechanism is in place to provide sufficient safeguards under Chapter 5 of the UK GDPR. Details of the securities will be published in the privacy information available on our provider’s website and upon request. We intend to retain the recordings as long as they are relevant to us/other people. For example, we may arrange future webinars covering the same topics as today’s webinar, which may act as a trigger for replacing the recording of this session with another recording. If you have any questions about how we process personal data, please do not hesitate to contact us via the presenter or by using the contact information detailed below. SUBJECT ACCESS REQUEST If you wish to make a Subject Access Request to enact any of your below-listed rights, you can do so by: Emailing: data-compliance@leadforensics.com Or by writing to: Data Compliance, Lead Forensics, Building 3000, Lakeside, North Harbour, Portsmouth, PO6 3EN. Additional proof of identification may be requested to verify your identity before disclosing personal data. We will process and respond to your request within 30 days; this service will be free of charge. RIGHT OF ACCESS TO DATA HELD Under article 15 of UK GDPR, You have a right to access the personal data we hold on you. If you believe that we are processing your data, you can make a Subject Access Request in regard of: * The purposes of our processing * The categories of personal data concerned * The categories of recipients to whom the personal data have been disclosed. * The envisaged period for which the personal data will be stored. * The existence of the right to request from the controller rectification or erasure of your personal data, the restriction of processing of your personal data, or the objection to processing your personal data. * The right to complain to a supervisory authority. * Where the personal data was not collected directly from you, any available information about the data source. * The existence of automated decision-making, including profiling, and any meaningful information about the logic involved and the significance and the envisaged consequences of such processing for you. * Information on the appropriate safeguards that have been put in place when your personal data has been transferred to an international organisation or third country. * A copy of the personal data that we process (as long as doing so does not adversely affect the rights and freedoms of others). RIGHT TO RECTIFICATION Under Article 16 of the UK GDPR, Lead Forensics must rectify, without undue delay, any inaccurate personal data if you believe that the personal data we hold on you is incorrect or incomplete. In that case, you can make a Subject Access Request to inform us of this inaccuracy and provide us with the necessary data to correct/complete our data files. RIGHT TO ERASURE (‘RIGHT TO BE FORGOTTEN’) Under Article 17 of the UK GDPR, you have the ‘right to be forgotten’. If you make an erasure request, a minimal amount of your personal data will be kept in our suppression files. This enables Lead Forensics to fulfil our legal obligation under Article 6(1)(c) of the UK GDPR to ensure that you are not contacted again. If you are not added to our suppression file, there is a risk that your data may be processed again in the future if your details are re-added to our software and our data procurement team. Therefore, we will keep a minimal amount of data (where applicable, name, business phone number, business email, and LinkedIn URL where applicable) in a suppression file with a note to say that you no longer wish to receive communication so that you are not contacted again in the future. Please enter your details here if you wish to unsubscribe from email communications. RIGHT TO RESTRICTION OF PROCESSING Under Article 18 of the UK GDPR, you have the right to request that Lead Forensics does not further process your personal data beyond storing it. This can be a useful alternative to requesting erasure. For example, you can ask to ensure that your entire data record is kept in our suppression files but will not be processed for sales or marketing purposes. RIGHT TO OBJECT Under Article 21 of the UK GDPR, you have the right to object to processing your personal data for direct marketing purposes. You have the right to object to receiving communication from Lead Forensics. All emails from Lead Forensics include an ‘unsubscribe’ option. If you are contacted via LinkedIn, you can reply to the message to request no other communication. If you receive a telephone call from us, you have the right to request not to receive any further calls verbally. Lead Forensics has a companywide CRM system, and your request to object will be logged to ensure that you do not receive other communication. YOUR RIGHT TO COMPLAIN TO A SUPERVISORY AUTHORITY Under Article 77 of the UK GDPR, you have the right to complain to a supervisory authority if you believe processing your personal data infringes your rights. The UK’s Information Commissioner’s Office (ICO) is the supervisory authority. If you wish to complain to the ICO, you can do so here: https://ico.org.uk/make-a-complaint/. Or by calling their helpline on 0303 123 1113 For questions relating to this policy, please get in touch with: data-compliance@leadforensics.com GET YOUR OWN LIVE DEMO NOW Speak to an expert UK: 0207 206 7293 | USA: 720 362 5033 PRODUCT * Overview * For Sales * For Marketing * Pricing CUSTOMERS * Case Studies RESOURCES * Webinars and Events * Blog * News * Revenue Calculator ABOUT US * Contact Us * Careers * Partnerships * Customer Login Search for: Show me my B2B website visitors Name(Required) Full Name Email(Required) Direct dial(Required) Website(Required) Email This field is for validation purposes and should be left unchanged. * Compliance Certificates * Compliance & Policies * Cookie Policy * Privacy Policy Website built by Hewitt Matthews WE USE COOKIES! We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. Cookie settings ACCEPT Manage consent Close PRIVACY OVERVIEW This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the ... Necessary Necessary Always Enabled Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously. CookieDurationDescriptionAWSALBCORS7 daysThis cookie is managed by Amazon Web Services and is used for load balancing.cookielawinfo-checkbox-advertisement1 yearSet by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. Functional functional Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features. CookieDurationDescription__cf_bm30 minutesThis cookie, set by Cloudflare, is used to support Cloudflare Bot Management.__zlcmid1 year__zlcmid is a cookie set by Zopim to help identify a user's chat session between page loads.bcookie2 yearsLinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID.bscookie2 yearsLinkedIn sets this cookie to store performed actions on the website.langsessionLinkedIn sets this cookie to remember a user's language setting.lidc1 dayLinkedIn sets the lidc cookie to facilitate data center selection.UserMatchHistory1 monthLinkedIn sets this cookie for LinkedIn Ads ID syncing. Performance performance Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors. Analytics analytics Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc. CookieDurationDescription__gtm_campaign_urlsessionThis cookie is used to collect campaign information from the referring URL, used to improve campaign relevance.__gtm_referrersessionThis cookie is used to identify and store the referring URL to improve the quality of campaigns._ga2 yearsThe _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors._ga_M827Q9YV222 yearsThis cookie is installed by Google Analytics._gat_UA-22580480-11 minuteA variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to._gcl_au3 monthsProvided by Google Tag Manager to experiment advertisement efficiency of websites using their services._gid1 dayInstalled by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously._session_id14 daysCookie set by G2 to store the visitor’s navigation by recording the landing pages. This allows the website to present products and indicate the efficiency of the website.Hotjar1 yearIn order to process data about your visit to a website, Hotjar stores first-party cookies on your browser.lfuuid9 years 8 months 7 days 9 hoursThis cookie is used to store information on user preferences, to provide offers that are targeted to individual interests.site_identity1000 daysThis cookie is set when the email recipient clicks through a Live Web Tracking tracked link. This cookie is for scout.salesloft.com. We do this to allow multi-site tracking.sli_token30 daysThis cookie is set when the email recipient clicks through a Live Web Tracking tracked link.sliguid12 monthsThis cookie provides an anonymous user identifier across multiple requests.slireg7 daysThis cookie identifies the Salesloft server region that the Team’s data is on.slirequested12 monthsOnce the sliguid cookie has been confirmed against a central server, this cookie is set for every request that comes in.UnbounceSessionCookies to track page stats and attribute a conversion event back to a specific page using the page ID and variant letter. Unbounce cookies do not store any personally identifiable information and cannot be used to identify an individual based on the information stored in them directly.undefinedneverWistia sets this cookie to collect data on visitor interaction with the website's video-content, to make the website's video-content more relevant for the visitor. Advertisement advertisement Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads. CookieDurationDescription_ccpx_u1 yearUnique ID to facilitate advertising_fbp3 monthsThis cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website._li_ss – liadm.com29 DaysUnique ID to facilitate advertisingfr3 monthsFacebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.IDE1 year 24 daysGoogle DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile.lidid – liadm.com1 yearUnique ID to facilitate advertisingNextRoll13 monthsNextRoll cookies are being used for the purpose of advertising. test_cookie15 minutesThe test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.tuid – usbrowserspeed.com1 yearUnique ID to facilitate advertising Others others Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet. CookieDurationDescriptionAnalyticsSyncHistory1 monthNo descriptionli_gc2 yearsNo descriptionloglevelneverNo description available.zte2095sessionNo description Save & Accept Powered by Notifications