Cookie Policy

Last updated: 15-Sep-2022

This cookie policy describes how HiGlobe (“HiGlobe”) uses “cookies” and other similar technologies, in connection with our Site and Services. Any capitalized term used and not otherwise defined below has the meaning assigned to it in the Privacy Policy.

1. WHAT IS A COOKIE?

Cookies are small text files that are stored in a computer’s browser directory. They help site providers with things like understanding how people use a site, remembering a User’s login details, and storing site preferences.

2. DOES HIGLOBE USE COOKIES?

Yes. We use cookies in accordance with our Privacy Policy to:

  • ensure that our Services function properly,
  • detect and prevent fraud,
  • understand how visitors use and engage with our Site, and
  • analyze and improve Services.

3. WHO SETS COOKIES WHEN I USE HIGLOBE'S SITE?

There are two main types of cookies that can be set:

  • First party cookies: these cookies are placed and read by HiGlobe directly when you use our Services,
  • Third party cookies: these cookies are not set by HiGlobe, but by other companies, like Google or Facebook, for site analytics purposes.

4. HOW HIGLOBE USE COOKIES

Cookies play an important role in helping us provide effective and safe Services. Below is a description of the commonly used cookie types and the purposes that apply to them.

Necessary Cookies

Some cookies are essential to the operation of our Site and Services and make it usable and secure by enabling basic functions like page navigation and access to secure areas of the Site. We use those cookies in a number of different ways, including:

  • Authentication. To remember your login state so you don’t have to log in as you navigate through our Site and dashboard.
  • Fraud Prevention and Detection. Cookies and similar technologies that we deploy through our Site help us learn things about computers and web browsers used to access the Services. This information helps us monitor for and detect potentially harmful or illegal use of our Services. For example, in order to process payments transactions for our Users, it is necessary for HiGlobe to collect information about the transaction and the Customer. To help secure these transactions and minimize fraud, we collect additional information through the use of cookies and other technologies in helping to identify bad actors and prevent them from making fraudulent transactions. Customers should check our Users’ sites for more information about the use of HiGlobe cookies for fraud detection.
  • Security. To protect user data from unauthorized access.
  • If required, or where we believe it is required by applicable law or legal process; or
  • Functionality. To keep our Site and Services working correctly, like showing you the right information for your selected location.

Preference Cookies

Preference cookies are used by HiGlobe to remember your preferences and to recognize you when you return to our Services.

Marketing Cookies

Marketing cookies are used by third party services to send content-appropriate advertising on their platforms.

Analytics Cookies

Analytics cookies help us understand how visitors interact with our Services. We use those cookies in a number of different ways, including:

  • Site Features and Services. To remember how you prefer to use our Services so that you don’t have to reconfigure your settings each time you log into your account.
  • To Analyze and Improve Our Services. To make our Site and Services work better for You. Cookies help us understand how people reach our Site and our Users’ sites. They give us insights into improvements or enhancements we need to make to our Site and Services.
  • Pixel tags (also known as web beacons and clear GIFs). May be used in connection with some Services to, among other things, track the actions of Users (such as email recipients), measure the success of our marketing campaigns and compile statistics about usage of the Services and response rates.
  • Third Party Analytics. Through Google Analytics in order to collect and analyze information about the use of the Services and report on activities and trends. This service may also collect information regarding the use of other sites, apps and online resources. You can learn about Google’s practices on the Google website. See further details below on how to manage these cookies.

5. CAN I OPT-OUT?

Yes, with the exception of those cookies that are necessary to provide you with our Services. Your web browser may allow you to manage your cookie preferences, including to delete and disable HiGlobe cookies. You can take a look at the help section of your web browser or follow the links below to understand your options. If you choose to disable cookies, some features of our Site or Services may not operate as intended.

Necessary Cookies

‍

Name
Company
Purpose
Duration
Int/Ext
Purpose
_ga
Google
Analytics
Session
Ext
Used to distinguish unique users by assigning a randomly generated number as a client identifier. In link with Google Universal Analytics
_fbp
Facebook Pixel
Analytics
03 months
Ext
The Facebook Pixel tracks URLs and domains visited, as well as the devices used by site visitors. Site visitor actions detected by the Facebook Pixel are tabulated in the Facebook Ads Manager and Analytics dashboard.
_hjSessionUser_*
Hotjar
Analytics
1 year
Ext
  • Set when a user first lands on a page.
  • Persists the Hotjar User ID which is unique to that site.
  • Ensures data from subsequent visits to the same site are attributed to the same user ID.
_hjid
Hotjar
Analytics
1 year
Ext
  • Set when a user first lands on a page.
  • Persists the Hotjar User ID which is unique to that site.
  • Ensures data from subsequent visits to the same site are attributed to the same user ID.
_hjUserAttributesHash
Hotjar
Analytics
Session
Ext
  • User Attributes sent through the Hotjar Identify API are cached for the duration of the session.
  • Enables Hotjar to know when an attribute has changed and needs to be updated.
_hjViewportId
Hotjar
Analytics
Session
Ext
  • Stores user viewport details such assize and dimensions.
_hjCachedUserAttributes
Hotjar
Analytics
Session
Ext
  • Stores User Attributes sent through the Hotjar Identify API, whenever the user is not in the sample.
  • Collected attributes will only be saved to Hotjar servers if the user interacts with a Hotjar Feedback tool.
  • Cookie used regardless of whether a Feedback tool is present.
_hjFirstSeen
Hotjar
Analytics
Session
Ext
  • Identifies a new user’s first session.
  • Used by Recording filters to identify new user sessions.
