Cookie Policy

Cookies are small bits of text sent by our servers to your computer or device when you access our services. They are stored in your browser and later sent back to our servers so that we can provide contextual content. Without cookies, using the web would be a much more frustrating experience. We use them to support your activities on our website. For example, your session (so you don't have to login again) or your shopping cart.
Cookies are also used to help us understand your preferences based on previous or current activity on our website (the pages you have visited), your language and country, which enables us to provide you with improved services. We also use cookies to help us compile aggregate data about site traffic and site interaction so that we can offer better site experiences and tools in the future.

Here is an overview of the cookies that may be stored on your device when you visit our website:

Category of Cookie Purpose Examples

Session & Security
(essential)

Authenticate users, protect user data and allow the website to deliver the services users expects, such as maintaining the content of their cart, or allowing file uploads.

The website will not work properly if you reject or discard those cookies.

session_id (Odoo)

Preferences
(essential)

Remember information about the preferred look or behavior of the website, such as your preferred language or region.

Your experience may be degraded if you discard those cookies, but the website will still work.

frontend_lang (Odoo)
Interaction History
(optional)

Used to collect information about your interactions with the website, the pages you've seen, and any specific marketing campaign that brought you to the website.

We may not be able to provide the best service to you if you reject those cookies, but the website will work.

im_livechat_previous_operator_pid (Odoo)
utm_campaign (Odoo)
utm_source (Odoo)
utm_medium (Odoo)

Advertising & Marketing
(optional)

Used to make advertising more engaging to users and more valuable to publishers and advertisers, such as providing more relevant ads when you visit other websites that display ads or to improve reporting on ad campaign performance.

Note that some third-party services may install additional cookies on your browser in order to identify you.

You may opt-out of a third-party's use of cookies by visiting the Network Advertising Initiative opt-out page. The website will still work if you reject or discard those cookies.

__gads (Google)
__gac (Google)

Analytics
(optional)

Understand how visitors engage with our website, via Google Analytics. Learn more about Analytics cookies and privacy information.

The website will still work if you reject or discard those cookies.

_ga (Google)
_gat (Google)
_gid (Google)
_gac_* (Google)

You can choose to have your computer warn you each time a cookie is being sent, or you can choose to turn off all cookies. Each browser is a little different, so look at your browser's Help menu to learn the correct way to modify your cookies.


What types of cookies used by GlobalPayGate?

Below is a list of the types of cookies and similar technologies used by the GlobalPayGate across our websites, mobile sites and mobile applications. Not all of these cookies will appear on every site or application, and this list is not exhaustive.

Cookie
Name
SourceCookie DescriptionCookie
Purpose
Duration
JSESSIONIDInternalJSESSIONID is a cookie in J2EE web application which is used in session tracking. Since HTTP is a stateless protocol, we need to use any session to remember state. JSESSIONID cookie is created by web container and send along with response to client.SessionSession
pathInternalIndicates a URL path that must exist in the requested resource before sending the Cookie header. The %x2F ("/") character is interpreted as a directory separator and sub directories will be matched as well (e.g. path=/docs, "/docs", "/docs/Web/", or "/docs/Web/HTTP" will all be matched).Directory Location--
SecureInternalA secure cookie will only be sent to the server when a request is made using SSL and the HTTPS protocol. However, confidential or sensitive information should never be stored or transmitted in HTTP Cookies as the entire mechanism is inherently insecure and this doesn't mean that any information is encrypted.Data Security--
HttpOnlyInternalHTTP-only cookies aren't accessible via JavaScript through the Document.cookie property, the XMLHttpRequest and Request APIs to mitigate attacks against cross-site scripting (XSS).Security--
pzConsentInternalThis cookie is used to remember your response to our consent box.Essential Cookies30 Days
__cfduidCloudflareThis cookie is used to override any security restrictions based on the IP address the visitor is coming from and also this cookie is used to identify individual clients behind a shared I.P address and apply security settings on a per-client basis. This cookie does not store personally identifying information.Analytics1 Year
driftt_aidDriftThese cookies are used to help remember you when you use the Drift messaging system on site.Functional Cookies2 Years
driftt_sidDriftThese cookies are used to help remember you when you use the Drift messaging system on site.Functional Cookies30 Minutes
driftt_wmdDriftThese cookies are used to help remember you when you use the Drift messaging system on site.Functional CookiesBrowser Session
NIDgoogle.comGoogle uses cookies NID to contribute to the personalization of the ads in Google properties, like Google search. For example, we use them to store your most recent searches, your previous interactions with an advertiser's ads or search results and your visits to an advertiser's website. In this way we can show you personalized ads on Google.Targeting Cookies45 Days
_gaInternalUsed to distinguish users.Analytics2 Years
_gid_UA-120911520-1InternalUsed to distinguish users.Analytics24 Hours
_gatInternalUsed to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>.Analytics1 Minute
__ascInternalUsed to distinguish users.Analytics1 Day
__aucInternalUsed to distinguish users.Analytics1 Year

We do not currently support Do Not Track signals, as there is no industry standard for compliance.