Back to Policies

Cookie Policy

At Nabu Pro, we are committed to protecting your privacy and ensuring transparency about how we use cookies and similar technologies on our website. This Cookie Policy explains how we use cookies, the types of cookies we use, and your choices regarding cookies. By using our website, you consent to the use of cookies in accordance with this policy. For more information about how we handle your data, please refer to our Privacy Policy.

How do we use cookies?

Essential cookies

Cookie Description Duration
nabu_pro_website_cookie_consent Used to store the user's cookie consent preferences. 1 year 1 month 1 day
nabu_pro_website_session Used to identify the user's browsing session. 2 days
XSRF-TOKEN Used to secure both the user and our website against cross-site request forgery attacks. 2 days
locale Records the language of the user. 1 year 1 month 1 day
industry Records the industry profile selected to adapt the content on non industry-specific pages. 1 month 2 days

Marketing cookies

Cookie Description Duration
bcookie [LinkedIn] Browser Identifier cookie to uniquely identify devices accessing LinkedIn to detect abuse on the platform 1 year 1 month 1 day
lidc [LinkedIn] To facilitate data center selection 1 day
li_gc [LinkedIn] Used to store consent of guests regarding the use of cookies for non-essential purposes 6 months 1 week 5 days
li_mc [LinkedIn] Used as a temporary cache to avoid database lookups for a member's consent for use of non-essential cookies and used for having consent information on the client side to enforce consent on the client side 6 months 1 week 5 days
li_fat_id [LinkedIn] Member indirect identifier for Members for conversion tracking, retargeting, analytics 1 month 2 days
li_giant [LinkedIn] Indirect indentifier for groups of LinkedIn Members used for conversion tracking 1 week
li_sugr [LinkedIn] Used to make a probabilistic match of a user's identity 3 months 6 days
oribi_cookie_test [LinkedIn] To determine if tracking can be enabled on current domain 30 minutes
oribili_user_guid Used to count unique visitors to a website 1 year 1 month 1 day
ln_or [LinkedIn] Used to determine if Oribi analytics can be carried out on a specific domain 1 day
ar_debug [LinkedIn] Supports Google attribution reporting API integration to mitigate signal loss 30 minutes

Analytics cookies

Cookie Description Duration
hjSessionUser_5187404 [Hotjar] Persists the Hotjar User ID which is unique to that site. Hotjar does not track users across different sites. 6 hours 5 minutes
hjSession_5187404 [Hotjar] Enables us to know whether the data set in _hjUserAttributes Local Storage item is up to date or not. 30 minutes
hjViewportId [Hotjar] Stores user viewport details such as size and dimensions 30 minutes
hjActiveViewportIds [Hotjar] Stores user active viewports IDs. 30 minutes
_hjCookieTest [Hotjar] Checks to see if the Hotjar Tracking Code can use cookies. If it can, a value of 1 is set. 1 minute
_hjLocalStorageTest [Hotjar] Checks if the Hotjar Tracking Code can use Local Storage. If it can, a value of 1 is set. 1 minute
_hjSessionStorageTest [Hotjar] Checks if the Hotjar Tracking Code can use Session Storage. If it can, a value of 1 is set 1 minute
_hjTLDTest [Hotjar] We try to store the _hjTLDTest cookie for different URL substring alternatives until it fails 1 minute
__hstc [Hubspot] The main cookie for tracking visitors. It contains the domain, hubspotutk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). 6 months 1 week 5 days
hubspotutk [Hubspot] This cookie keeps track of a visitor’s identity. It is passed to HubSpot on form submission and used when deduplicating contacts. It contains an opaque GUID to represent the current visitor. 6 months 1 week 5 days
__hssc [Hubspot] 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. 30 minutes
__hssrc [Hubspot] Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session. It contains the value “1” when present. 30 minutes

Change my cookie preferences

By clicking the following button, your cookie preferences will be reset and you will be asked for your consent again.

Table of Contents