cookie policy
1. What are “cookies”?
When you visit one of K&H Bank Group's websites your browser may store a mini file, i.e., a cookie. Some of the cookies used by us are indispensable for the proper operation of our sites, while others collect information related to their use, allowing us to upgrade our sites to offer even more convenient and useful services. Temporary or “session cookies” are erased when the browser is closed while “permanent cookies” stay in your browser for a longer time.
2. What are “cookies” for?
The K&H Bank Group uses cookies on its websites for the following purposes:
- facilitate navigation on our websites and allow for faster downloading
- allow us to regularly improve user experience
- allow us to upload content to our websites best suited to the needs of visitors
- allow us to gain an insight into visitors’ use of our online-based services and introduce improvements based on past experience
- allow us to display the most relevant offers to our visitors
3. Types of “cookies” used
3.1. Cookies not requiring consent
used cookies during visiting of kh.hu
“basic cookies”
| Cookie name | Creator | What data is collected? | Purpose of use | Technical type | Cookie level | Expiration date | Data transfer outside the EEA |
|---|---|---|---|---|---|---|---|
| dtCookie | Dynatrace | v4 session status: v_4_key1_value1_key2_value2_keyN_valueN optional "key" values: srv sn mvisitor msn perc ol mul app:<appID> |
Visit tracking | 1st party | Basic | Session | No |
| dtLatC | Dynatrace | Number value | Measures server latency for performance monitoring | 1st party | Basic | Session | No |
| dtPC | Dynatrace | <serverID>$<randomValue>_<currentMillis> v<randomValue>e<eventCount> | Identification of which service server the data is sent to. It also contains a session ID | 1st party | Basic | Session | No |
| dtSa | Dynatrace | Operation name | Serves as intermediate storage for cross-page operations | 1st party | Basic | Session | No |
| dtValidationCookie | Dynatrace | (Undetermined) | Cookie used to determine the top-level domain name | 1st party | Basic | Session, but a few seconds after its creation, it is deleted as a result of a script | No |
| dtDisabled | Dynatrace | True/False value | Specifies whether RUM JavaScript should be deactivated for cost and traffic control or overload prevention | 1st party | Basic | Session | No |
| rxVisitor | Dynatrace | Visitor ID | ID used to identify sessions | 1st party | Basic | Session | No |
| rxvt | Dynatrace | Time stamp | It determines the end of the session in time | 1st party | Basic | Session | No |
| COOKIE_SUPPORT | kh.hu | Yes/No status | Set by Liferay, it is used to check whether the visitor's browser supports cookies | 1st party | Basic | T+1 year | No |
| GUEST_LANGUAGE_ID | kh.hu | Preferred language ID | Store the visitor's preferred language ID | 1st party | Basic | T+1 year | No |
| JSESSIONID | kh.hu | Webserver session ID | Store a session ID so it can track the number of sessions | 1st party | Basic | Session | No |
| kh_cookie_level1 | kh.hu | Yes/No status | Store the consent acceptance level | 1st party | Basic | T+1 year | No |
| kh_cookie_level3 | kh.hu | Yes/No status | Store the consent acceptance level | 1st party | Basic | T+1 year | No |
| kh_cookie_level4 | kh.hu | Yes/No status | Store the consent acceptance level | 1st party | Basic | T+1 year | No |
| LFR_SESSION_STATE_20161 | kh.hu | Time stamp | It is only used to control the timestamp of the expiration of a user session to the Liferay server | 1st party | Basic | Session | No |
| PD_STATEFUL_<UUID> | kh.hu | Vhost-website-kh-hu | WEBSITE | 1st party | Basic | Session | No |
| TS01193f10 | kh.hu | Random string | WEBSITE | 1st party | Basic | Session | No |
| LPSID-49661909 | LivePerson | Session information | It belongs to LivePerson and is used to provide a live chat function. Visitor session status, for the currently active session and the most recent session | 1st party | Basic | Session | Yes - UK |
| LPVID | LivePerson | Visitor ID in Conversational Cloud | It belongs to LivePerson. This cookie is the visitor ID identified in the Conversational Cloud | 1st party | Basic | T+1 year | Yes - UK |
| TS5357fe25027 | kh.hu | Random character chain | WEBSITE | 1st party | Basic | Session | No |
| _gid | Google Analytics | Session ID, browser ID | It is used to determine how many people visited the page on a given day (not how many times). - For Google Analytics reports, storing information anonymously and assigning a randomly generated number to recognize unique visitors. When the page is loaded the cookie is downloaded, but data is not sent in the absence of statistical consent, as Google Tag Manager blocks the Google Analytics measurement code from running on the page, so the data stored in the cookie is not sent to the Google Analytics server either. | 1st party | Basic | T+1 day | Yes |
| _ga | Google Analytics | Domain ID, random browser ID | The Google Analytics measurement code that is loaded on the website after consent can be used to identify that the currently measured visitor has already visited the website on the currently used device with the currently used browser. (=not a new user, but a returning one). It is also used by Facebook to link all website interactions of 1-1 users (page views, important clicks, callback requests) into a chain, as the user's "journey" from the first visit to the last. When the page is loaded the cookie is downloaded, but data is not sent in the absence of statistical consent, as Google Tag Manager blocks the Google Analytics measurement code from running on the page, so the data stored in the cookie is not sent to the Google Analytics server either. | 1st party | Basic | T+2 years | Yes |
| _gac_UA-73003413-2 | Google Analytics | Uniqe ID | It comes from Google Analytics and is used by advertisers to measure user activity and the performance of advertising campaigns. It is only entered when an ad is clicked, and the data is processed by Google Analytics only when it is accepted at the marketing level. When the page is loaded the cookie is downloaded, but data is not sent in the absence of statistical consent, as Google Tag Manager blocks Google Analytics from using personalized advertising functions, the data stored in the cookie is used by the Google Analytics system for statistical purposes only. If statistical consent is not given, the data stored in the cookie will not be forwarded to Google Analytics. | 3rd party | Basic | T+90 days | No |
| ai_session | idopontfoglalas.kh.hu | ID of the given browsing session. It can be used to connect the steps belonging to the same process on the server side | The unique ID of the booking process in the browser | 3rd party | Basic | Session | No |
| Linistry.EntryUrl | idopontfoglalas.kh.hu | Encoded URL | This is where Linistry stores the URL from which the customer first opened the process (entry point) | 3rd party | Basic | T+1 day | No |
| ai_user | idopontfoglalas.kh.hu | Id and session start date | Technical cookie, for technical reasons, a unique identifier is randomly generated for the user. Marketing activity is not related to it | 3rd party | Basic | T+1 year | No |
| Linistry.Culture | idopontfoglalas.kh.hu | Country code (hu) | It stores the (preferred) selected language by the customer. The interface appears in this language | 3rd party | Basic | T+1 year | No |
| Linistry.Breadcrumb | idopontfoglalas.kh.hu | Encoded Breadcrumb | Technical cookie, we store it for technical reasons which shows the route the user takes on the page so that the "Back" arrow takes him to the right place. It is necessary because there are pages to which it is pointless to go back | 3rd party | Basic | T+1 day | No |
| .AspNet.Consent | idopontfoglalas.kh.hu | It shows whether the visitor has accepted the cookie consent, if not, the cookie consent widget is displayed | Linistry stores here that the user has given the consent to use the service (technically mandatory cookies, no marketing activity is included) | 3rd party | Basic | T+1 year | Yes |
used cookies during visiting of khdirektbiztositas.hu and biztositas.kh.hu
| Cookie name | Creator | What data is collected? | Purpose of use | Technical type | Cookie level | Expiration date | Data transfer outside the EEA |
|---|---|---|---|---|---|---|---|
| dtCookie | Dynatrace | v4 session status: v_4_key1_value1_key2_value2_keyN_valueN optional "key" values: srv sn mvisitor msn perc ol mul app:<appID> |
Visit tracking | 1st party | Basic | Session | No |
| dtLatC | Dynatrace | Number value | Measures server latency for performance monitoring | 1st party | Basic | Session | No |
| dtPC | Dynatrace | <serverID>$<randomValue>_<currentMillis> v<randomValue>e<eventCount> | Identification of which service server the data is sent to. It also contains a session ID | 1st party | Basic | Session | No |
| dtSa | Dynatrace | Operation name | Serves as intermediate storage for cross-page operations | 1st party | Basic | Session | No |
| dtValidationCookie | Dynatrace | (Undetermined) | Cookie used to determine the top-level domain name | 1st party | Basic | Session, but a few seconds after its creation, it is deleted as a result of a script | No |
| dtDisabled | Dynatrace | True/False value | Specifies whether RUM JavaScript should be deactivated for cost and traffic control or overload prevention | 1st party | Basic | Session | No |
| rxVisitor | Dynatrace | Visitor ID | ID used to identify sessions | 1st party | Basic | Session | No |
| rxvt | Dynatrace | Time stamp | It determines the end of the session in time | 1st party | Basic | Session | No |
| JSESSIONID | khdirektbiztositas.hu | Webserver session ID | Store a session ID so it can track the number of sessions | 1st party | Basic | session | No |
| PD_STATEFUL_<UUID> | khdirektbiztositas.hu | Vhost-website-kh-hu | WEBSITE | 1st party | Basic | session | No |
| TS01db1945 | khdirektbiztositas.hu | Random string | WEBSITE | 1st party | Basic | session | No |
| TS2f2776c3027 | khdirektbiztositas.hu | Random string | WEBSITE | 1st party | Basic | session | No |
| TS01e35059 | khdirektbiztositas.hu | Random string | WEBSITE | 1st party | Basic | session | No |
| LPSID-49661909 | LivePerson | Session information | It belongs to LivePerson and is used to provide a live chat function. Visitor session status, for the currently active session and the most recent session | 1st party | Basic | session | Yes - UK |
| LPVID | LivePerson | Visitor ID in Conversational Cloud | It belongs to LivePerson. This cookie is the visitor ID identified in the Conversational Cloud | 1st party | Basic | T+1 year | Yes - UK |
| kh_cookie_level1 | khdirektbiztositas.hu | Yes/No status | Store the consent acceptance level | 1st party | Basic | T+1 year | No |
| kh_cookie_level3 | khdirektbiztositas.hu | Yes/No status | Store the consent acceptance level | 1st party | Basic | T+1 year | No |
| kh_cookie_level4 | khdirektbiztositas.hu | Yes/No status | Store the consent acceptance level | 1st party | Basic | T+1 year | No |
| _ga | Google Analytics | Domain ID, random browser ID | The Google Analytics measurement code that is loaded on the website after consent can be used to identify that the currently measured visitor has already visited the website on the currently used device with the currently used browser. (=not a new user, but a returning one). It is also used by Facebook to link all website interactions of 1-1 users (page views, important clicks, callback requests) into a chain, as the user's "journey" from the first visit to the last. When the page is loaded the cookie is downloaded, but data is not sent in the absence of statistical consent, as Google Tag Manager blocks the Google Analytics measurement code from running on the page, so the data stored in the cookie is not sent to the Google Analytics server either | 1st party | basic | T+2 years | yes |
| _gid | Google Analytics | Session ID, browser ID | It is used to determine how many people visited the page on a given day (not how many times). - For Google Analytics reports, storing information anonymously and assigning a randomly generated number to recognize unique visitors. When the page is loaded the cookie is downloaded, but data is not sent in the absence of statistical consent, as Google Tag Manager blocks the Google Analytics measurement code from running on the page, so the data stored in the cookie is not sent to the Google Analytics server either | 1st party | basic | T+1 day | Yes |
used cookies during visiting of karrier.kh.hu
“basic cookies”
| Cookie name | Creator | What data is collected? | Purpose of use | Technical type | Cookie level | Expiration date | Data transfer outside the EEA |
|---|---|---|---|---|---|---|---|
| spublic | Nexum Career Portal | It does not collect data | It identifies the session. | 1st party | System | Session | No |
| cookie_terms_accepted | Nexum Career Portal | It does not collect data | Here we store whether the user has accepted cookie management. | 1st party | System | T+2 years | No |
| cookie_terms_accepted_date | Nexum Career Portal | It does not collect data | Enter the date of acceptance of cookie management. | 1st party | System | T+2 years | No |
| accepted_cookies | Nexum Career Portal | It does not collect data | Here we store what type of cookies the user has allowed to be stored. | 1st party | System | T+2 years | No |
| kh_cookie_level1 | kh.hu | Yes/No status | Store the consent acceptance level. | 1st party | Basic | T+180 days | No |
| kh_cookie_level3 | kh.hu | Yes/No status | Store the consent acceptance level. | 1st party | Basic | T+180 days | No |
| kh_cookie_level4 | kh.hu | Yes/No status | Store the consent acceptance level. | 1st party | Basic | T+180 days | No |
3.2. “Cookies requiring consent”
used cookies during visiting of kh.hu
“statistical cookies”
| Cookie name | Creator | What data is collected? | Purpose of use | Technical type | Cookie level | Expiration date | Data transfer outside the EEA |
|---|---|---|---|---|---|---|---|
| _ga_D967W7RZKJ | Google Analytics | Session ID (live pages) | It helps to identify and treat a user's individual visit (=session) as a unit, which is the sum of page views and other interactions (clicks, video views, etc.) within a given time frame | 1st party | statistical | T+2 years | Yes |
| _hjAbsoluteSessionInProgress | Hotjar | Yes/No status | Used to detect the user's first page view session | 1st party | statistical | T+30 minutes | Yes |
| _hjFirstSeen | Hotjar | Yes/No status | Used to detect the first session (visit) of a new user. It helps in calculating the length of the session (visit) | 1st party | statistical | Session | No |
| _hjIncludedInPageviewSample | Hotjar | Yes/No status | Set to determine if a user is included in the data sampling defined by your site's daily page views limit | 1st party | statistical | T+30 minutes | No |
| _hjIncludedInSessionSample | Hotjar | Yes/No status | Set to determine if a user is included in the data sampling defined by your site's daily session limit | 1st party | statistical | T+30 minutes | No |
| _hjSession_79976 | Hotjar | Data packet stored with base64 encoding, including a session ID, a time stamp and a yes/no status, which indicates that the given session is part of the statistical sampling | Ensures that subsequent requests during a session also belong to the same session | 1st party | statistical | T+30 minutes | No |
| _hjSessionRejected | Hotjar | Returns 1 when Hotjar refused to connect the session to WebSocket due to server overload | Returns 1 when Hotjar refused to connect the session to WebSocket due to server overload | 1st party | statistical | Session | No |
| _hjSessionUser_79976 | Hotjar | Data packet stored with base64 encoding, including a session ID, a time stamp and a yes/no status, which indicates that the given session is part of the statistical sampling | This helps to organize the entire life journey of the user in a chain in the reports | 1st party | statistical | T+1 year | No |
| _hjIncludedInSessionSample_79976 | kh.hu | Boolean true/false value |
Set to determine if a user is included in the data sampling defined by your site's daily session limit | 1st party | statistical | T+1 year | No |
“marketing cookies”
| Cookie name | Creator | What data is collected? | Purpose of use | Technical type | Cookie level | Expiration date | Data transfer outside the EEA |
| __exponea_etc__ | Bloomreach (korábban Exponea) | User ID | Storage of unique user id | 1st party | Marketing | T+7 day - T+3 year (browser dependent) | No |
| __exponea_time2__ | Bloomreach (korábban Exponea) | Time zone | The service corrects the time of its own servers with the time of the visitor (time zone difference) | 1st party | Marketing | T+1 day | No |
| xnpe_978d367c-12bf-11eb-ac68-86681a435db2 | Bloomreach (korábban Exponea) | User ID | Storage of unique user id | 1st party | Marketing | T+3 years | No |
| _fbc | Facebook click ID | With this can link website interactions (e.g. callback requests) back to the last click on Facebook, which is typically a Facebook ad. This makes a Facebook campaign measurable and optimisable. | 1st party | Marketing | T+3 months | Yes | |
| _fbp | Domain ID, random browser ID | The Facebook measurement code that is loaded on the website after consent can be used to identify that the currently measured visitor has already visited the website on the currently used device with the currently used browser. (=not a new user, but a returning one). It is also used by Facebook to link all website interactions of 1-1 users (page views, important clicks, callback requests) into a chain, as the user's "journey" from the first visit to the last | 1st party | Marketing | T+3 months | Yes | |
| 1P_JAR | Time stamp | Used by Google to display personalized ads on Google websites based on recent searches and previous interactions | 3rd party | Marketing | T+1 month | Yes | |
| AEC | Browser ID | Used by Google to store user settings and information while viewing pages crawled by Google | 3rd party | Marketing | T+6 months | Yes | |
| CONSENT | Composite value: yes/no status regarding their own consent, time stamp and language ID | Google stores here whether and when the user gave consent to data collection | 3rd party | Marketing | T+2 years | Yes | |
| IDE | Browser ID | Used by Google to store user settings and information while viewing pages crawled by Google (DoubelClick cookie) | 3rd party | Marketing | T+13 months | Yes | |
| NID | Browser ID | Used by Google to display personalized ads on Google websites based on recent searches and previous interactions | 3rd party | Marketing | T+6 months | Yes | |
| SID | Browser ID | Store the user's Google account ID in coded and digitally signed form and store the last login time | 3rd party | Marketing | T+2 years | Yes | |
| _gcl_au | Google Ads | Goolge Ads ads click ID | It helps Google Ads that if the user moves from the landing page of the ad to another sub-page to connected achieved business goals (e.g. callback request) with the Google Ads ad that triggered the visit. This will helps to find effective ads, helps optimize the ad costs, and increase the advertising effectiveness. | 1st party | Marketing | T+3 months | Yes |
| _gaexp | Google Optimize | Experiment and session ID | Store Google Optimize experiment and session ids for A/B tests | 1st party | Marketing | T+90 days | Yes |
| _opt_awcid | Google Optimize | Google Ads advertiser ID | If the Google Optimize experiment is started as a result of a certain Google Ads advertiser, campaign, ad group or targeting, the system can later identify which Google Ads element the partial results of the A/B test should be collected for |
1st party | Marketing | T+1 day | Yes |
| _opt_awmid | Google Optimize | Google Ads campaign ID | If the Google Optimize experiment is started as a result of a certain Google Ads advertiser, campaign, ad group or targeting, the system can later identify which Google Ads element the partial results of the A/B test should be collected for | 1st party | Marketing | T+1 day | Yes |
| _opt_awgid | Google Optimize | Google Ads ad group ID | If the Google Optimize experiment is started as a result of a certain Google Ads advertiser, campaign, ad group or targeting, the system can later identify which Google Ads element the partial results of the A/B test should be collected for | 1st party | Marketing | T+1 day | Yes |
| _opt_awkid | Google Optimize | Google Ads target ID | If the Google Optimize experiment is started as a result of a certain Google Ads advertiser, campaign, ad group or targeting, the system can later identify which Google Ads element the partial results of the A/B test should be collected for | 1st party | Marketing | T+1 day | Yes |
| _opt_utmc | Google Optimize | Store the utm_campaign URL parameter | If the Google Optimize experiment targets a certain utm_campaign campaign name, this cookie helps Google Optimize maintain targeting on subsequently visited pages within the session | 1st party | Marketing | T+1 day | Yes |
| _opt_expid | Google Optimize | During redirect A/B tests, experiment and variant ID, and reference to the redirected page | If during the A/B test two separate pages are the subject of the test, then the parameters of the experiments are transferred from the original page version to the test version with the help of this | 1st party | Marketing | T+10 seconds | Yes |
| currentArticle | kh.hu | Actual click name | It monitors which articles may have been helpful in using the contact forms on the website, ergo which articles was part of the anonymous user's journey to using the form. | 1st party | Marketing | T+1 year | No |
| KH_COOKIE_GCLID | kh.hu | Google Ads paid click ID | Store Google Ads click ID, with which we can return additional anonymous data to Google Ads for analysis purposes | 1st party | Marketing | T+1 month | No |
| KH_COOKIE_UTM_CAMPAIGN | kh.hu | The name of the last detected external traffic campaign | Identification of traffic sent by a campaign | 1st party | Marketing | T+1 month | No |
| KH_COOKIE_UTM_CLIENTID | kh.hu | Unique ID number for the given browser and website | It stores the unique ID used by Google Analytics, trough this can expend the Google Analytics aggregate data from the server side with strictly non-client data | 1st party | Marketing | T+1 month | No |
| KH_COOKIE_UTM_CONTENT | kh.hu | The name of the ad in the last clicked external traffic campaign | Identifies what the user clicked on the site, such as a banner ad or a text link | 1st party | Marketing | T+1 month | No |
| KH_COOKIE_UTM_MEDIUM | kh.hu | Link type of the last detected external traffic campaign | Identifies the type of link used, such as cpc or email | 1st party | Marketing | T+1 month | No |
| KH_COOKIE_UTM_SOURCE | kh.hu | Website address of the last detected external traffic campaign | Identifies search terms | 1st party | Marketing | T+1 month | No |
| KH_COOKIE_UTM_TERM | kh.hu | Keyword or targeting name that can be assigned to the last detected external traffic campaign | Identifies the sent traffic of the website | 1st party | Marketing | T+1 month | No |
| khPerso | kh.hu | Visited product pages whitin kh.hu | Display personalized content on certain subpages of kh.hu based on previously visited product pages | 1st party | Marketing | 1 month | No |
| khPersoViewed | kh.hu | Yes/No status | Display personalized content on certain subpages of kh.hu based on previously visited product pages | 1st party | Marketing | 1 month | No |
| lastArticle | kh.hu | Previous article name |
It monitors which articles may have been helpful in using the contact forms on the website, ergo which articles was part of the anonymous user's journey to using the form. | 1st party | Marketing | T+1 year | No |
| lastArticlesCategory | kh.hu | Category list of last viewed article pages | It monitors which articles may have been helpful in using the contact forms on the website, ergo which articles was part of the anonymous user's journey to using the form. | 1st party | Marketing | T+1 year | No |
| sessionArticlesCategory | kh.hu | Category list of last viewed article pages | It monitors which articles may have been helpful in using the contact forms on the website, ergo which articles was part of the anonymous user's journey to using the form. | 1st party | Marketing | session | No |
| kh_notification_ask | kh.hu | True / False | Notification appeared | 1st party | Marketing | T + 7 days | No |
| KH_STICKY_STATE_<number> | kh.hu | True / False | The purpose of the cookie is to fulfill the business requirement that if the user has closed the sticky bar once, it should not appear open to him/her for a certain day when he/she returns to the page | 1st party | Marketing | T+1 year | No |
| _gcl_aw | Google Ads | GCL ID | The Conversion Linker put it down and helps to identify and retarget the clicked ad | 3rd party | Marketing | T+3 months | No |
| _gat_UA-73003413-2 | Google Analytics | Random number | Ensuring that the frequency of data transmitted to Google Analytics is not high, thereby protecting the Google Analytics service itself from being overloaded | 1st party | Marketing | T+1 minute | Yes |
| bcookie | .linkedin.com | Browser reletad data | Browser Identifier cookie to uniquely indentify devices accessing LinkedIn to detect abuse on the platform and diagnostic purposes | 3rd party | Marketing | T + 1 year | Yes |
| bscookie | .www.linkedin.com | User ID | Used for remembering that a logged in user is verified by two factor authentication and has previously logged in | 3rd party | Marketing | T + 1 year | Yes |
| li_alerts | .linkedin.com | User ID | Used to track impressions of LinkedIn alerts, such as the Cookie Banner and to implement cool off periods for display of alerts | 3rd party | Marketing | T + 1 year | Yes |
| li_gc | .linkedin.com | Browser ID | Used to store consent of guests regarding the use of cookies for non-essential purposes | 3rd party | Marketing | T + 6 months | Yes |
| li_rm | .www.linkedin.com | Browser ID | Used as part of LinkedIn's Remember Me Feature and is set when a user clicks "Remember me" on their device to make logging in on that device easier | 3rd party | Marketing | T + 1 year | Yes |
| lidc | .www.linkedin.com | Session ID | To facilitate data center selection | 3rd party | Marketing | T + 24 hour | Yes |
| c_user | .facebook.com | Unique user ID | To store a unique user ID | 3rd party | Marketing | T+30 days | Yes |
| datr | .facebook.com | Browsing device information | To provide fraud prevention | 3rd party | Marketing | T+2 years | Yes |
| sb | .facebook.com | Browsing device information | To store browser details | 3rd party | Marketing | T+2 years | Yes |
| xs | .facebook.com | Session ID | To store a unique session ID | 3rd party | Marketing | T+3 months | Yes |
| tt_viewer | teads.tv | Teads User ID | Used for frequency capping, audience targeting, measurement and optimization | 3rd party | Marketing | T+1 year | Yes |
| tt_bluekai | teads.tv | N/A | Avoid calling to bluekai. When this cookieis set, the Bluekai pixel URL is not added to the usersync iframe. This avoid sunnecessary calls to Bluekai | 3rd party | Marketing | T+1 day | Yes |
| tt_emetriq | teads.tv | N/A | Avoid calling to emetriq | 3rd party | Marketing | T+1 day | Yes |
| tt_exelate | teads.tv | N/A | Avoid calling to Exelate. When this cookieis set, the Exelate pixel URL is not added to the user synciframe. This avoid sunnecessary calls to Exelate. | 3rd party | Marketing | T+1 day | Yes |
| tt_liveramp | teads.tv | N/A | Avoid calling to liveramp | 3rd party | Marketing | T+1 day | Yes |
| tt_neustar | teads.tv | N/A | Avoid calling to neustar | 3rd party | Marketing | T+1 day | Yes |
| tt_retargetly | teads.tv | N/A | Avoid calling to retargetly | 3rd party | Marketing | T+1 day | Yes |
| tt_salesforce | teads.tv | N/A | Avoid calling to salesforce | 3rd party | Marketing | T+1 day | Yes |
| tt_skp | teads.tv | N/A | Avoid calling to SKP | 3rd party | Marketing | T+1 day | Yes |
| tt_dar | teads.tv | N/A | Avoid calling to DAR | 3rd party | Marketing | T+1 day | Yes |
| _tfpvi | kh.hu | Teads User ID within the publisher's domain | GDPR purpose1,2,3,7 (for frequency-capping, ad-collision andaudience based interests, product measurements) | 1st party | Marketing | T+1 year | Yes |
used cookies during visiting of khdirektbiztositas.hu and biztositas.kh.hu
“statistical cookies”
| Cookie name | Creator | What data is collected? | Purpose of use | Technical type | Cookie level | Expiration date | Data transfer outside the EEA |
|---|---|---|---|---|---|---|---|
| _ga_D967W7RZKJ | Google Analytics | Session ID (live pages) | It helps to identify and treat a user's individual visit (=session) as a unit, which is the sum of page views and other interactions (clicks, video views, etc.) within a given time frame | 1st party | statistical | T+2 years | Yes |
| _ga_VQ6BTML9JL | Google Analytics | Session ID (live pages) | It helps to identify and treat a user's individual visit (=session) as a unit, which is the sum of page views and other interactions (clicks, video views, etc.) within a given time frame | 1st party | statistical | T+2 years | Yes |
| _hjAbsoluteSessionInProgress | Hotjar | Yes/No status | A felhasználó első oldalmegtekintési munkamenetének észlelésére szolgál | 1st party | statistical | T+30 minutes | Yes |
| _hjFirstSeen | Hotjar | Yes/No status | Used to detect the first session (visit) of a new user. It helps in calculating the length of the session (visit) | 1st party | statistical | session | No |
| _hjid | Hotjar | Unique ID in UUID format | It marks the visitor on the page opened in the given browser with a random identifier, which helps Hotjar to recognize that he has visited the page before during a subsequent visit (on the same device, in the same browser). This helps to organize the entire life journey of the user in a chain in the reports | 1st party | statistical | T+1 year | No |
| _hjIncludedInPageviewSample | Hotjar | Yes/No status | Set to determine if a user is included in the data sampling defined by your site's daily page views limit | 1st party | statistical | T+30 minutes | No |
| _hjIncludedInSessionSample | Hotjar | Yes/No status | Set to determine if a user is included in the data sampling defined by your site's daily session limit | 1st party | statistical | T+30 minutes | No |
| _hjSession_153384 | Hotjar | Data packet stored with base64 encoding, including a session ID, a time stamp and a yes/no status, which indicates that the given session is part of the statistical sampling | Ensures that subsequent requests during a session also belong to the same session | 1st party | statistical | T+30 minutes | No |
| _hjSessionRejected | Hotjar | Returns 1 when Hotjar refused to connect the session to WebSocket due to server overload | Returns 1 when Hotjar refused to connect the session to WebSocket due to server overload | 1st party | statistical | Session | No |
| _hjSessionUser_153384 | Hotjar | Data packet stored with base64 encoding, including a session ID, a time stamp and a yes/no status, which indicates that the given session is part of the statistical sampling | Ensures that subsequent requests during a session also belong to the same session | 1st party | statistical | T+30 minutes | No |
“marketing cookies”
| Cookie name | Creator | What data is collected? | Purpose of use | Technical type | Cookie level | Expiration date | Data transfer outside the EEA |
|---|---|---|---|---|---|---|---|
| _fbc | Facebook click ID | With this can link website interactions (e.g. callback requests) back to the last click on Facebook, which is typically a Facebook ad. This makes a Facebook campaign measurable and optimisable | 1st party | Marketing | T+3 months | Yes | |
| _fbp | Domain ID, random browser ID | The Facebook measurement code that is loaded on the website after consent can be used to identify that the currently measured visitor has already visited the website on the currently used device with the currently used browser. (=not a new user, but a returning one). It is also used by Facebook to link all website interactions of 1-1 users (page views, important clicks, callback requests) into a chain, as the user's "journey" from the first visit to the last | 1st party | Marketing | T+3 months | Yes | |
| 1P_JAR | Time stamp | Used by Google to display personalized ads on Google websites based on recent searches and previous interactions | 3rd party | Marketing | T+1 month | Yes | |
| AEC | Browser ID | Used by Google to store user settings and information while viewing pages crawled by Google | 3rd party | Marketing | T+6 months | Yes | |
| CONSENT | Composite value: yes/no status regarding their own consent, time stamp and language ID | Google stores here whether and when the user gave consent to data collection | 3rd party | Marketing | T+2 years | Yes | |
| IDE | Browser ID | Used by Google to store user settings and information while viewing pages crawled by Google (DoubelClick cookie) | 3rd party | Marketing | T+13 months | Yes | |
| NID | Browser ID | Used by Google to display personalized ads on Google websites based on recent searches and previous interactions | 3rd party | Marketing | T+6 months | Yes | |
| SID | Browser ID | Store the user's Google account ID in coded and digitally signed form and store the last login time | 3rd party | Marketing | T+2 years | Yes | |
| _gcl_au | Google Ads | Goolge Ads ads click ID | It helps Google Ads that if the user moves from the landing page of the ad to another sub-page to connected achieved business goals (e.g. callback request) with the Google Ads ad that triggered the visit. This will helps to find effective ads, helps optimize the ad costs, and increase the advertising effectiveness. | 1st party | Marketing | T+3 months | Yes |
| _gaexp | Google Optimize | Experiment and session ID | Store Google Optimize experiment and session ids for A/B tests | 1st party | Marketing | T+90 days | Yes |
| _opt_awcid | Google Optimize | Google Ads advertiser ID | If the Google Optimize experiment is started as a result of a certain Google Ads advertiser, campaign, ad group or targeting, the system can later identify which Google Ads element the partial results of the A/B test should be collected for |
1st party | Marketing | T+1 day | Yes |
| _opt_awmid | Google Optimize | Google Ads campaign ID | If the Google Optimize experiment is started as a result of a certain Google Ads advertiser, campaign, ad group or targeting, the system can later identify which Google Ads element the partial results of the A/B test should be collected for |
1st party | Marketing | T+1 day | Yes |
| _opt_awgid | Google Optimize | Google Ads ad group ID | If the Google Optimize experiment is started as a result of a certain Google Ads advertiser, campaign, ad group or targeting, the system can later identify which Google Ads element the partial results of the A/B test should be collected for |
1st party | Marketing | T+1 day | Yes |
| _opt_awkid | Google Optimize | Google Ads target ID | If the Google Optimize experiment is started as a result of a certain Google Ads advertiser, campaign, ad group or targeting, the system can later identify which Google Ads element the partial results of the A/B test should be collected for |
1st party | Marketing | T+1 day | Yes |
| _opt_utmc | Google Optimize | Store the utm_campaign URL parameter | If the Google Optimize experiment targets a certain utm_campaign campaign name, this cookie helps Google Optimize maintain targeting on subsequently visited pages within the session |
1st party | Marketing | T+1 day | Yes |
| _opt_expid | Google Optimize | During redirect A/B tests, experiment and variant ID, and reference to the redirected page | If during the A/B test two separate pages are the subject of the test, then the parameters of the experiments are transferred from the original page version to the test version with the help of this | 1st party | Marketing | T+10 seconds | Yes |
used cookies during visiting of karrier.kh.hu
“statistical cookies”
| Cookie name | Creator | What data is collected? | Purpose of use | Technical type | Cookie level | Expiration date | Data transfer outside the EEA |
|---|---|---|---|---|---|---|---|
| _ga | Google Analytics | Domain ID, random browser ID | The Google Analytics measurement code that is loaded on the website after consent can be used to identify that the currently measured visitor has already visited the website on the currently used device with the currently used browser. (=not a new user, but a returning one). It is also used by Facebook to link all website interactions of 1-1 users (page views, important clicks, callback requests) into a chain, as the user's "journey" from the first visit to the last. When the page is loaded the cookie is downloaded, but data is not sent in the absence of statistical consent, as Google Tag Manager blocks the Google Analytics measurement code from running on the page, so the data stored in the cookie is not sent to the Google Analytics server either. | 3rd party | Statistical | T+2 years | Yes |
| __utma | Google Analytics | User ID | Used to distinguish users and sessions. The cookie is created when the javascript library executes and no __utma cookies exists. The cookie is updated every time data is sent to Google Analytics. | 3rd party | Statistical | T+2 years | Yes |
| __utmb | Google Analytics | Timestamp | Used to define new sessions/visits and store the date of the visit. The cookie is created when the JavaScript library is executed and no __utmb cookies exist. The cookie is updated each time data is sent to Google Analytics. | 3rd party | Statistical | T+30 minutes | Yes |
| __utmc | Google Analytics | Timestamp | Used to store the time of the visit. It is not used in ga.js. Configured to work with urchin.js. Previously, this cookie worked with the __utmb cookie to determine if the user was in a new session/visit. | 3rd party | Statistical | Session | Yes |
| __utmt | Google Analytics | It does not collect data. | Used to store the number of service requests and to control the speed of requests. | 3rd party | Statistical | T+10 minutes | Yes |
| __utmz | Google Analytics | Keyword used, search engine, traffic source | Used to store keywords and seach engines. Stores the user traffic source or campaign information. It is updated with each data transmission. | 3rd party | Statistical | T+6 months | Yes |
“marketing cookies”
| Cookie name | Creator | What data is collected? | Purpose of use | Technical type | Cookie level | Expiration date | Data transfer outside the EEA |
|---|---|---|---|---|---|---|---|
| _gcl_au | Google Ads | Goolge Ads ads click ID | It helps Google Ads that if the user moves from the landing page of the ad to another sub-page to connected achieved business goals (e.g. callback request) with the Google Ads ad that triggered the visit. This will helps to find effective ads, helps optimize the ad costs, and increase the advertising effectiveness. | 3rd party | Marketing | T+3 months | Yes |
| _fbc | Facebook pixel | Browsing device information | Stores the last visit. | 3rd party | Marketing | T+90 days | Yes |
| wd | Facebook pixel | Screen resolution | Reads the screen resolution. | 3rd party | Marketing | T+7 days | Yes |
| sb | Facebook pixel | Browsing device information | Stores the browser data. | 3rd party | Marketing | T+2 years | Yes |
| fr | Facebook pixel | Social media account details | Provides ad display or retargeting. | 3rd party | Marketing | T+90 days | Yes |
| _fbp | Facebook pixel | Domain ID, random browser ID | Stores and tracks website visits. | 3rd party | Marketing | T+90 days | Yes |
4. Maximum security
It is important to stress that the cookies we use do not register any visitor ID or password and therefore their confidentiality is not infringed. The same statement also applies to our electronic banking services both in terms of the default setting of cookies and the use of cookies requiring consent.
5. Checking “cookie preferences”, disabling “cookies”
Modern browsers allow you to change the “cookie” settings. Some browsers allow “cookies” by default although you can change this setting at any time to prevent automatic acceptance. If you change the setting the browser will ask you every time to decide what to do with the “cookies”.
Please note that “cookies” are intended to improve the functionality of our website and to support its processes. If you disable “cookies" you may not be able to use all our website’s functions and the site may not work in your browser as intended.
You can also delete cookies at any time by deleting the browser history.
Follow the following links for detailed information about how to set “cookie” preferences in various browsers: