General

This document describes the use of cookies on the websites vialet.eu, vialet.pl, ib.vialet.eu and hub.vialet.eu indicating the purpose of the use of cookies, as well as users' rights during the use of cookies. Cookies help to provide, improve and protect the financial services provided by UAB “Via Payments” (VIALET), providing more convenient offers in response to client's needs and more convenient and safer use.

 

What are cookies?

A cookie is a small text file stored on a computer or other device when you visit a website. The text file contains information that is used to improve the experience of a website for visitors to specific web sites.

What cookies do vialet.eu, vialet.pl, ib.vialet.eu and hub.vialet.eu use and what is the purpose?

VIALET uses following types of cookies:

●      Session cookies - temporary cookies deleted when you close your browser. 

●      Persistent cookies - persistent cookies remain on your device until you erase them or they expire.

●      First-party cookies - cookies stored directly by our website. It allows us to collect analytics data, remember language settings, and perform other useful functions that help provide a good user experience.

●      Third-party cookies - cookies provided by third parties, such as Google, to track website activity such as session duration, pages per session, bounce rate etc. of individuals using the webpage, along with the information on the source of the traffic.

You can see each cookie we use and our reasons for using them below.

We use four groups of cookies on VIALET websites (the “Websites”): vialet.eu, vialet.pl, ib.vialet.eu and hub.vialet.eu:

 

1.     Necessary cookies:

These cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personal data.

1.1. Cookie XSRF-TOKEN: First party cookies.  Duration 2 hours. This cookie is used for security purposes.

1.2. Cookie JSESSIONID: First party cookies. Duration - session. This cookie is generated by servlet containers like Tomcat and used for session management for the HTTP protocol.

1.3. Cookie SRVSEC: First party cookies.  Duration - session. It provides the value of the cookie inserted by proxy. When the client comes back, then proxy knows directly which server to choose for this client.

1.4. Cookie Default-login-type: First party cookies. Duration - 1 year. On the login page when you select the tab for security means it remembers what you have selected. For example, if you choose to login with DIGIPASS and close the tab, the next time a page is opened DIGIPASS will be selected.

 

2.    Preference/functional cookies:

These cookies are used to recognize users, and may be used to remember user settings and preferences (such as language or region).

2.1. Cookie intercom-session-mct8pkrx: Third party. Duration - 7 days (from each log in). Allows users to access their conversations and have data communicated on logged out pages for 1 week.

2.2. Cookie intercom-id-mct8pkrx: Third party. Duration - 9 Months. Allows visitors to see any conversations they've had on Intercom websites.

2.3. Cookie G_ENABLED_IDPS: Third party. Duraton - persistent. Enables Google sign in with Google account.

2.4. Cookie LS_CSRF_TOKEN: Third party. Duration - session. This cookie (Zoho) is used for security purposes in order to avoid Cross-Site Request Forgery, (CSRF) for the AJAX calls made by the visitor.

2.5. Cookie vialeteu-_zldp: Third party. Duration - 2 years. This cookie identifies the unique visitors for the website.

2.6. Cookie vialeteu-_zldt: Third party. Duration - 1 day. This cookie identifies unique visits for a visitor in the website.

 

3.    Analytics/performance cookies:

These cookies help us recognize and count the number of visitors to the Websites, understand how visitors interact with the Websites, by collecting and reporting information anonymously. These cookies assist in improving the functionality and usability of the Websites.

3.1. Cookie _hjSessionUser_1488518: Third party. Duration - 1 year. Used to store your Hotjar User ID, unique to this site on this browser.

3.2. Cookie _ga: Third party. Duration - 2 years. Google Analytics: Registers a unique ID that is used to generate statistical data on how the visitor uses the website.

3.3. Cookie _gid: Third party. Duration - session. Google Analytics: Registers a unique ID that is used to generate statistical data on how the visitor uses the website.

3.4. Cookie _hjAbsoluteSessionInProgress: Third party. Duration - 30 minutes. Used to detect the first page view session of a user.

3.5. Cookie _hjSessionUser_2249737: Third party. Duration - 1 year. Used to store your Hotjar User ID, unique to this site on this browser.

 

4.    Targeting/Marketing cookies:

These cookies are used to track visitors across websites, to record a user’s visit to a website, pages visited and links follows. These are usually placed by advertising networks with the intention to display ads that are relevant to individual users, by collecting information about your browsing history.

4.1. Cookie __smVID: Third party. Duration - 29 days. Necessary for the sign-up function on the website. This function is provided by Sumo.com.

4.2. Cookie __smToken: Third party. Duration - 1 year. The __smToken is set once you login to Sumo and is checked to verify whether you are logged into Sumo or not.

4.3. Cookie _fbp: Third party. Duration - 3 months. This cookie is set by Facebook as part of their embedded services on our websites (likes, sharing etc.).

4.4. Cookie _gcl_au: Third party. Duration - 3 months. Used as a conversion linker tag in web and AMP containers that can be configured to link across domains for cases where you have the landing pages and conversion pages on multiple domains for Google Adsense.

4.5. Cookie AF_SYNC: Third party. Duration - 7 days. This cookie collects information about your actions on websites that have embedded a Vimeo video.

4.6. Cookie afUserId: Third party. Duration - 2 years. This cookie collects information about your actions on websites that have embedded a Vimeo video.

 

How can a user choose and change cookie usage?

If you do not want cookies on your devices being used, you can change your browser's security settings. Please note that changes to security settings must be performed by each browser individually and the setting methods used may vary. However, remember that without the approval of the session cookies with the help either of the websites vialet.eu, vialet.pl, ib.vialet.eu and hub.vialet.eu, you will not be able to fully explore the financial services provided by VIALET. To find out how to reject and delete cookies, please visit http://www.allaboutcookies.org/