www.idenfy.com
Open in
urlscan Pro
141.193.213.11
Public Scan
URL:
https://www.idenfy.com/privacy-policy/
Submission: On May 06 via api from US — Scanned from DE
Submission: On May 06 via api from US — Scanned from DE
Form analysis
6 forms found in the DOM<form>
<fieldset>
<legend class="visuallyhidden">Consent Selection</legend>
<div id="CybotCookiebotDialogBodyFieldsetInnerContainer">
<div class="CybotCookiebotDialogBodyLevelButtonWrapper"><label class="CybotCookiebotDialogBodyLevelButtonLabel" for="CybotCookiebotDialogBodyLevelButtonNecessary"><strong
class="CybotCookiebotDialogBodyLevelButtonDescription">Necessary</strong></label>
<div class="CybotCookiebotDialogBodyLevelButtonSliderWrapper CybotCookiebotDialogBodyLevelButtonSliderWrapperDisabled"><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessary"
class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelButtonDisabled" disabled="disabled" checked="checked"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></div>
</div>
<div class="CybotCookiebotDialogBodyLevelButtonWrapper"><label class="CybotCookiebotDialogBodyLevelButtonLabel" for="CybotCookiebotDialogBodyLevelButtonPreferences"><strong
class="CybotCookiebotDialogBodyLevelButtonDescription">Preferences</strong></label>
<div class="CybotCookiebotDialogBodyLevelButtonSliderWrapper"><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferences" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox"
data-target="CybotCookiebotDialogBodyLevelButtonPreferencesInline" checked="checked" tabindex="0"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></div>
</div>
<div class="CybotCookiebotDialogBodyLevelButtonWrapper"><label class="CybotCookiebotDialogBodyLevelButtonLabel" for="CybotCookiebotDialogBodyLevelButtonStatistics"><strong
class="CybotCookiebotDialogBodyLevelButtonDescription">Statistics</strong></label>
<div class="CybotCookiebotDialogBodyLevelButtonSliderWrapper"><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatistics" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox"
data-target="CybotCookiebotDialogBodyLevelButtonStatisticsInline" checked="checked" tabindex="0"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></div>
</div>
<div class="CybotCookiebotDialogBodyLevelButtonWrapper"><label class="CybotCookiebotDialogBodyLevelButtonLabel" for="CybotCookiebotDialogBodyLevelButtonMarketing"><strong
class="CybotCookiebotDialogBodyLevelButtonDescription">Marketing</strong></label>
<div class="CybotCookiebotDialogBodyLevelButtonSliderWrapper"><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketing" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox"
data-target="CybotCookiebotDialogBodyLevelButtonMarketingInline" checked="checked" tabindex="0"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></div>
</div>
</div>
</fieldset>
</form>
<form><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelButtonDisabled" disabled="disabled" checked="checked"> <span
class="CybotCookiebotDialogBodyLevelButtonSlider"></span></form>
<form><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox" data-target="CybotCookiebotDialogBodyLevelButtonPreferences"
checked="checked" tabindex="0"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></form>
<form><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox" data-target="CybotCookiebotDialogBodyLevelButtonStatistics"
checked="checked" tabindex="0"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></form>
<form><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox" data-target="CybotCookiebotDialogBodyLevelButtonMarketing" checked="checked"
tabindex="0"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></form>
<form class="CybotCookiebotDialogBodyLevelButtonSliderWrapper"><input type="checkbox" id="CybotCookiebotDialogBodyContentCheckboxPersonalInformation" class="CybotCookiebotDialogBodyLevelButton"> <span
class="CybotCookiebotDialogBodyLevelButtonSlider"></span></form>
Text Content
Powered by Cookiebot * Consent * Details * [#IABV2SETTINGS#] * About THIS WEBSITE USES COOKIES We use cookies to optimise our service, also to personalise content and ads, to provide social media features, and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners who may combine it with other information that you’ve provided to them or that they’ve collected from your use of their services. You consent to our cookies if you continue to use our website. Consent Selection Necessary Preferences Statistics Marketing Show details * Necessary 87 Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. * Cookiebot 2 Learn more about this provider 1.gifUsed to count the number of sessions to the website, necessary for optimizing CMP product delivery. Expiry: SessionType: Pixel CookieConsentStores the user's cookie consent state for the current domain Expiry: 1 yearType: HTTP * Elink 1 Learn more about this provider _elink_production_sessionPending Expiry: SessionType: HTTP * Google 9 Learn more about this provider IDEUsed by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user. Expiry: 1 yearType: HTTP pagead/landingCollects data on visitor behaviour from multiple websites, in order to present more relevant advertisement - This also allows the website to limit the number of times that they are shown the same advertisement. Expiry: SessionType: Pixel test_cookieUsed to check if the user's browser supports cookies. Expiry: 1 dayType: HTTP ads/ga-audiencesUsed by Google AdWords to re-engage visitors that are likely to convert to customers based on the visitor's online behaviour across websites. Expiry: SessionType: Pixel _gaRegisters a unique ID that is used to generate statistical data on how the visitor uses the website. Expiry: 2 yearsType: HTTP _ga_#Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit. Expiry: 2 yearsType: HTTP _gcl_au [x2]Used by Google AdSense for experimenting with advertisement efficiency across websites using their services. Expiry: 3 monthsType: HTTP tdRegisters statistical data on users' behaviour on the website. Used for internal analytics by the website operator. Expiry: SessionType: Pixel * Hotjar 3 Learn more about this provider _hjSession_#Collects statistics on the visitor's visits to the website, such as the number of visits, average time spent on the website and what pages have been read. Expiry: 1 dayType: HTTP _hjSessionUser_#Collects statistics on the visitor's visits to the website, such as the number of visits, average time spent on the website and what pages have been read. Expiry: 1 yearType: HTTP _hjTLDTestRegisters statistical data on users' behaviour on the website. Used for internal analytics by the website operator. Expiry: SessionType: HTTP * Hubspot 16 Learn more about this provider hubspot-pricingPending Expiry: 1 yearType: HTTP rc::aThis cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. Expiry: PersistentType: HTML rc::bThis cookie is used to distinguish between humans and bots. Expiry: SessionType: HTML rc::cThis cookie is used to distinguish between humans and bots. Expiry: SessionType: HTML __ptq.gifSends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. Expiry: SessionType: Pixel __hssc [x3]Collects statistical data related to the user's website visits, such as the number of visits, average time spent on the website and what pages have been loaded. The purpose is to segment the website's users according to factors such as demographics and geographical location, in order to enable media and marketing agencies to structure and understand their target groups to enable customised online advertising. Expiry: 1 dayType: HTTP __hssrc [x3]Collects statistical data related to the user's website visits, such as the number of visits, average time spent on the website and what pages have been loaded. The purpose is to segment the website's users according to factors such as demographics and geographical location, in order to enable media and marketing agencies to structure and understand their target groups to enable customised online advertising. Expiry: SessionType: HTTP __hstc [x3]Collects statistical data related to the user's website visits, such as the number of visits, average time spent on the website and what pages have been loaded. The purpose is to segment the website's users according to factors such as demographics and geographical location, in order to enable media and marketing agencies to structure and understand their target groups to enable customised online advertising. Expiry: 180 daysType: HTTP messagesUtk [x2]Stores a unique ID string for each chat-box session. This allows the website-support to see previous issues and reconnect with the previous supporter. Expiry: 180 daysType: HTTP * LinkedIn 3 Learn more about this provider li_gcStores the user's cookie consent state for the current domain Expiry: 180 daysType: HTTP lidcRegisters which server-cluster is serving the visitor. This is used in context with load balancing, in order to optimize user experience. Expiry: 1 dayType: HTTP bscookieThis cookie is used to identify the visitor through an application. This allows the visitor to login to a website through their LinkedIn application for example. Expiry: 1 yearType: HTTP * New Relic 1 Learn more about this provider JSESSIONIDPreserves users states across page requests. Expiry: SessionType: HTTP * RudderStack 2 Learn more about this provider __tld__Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences. Expiry: SessionType: HTTP test_rudder_cookieThis cookie determines whether the browser accepts cookies. Expiry: 1 yearType: HTTP * Typeform 20 Learn more about this provider #.#-#-#-#-#.ackUsed to contain user’s survey and quiz answers in Local Storage. Expiry: PersistentType: HTML #.#-#-#-#-#.inProgressUsed to contain user’s survey and quiz answers in Local Storage. Expiry: PersistentType: HTML #.#-#-#-#-#.queueUsed to contain user’s survey and quiz answers in Local Storage. Expiry: PersistentType: HTML #.#-#-#-#-#.reclaimEndUsed to contain user’s survey and quiz answers in Local Storage. Expiry: PersistentType: HTML #.#-#-#-#-#.reclaimStartUsed to contain user’s survey and quiz answers in Local Storage. Expiry: PersistentType: HTML rl_anonymous_idRegisters statistical data on users' behaviour on the website. Used for internal analytics by the website operator. Expiry: PersistentType: HTML rl_group_idRegisters statistical data on users' behaviour on the website. Used for internal analytics by the website operator. Expiry: PersistentType: HTML rl_group_traitRegisters statistical data on users' behaviour on the website. Used for internal analytics by the website operator. Expiry: PersistentType: HTML rl_page_init_referrerRegisters how the user has reached the website to enable pay-out of referral commission fees to partners. Expiry: PersistentType: HTML rl_page_init_referring_domainRegisters how the user has reached the website to enable pay-out of referral commission fees to partners. Expiry: PersistentType: HTML rl_sessionCollects data on the user's visits to the website, such as the number of visits, average time spent on the website and what pages have been loaded with the purpose of generating reports for optimising the website content. Expiry: PersistentType: HTML rl_traitRegisters statistical data on users' behaviour on the website. Used for internal analytics by the website operator. Expiry: PersistentType: HTML rl_user_idRegisters statistical data on users' behaviour on the website. Used for internal analytics by the website operator. Expiry: PersistentType: HTML #-visitorIdThis cookie is used for pricing forms Expiry: PersistentType: HTML attribution_user_idThis cookie is used for pricing forms Expiry: 1 yearType: HTTP AWSALBTGRegisters which server-cluster is serving the visitor. This is used in context with load balancing, in order to optimize user experience. Expiry: 7 daysType: HTTP AWSALBTGCORSContact forms functionality Expiry: 7 daysType: HTTP dd_cookie_test_#Registers data on visitors' website-behaviour. This is used for internal analysis and website optimization. Expiry: 1 dayType: HTTP tf_respondent_ccContact forms functionality Expiry: 6 monthsType: HTTP tracking_session_idDetermines when the visitor last visited the different subpages on the website, as well as sets a timestamp for when the session started. Expiry: 1 dayType: HTTP * app.supademo.com 1 supademo-viewerPending Expiry: 1 yearType: HTTP * g2.com g2crowd.com hsforms.com idenfy.com vimeo.com www.idenfy.com 8 __cf_bm [x8]This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. Expiry: 1 dayType: HTTP * g2.com vimeo.com 2 cf_clearance [x2]This cookie is used to distinguish between humans and bots. Expiry: 1 yearType: HTTP * hsforms.com vimeo.com 3 _cfuvid [x3]This cookie is a part of the services provided by Cloudflare - Including load-balancing, deliverance of website content and serving DNS connection for website operators. Expiry: SessionType: HTTP * idenfy.com 9 emailPreserves users states across page requests. Expiry: SessionType: HTTP gclidUsed to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. Expiry: SessionType: HTTP handl_original_refRegisters how the user has reached the website to enable pay-out of referral commission fees to partners. Expiry: SessionType: HTTP handl_refRegisters how the user has reached the website to enable pay-out of referral commission fees to partners. Expiry: SessionType: HTTP utm_campaignCollects information on user preferences and/or interaction with web-campaign content - This is used on CRM-campaign-platform used by website owners for promoting events or products. Expiry: SessionType: HTTP utm_contentUsed to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. Expiry: SessionType: HTTP utm_mediumCollects information on user preferences and/or interaction with web-campaign content - This is used on CRM-campaign-platform used by website owners for promoting events or products. Expiry: SessionType: HTTP utm_sourceDetermines how the user accessed the website. This information is used by the website operator in order to measure the efficiency of their marketing. Expiry: SessionType: HTTP utm_termDetermines how the user accessed the website. This information is used by the website operator in order to measure the efficiency of their marketing. Expiry: SessionType: HTTP * js.hs-analytics.net typeform.com 3 hubspotutk [x3]Keeps track of a visitor's identity. This cookie is passed to the marketing platform HubSpot on form submission and used when de-duplicating contacts. Expiry: 180 daysType: HTTP * www.g2.com 4 AWSALBRegisters which server-cluster is serving the visitor. This is used in context with load balancing, in order to optimize user experience. Expiry: 7 daysType: HTTP AWSALBCORSRegisters which server-cluster is serving the visitor. This is used in context with load balancing, in order to optimize user experience. Expiry: 7 daysType: HTTP events_distinct_idSets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. Expiry: SessionType: HTTP va_sidenav_openPending Expiry: 1 yearType: HTTP * Preferences 1 Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. * idenfy.com 1 usernameCollects data of the user's website navigation and activity, including name and contact details entered into forms. Expiry: SessionType: HTTP * Statistics 8 Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. * Hotjar 2 Learn more about this provider hjActiveViewportIdsThis cookie contains an ID string on the current session. This contains non-personal information on what subpages the visitor enters – this information is used to optimize the visitor's experience. Expiry: PersistentType: HTML hjViewportIdSaves the user's screen size in order to adjust the size of images on the website. Expiry: SessionType: HTML * LinkedIn 1 Learn more about this provider AnalyticsSyncHistoryUsed in connection with data-synchronization with third-party analysis service. Expiry: 30 daysType: HTTP * Vimeo 1 Learn more about this provider vuidCollects data on the user's visits to the website, such as which pages have been read. Expiry: 2 yearsType: HTTP * g2.com 1 _g2_session_idSets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. Expiry: SessionType: HTTP * idenfy.com 3 handl_ipCollects data such as visitors' IP address, geographical location and website navigation - This information is used for internal optimization and statistics for the website's operator. Expiry: 30 daysType: HTTP handl_landing_pageUsed by the website's owners to identify how the visitor accessed the website. This is used for statistical purposes. Expiry: 30 daysType: HTTP handl_urlUsed by the website's owners to identify how the visitor accessed the website. This is used for statistical purposes. Expiry: 30 daysType: HTTP * Marketing 34 Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. * Meta Platforms, Inc. 3 Learn more about this provider lastExternalReferrerDetects how the user reached the website by registering their last URL-address. Expiry: PersistentType: HTML lastExternalReferrerTimeDetects how the user reached the website by registering their last URL-address. Expiry: PersistentType: HTML _fbpUsed by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers. Expiry: 3 monthsType: HTTP * Google 2 Learn more about this provider _GRECAPTCHAThis cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. Expiry: 180 daysType: HTTP pagead/1p-user-list/#Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. Expiry: SessionType: Pixel * Hubspot 2 Learn more about this provider rc::fThis cookie is used to distinguish between humans and bots. Expiry: PersistentType: HTML HUBLYTICS_EVENTS_53Collects data on visitor behaviour from multiple websites, in order to present more relevant advertisement - This also allows the website to limit the number of times that they are shown the same advertisement. Expiry: PersistentType: HTML * LinkedIn 4 Learn more about this provider bcookieUsed by the social networking service, LinkedIn, for tracking the use of embedded services. Expiry: 1 yearType: HTTP li_sugrCollects data on user behaviour and interaction in order to optimize the website and make advertisement on the website more relevant. Expiry: 3 monthsType: HTTP UserMatchHistoryEnsures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. Expiry: 30 daysType: HTTP li_adsIdCollects data on user behaviour and interaction in order to optimize the website and make advertisement on the website more relevant. Expiry: PersistentType: HTML * YouTube 8 Learn more about this provider LAST_RESULT_ENTRY_KEYUsed to track user’s interaction with embedded content. Expiry: SessionType: HTTP nextIdUsed to track user’s interaction with embedded content. Expiry: SessionType: HTTP remote_sidNecessary for the implementation and functionality of YouTube video-content on the website. Expiry: SessionType: HTTP requestsUsed to track user’s interaction with embedded content. Expiry: SessionType: HTTP TESTCOOKIESENABLEDUsed to track user’s interaction with embedded content. Expiry: 1 dayType: HTTP VISITOR_INFO1_LIVETries to estimate the users' bandwidth on pages with integrated YouTube videos. Expiry: 180 daysType: HTTP VISITOR_PRIVACY_METADATAStores the user's cookie consent state for the current domain Expiry: 180 daysType: HTTP YSCRegisters a unique ID to keep statistics of what videos from YouTube the user has seen. Expiry: SessionType: HTTP * app.supademo.com 2 mp_#_mixpanel [x2]Pending Expiry: SessionType: HTTP * cdn.ampproject.org 13 #-#Pending Expiry: SessionType: HTML iU5q-!O9@$Registers a unique ID to keep statistics of what videos from YouTube the user has seen. Expiry: SessionType: HTML LogsDatabaseV2:V#||LogsRequestsStorePending Expiry: PersistentType: IDB ServiceWorkerLogsDatabase#SWHealthLogNecessary for the implementation and functionality of YouTube video-content on the website. Expiry: PersistentType: IDB ytidb::LAST_RESULT_ENTRY_KEYStores the user's video player preferences using embedded YouTube video Expiry: PersistentType: HTML YtIdbMeta#databasesUsed to track user’s interaction with embedded content. Expiry: PersistentType: IDB yt-remote-cast-availableStores the user's video player preferences using embedded YouTube video Expiry: SessionType: HTML yt-remote-cast-installedStores the user's video player preferences using embedded YouTube video Expiry: SessionType: HTML yt-remote-connected-devicesStores the user's video player preferences using embedded YouTube video Expiry: PersistentType: HTML yt-remote-device-idStores the user's video player preferences using embedded YouTube video Expiry: PersistentType: HTML yt-remote-fast-check-periodStores the user's video player preferences using embedded YouTube video Expiry: SessionType: HTML yt-remote-session-appStores the user's video player preferences using embedded YouTube video Expiry: SessionType: HTML yt-remote-session-nameStores the user's video player preferences using embedded YouTube video Expiry: SessionType: HTML * Unclassified 6 Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. * app.supademo.com 6 demo-clt2vtagb58xiped7tkeg0ua0Pending Expiry: PersistentType: HTML demo-cltfi73rj0zjup6h5l9ikbdr4Pending Expiry: PersistentType: HTML demo-cltsc3s5x2m8pvnjwsemkxi31Pending Expiry: PersistentType: HTML demo-clu0x3ogu09y3xfvvpq22pdlxPending Expiry: PersistentType: HTML demo-NzM1pQBbScC3uvbhXIqWgPending Expiry: PersistentType: HTML __mp_opt_in_out_#Pending Expiry: SessionType: HTTP Cross-domain consent[#BULK_CONSENT_DOMAINS_COUNT#] [#BULK_CONSENT_TITLE#] List of domains your consent applies to: [#BULK_CONSENT_DOMAINS#] Cookie declaration last updated on 11.04.24 by Cookiebot [#IABV2_TITLE#] [#IABV2_BODY_INTRO#] [#IABV2_BODY_LEGITIMATE_INTEREST_INTRO#] [#IABV2_BODY_PREFERENCE_INTRO#] [#IABV2_LABEL_PURPOSES#] [#IABV2_BODY_PURPOSES_INTRO#] [#IABV2_BODY_PURPOSES#] [#IABV2_LABEL_FEATURES#] [#IABV2_BODY_FEATURES_INTRO#] [#IABV2_BODY_FEATURES#] [#IABV2_LABEL_PARTNERS#] [#IABV2_BODY_PARTNERS_INTRO#] [#IABV2_BODY_PARTNERS#] Cookies are small text files that can be used by websites to make a user's experience more efficient. The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies we need your permission. This site uses different types of cookies. Some cookies are placed by third party services that appear on our pages. You can at any time change or withdraw your consent from the Cookie Declaration on our website. Learn more about who we are, how you can contact us and how we process personal data in our Privacy Policy. Do not sell or share my personal information Use necessary cookies only Selection only Customize Allow all cookies Powered by Cookiebot by Usercentrics Skip to content Try for free * Products * KNOW YOUR CUSTOMER * Identity VerificationFull-stack identity verification service * NFC VerificationNFC chip-based identity verification * AML Screening & MonitoringSanctions, PEPs & Watchlists to monitor your customers * Know Your BusinessBusiness verification solution with everything you ever need in one API * FRAUD PREVENTION * Address VerificationReview documents with manual supervision * Phone VerificationDeep phone number check & validation * Fraud ScoringAssess the risk score of your customer * Proxy DetectionFilter customer’s IP to improve transparency * BY INDUSTRY * Fintech * Blockchain & Cryptocurrency * Proxy Networks * Gaming * Transportation & Sharing Economy * Streaming Platforms * Pricing * Developers * Resources * INFORMATION * Blog * Supported Documents * Glossary * Security and Compliance * GET TO KNOW US * About us * Customers * Partner program * Log in * Talk to Sales * Try for free PRIVACY POLICY We are very delighted that you have shown interest in our enterprise. Data protection is of a particularly high priority for the management of the UAB “iDenfy”. The use of the Internet pages of the UAB “iDenfy” is possible without any indication of personal data; however, if a data subject wants to use special enterprise services via our website, processing of personal data could become necessary. If the processing of personal data is necessary and there is no statutory basis for such processing, we generally obtain consent from the data subject. The processing of personal data, such as the name, address, e-mail address, or telephone number of a data subject shall always be in line with the General Data Protection Regulation (GDPR), and in accordance with the country-specific data protection regulations applicable to the UAB “iDenfy”. By means of this data protection declaration, our enterprise would like to inform the general public of the nature, scope, and purpose of the personal data we collect, use and process. Furthermore, data subjects are informed, by means of this data protection declaration, of the rights to which they are entitled. As the processor, the UAB “iDenfy” has implemented numerous technical and organizational measures to ensure the most complete protection of personal data processed through this website. However, Internet-based data transmissions may in principle have security gaps, so absolute protection may not be guaranteed. For this reason, every data subject is free to transfer personal data to us via alternative means, e.g. by telephone and to take personal responsibility to ensure transferred data safety. 1. Definitions The data protection declaration of the UAB “iDenfy” is based on the terms used by the European legislator for the adoption of the General Data Protection Regulation (GDPR) 2016/679. Our data protection declaration should be legible and understandable for the general public, as well as our customers and business partners. To ensure this, we would like to first explain the terminology used. In this data protection declaration, we use, inter alia, the following terms: * Personal data – Personal data means any information relating to an identified or identifiable natural person (“data subject”). An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person. * Data subject – Data subject is any identified or identifiable natural person, whose personal data is processed by the controller responsible for the processing. * Processing – Processing is any operation or set of operations that are performed on personal data or on sets of personal data, whether or not by automated means, such as collection, recording, organization, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction. * Restriction of processing – Restriction of processing is the marking of stored personal data with the aim of limiting their processing in the future. * Profiling – Profiling means any form of automated processing of personal data consisting of the use of personal data to evaluate certain personal aspects relating to a natural person, in particular, to analyze or predict aspects concerning that natural person’s performance at work, economic situation, health, personal preferences, interests, reliability, behavior, location or movements. * Pseudonymization – Pseudonymisation is the processing of personal data in such a manner that the personal data can no longer be attributed to a specific data subject without the use of additional information, provided that such additional information is kept separately and is subject to technical and organizational measures to ensure that the personal data are not attributed to an identified or identifiable natural person. * Controller or controller responsible for the processing – Controller or controller responsible for the processing is the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data; where the purposes and means of such processing are determined by Union or Member State law, the controller or the specific criteria for its nomination may be provided for by Union or Member State law. In our case, Controller is the customer or the client of the iDenfy. iDenfy only acts as a controller when collecting cookies from non-customer/client needs, starts marketing campaign or if the possible candidate/employee enters the website. * Processor – Processor is a natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller. * Recipient – Recipient is a natural or legal person, public authority, agency or another body, to which the personal data are disclosed, whether a third party or not. However, public authorities which may receive personal data in the framework of a particular inquiry in accordance with Union or Member State law shall not be regarded as recipients; the processing of those data by those public authorities shall be in compliance with the applicable data protection rules according to the purposes of the processing. * Third-party – Third party is a natural or legal person, public authority, agency or body other than the data subject, controller, processor and persons who, under the direct authority of the controller or processor, are authorized to process personal data. * Consent – Consent of the data subject is any freely given, specific, informed and unambiguous indication of the data subject’s wishes by which he or she, by a statement or by clear affirmative action, signifies agreement to the processing of personal data relating to him or her. * Freemium version – iDenfy provides free identity verification services for data controllers. These freemium accounts are with limited functions. * Premium version – iDenfy provides paid identity verification services for data controllers. These premium accounts usually don’t have functionality limitations. * Trust service version – iDenfy provides identity verification services compliant with trust service requirements. Trust service policies are being applied in this package according to policies outlined in eIDAS Regulation (EU) 910/2014 (“eIDAS”), ETSI Standards 119 461, 319 401 2. Name and Address of the processor Processor for the purposes of the General Data Protection Regulation (GDPR), other data protection laws applicable in Member states of the European Union and other provisions related to data protection is: UAB “iDenfy” (Further in the text: iDenfy) Baršausko street 59, 51423 Kaunas, Lithuania Phone: +370 640 84466 Email: dpo@idenfy.com Website: www.idenfy.com iDenfy may act in the role either as a Data Controller or Data Processor. 3. Cookies The Internet pages of the UAB “iDenfy” use cookies. Cookies are text files that are stored in a computer system via an Internet browser. Many Internet sites and servers use cookies. Many cookies contain a so-called cookie ID. A cookie ID is a unique identifier of the cookie. It consists of a character string through which Internet pages and servers can be assigned to the specific Internet browser in which the cookie was stored. This allows visited Internet sites and servers to differentiate the individual browser of the data subject from other Internet browsers that contain other cookies. A specific Internet browser can be recognized and identified using the unique cookie ID. Through the use of cookies, the UAB “iDenfy” can provide the users of this website with more user-friendly services that would not be possible without the cookie setting. By means of a cookie, the information and offers on our website can be optimized with the user in mind. Cookies allow us, as previously mentioned, to recognize our website users. The purpose of this recognition is to make it easier for users to utilize our website. The website user that uses cookies e.g. does not have to enter access data each time the website is accessed, because this is taken over by the website, and the cookie is thus stored on the user’s computer system. Another example is the cookie of a shopping cart in an online shop. The online store remembers the articles that a customer has placed in the virtual shopping cart via a cookie. The data subject may, at any time, prevent the setting of cookies through our website by means of a corresponding setting of the Internet browser used, and may thus permanently deny the setting of cookies. Furthermore, already set cookies may be deleted at any time via an Internet browser or other software programs. This is possible in all popular Internet browsers. If the data subject deactivates the setting of cookies in the Internet browser used, not all functions of our website may be entirely usable. More is defined in www.idenfy.com/cookie-policy. 4. Collection of general data and information The website of the UAB “iDenfy” collects a series of general data and information when a data subject or automated system calls up the website. This general data and information are stored in the server log files Processed data: * the person’s name; * surname; * gender; * identity document number; * personal code (if it is issued); * identity number (i.e. national identification number) (if it is issued); * birth date; * identity document expiry date; * identity document issued date ((if it is issued); * identity document photograph(s); * face photograph(s); * citizenship/nationality; * client id; * identification date and method. * IP address. * device fingerprint (“user-agent”). Processed information is needed to (1) deliver the content of our website correctly, (2) optimize the content of our website as well as its advertisement, (3) ensure the long-term viability of our information technology systems and website technology, and (4) provide law enforcement authorities with the information necessary for criminal prosecution in case of a cyber-attack, (5) provide products and services for our clients and fulfill the agreement conditions between the Parties 5. Data processing place iDenfy stores data until retention only in the Amazon AWS Europe (Dublin, Ireland). In some extra cases data can be sent outside the European union but only if additional and necessary safety guards would be ensured (Standard contractual clauses and similar). 6. Registration on our website The data subject has the possibility to register on the website of the controller with an indication of personal data. Which personal data are transmitted to the controller is determined by the respective input mask used for the registration. The personal data entered by the data subject are collected and stored exclusively for internal use by the controller, and for his own purposes. The controller may request transfer to one or more processors (e.g. a parcel service) that also uses personal data for an internal purpose which is attributable to the controller. By registering on the website of the controller, the IP address—assigned by the Internet service provider (ISP) and used by the data subject—date, and time of the registration are also stored. The storage of this data takes place against the background that this is the only way to prevent the misuse of our services, and, if necessary, to make it possible to investigate committed offenses. Insofar, the storage of this data is necessary to secure the controller. This data is not passed on to third parties unless there is a statutory obligation to pass on the data, or if the transfer serves the aim of criminal prosecution. The registration of the data subject, with the voluntary indication of personal data, is intended to enable the controller to offer the data subject contents or services that may only be offered to registered users due to the nature of the matter in question. Registered persons are free to change the personal data specified during the registration at any time, or to have them completely deleted from the data stock of the controller. iDenfy acts as a Data Processor when dealing with Customers/Clients collected data. iDenfy as a Data processor will cooperate with Data Controller to ensure that the data controller at any time could provide information upon request to each data subject as to what personal data are stored about the data subject. 7. Contact possibility via the website The website of the UAB “iDenfy” contains information that enables a quick electronic contact to our enterprise, as well as direct communication with us, which also includes a general address of the so-called electronic mail (e-mail address). If iDenfy as a Data processor receives request from the Data Subject, the obligation of iDenfy is to transfer such a request to the Data Controller and cooperate with Controller for answer granting, if needed. 8. Routine erasure and blocking of personal data The data processor shall process and store the personal data of the data subject only for the period necessary to achieve the purpose of storage, or as far as this is granted by the European legislator or other legislators in laws or regulations to which the processor is subject to. If the storage purpose is not applicable, or if a storage period prescribed by the European legislator or another competent legislator expires, the personal data are routinely blocked or erased in accordance with legal requirements. 9. Rights of the data subject * Right of confirmation – Each data subject shall have the right granted by the European legislator to obtain from the controller the confirmation as to whether or not personal data concerning him or her are being processed. If a data subject wishes to avail himself of this right of confirmation, he or she may, at any time, contact any employee from where services are bought/granted. iDenfy as a Data processor will act in the Agreement with Data Controller and will cooperate with Data Controller to fulfill this Data Subject request. All request regarding this Data subject right can be sent to dpo@idenfy.com. * Right of access, Each data subject shall have the right granted by the European legislator to obtain from the controller free information about his or her personal data stored at any time and a copy of this information. Furthermore, the European directives and regulations grant the data subject access to the following information: * the purposes of the processing; * the categories of personal data concerned; * the recipients or categories of recipients to whom the personal data have been or will be disclosed, in particular recipients in third countries or international organizations; * where possible, the envisaged period for which the personal data will be stored, or, if not possible, the criteria used to determine that period; * the existence of the right to request from the controller rectification or erasure of personal data, or restriction of processing of personal data concerning the data subject, or to object to such processing; * the existence of the right to lodge a complaint with a supervisory authority; * where the personal data are not collected from the data subject, any available information as to their source; * the existence of automated decision-making, including profiling, referred to in Article 22(1) and (4) of the GDPR and, at least in those cases, meaningful information about the logic involved, as well as the significance and envisaged consequences of such processing for the data subject. Furthermore, the data subject shall have a right to obtain information as to whether personal data are transferred to a third country or to an international organization. Where this is the case, the data subject shall have the right to be informed of the appropriate safeguards relating to the transfer. If a data subject wishes to avail himself of this right of access, he or she may, at any time, contact any employee of the controller and iDenfy as Data Processor will act accordingly Agreement made with Data Controller and support Controller with all known information. * Right to rectification – Each data subject shall have the right granted by the European legislator to obtain from the controller without undue delay the rectification of inaccurate personal data concerning him or her. Taking into account the purposes of the processing, the data subject shall have the right to have incomplete personal data completed, including by means of providing a supplementary statement. If a data subject wishes to exercise this right to rectification, he or she may, at any time, contact any employee of the controller by sending an email to dpo@idenfy.com. * Right to erasure (Right to be forgotten) Each data subject shall have the right granted by the European legislator to obtain from the controller the erasure of personal data concerning him or her without undue delay, and the controller shall have the obligation to erase personal data without undue delay where one of the following grounds applies, as long as the processing is not necessary: * The personal data are no longer necessary in relation to the purposes for which they were collected or otherwise processed. * The data subject withdraws consent to which the processing is based according to point (a) of Article 6(1) of the GDPR, or point (a) of Article 9(2) of the GDPR, and where there is no other legal ground for the processing. * The data subject objects to the processing pursuant to Article 21(1) of the GDPR and there are no overriding legitimate grounds for the processing or the data subject objects to the processing pursuant to Article 21(2) of the GDPR. * The personal data have been unlawfully processed. * The personal data must be erased for compliance with a legal obligation in Union or Member State law to which the controller is subject. * The personal data have been collected in relation to the offer of information society services referred to in Article 8(1) of the GDPR. If one of the aforementioned reasons applies, and a data subject wishes to request the erasure of personal data stored by the UAB “iDenfy”, he or she may, at any time, contact any employee of the controller. An employee of UAB “iDenfy” shall promptly ensure that the erasure request is complied with immediately. Where the controller has made personal data public and is obliged pursuant to Article 17(1) to erase the personal data, the controller, taking account of available technology and the cost of implementation, shall take reasonable steps, including technical measures, to inform other controllers processing the personal data that the data subject has requested the erasure by such controllers of any links to, or copy or replication of, those personal data, as far as processing is not required. Employees of the UAB “iDenfy” will arrange the necessary measures in individual cases. * Right of restriction of processing – Each data subject shall have the right granted by the European legislator to obtain from the controller restriction of processing where one of the following applies: * The accuracy of the personal data is contested by the data subject, for a period enabling the controller to verify the accuracy of the personal data. * The processing is unlawful and the data subject opposes the erasure of the personal data and requests instead of the restriction of their use instead. * The controller no longer needs the personal data for the purposes of the processing, but they are required by the data subject for the establishment, exercise or defense of legal claims. * The data subject has objected to processing pursuant to Article 21(1) of the GDPR pending the verification whether the legitimate grounds of the controller override those of the data subject. If one of the aforementioned conditions is met, and a data subject wishes to request the restriction of the processing of personal data stored by the UAB “iDenfy”, he or she may at any time contact any employee of the controller. The employee of the UAB “iDenfy” will arrange the restriction of the processing. * Right to data portability – Each data subject shall have the right granted by the European legislator, to receive the personal data concerning him or her, which was provided to a controller, in a structured, commonly used and machine-readable format. He or she shall have the right to transmit those data to another controller without hindrance from the controller to which the personal data have been provided, as long as the processing is based on consent pursuant to point (a) of Article 6(1) of the GDPR or point (a) of Article 9(2) of the GDPR, or on a contract pursuant to point (b) of Article 6(1) of the GDPR, and the processing is carried out by automated means, as long as the processing is not necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller. Furthermore, in exercising his or her right to data portability pursuant to Article 20(1) of the GDPR, the data subject shall have the right to have personal data transmitted directly from one controller to another, where technically feasible and when doing so does not adversely affect the rights and freedoms of others. In order to assert the right to data portability, the data subject may at any time contact any employee of the UAB “iDenfy” by sending an email to dpo@idenfy.com. * Right to object – Each data subject shall have the right granted by the European legislator to object, on grounds relating to his or her particular situation, at any time, to processing of personal data concerning him or her, which is based on point (e) or (f) of Article 6(1) of the GDPR. This also applies to profiling based on these provisions. The UAB “iDenfy” shall no longer process the personal data in the event of the objection, unless we can demonstrate compelling legitimate grounds for the processing which override the interests, rights, and freedoms of the data subject, or for the establishment, exercise or defense of legal claims. If the UAB “iDenfy” processes personal data for direct marketing purposes, the data subject shall have the right to object at any time to processing of personal data concerning him or her for such marketing. This applies to profiling to the extent that it is related to such direct marketing. If the data subject objects to the UAB “iDenfy” to the processing for direct marketing purposes, the UAB “iDenfy” will no longer process the personal data for these purposes. In addition, the data subject has the right, on grounds relating to his or her particular situation, to object to the processing of personal data concerning him or her by the UAB “iDenfy” for scientific or historical research purposes, or for statistical purposes pursuant to Article 89(1) of the GDPR, unless the processing is necessary for the performance of a task carried out for reasons of public interest. In order to exercise the right to object, the data subject may contact any employee of the UAB “iDenfy”. In addition, the data subject is free in the context of the use of information society services, and notwithstanding Directive 2002/58/EC, to use his or her right to object by automated means using technical specifications. * Automated individual decision-making, including profiling – Each data subject shall have the right granted by the European legislator not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning him or her, or similarly significantly affects him or her, as long as the decision (1) is not is necessary for entering into, or the performance of, a contract between the data subject and a data controller, or (2) is not authorized by Union or Member State law to which the controller is subject and which also lays down suitable measures to safeguard the data subject’s rights and freedoms and legitimate interests, or (3) are not based on the data subject’s explicit consent. If the decision (1) is necessary for entering into, or the performance of, a contract between the data subject and a data controller, or (2) it is based on the data subject’s explicit consent, the UAB “iDenfy” shall implement suitable measures to safeguard the data subject’s rights and freedoms and legitimate interests, at least the right to obtain human intervention on the part of the controller, to express his or her point of view and contest the decision. If the data subject wishes to exercise the rights concerning automated individual decision-making, he or she may, at any time, contact any employee of the UAB “iDenfy” by sending an email to dpo@idenfy.com. * Right to withdraw data protection consent – Each data subject shall have the right granted by the European legislator to withdraw his or her consent to the processing of his or her personal data at any time. If the data subject wishes to exercise the right to withdraw the consent, he or she may, at any time, contact any employee of the UAB “iDenfy”. ! Clarification: All of the requests which are made in the case when iDenfy acts as a Data processor will be transferred to the Data Controller or iDenfy will act upon a Data Processing Agreement which is made with Data Controller and will support Data Controller upon request. All of the requests which are made in the case when iDenfy acts as a Data Controller will be fulfilled regarding GDPR 2016/679 clauses (Data Subject rights; Data Controller obligations) and will be answered per 30 days. 10. Data protection provisions about the application and use of Facebook On this website, there are integrated components of the enterprise Facebook. Facebook is a social network. A social network is a place for social meetings on the Internet, an online community, which usually allows users to communicate with each other and interact in a virtual space. A social network may serve as a platform for the exchange of opinions and experiences, or experiences or enable the Internet community to provide personal or business-related information. Facebook allows social network users to include the creation of private profiles, upload photos, and network through friend requests. The operating company of Facebook is Facebook, Inc., 1 Hacker Way, Menlo Park, CA 94025, United States. If a person lives outside of the United States or Canada, the controller is the Facebook Ireland Ltd., 4 Grand Canal Square, Grand Canal Harbour, Dublin 2, Ireland. With each call-up to one of the individual pages of this Internet website, which is operated by the controller and into which a Facebook component (Facebook plug-ins) was integrated, the web browser on the information technology system of the data subject is automatically prompted to download a display of the corresponding Facebook component from Facebook through the Facebook component. An overview of all the Facebook Plug-ins may be accessed under https://developers.facebook.com/docs/plugins/. During the course of this technical procedure, Facebook is made aware of what specific sub-site of our website was visited by the data subject. If the data subject is logged in at the same time on Facebook, Facebook detects with every call-up to our website by the data subject—and for the entire duration of their stay on our Internet site—which specific sub-site of our Internet page was visited by the data subject. This information is collected through the Facebook component and associated with the respective Facebook account of the data subject. If the data subject clicks on one of the Facebook buttons integrated into our website, e.g. the “Like” button, or if the data subject submits a comment, then Facebook matches this information with the personal Facebook user account of the data subject and stores the personal data. Facebook always receives, through the Facebook component, information about a visit to our website by the data subject, whenever the data subject is logged in at the same time on Facebook during the time of the call-up to our website. This occurs regardless of whether the data subject clicks on the Facebook component or not. If such a transmission of information to Facebook is not desirable for the data subject, then he or she may prevent this by logging off from their Facebook account before a call-up to our website is made. The data protection guideline published by Facebook, which is available at https://facebook.com/about/privacy/, provides information about the collection, processing and use of personal data by Facebook. In addition, it is explained there what setting options Facebook offers to protect the privacy of the data subject. In addition, different configuration options are made available to allow the elimination of data transmission to Facebook. These applications may be used by the data subject to eliminate data transmission to Facebook. 11. Data protection provisions about the application and use of Google Analytics (with anonymization function) On this website, there are integrated component of Google Analytics (with the anonymizer function). Google Analytics is a web analytics service. Web analytics is the collection, gathering, and analysis of data about the behavior of visitors to websites. A web analysis service collects, inter alia, data about the website from which a person has come (the so-called referrer), which sub-pages were visited, or how often and for what duration a sub-page was viewed. Web analytics are mainly used for the optimization of a website and in order to carry out a cost-benefit analysis of Internet advertising. The operator of the Google Analytics component is Google Inc., 1600 Amphitheatre Pkwy, Mountain View, CA 94043-1351, United States. For web analytics, through Google Analytics iDenfy uses the application “_gat. _anonymizeIp”. By means of this application, the IP address of the Internet connection of the data subject is abridged by Google and anonymized when accessing our websites from a Member State of the European Union or another Contracting State to the Agreement on the European Economic Area. The purpose of the Google Analytics component is to analyze the traffic on our website. Google uses the collected data and information, inter alia, to evaluate the use of our website and to provide online reports, which show the activities on our websites, and to provide other services concerning the use of our Internet site for us. Google Analytics places a cookie on the information technology system of the data subject. The definition of cookies is explained above. With the setting of the cookie, Google is enabled to analyze the use of our website. With each call-up to one of the individual pages of this Internet site and into which a Google Analytics component was integrated, the Internet browser on the information technology system of the data subject will automatically submit data through the Google Analytics component for the purpose of online advertising and the settlement of commissions to Google. During the course of this technical procedure, the enterprise Google gains knowledge of personal information, such as the IP address of the data subject, which serves Google, inter alia, to understand the origin of visitors and clicks, and subsequently create commission settlements. The cookie is used to store personal information, such as the access time, the location from which the access was made, and the frequency of visits of our website by the data subject. With each visit to our Internet site, such as personal data, including the IP address of the Internet access used by the data subject, will be transmitted to Google in the United States of America. These personal data are stored by Google in the United States of America. Google may pass these personal data collected through the technical procedure to third parties. The data subject may, as stated above, prevent the setting of cookies through our website at any time by means of a corresponding adjustment of the web browser used and thus permanently deny the setting of cookies. Such an adjustment to the Internet browser used would also prevent Google Analytics from setting a cookie on the information technology system of the data subject. In addition, cookies already in use by Google Analytics may be deleted at any time via a web browser or other software programs. In addition, the data subject has the possibility of objecting to a collection of data that are generated by Google Analytics, which is related to the use of this website, as well as the processing of this data by Google and the chance to preclude any such. For this purpose, the data subject must download a browser add-on under the link https://tools.google.com/dlpage/gaoptout and install it. This browser add-on tells Google Analytics through a JavaScript, that any data and information about the visits of Internet pages may not be transmitted to Google Analytics. The installation of the browser add-ons is considered an objection by Google. If the information technology system of the data subject is later deleted, formatted, or newly installed, then the data subject must reinstall the browser add-ons to disable Google Analytics. If the browser add-on was uninstalled by the data subject or any other person who is attributable to their sphere of competence, or is disabled, it is possible to execute the reinstallation or reactivation of the browser add-ons. Further information and the applicable data protection provisions of Google may be retrieved under https://www.google.com/intl/en/policies/privacy/ and under http://www.google.com/analytics/terms/us.html. Google Analytics is further explained under the following Link https://www.google.com/analytics/. 12. Data protection provisions about the application and use of Google-AdWords On this website, there is integrated Google AdWords. Google AdWords is a service for Internet advertising that allows the advertiser to place ads in Google search engine results and the Google advertising network. Google AdWords allows an advertiser to pre-define specific keywords with the help of which an ad on Google’s search results only then displayed when the user utilizes the search engine to retrieve a keyword-relevant search result. In the Google Advertising Network, the ads are distributed on relevant web pages using an automatic algorithm, taking into account the previously defined keywords. The operating company of Google AdWords is Google Inc., 1600 Amphitheatre Pkwy, Mountain View, CA 94043-1351, UNITED STATES. The purpose of Google AdWords is the promotion of our website by the inclusion of relevant advertising on the websites of third parties and in the search engine results of the search engine Google and an insertion of third-party advertising on our website. If a data subject reaches our website via a Google ad, a conversion cookie is filed on the information technology system of the data subject through Google. The definition of cookies is explained above. A conversion cookie loses its validity after 30 days and is not used to identify the data subject. If the cookie has not expired, the conversion cookie is used to check whether certain sub-pages, e.g, the shopping cart from an online shop system, were called up on our website. Through the conversion cookie, both Google and the controller can understand whether a person who reached an AdWords ad on our website generated sales, that is, executed or canceled a sale of goods. The data and information collected through the use of the conversion cookie is used by Google to create visit statistics for our website. These visit statistics are used in order to determine the total number of users who have been served through AdWords ads to ascertain the success or failure of each AdWords ad and to optimize our AdWords ads in the future. Neither our company nor other Google AdWords advertisers receive information from Google that could identify the data subject. The conversion cookie stores personal information, e.g. the Internet pages visited by the data subject. Each time we visit our Internet pages, personal data, including the IP address of the Internet access used by the data subject, is transmitted to Google in the United States of America. These personal data are stored by Google in the United States of America. Google may pass these personal data collected through the technical procedure to third parties. The data subject may, at any time, prevent the setting of cookies by our website, as stated above, by means of a corresponding setting of the Internet browser used and thus permanently deny the setting of cookies. Such a setting of the Internet browser used would also prevent Google from placing a conversion cookie on the information technology system of the data subject. In addition, a cookie set by Google AdWords may be deleted at any time via the Internet browser or other software programs. The data subject has a possibility of objecting to the interest-based advertisement of Google. Therefore, the data subject must access from each of the browsers in use the link www.google.de/settings/ads and set the desired settings. Further information and the applicable data protection provisions of Google may be retrieved under https://www.google.com/intl/en/policies/privacy/. 13. Data protection provisions about the application and use of LinkedIn There are integrated components of the LinkedIn Corporation on this website. LinkedIn is a web-based social network that enables users with existing business contacts to connect and to make new business contacts. Over 400 million registered people in more than 200 countries use LinkedIn. Thus, LinkedIn is currently the largest platform for business contacts and one of the most visited websites in the world. The operating company of LinkedIn is LinkedIn Corporation, 2029 Stierlin Court Mountain View, CA 94043, UNITED STATES. For privacy matters outside of the UNITED STATES LinkedIn Ireland, Privacy Policy Issues, Wilton Plaza, Wilton Place, Dublin 2, Ireland, is responsible. With each call-up to one of the individual pages of this Internet site on which a LinkedIn component (LinkedIn plug-in) was integrated, the Internet browser on the information technology system of the data subject is automatically prompted to the download of a display of the corresponding LinkedIn component of LinkedIn. Further information about the LinkedIn plug-in may be accessed under https://developer.linkedin.com/plugins. During the course of this technical procedure, LinkedIn gains knowledge of what specific sub-page of our website was visited by the data subject. If the data subject is logged in at the same time on LinkedIn, LinkedIn detects with every call-up to our website by the data subject—and for the entire duration of their stay on our Internet site—which specific sub-page of our Internet page was visited by the data subject. This information is collected through the LinkedIn component and associated with the respective LinkedIn account of the data subject. If the data subject clicks on one of the LinkedIn buttons integrated on our website, then LinkedIn assigns this information to the personal LinkedIn user account of the data subject and stores the personal data. LinkedIn receives information via the LinkedIn component that the data subject has visited our website, provided that the data subject is logged in at LinkedIn at the time of the call-up to our website. This occurs regardless of whether the person clicks on the LinkedIn button or not. If such a transmission of information to LinkedIn is not desirable for the data subject, then he or she may prevent this by logging off from their LinkedIn account before a call-up to our website is made. LinkedIn provides under https://www.linkedin.com/psettings/guest-controls the possibility to unsubscribe from e-mail messages, SMS messages and targeted ads, as well as the ability to manage ad settings. LinkedIn also uses affiliates such as Eire, Google Analytics, BlueKai, DoubleClick, Nielsen, Comscore, Eloqua, and Lotame. The setting of such cookies may be denied under https://www.linkedin.com/legal/cookie-policy. The applicable privacy policy for LinkedIn is available under https://www.linkedin.com/legal/privacy-policy. The LinkedIn Cookie Policy is available under https://www.linkedin.com/legal/cookie-policy. 14. Data protection provisions about the application and use of HubSpot There is integrated components of the HubSpot Inc on this website. HubSpot is a developer and marketer of software products for inbound marketing and sales. It was founded in 2006. Its products and services aim to provide tools for social media marketing, content management, web analytics, and search engine optimization, sales data, contact storing and analyzation. The operating company of Hubspot is Hubspot Inc, 25 First Street, 2nd Floor Cambridge, MA 02141, UNITED STATES. For privacy matters outside of the UNITED STATES. Hubspot Inc is listed in the PrivacyShield framework that means it is safe to process data with Hubspot outside European Union jurisdiction. Hubspot is used to collect traffic data, contact data, arrange meetings, to track the sales process. 15. Data protection provisions about the application and use of WP Engine INC This page is hosted in the company WP Engine INC. The vendor is hosting service provider in European Union jurisdiction, Germany. 16. Data protection provisions about the application and use of Mailchimp For some email subscriptions, we may use Mailchimp services to deliver news, and updates via email. The operating company of Vonage is Vonage INC, 23 Main Street, Holmdel, NJ 07733, UNITED STATES. For privacy matters outside of the UNITED STATES. The Rocket Science Group, LLC is listed in the PrivacyShield framework which means it is safe to process data with Mailchimp outside European Union jurisdiction, more regarding data security https://mailchimp.com/en-gb/about/security/ 17. Data protection provisions about the application and use of Vonage We may use Vonage to deliver call service, SMS, or other telephony services. The operating company of Mailchimp is The Rocket Science Group, LLC 675 Ponce de Leon Ave NE Suite 5000 Atlanta, GA 30308 UNITED STATES. For privacy matters outside of the UNITED STATES company has implemented high-security standards ISO 27001, PCI-DSS, SOC, HITRUST, and CSA STAR https://www.vonage.com/unified-communications/platform/security-reliability/ 18. Data protection provisions about the application and use of Typeform We may use Typeform to deliver the form submission service. The vendor is the forms service provider in European Union jurisdiction, Spain, more regarding data security https://www.typeform.com/help/a/security-at-typeform-360029259552/#h_01FDEP494ZGQY2TTCSJZ2BG4ZJ 19. Data protection provisions about the application and use of Cookiebot We may use Cookiebot to deliver cookie consent. The operating company of CookieBot is Cybot A/S, Havnegade 39, 1058, Copenhagen, Denmark. The vendor is the cookie consent service provider in European Union jurisdiction, Denmark, more regarding data security https://www.typeform.com/help/a/security-at-typeform-360029259552/#h_01FDEP494ZGQY2TTCSJZ2BG4ZJ 20. Data protection provisions about the application and use of HotJar We may use HotJar Ltd to deliver the freemium service. The vendor is the forms service provider stores in European Union jurisdiction, Malta, more regarding data security https://www.hotjar.com/legal/compliance/gdpr-commitment/ 20. Legal basis for the processing Art. 6(1) lit. a GDPR serves as the legal basis for processing operations for which we obtain consent for a specific processing purpose. If the processing of personal data is necessary for the performance of a contract to which the data subject is a party, as is the case, for example, when processing operations are necessary for the supply of goods or to provide any other service, the processing is based on Article 6(1) lit. b GDPR. The same applies to such processing operations which are necessary for carrying out pre-contractual measures, for example in the case of inquiries concerning our products or services. Is our company subject to a legal obligation by which processing of personal data is required, such as for the fulfillment of tax obligations, the processing is based on Art. 6(1) lit. c GDPR. Finally, processing operations could be based on Article 6(1) lit. f GDPR. This legal basis is used for processing operations that are not covered by any of the abovementioned legal grounds, if the processing is necessary for the purposes of the legitimate interests pursued by our company or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data. Such processing operations are particularly permissible because they have been specifically mentioned by the European legislator. He considered that a legitimate interest could be assumed if the data subject is a client of the controller (Recital 47 Sentence 2 GDPR). 21. The legitimate interests pursued by the controller or by a third party Where the processing of personal data is based on Article 6(1) lit. f GDPR our legitimate interest is to carry out our business in favor of the well-being of all our employees and the shareholders. 22. Period for which the personal data will be stored The criteria used to determine the period of storage of personal data is the respective statutory retention period. Mostly data retention periods are agreed upon with the Data Controller (Customer/Client of iDenfy) if premium or trust service versions are used and might vary: * 1 day * 30 days * 60 days * 5 years * 8 years * 10 years If the freemium version is in use when the data retention period is 30 days. After the expiration of that period, the corresponding data is routinely deleted, as long as it is no longer necessary for the fulfillment of the contract or the initiation of a contract. If Data Controller considers data as required to archive iDenfy will act under Controller’s requirements and will store data upon Data Controller’s request. 23. Provision of personal data as a statutory or contractual requirement; Requirement necessary to enter into a contract; Obligation of the data subject to provide the personal data; possible consequences of failure to provide such data We clarify that the provision of personal data is partly required by law (e.g. tax regulations) or can also result from contractual provisions (e.g. information on the contractual partner). Sometimes it may be necessary to conclude a contract that the data subject provides us with personal data, which must subsequently be processed by us. The data subject is, for example, obliged to provide us with personal data when our company signs a contract with him or her. The non-provision of the personal data would have the consequence that the contract with the data subject could not be concluded. Before personal data is provided by the data subject, the data subject must contact any employee. The employee clarifies to the data subject whether the provision of the personal data is required by law or contract or is necessary for the conclusion of the contract, whether there is an obligation to provide the personal data and the consequences of non-provision of the personal data. 24. Existence of automated decision-making As a responsible company, we are transparent and share information about automated decision-making. Automated decision-making processing activity is made during identification process if biometrical identification were chosen. All relevant details, steps and decision are visible for the Data subject. If any additional questions: dpo@idenfy.com . 25. Document History * 2020-03-02 Document created; * 2020-03-02 Document approved by Domantas Ciulde the director of UAB “Identifikaciniai Projektai”; * 2021-01-08 Document re-viewed; * 2021-02-10 Document updated; * 2021-02-10 Document approved by Domantas Ciulde the director of UAB “Identifikaciniai Projektai”; * 2022-06-22 Changed company name from UAB “Identifikaciniai Projektai” to UAB “iDenfy”; * 2022-06-22 Changed email from info@idenfy.com to dpo@idenfy.com; * 2022-06-22 Added subprocessor Mailchimp Inc; * 2022-06-22 Added subprocessor Vonage; * 2022-06-22 Added subprocessor Typeform; * 2022-06-22 Added subprocessor CookieBot; * 2021-06-22 Document approved by Domantas Ciulde the director of UAB “iDenfy”; * 2022-12-27 Added freemium, premium, and trust service plans retention time; * 2022-12-27 Document approved by Domantas Ciulde the director of UAB “iDenfy”; * 2023-03-17 Added subprocessor HotJar; * 2023-03-17 Document approved by Domantas Ciulde the director of UAB “iDenfy”; All iDenfy’s products are protected with the number one cyber insurance package and the Technology Errors & Omissions insurance. Products * KNOW YOUR CUSTOMER * Identity Verification * AML Software * Business Verification * NFC Verification * Know Your Business Solution * FRAUD PREVENTION * Phone Number Verification * Proxy Detection * Proof of Address Verification * Customer’s Risk Score Verification Supported Industries * Fintech * Cryptocurrency & Blockchain * Proxy Networks * Gaming * Online Gambling * Digital Wallets * Transportation * Streaming Resources * Blog * Newsroom * Roadmap * Supported Documents * Security and Compliance * WordPress Integration * WooCommerce integration * Glossary * Help Center Company * About us * Customers * Careers * Partner program * Cyber Insurance * Report Abuse * Contact us Trademark registration number: 018171228. ISO 27001 certificate number TIC 1512120135 All Rights Reserved © iDenfyTM 2024 * Service status * Privacy policy * Cookie policy