_hjSession_*
Hotjar
Analytics
30 mins
Ext
  • Holds current session data.
  • Ensures subsequent requests in the session window are attributed to the same session.
_hjSessionTooLarge
Hotjar
Analytics
30 mins
Ext
  • Causes Hotjar to stop collecting data if a session becomes too large.
  • Determined automatically by a signal from the WebSocket server if the session size exceeds the limit.
_hjSessionResumed
Hotjar
Analytics
Session
Ext
  • Set when a session/recording is reconnected to Hotjar servers after a break in connection.
_hjAbsoluteSessionInProgress
Hotjar
Analytics
30 mins
Ext
  • Used to detect the first pageview session of a user.
_hjTLDTest
Hotjar
Analytics
Session
Ext
  • Hotjar tries to store the _hjTLDTest cookie for different URL substring alternatives until it fails.
  • After this check, the cookie is removed.
_hjLocalStorageTest
Hotjar
Analytics
100ms
Ext
  • Checks if the Hotjar Tracking Code canuse local storage.
    If it can, a value of 1 is set.
  • Data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created.
_hjIncludedInSessionSample
Hotjar
Analytics
30 mins
Ext
  • Set to determine if a user is included
    in the data sampling defined by your
    site's daily session limit.
_hjRecordingLastActivity
Hotjar
Analytics
Session
Ext
  • Updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records).
_hjRecordingEnabled
Hotjar
Analytics
Session
Ext
  • Read when the Recording module is initialized to see if the user is already in a recording in a particular session.
_hjClosedSurveyInvites
Hotjar
Analytics
365 days
Ext
  • Ensures the same invite does not reappear if it has already been shown.
_hjMinimizedPolls
Hotjar
Analytics
365 days
Ext
  • Ensures that the Survey stays minimized when the user navigates through your site.
_hjShownFeedbackMessage
Hotjar
Analytics
365 days
Ext
  • Ensures the Feedback widget will load
    as minimized if the user navigates to
    another page where it is set to show.
_hjDonePolls
Hotjar
Analytics
365 days
Ext
  • Set when a user completes an on-site Survey.
  • Ensures the same Survey does not reappear if it has already been filled in.
_hjSessionRejected
Hotjar
Analytics
Session
Ext
  • Used to ensure performance of Hotjar
_hjIncludedInPageviewSample
Hotjar
Analytics
30 mins
Ext
Hotjar Cookie that is used to inform whether a visitor of the Site is included in the data sampling defined by the Site’s daily session limit
amp_*
Amplitude
Analytics
400 days
Ext
Used to track:
‍
  • A randomly generated device id
  • The current session id
  • The current user id if a user id is set
  • The last event time
  • A few sequence ids in order to sequence events and identifies correctly
_fbp
Facebook
Marketing
3 Months
Ext
  • Used by facebook to store and track visits across websites
usida
Facebook
Marketing
Session
Ext
  • Collects a combination of the user’s browser and unique identifier, used to tailor advertising to users
datr
Facebook
Marketing
2 years
Ext
  • Used by facebook for fraud prevention
wd
Facebook
Marketing
7 days
Ext
  • Stores the user screen resolution
gatsby-gdpr-hotjar
Higlobe
Necessary
400 days
Int
  • Used to track the cookie preference for hotjar
gatsby-i18next-language
Higlobe
Necessary
localstorage
Int
  • Used to track language preferences
amplitude_unsent
Amplitude
Analytics
localstorage
Ext
  • Used to track unset amplitude events
mprtcl-prodv4-*
mParticle
Analytics
localstorage
Ext
  • Used by mParticle to identify tracker
mprtcl-v4-*
mParticle
Necessary
localstorage
Ext
  • Used to track identity and cookie preferences
amplitude_unsent_identify-*
Amplitude
Analytics
localstorage
Ext
  • Used to by Amplitude to store unsent tracking events
__zlcmid
Zendesk
Necessary
365 days
Ext
  • stores visitor's ID for widget's authentication
language
Higlobe
Necessary
localstorage
Int
  • Used to store language preferences
email
Higlobe
Necessary
localstorage
Int
  • Used to store email for onboarding
CognitoIdentityServic eProvider.*.clockDrift
Amazon Cognito
Necessary
localstorage
Ext
  • Used for user authentication, authorization & session mgmt
CognitoIdentityServic
eProvider.*.refreshTo
ken
Amazon Cognito
Necessary
localstorage
Ext
  • Used for user authentication, authorization & session mgmt
CognitoIdentityServic
eProvider.*.accessTok
en
Amazon Cognito
Necessary
localstorage
Ext
  • Used for user authentication, authorization & session mgmt
CognitoIdentityServic
eProvider.*.userData
Amazon Cognito
Necessary
localstorage
Ext
  • Used for user authentication, authorization & session mgmt
CognitoIdentityServic
eProvider.*.LastAuth
User
Amazon Cognito
Necessary
localstorage
Ext
  • Used for user authentication, authorization & session mgmt
CognitoIdentityServic
eProvider.*.idToken
Amazon Cognito
Necessary
localstorage
Ext
  • Used for user authentication, authorization & session mgmt
_dd_s
Datadog
Analytics
20 minutes
Ext
  • This is an analytical cookie from Datadog that is used to store data related to the performance of the website
consentAnalytics
Higlobe
Analytics
400 days
Int
  • Used to track the consent state of analytics of application

Lowest cost guaranteed

Start Now