Cookiepolicy
Version 1.0, 2025-04-07.
1. INTRODUCTION
This cookie policy (the ‘Cookie Policy’) describes how Centuri AB, reg. no. 556558-6210, with address Södra Agnegatan 29, 112 29, Stockholm (‘we’, ‘our’ and ‘us’), uses cookies and any other similar technologies that collect information about visits to and use of our website and related pages, (hereinafter collectively referred to as the ‘Website’).
We may update this Cookie Policy from time to time and the new version will be effective upon posting on our website. At the top of the page you can see the date of the latest version of the Cookie Policy.
If you want to know more about how we process cookies, you are always welcome to contact us, e.g. at the address above or via our e-mail address: info@centuri.se.
2. COOKIES
2.1 Our Website uses so-called cookies. Cookies are small text files that a website places or requests access to on the visitor's computer or mobile device. Cookies and other similar technologies enable websites to remember a visitor when he or she returns to the website from the same device used for a previous visit and can be used for various functions on websites, such as saving previous searches or customising the content of the website according to the visitor's previous use. The cookies and other similar technologies we use on the Website are described in section 3 below.
2.2 There are two types of cookies:
• Permanent cookies, which are stored on the visitor's computer for a fixed period of time and then disappear; and
• Session cookies, which are temporarily stored in the computer's memory during the visit to the website and disappear when the visitor closes the browser.
Cookies can be set by the Website (a so-called first-party cookie) or by someone other than the Website (a so-called third-party cookie). You can manage and switch off first-party and third-party cookies by changing the settings in your browser, see section 4 below.
If you choose not to allow cookies, it is possible that some features of the Website will not work as you expect. This may affect the Site's ability to tailor content to your preferences, which may result in a less personalised user experience. Furthermore, it may affect our ability to track and analyse user behaviour, which may limit our ability to improve the functionality and usability of the Website.
2.3 Cookies have different purposes and can be divided into the following categories according to their purpose:
• Strictly necessary cookies: This category of cookies is placed when you use our services and visit the Website. Functional, analytical and marketing cookies are placed only after you have given your consent to them. You can withdraw your consent at any time by changing your cookie settings. Strictly necessary cookies are placed in order for the Website to function in the way you expect. Without such cookies, we cannot provide the service you request, as they are essential to the functioning of the Website.
• Functionality and analytics cookies: This category of cookies helps us to understand how visitors use the Website and to ensure that it functions optimally. These cookies may collect information about how visitors use our Website.
2.4 Cookies may collect personal data, such as IP addresses. We process all personal data in accordance with our privacy policy.
3. OTHER SIMILAR TECHNOLOGIES
3.1 In addition to cookies, we also use ‘pixel tags’, ‘web beacons’, ‘JavaScript’ or similar technologies that enable us to, among other things, track your activity when you use the Site or receive emails, (collectively, ‘Similar Technologies’). Similar Technologies may also be used in connection with our online advertising or in our emails, either by us or by our suppliers, business partners or other third parties.
3.2 Similar Technologies are used to collect, typically, anonymous data to identify certain information, e.g. to compile reports of tracking information regarding the demographics, usage patterns and purchases of those using the Website, and also other information to improve the user experience and our services. We may disclose these reports to, for example, advertisers. The tracking information in these reports cannot be linked to the identity of individual users or other personal data. We may link tracking information to personal data voluntarily provided by users of the Website in order to analyse the information. When such linking occurs, the linked information is treated as personal data in accordance with our privacy policy.
3.3 We may use Similarity Techniques in our HTML-based emails to find out which emails recipients have opened. Similarity Techniques may also be used to identify why you are visiting the Site and how you got there, for example, if a contributing factor has been one of our adverts or emails
3.4 Similar Technologies may also be used by other companies to track visits to their websites in order to identify whether the visitor found their website via our Website or to confirm that you are an authorised recipient of their services or benefits.
4. COOKIES AND SIMILAR TECHNOLOGIES ON THE WEBSITE
|
Name |
Supplier |
Purpose |
Storage time |
|
__hs_opt_out |
Hubspot |
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. It contains the string "yes" or "no". |
It expires in 6 months. |
|
__hs_do_not_track |
Hubspot |
This cookie can be set to prevent the tracking code from sending any information to HubSpot. It contains the string "yes". |
It expires in 6 months.
|
|
__hs_initial_opt_in
|
Hubspot |
This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode. It contains the string "yes" or "no". |
It expires in seven days.
|
|
__hs_cookie_cat_pref
|
Hubspot |
This cookie is used to record the categories a visitor consented to. It contains data on the consented categories. |
It expires in 6 months.
|
|
__hs_gpc_banner_dismiss
|
Hubspot |
This cookie is used when the Global Privacy Control banner is dismissed. It contains the string "yes" or "no". |
It expires in 180 days.
|
|
__hs_notify_banner_dismiss
|
Hubspot |
This cookie is used when the website uses a Notify consent banner type. It contains a boolean value of True. |
It expires in 180 days.
|
|
hs_ab_test
|
Hubspot |
This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before. It contains the id of the A/B test page and the id of the variation that was chosen for the visitor. |
It expires at the end of the session.
|
|
<id>_key
|
Hubspot |
When visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login again. The cookie name is unique for each password-protected page. It contains an encrypted version of the password so future visits to the page will not require the password again. |
It expires in 14 days.
|
|
hs-messages-is-open
|
Hubspot |
This cookie is used to determine and save whether the chat widget is open for future visits. It is set in your visitor's browser when they start a new chat, and resets to re-close the widget after 30 minutes of inactivity. If your visitor manually closes the chat widget, it will prevent the widget from re-opening on subsequent page loads in that browser session for 30 minutes. It contains a boolean value of True if present. |
It expires in 30 minutes.
|
|
hs-messages-hide-welcome-message
|
Hubspot |
This cookie is used to prevent the chat widget welcome message from appearing again for one day after it is dismissed. It contains a boolean value of True or False. |
It expires in one day.
|
|
__hsmem
|
Hubspot |
This cookie is set when visitors log in to a HubSpot-hosted site. It contains encrypted data that identifies the membership user when they are currently logged in. |
It expires in seven days.
|
|
hs-membership-csrf
|
Hubspot |
This cookie is used to ensure that content membership logins cannot be forged. It contains a random string of letters and numbers used to verify that a membership login is authentic. |
It expires at the end of the session.
|
|
hublytics_events_53
|
Hubspot |
This browser storage entry is used by HubSpot Product to temporarily store tracking events created by HubSpot Product until they get dispatched over the network. It's stored either on the Browser's Session Storage or Local Storage based on the presence or lack of tracking consent. When tracking consent isn't given, this cookie stays within the current browser session and expires at the end of the session. This "cookie" will remain empty and not store anything. It contains metadata regarding tracking events that HubSpot collects throughout the user's journey at HubSpot. It doesn't contain personal identifiable information or information that can identify your device or hardware. |
It can't be manually removed and is automatically created whenever conditions are met. |
|
hs.superstore.laboratory.<id>
|
Hubspot |
It contains an offline cache of cohorts that a user got assigned for HubSpot Product experiments. It doesn't contain personal identifiable information or information that can identify your device or hardware HubSpot experiments are anonymous and aren't attached to user sessions. However, if tracking consent is given, specific experiments might be tied to identifiable user sessions. The individual contents of this storage entry expire automatically upon specific dates determined by HubSpot Product. Often, these are 48 hours. |
It can't be manually removed and is automatically created whenever conditions are met.
|
|
__cfruid |
Hubspot |
This cookie is set by HubSpot’s CDN provider because of their rate limiting policies. |
It expires at the end of the session. Learn more about Cloudflare cookies. |
|
_tt_session |
Albacross |
Albacross use it to keep the context of a user (e.g. keep them logged in). |
1 year |
|
cid |
Albacross |
Albacross use it for identifying candidates in our chat so that you can resume conversation after leaving the jobsite or careersite page. |
1 year |
4.2 The website uses the following cookies and similar technologies for functionality and analysis:
|
Same |
Supplier |
Purpose |
Storage time |
|
__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). |
It expires in 6 months.
|
|
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. |
It expires in 6 months.
|
|
__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. |
It expires in 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. |
It expires at the end of the session.
|
|
messagesUtk |
Hubspot |
This cookie is used to recognize visitors who chat with you via the chatflows tool. If the visitor leaves your site before they're added as a contact, they will have this cookie associated with their browser. With the Consent to collect chat cookies setting turned on: o If you chat with a visitor who later returns to your site in the same cookied browser, the chatflows tool will load their conversation history. o The messagesUtk cookie will be treated as a necessary cookie. When the Consent to collect chat cookies setting is turned off, the messagesUtk cookie is controlled by the Consent to process setting in your chatflow. HubSpot will not drop the messagesUtk cookie for visitors who have been identified through the Visitor Identification API. The analytics cookie banner will not be impacted. This cookie will be specific to a subdomain and will not carry over to other subdomains. For example, the cookie dropped for info.example.com will not apply to the visitor when they visit www.example.com, and vice versa. It contains an opaque GUID to represent the current chat user. |
It expires after 6 months.
|
|
Chatflow cookie consent text
|
Hubspot |
With the Consent to collect chat cookies setting enabled, HubSpot will prompt visitors for consent to drop a cookie in their browser before the start a chat or when they attempt to the leave the page during a chat conversation. This cookie is used to interact with website visitors and provide a visitor's chat history. If you choose to display the banner before the visitor starts a chat and the visitor does not give consent, they will not be able to start the chat. If you choose to display the banner upon exit intent, however, the visitor can start the chat, but if they don't consent to cookies before navigating away from the page, the chat widget will reset and the conversation will end. With this setting disabled, a visitor can start a chat and give consent to process their information via the Consent to process setting. Visitors can also accept or decline cookies on the HubSpot cookie banner if it is enabled on your pages. |
If a visitor accepts the cookie when they start a chat, but then clicks Decline on the HubSpot cookie banner, the cookie will be removed. If a visitor clicks Decline on the HubSpot cookie banner before starting a chat, HubSpot will not drop a cookie or prompt them to consent to cookies in the chat widget.
|
|
referrer |
Albacross |
Albacross use it to identify the address of the webpage that is linked to Albacross. |
1 year |
|
cookieconsent_dismissed |
Albacross |
Albacross use it to not show you the cookie consent bar once you accept it. |
1 year |
|
ti |
Albacross |
Albacross use it to know which pages a visitor is browsing on. |
1 year |
5. BROWSER SETTINGS
5.1 If you do not accept our use of cookies or similar technologies, you can change the settings in your browser so that cookies are not placed. You can also delete previously stored cookies through your browser. In addition, some browsers offer the possibility to switch off cross-site tracking technologies. Please use your browser's help section for more information.
5.2 If you choose not to allow cookies, it is possible that some features of the websites you visit will not work as you expect them to. Your choice not to allow cookies will not result in the deletion of previously placed cookies.