Cookies and Similar Technologies
Last update: December, 2023. Previous version.
Cookies are a small piece of data sent from a website and stored on the user’s computer by the user’s web browser while the user is browsing. They help website providers with things like understanding how people use a website or a platform, remembering a user’s login details, and storing website/platform preferences. This page explains how we use cookies to help us ensure that our services function properly, prevent fraud, and analyze and improve the services in accordance with our Privacy Notice.
1. How We Use Cookies
Cookies play an important role in helping us provide personal, effective and safe services. We use cookies on our website and Merchant Dashboard. We change the cookies periodically as we improve or add to our services, but we generally use cookies for the following purposes:
- To operate our services. Some cookies are essential to the operation of our website and Merchant Dashboard. We use those cookies in a number of different ways, including:
- Functionality. We use functional cookies, for example, to remember your language preferences to save you the trouble of having to change these every time you enter our website or Merchant Dashboard. Without these cookies, our website or Merchant Dashboard would not work properly and you would not be able to use certain important features.
- Fraud prevention and detection. Cookies and similar technologies that we deploy through websites and the Merchant Dashboard 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.
- To analyze and improve our services. We use cookies to help us understand how visitors arrived at our website or Merchant Dashboard, how and how long they use it and how we can improve their experience. This type of so-called “analytics” cookies can provide us with anonymous information to help us understand which parts of our website or Merchant Dashboard interest our visitors and if they experience any errors. We use these cookies to test different designs and features for our sites and we also use them to help us monitor how our visitors reach our sites.
2. How We Use Other Technologies
Third Party Analytics. We use Google Analytics. We have set our Google Analytics to protect your privacy to the maximum extent. For example, we have concluded a data processing agreement with Google to protect your data. We have also made sure that the last octet of your IP-address is invisible and have turned off the setting which allows sharing data with Google. We are also not using any other Google Analytics related cookie services which are offered by Google.
3. How To Manage Cookies
Your web browser may allow you to change your cookie preferences, including to delete and disable dLocal cookies. Please consult the help section of your web browser or follow the links below to understand your options, but please note that if you choose to disable the cookies, some features of our website or services may not operate as intended.
- Chrome: https://support.google.com/chrome/answer/95647?hl=en
- Explorer: https://support.microsoft.com/en-us/windows/delete-and-manage-cookies…
- Safari: https://support.apple.com/kb/PH21411
- Firefox: https://support.mozilla.org/en-US/kb/cookies-information-websites-store…
- Opera: http://www.opera.com/help/tutorials/security/cookies/
- Edge: https://support.microsoft.com/en-us/windows/microsoft-edge-browsing-data-and-privacy…
4. Cookie Table
Cookies that we commonly use are listed below. This list is not exhaustive, but describes the main reasons we typically set cookies.
Necessary
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
COOKIE NAME | PURPOSE | TYPE | INFORMATION | LOCATION |
GCLB | CDN Load Balancer settings. | Session | https://cloud.google.com/load-balancing/docs/choosing-load-balancer?hl=es-419#:~:text=Thus%2C%20regional%20load%20balancers%20guarantee,clients%20and%20the%20load%20balancer. | Website |
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
COOKIE NAME | PURPOSE | INFO | LOCATION |
_ga | to store and count pageviews. | https://cookiedatabase.org/cookie/google-analytics/_ga/ | Website |
_ga_* | to store and count pageviews. | https://cookiedatabase.org/cookie/google-analytics/_ga_/ | Website |
_gid | Use of Google Analytics linked to Hubspot. To store and count pageviews. | https://cookiedatabase.org/cookie/google-analytics/_gid/ & https://f.hubspotusercontent10.net/hubfs/4300763/20210831_CookieManagementPolicy_AppendixTableEN.pdf | Website |
AnalyticsSyncHistory | to store and track visits across websites. | https://cookiedatabase.org/cookie/linkedin/analyticssynchistory/ | Website |
_gcl_au | to store and track conversions. | https://cookiedatabase.org/cookie/google-adsense/_gcl_au/. &. https://support.google.com/tagmanager/thread/6211471?hl=en | Website |
li_sugr | to store and track a visitor's identity. | https://cookiedatabase.org/cookie/linkedin/li_sugr/ & https://www.linkedin.com/legal/l/cookie-table | Website |
_hjSessionUser_* | _hjSessionUser_* to store a unique user ID. | Website | |
gpv_pn | Used to retain and retrieve the previous page visited in Adobe Analytics | https://es.linkedin.com/legal/l/cookie-table? | Website |
s_tslv | Used to retain and retrieve the time since the last visit in Adobe Analytics | https://es.linkedin.com/legal/l/cookie-table? | Website |
s_ppv | Used by Adobe Analytics to retain and retrieve the percentage of the page that was last viewed | https://es.linkedin.com/legal/l/cookie-table? | Website |
s_tp | to track the percentage of the page last viewed | https://es.linkedin.com/legal/l/cookie-table? | Website |
s_plt | to track how long it took to load the previous page | https://es.linkedin.com/legal/l/cookie-table? | Website |
AMCVS_*AdobeOrg | to store and track interaction. | https://cookiedatabase.org/cookie/adobeexperiencecloud/amcvs_adobeorg/ | Website |
AMCV_*AdobeOrg | to store last visit. | https://cookiedatabase.org/cookie/adobeexperiencecloud/amcv_adobeorg/ | Website |
s_pltp | to provide the page name (URL) value for Adobe Analytics to use | https://es.linkedin.com/legal/l/cookie-table? | Website |
s_ips | to track the percentage of the page last viewed | https://es.linkedin.com/legal/l/cookie-table? | Website |
_hjSessionUser_{site_id} | Set when a user first lands on a page.Persists the Hotjar User ID which is unique to that site. Hotjar does not track users across different sites.Ensures data from subsequent visits to the same site are attributed to the same user ID.365 days duration.JSON data type. | Merchant Dashboard | |
_hjSessionUser_{site_id} | 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. 365 days duration. UUID data type. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjFirstSeen | Identifies a new user’s first session. | Merchant Dashboard | |
_hjHasCachedUserAttributes | Enables us to know whether the data set in _hjUserAttributes Local Storage item is up to date or not. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjUserAttributesHash | Enables us to know when any User Attribute has changed and needs to be updated. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjUserAttributes | Stores User Attributes sent through the Hotjar Identify API. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
hjViewportId | Stores user viewport details such as size and dimensions. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
hjActiveViewportIds | Stores user active viewports IDs. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjSession_{site_id} | Holds current session data. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjSessionTooLarge | Causes Hotjar to stop collecting data if a session becomes too large. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjSessionResumed | Set when a session/recording is reconnected to Hotjar servers after a break in connection. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjCookieTest | Checks to see if the Hotjar Tracking Code can use cookies. If it can, a value of 1 is set. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjLocalStorageTest | Checks if the Hotjar Tracking Code can use Local Storage. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjSessionStorageTest | Checks if the Hotjar Tracking Code can use Session Storage. If it can, a value of 1 is set. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjIncludedInPageviewSample | Set to determine if a user is included in the data sampling defined by your site's pageview limit. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjIncludedInSessionSample_{site_id} | Set to determine if a user is included in the data sampling defined by your site's daily session limit. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjAbsoluteSessionInProgress | Used to detect the first pageview session of a user. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjTLDTest | We try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjRecordingEnabled | Set when a Recording starts. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjRecordingLastActivity | Updated when a user recording starts and when data is sent to the server (the user performs an action that Hotjar records). | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjClosedSurveyInvites | Set when a user interacts with a Link Survey invitation modal. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjDonePolls | Set when a user completes an on-site Survey. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjMinimizedPolls | Set when a user minimizes an on-site Survey. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
_hjShownFeedbackMessage | Set when a user minimizes or completes a Feedback widget. | https://help.hotjar.com/hc/en-us/articles/6952777582999 | Merchant Dashboard |
Advertisement
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
COOKIE NAME | PURPOSE | TYPE | INFO | LOCATION |
UserMatchHistory | to provide ad delivery or retargeting. | N/A | https://www.linkedin.com/legal/l/cookie-table | Website |
1P_JAR | to provide ad delivery or retargeting. | N/A | https://cookiedatabase.org/cookie/google-ads-optimization/1p-jar/ | Website |
NID | to provide ad delivery or retargeting, store user preferences. | N/A | https://cookiedatabase.org/cookie/google-ads-optimization/nid/ | Website |
IDE | to provide ad delivery or retargeting. | N/A | https://cookiedatabase.org/cookie/google-doubleclick/ide/. &. https://policies.google.com/technologies/cookies | Website |
DV | proporciona entrega o retargeting de anuncios. | N/A | https://cookiedatabase.org/cookie/google-ads-optimization/dv/ | Website |
_gcl_aw | Used through Google Ads to understand user interaction with the site and advertising | N/A | https://es.linkedin.com/legal/l/cookie-table? | Website |
VISITOR_INFO1_LIVE | to provide ad delivery or retargeting, store and track a visitor's identity, Store and track interaction. For example, the ‘VISITOR_INFO1_LIVE’ cookie may enable personalized recommendations on YouTube based on past views and searches. | N/A | https://cookiedatabase.org/cookiefunctions/track-a-visitors-identity/ | Website |
Functionality
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
COOKIE NAME | PURPOSE | INFO | LOCATION |
lang | Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings. | https://www.linkedin.com/legal/l/cookie-table | Website |
lidc | to provide load balancing functionality. | https://www.linkedin.com/legal/l/cookie-table | Website |
bcookie | to store browser details. | https://www.linkedin.com/legal/l/cookie-table | Website |
__hstc | to store time of visit. | https://knowledge.hubspot.com/reports/what-cookies-does-hubspot-set-in-a-visitor-s-browser | Website |
hubspotutk | to store and track a visitor's identity. | https://knowledge.hubspot.com/reports/what-cookies-does-hubspot-set-in-a-visitor-s-browser | Website |
__hs_cookie_cat_pref | to store cookie consent preferences. | https://knowledge.hubspot.com/reports/what-cookies-does-hubspot-set-in-a-visitor-s-browser | Website |
__hssc | This cookie keeps track of sessions. This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp. It expires in 30 minutes. | https://knowledge.hubspot.com/reports/what-cookies-does-hubspot-set-in-a-visitor-s-browser | Website |
__hssrc | to store a unique session ID. | https://knowledge.hubspot.com/reports/what-cookies-does-hubspot-set-in-a-visitor-s-browser | Website |
PHPSESSID | to provide functions across pages. | https://cookiedatabase.org/cookie/php/phpsessid/ | Website |
AEC | ensure that requests within a browsing session are made by the user, and not by other sites. | https://cookiedatabase.org/cookie/cloudflare/__cf_bm/ & https://developers.cloudflare.com/fundamentals/get-started/reference/cloudflare- | Website |
__cf_bm | ensure that requests within a browsing session are made by the user, and not by other sites. | https://cookiedatabase.org/cookie/cloudflare/__cf_bm/ & https://developers.cloudflare.com/fundamentals/get-started/reference/cloudflare- | Website |
_GRECAPTCHA | to provide spam protection. | https://cookiedatabase.org/cookie/google-recaptcha/_grecaptcha/. &. https://developers.google.com/recaptcha/docs/faq | Website |
test_cookie | Test cookie used by Google DoubleClick to check that cookies can be set. | https://docs.authsignal.com/integrations/supabase | Website |
supabase-auth-token | This guide shows how to integrate Authsignal with Next.js and Supabase in order to add an MFA step after sign-in. The user flow is as follows: 1. The user enters their email and password to sign in 2. If the user has set up MFA, they're prompted to complete an MFA challenge (via Authenticator App) in order to complete sign-in 3. If the user has not set up MFA, they're signed in immediately and will see a button to set up MFA The approach uses a temporary encrypted cookie to ensure that the Supabase auth cookies - access_token and refresh_token - are only set if the MFA challenge was successful. Session data is encrypted using @hapi/iron. | https://docs.authsignal.com/integrations/supabase | Website |
__stripe_mid | to provide fraud prevention. | https://cookiedatabase.org/cookie/stripe/__stripe_mid/ | Website |
CONSENT | to store cookie consent preferences. | https://cookiedatabase.org/cookie/google-ads-optimization/consent/ & https://policies.google.com/technologies/cookies?hl=es | Website |
SOCS | Same as CONSENT but 13 months instead of 2 years | https://policies.google.com/technologies/cookies?hl=es | Website |
s_cc | Used to determine if cookies are enabled for Adobe Analytics | https://es.linkedin.com/legal/l/cookie-table? | Website |
ar_debug | to store and track conversions | https://sproutsocial.com/es/cookie-notice/sproutsocial-website/ | Website |
YSC | to store and track interaction, ‘YSC’ is used by YouTube to remember user input and associate a user’s actions. This cookie lasts for as long as the user keeps their browser open. | https://cookiedatabase.org/cookie/youtube/ysc/ | Website |