Cookie policy

This Cookie Policy is part of our Privacy Policy. For more information about us, and how we protect Personal Data, please see our Privacy Policy.

In order to provide you with a more personalized service, we need to remember and store information about how you use our websites. This is done by using small text files called cookies. Cookies contain small amounts of information and are downloaded to your computer or other device by a service for our websites.

Your web browser then sends these cookies back to our websites on each subsequent visit so that it can remember things such as your user preferences. You can find more detailed information about cookies and how they work at http://www.aboutcookies.org/.

Whenever you use our websites, information may be collected through the use of cookies and other technologies. By using our websites, you agree to our use of cookies as described in this Cookie Policy.

What cookies do we use and why?
Klaveness Digital AS uses different types of cookies. These cookies are set for every Visitor to any of our sites. The cookies are used to enable sharing of articles and analyze the usage of our sites. We do this to improve user experience for Visitors, and do not track individuals.

The cookies used fall into two categories:
Essential/necessary cookies: these cookies do not require consent
Consent banner cookies: these cookies are included in the consent banner under GDPR

Specific cookie names and descriptions are listed below.

Essential/necessary cookies

__hs_opt_out (Expires: 2 years)
This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again. This cookie is set when you give visitors the choice to opt out of cookies.

__hs_do_not_track (Expires: 2 years)
This cookie can be set to prevent the tracking code from sending any information to HubSpot. Setting this cookie is different from opting out of cookies, which still allows anonymized information to be sent to HubSpot.

__hs_testcookie (Expires: Session cookie)
This cookie is used to test whether the visitor has support for cookies enabled.

hs_ab_test (Expires: Session cookie)
This cookie is used to consistently serve visitors the same version of an A/B test page that they’ve seen before.

hs_lang_switcher_choice
This cookie is used to consistently redirect visitors to the language version of a page in the language they’ve selected on this top-level private domain in the past (if such a language version exists).

<id>_key
When visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login. The cookie name is unique for each password-protected page.

hs-messages-is-open (TTL 30 min)
This cookie is used on the visitor UI side so HubSpot can determine/save whether the chat widget is open for future visits. It resets after 30 minutes to re-close the widget after 30 minutes of inactivity

hs-messages-hide-welcome-message (TTL 1 day)
When you dismiss the welcome message in your messages tool, a cookie is set to prevent it from appearing again for one day.

__stid
This cookie is used to enable sharing of articles from our website. This also includes a script that makes it possible for Facebook to set a cookie. If you are logged in to Facebook, they will set a cookie on our site when you visit. This is to enable sharing of articles with Facebook.

__unam
This cookie is used to enable sharing of articles from our website.

Consent banner cookies

__hstc (Expires: 2 years)
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).

hubspotutk (Expires: 10 years)
This cookie is used for to keep track of a visitor's identity. This cookie is passed to HubSpot on form submission and used when de-duplicating contacts.

__hssc (Expires: 30 min)
This cookie keeps track of sessions. This is used to determine if we 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.

__hssrc (Expires: Session cookie)
Whenever HubSpot changes the session cookie, this cookie is also set. We set it to 1 and use it to determine if the visitor has restarted their browser. If this cookie does not exist when we manage cookies, we assume it is a new session.

messagesUtk
This cookie is used to recognize visitors who chat with you via the messages tool. If the visitor leaves your site before they're added as a contact, they will have this cookie associated with their browser. If you have a history of chatting with a visitor and they return to your site later in the same cookied browser, the messages tool will load your conversation history with that visitor.

_gat (Expires: 1 min)
This cookie is used to generate traffic statistics to understand users in order to improve the user experience

_ga (Expires: 2 years)
This cookie is used to generate traffic statistics to understand users in order to improve the user experience

_gid (Expires: 24 hours)
This cookie is used to generate traffic statistics to understand users in order to improve the user experience

AMP_TOKEN (Expires: 30 seconds to 1 year)
Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service.

_gac_<property-id> (Expires: 90 days)
Contains campaign related information for the user. If you have linked your Google Analytics and AdWords accounts, AdWords website conversion tags will read this cookie unless you opt-out.

__utma (Expires: 2 years)
Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics.

__utmt (Expires: 10 min)
Used to throttle request rate.

__utmb (Expires: 30 min)
Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.

__utmc (Expires: Session cookie)
Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit.

__utmz (Expires: 6 months)
Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.

__utmv (Expires : 2 years)
Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics.

How to control cookies?
By using this website you agree that we can place cookies on your computer or device as explained above. However, you can control and manage cookies in various ways. Please bear in mind that removing or blocking cookies can impact on your user experience and parts of our websites may no longer be fully accessible.

For more information on how to modify your browser settings to block or filter cookies, see http://www.aboutcookies.org/ or http://www.cookiecentral.com/faq/.

Social buttons
We use “social buttons” to enable our users to share content. These are buttons for third party social media sites, such as LinkedIn. When sharing content through the use of social buttons, a cookie from such third party social media site may be stored on your device.

We cannot control the cookies you receive by such third parties. Please review the respective terms of use and privacy policies of these third parties to understand exactly how they use your information and to find out how to opt-out, or delete, such information.

We may modify or amend this Cookie Policy from time to time at our discretion. When we make changes to this notice, we will amend the revision date at the top of this page, and such modified or amended Cookie Policy shall be effective as of that revision date. We encourage you to periodically review this Cookie Policy to be informed about how we are using cookies.

Please contact us if you would like more detailed information on the cookies we use at privacy@cargovalue.com.