White-Label Payment Gateway: How Does It Work?
Explore how a white-label payment gateway can help your business simplify payment processing with secure, branded solutions tailored to your needs.
This cookie policy applies to webpage https://ecomcharge.com
In this Cookie Policy (hereinafter, the Policy), we inform you about the technologies used on this website that help ensure the proper functioning of the website or monitor and analyse the behaviour of visitors of the website during their browsing sessions.
A cookie is a small text file that a website sends to your web browser when you visit it and stores it on the device that you are using. For this reason, the site may “remember” your actions and options (such as registration name, language, font size, and other display options) for a certain period of time so that you do not have to re-enter them each time you visit the site.
The websites use own/first party and/or third party cookies. According to the function they perform, the cookies classify to:
Cookies are divided into session and persistent cookies according to their validity period.
In terms of the location of their creation, there are two types of cookies:
Trackers and digital fingerprinting are more sophisticated technologies that work without cookies (files stored on the user’s device). For example, when a webpage uses tracking pixels / tags, a 1-pixel “image” is loaded each time a user accesses a particular webpage element, so that the server learns that a particular user with a specific IP address was in that webpage element, and that information is stored on the server. If the user does not consent to the collection of personal data, such elements of the website are disabled immediately. Digital IDs are highly accurate, generated by a user’s smart device, and unique IDs allow the same user to be identified at any time later.
Web beacons, uXDT, or Ultrasonic tracking technology work in such a way that when a website is visited, the computer generates an ultrasonic signal that is inaudible to humans but received by other smart devices running a certain app at the same time. The use of this technology requires a data protection impact assessment.
We use the following cookies on the website:
We use cookies so that:
We do not use cookies to identify you. The cookies on our website are not used for any purpose other than those described here.
We use the following cookies on the website:
Cookie Name | Cookie Category | Description | Validity period |
---|---|---|---|
yabs-sid | Mandatory | This cookie is used to maintain session state and ensure the proper functioning of the website. | 1 year |
__hssc | Marketing | This cookie is associated with the HubSpot service. It keeps track of sessions and is used to determine if the session number and timestamps should be incremented. | 1 day |
__hssrc | Marketing | This cookie is set by HubSpot and is used to determine if the user has restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session. | Session |
_gat_gtag_UA_38195514_1 | Functionality | This cookie is used to throttle the request rate and control data collection on high-traffic websites using Google Analytics. | 1 year 2 months |
_gat | Functionality | This is another variation of the Google Analytics cookie used to control request rates. | 1 year 2 months |
_ga_9WRXD0MJ5B | Functionality | This cookie is associated with Google Analytics and is used to distinguish users. | 1 year 2 months |
_ga_0BGCPSN9BL | Functionality | Another Google Analytics cookie that is used to distinguish users. | 1 year 2 months |
_ga | Functionality | This is the main Google Analytics cookie used to distinguish users. | 1 year 2 months |
viewed_cookie_policy | Mandatory | This cookie is used to remember if a user has accepted the cookie policy on the website. | 1 year |
_ga_FVNEDQV22Z | Functionality | A variation of the Google Analytics cookie used to distinguish users. | 1 year 2 months |
CookieLawInfoConsent | Mandatory | This cookie is set by the Cookie Law Info plugin and is used to store the user’s cookie consent status. | 1 year |
hubspotutk | Marketing | This cookie is used by HubSpot to track users and collect information for analytics. | 1 day |
cookielawinfo-checkbox-Mandatory | Mandatory | This cookie is set by the Cookie Law Info plugin and is used to store the user’s choice regarding Mandatory cookies. | 1 year |
__hstc | Marketing | The main cookie for tracking visitors. It contains the domain, utk (see below), initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). | 1 day |
_gid | Functionality | This cookie is associated with Google Analytics and is used to distinguish users. | 1 year |
cookielawinfo-checkbox-non-Mandatory | Mandatory | This cookie is set by the Cookie Law Info plugin and is used to store the user’s choice regarding non-Mandatory cookies. | 1 year |
_session_id | Mandatory | This cookie is used to identify a user’s session on the website. | 1 year |
We regularly use Google Analytics software to optimize marketing messages from Google LLC. It allows tracking visitors online behaviour: the time spent on the website, geographic location and usage specifics of the website. This information is collected through tracking pixels and/or cookies. The information obtained through tracking pixels and/or cookies is anonymous and is not bundled with personal data. Google processes personal information on its servers in various countries around the world. Personal information can be processed on a server that is not in the country where the user resides. We do not share this information with any other third parties that would be able to access it freely. If you do not agree to this analysis, you may change your cookie settings from the homepage or by clicking >here.
This website has an interface with third-party communication channels “LinkedIn” and “Facebook”, where we place information about the Company’s activities and act as separate data controllers. The cookies used by this channel allow us to obtain aggregated statistics and insights into how visitors interact with our posts, ads, this website, videos, and other content on these social media.
You can learn more about the third-party monitoring technologies used on our website here:
Cookie identifier | Description | The moment of creation | Expiry date |
---|---|---|---|
„LinkedIn“ visitor monitoring technologies used | „LinkedIn“ visitor monitoring technologies are used to identify the visitor, ensure the safety of the visitor’s account, monitor his behavior and provide adapted content, including advertisements. | During the visit | More information about LinkedIn cookies: https://www.linkedin.com/legal/cookie-policy |
User monitoring technologies used by Facebook | Facebook visitor and Messenger user monitoring technologies are used to identify the visitor, monitor their behavior and improve their content. | During the visit | More information about Facebook and Facebook Messenger cookies: https://www.facebook.com/policies/cookies. |
In order for the website to function properly, you do not have to accept all the cookies used here but doing so will make browsing easier for you. You can block all but the Mandatory cookies, however, some features of this website may not work as intended and you may need to reset some options each time you visit our website.
Most browsers allow you:
You can opt out of using cookies by changing your cookie settings located in the website footer or through the pop-up window that appears when visiting the website. Click on the Cookie Settings link in the footer or pop-up window and disable the cookies you prefer, except for essential ones.
Any questions, claims, or information requests regarding personal data protection should be directed to the eComCharge UAB Data Protection Officer – UAB ‘Privacy Partners,’ phone: +370 698 25292, email: gdpr@privacypartners.lt. Please note that a Data Subject Access Request or any other requests related to specific personal data can be executed only after the identification and authentication of the requester.