Cookie Policy

Version 2.0 / Last modifications: Sep 21 2026

This website https://tietalent.com (thereafter called the 'site') is published and operated by TieTalent SA and its subsidiaries (TieTalent),a Swiss company headquartered at Chemin du Closel 5, 1020 Renens. TieTalent GmbH, a German company based at Heilbronner Str. 150 70191 Stuttgart Germany as well as TieTalent Barcelona SL, a Spanish company based at Av. de Francesc Cambó 17 08003 Barcelona Spain, are subsidiaries of TieTalent SA.

Email address: info@tietalent.com

Phone: +41 (0) 78 226 07 07
  1. In general

    1. Definitions. In general, the terms starting with a capital letter in the present Cookie Policy have the meaning attributed to them in the General Terms and Conditions or, otherwise in the present terms and conditions.
    2. Relationship with the General Terms and Conditions. The present Cookie Policy applies in addition to the General Terms and Conditions and the other documents in the Contractual documentation, especially the Privacy Policy. In the event of conflict between the General Terms and Conditions and the present Cookie Policy, the Cookie Policy shall prevail.
    3. A table summarising the Cookies used by TieTalent is attached to the present Cookie Policy.
  2. Purpose

    1. The present Cookie Policy is intended to inform Users of the type of Cookies used by TieTalent and certain third parties and how they are used.
    2. Users who do not agree with the present Cookie Policy can block Cookies from their browser. In such case, all or some of the Website, the Platform or the Services may be inaccessible or not usable.
    3. The present Cookie Policy covers the TieTalent website and platform (tietalent.com) as well as the Candidate Intelligence service (intelligence.tietalent.com), including its partner portal and the Candidate Intelligence Chrome extension. The table below lists the Cookies and similar technologies used by each.
  3. Definition

    1. Cookies are the equivalent of a small text file, stored on the devices Users use to access the Website or Platform (computer, tablet, telephone, etc.)
    2. Cookies are placed by TieTalent or third parties on the devices Users use to consult the Website or the Platform in order to collect the information on their browsing or to optimise/personalise their experience.
    3. Similar technologies. In addition to Cookies, TieTalent uses the browser's local storage and session storage, and the storage of the Candidate Intelligence Chrome extension, to keep preferences, temporary drafts and sign-in information on the User's device. They are listed in the table below and are treated like Cookies under the present Cookie Policy. Users can delete them from their browser settings or by removing the extension.
  4. Cookies - Issuers

    1. TieTalent Cookies These are cookies deposited by TieTalent.
    2. Third-party Cookies. These are Cookies deposited by third parties (like Google, HubSpot, Hotjar, hCaptcha, Stripe, etc.).
  5. Cookies - Types and use

    1. Strictly necessary cookies. Certain Cookies are necessary for using our Services. They are mainly TieTalent cookies. These Cookies are used in particular to provide Users with secure access the Platform
    2. Analytical cookies Certain Cookies enable TieTalent to understand how Users use the Platform and how the Platform performs. They are TieTalent Cookies and third-party Cookies. These Cookies enable TieTalent to recognise and count the number of Users on the Website or Platform and to determine how they use the Website and Platform. This information helps TieTalent to improve the Website, Platform and the Services it offers.
    3. Functional Cookies Certain Cookies are used to allow the Platform to post personalised content for Users, for example, to post Users’ names and register their preferences. They are mainly TieTalent cookies.
    4. Advertising Cookies. Certain Cookies are used to present advertising which correspond to Users’ areas of interest on or outside the Platform. They are mainly third-party Cookies, over which TieTalent has no control.
    5. Social media Cookies. Certain Cookies are used to enable Users to connect to the Platform via social media plugins or to share different content on said social platforms. These Cookies can also permit personalised content to be posted on social media. They are mainly third-party Cookies, over which TieTalent has no control.
    6. Cookies for payment security. Certain Cookies are used to secure payments made through the Platform. These Cookies are mainly third-party Cookies issued by TieTalent financial partners. TieTalent has no control over these Cookies.
  6. Cookie Management

    1. Users can configure the use of Cookies by choosing at any time to deactivate use of all or part of TieTalent Cookies and/or third-party Cookies.
    2. Cookies can be configured through each device used to navigate the Website or the Platform and according to the types listed by these platforms in their respective documentation.
    3. Note that certain Cookies are necessary to use certain services (Clause5.1) and that if all or part of them are deactivated it may be impossible to access or use certain services.
    4. The consequence of deactivating analytical Cookies (Clause 5.2) prevents the User’s browser from sending information to the issuers of said Cookies and does not in principle prevent use of the Platform.
    5. Deactivating functional Cookies (Clause 5.3) may prevent access to all or part of the Services offered by TieTalent.
    6. Deactivating advertising Cookies (Clause 5.4) prevents the presentation of advertising linked to the User’s areas of interest but has no consequences on the posting of advertising as such. So deactivating this type of Cookies does not prevent the posting of advertising nor in principle does it prevent use of the Website or the Platform.
    7. Deactivating social media Cookies (Clause 5.5) does not prevent in principle the use of the Website or the Platform, it only prevents access to certain services such as sharing buttons on social media.
    8. Deactivating Cookies for payment security (Clause5.6) may prevent the use of certain TieTalent Services.
    9. TieTalent cannot be held liable for the use of data collected by third parties and/or for Cookies deposited by them. Users are responsible for managing Cookies according to each issuer. For further information on third-party Cookies, please refer to each issuer’s Cookie policy.
    10. How to manage Cookies. Users can delete or block Cookies at any time in their browser settings: Chrome, Firefox, Safari, Edge. Data stored by the Candidate Intelligence Chrome extension is removed by signing out or by uninstalling the extension.
    11. Opting out of third-party Cookies. Users can opt out of Google Analytics with the Google Analytics opt-out add-on, manage Google advertising in their Google ad settings, opt out of Hotjar here, and consult the HubSpot cookie policy.
  7. Legal basis and consent

    1. Strictly necessary Cookies are used without consent because they are required to provide the service the User has requested (for example authentication, security and payment).
    2. Functional, analytical and advertising Cookies that are not strictly necessary are used on the basis of the User’s consent (Art. 6(1)(a) GDPR). Users can withdraw their consent at any time as described in clause 6, without affecting the lawfulness of the processing carried out before the withdrawal.
    3. Personal data collected through Cookies is processed in accordance with the Privacy Policy and the applicable data protection law, in particular the Swiss Federal Act on Data Protection and the EU General Data Protection Regulation.
  8. Third parties and international transfers

    1. Third-party providers (such as Google, HubSpot, Hotjar, hCaptcha and Stripe) act under their own privacy policies. They may process data outside Switzerland and the European Economic Area, including in the United States, in accordance with applicable data protection law (for example on the basis of adequacy decisions or standard contractual clauses).
    2. The duration for which each Cookie is stored is indicated in the table below. Cookies are not kept longer than this duration unless the User renews them by visiting again.
  9. Contact and changes

    1. For any question about this Cookie Policy, Users can write to info@tietalent.com.
    2. TieTalent may update this Cookie Policy, in particular when it adds or removes Cookies or changes providers. The version and date of the last modification are indicated at the top of this page.

TieTalent website and platform (tietalent.com)

  • TieTalent cookies

    NamePurposeCategoryDuration
    accept_cookiesRemembers that you have answered the cookie banner, so it is not shown again.Strictly necessary365 days
    access_tokenAuthenticates you after you log in (HttpOnly, not readable by scripts).Strictly necessaryUntil the login session expires (typically 1 hour)
    refresh_tokenLets us renew your login without asking for your credentials again, for example when you selected "Remember me" (HttpOnly).Strictly necessary14 days
    session_activeIndicates that you are logged in, so the Google One Tap sign-in prompt is not shown to logged-in users.FunctionalUntil the login session expires (typically 1 hour)
  • Laravel & PHP cookies

    NamePurposeCategoryDuration
    remember_web_*Generated when you select the "Remember me" checkbox on the login page. It lets you log in again quickly when your session has ended. It is deleted when you log out.Functional5 years
    laravel_sessionIdentifies your session on the platform.Strictly necessary24 hours
    XSRF-TOKENContains a unique token that protects the website against cross-site request forgery attacks.Strictly necessary24 hours
    PHPSESSIDEstablishes a user session and passes state data via a temporary session cookie.Strictly necessarySession
  • Google Analytics

    NamePurposeCategoryDuration
    _gaUsed to distinguish users and measure how the website is used.AnalyticsUp to 2 years (400 days in Chrome)
    _ga_<measurement id>Used by Google Analytics 4 to persist the session state (for example _ga_BTH3EX5C3K).AnalyticsUp to 2 years (400 days in Chrome)
    _gidUsed to distinguish users.Analytics24 hours
  • Google Ads

    NamePurposeCategoryDuration
    _gcl_auUsed by Google to store and measure how visitors reach us from Google advertising (conversion linking).Marketing90 days
  • Google Sign-In (One Tap)

    NamePurposeCategoryDuration
    g_stateSet by Google when the Google One Tap sign-in prompt is displayed. It remembers whether you dismissed the prompt so it is not repeatedly shown. Other Google cookies are governed by Google's privacy policy.FunctionalUp to 6 months
  • hCaptcha

    NamePurposeCategoryDuration
    hCaptcha cookies (hcaptcha.com)Used for the anti-bot check on sign-up, verification and password-reset forms. hCaptcha sets its own cookies and storage to tell humans from bots; their names and durations are defined by hCaptcha (see hcaptcha.com/privacy).Strictly necessarySet by hCaptcha
  • Hotjar

    NamePurposeCategoryDuration
    _hjSessionResumedThis cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.AnalyticsSession
    _hjIncludedInPageviewSampleThis cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit.Analytics30 minutes
    _hjAbsoluteSessionInProgressThis cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.Analytics30 minutes
    _hjTLDTestWhen the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.AnalyticsSession
    _hjidHotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.Analytics1 year
  • HubSpot

    NamePurposeCategoryDuration
    messagesUtkUsed to recognize visitors who chat with TieTalent via the HubSpot widget on the public website.Functional180 days
    hs-messages-hide-welcome-messageRemembers that you closed the welcome message of the HubSpot chat widget, so it is not shown again straight away.Functional1 day
    hubspotutkKeeps track of a visitor's identity. It is passed to HubSpot on form submission and used when de-duplicating contacts.Analytics180 days
    __hsscKeeps track of sessions. It is used to determine whether to increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each page view in a session) and the session start timestamp.Analytics30 minutes
    __hssrcSet whenever HubSpot changes the session cookie. It is set to 1 and used to determine whether the visitor has restarted their browser. If it does not exist, the visit is treated as a new session.AnalyticsSession
    __hstcThe main cookie for tracking visitors. It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit) and session number (increments for each subsequent session).Analytics180 days
  • Browser storage (local and session storage)

    NamePurposeCategoryDuration
    talent-first-time-login-seen_<user id>Local storage. Remembers that a talent has already seen the first-login welcome dialog.FunctionalUntil cleared
    <page path> (scroll position)Session storage. Saves the scroll position of company list pages so you return to the same place after navigating back.FunctionalBrowser tab session

Candidate Intelligence (intelligence.tietalent.com)

  • Candidate Intelligence cookies

    NamePurposeCategoryDuration
    localeStores your language choice (en, de or fr) for the Candidate Intelligence app.Functional365 days
    ats_view / __Secure-ats_viewGrants access to a single shared ATS candidate report after you open its secure link. Limited to that report's path (HttpOnly).Strictly necessaryUntil the report link expires
    pi.session-token / __Secure-pi.session-tokenKeeps partner integrators signed in to the partner portal (HttpOnly). The __Secure- variant is used on HTTPS.Strictly necessary30 days
    pi.enroll-token / __Secure-pi.enroll-tokenShort-lived token that lets a partner integrator complete two-factor authentication setup (HttpOnly).Strictly necessary10 minutes
  • Authentication cookies (Auth.js)

    NamePurposeCategoryDuration
    authjs.session-token / __Secure-authjs.session-tokenIdentifies your signed-in Candidate Intelligence session (HttpOnly).Strictly necessary30 days
    authjs.csrf-token / __Host-authjs.csrf-tokenProtects sign-in and sign-out from cross-site request forgery.Strictly necessarySession
    authjs.callback-url / __Secure-authjs.callback-urlRemembers the page to return to after you sign in.Strictly necessarySession
    authjs.state / __Secure-authjs.stateProtects the "Continue with Google" sign-in from forged requests.Strictly necessary15 minutes
    authjs.pkce.code_verifier / __Secure-authjs.pkce.code_verifierSecures the code exchange during "Continue with Google" sign-in.Strictly necessary15 minutes
  • Google Sign-In

    NamePurposeCategoryDuration
    Google cookies (google.com)When you choose "Continue with Google", Google sets its own cookies on google.com. They are governed by Google's privacy policy.FunctionalSet by Google
  • Stripe (payments)

    NamePurposeCategoryDuration
    Stripe cookies (stripe.com)When you buy credits you are redirected to Stripe Checkout, which sets its own cookies on stripe.com to secure the payment and prevent fraud. Candidate Intelligence does not load Stripe scripts on its own pages.Strictly necessarySet by Stripe
  • Browser storage (local and session storage)

    NamePurposeCategoryDuration
    ci.rememberedAccountsLocal storage. Remembers up to 5 email addresses you signed in with on this device, to offer quick sign-in.Functional365 days
    ci.pendingMagicLinkAuthLocal storage. Remembers the email address of a sign-in link you requested so the app can complete sign-in.Strictly necessary20 minutes
    ci.signInContextSession storage. Remembers that you just signed out so the sign-in page can adapt.Strictly necessaryBrowser tab session
    ci.cv-draftSession storage. Temporarily keeps the CV text or profile link you entered while you sign in, so it is not lost.FunctionalBrowser tab session
    ci-partner-sidebar-collapsedLocal storage. Remembers whether the partner portal sidebar is collapsed.FunctionalUntil cleared
  • Chrome extension storage

    NamePurposeCategoryDuration
    extensionTokenExtension storage. Device access token that connects the extension to your account. Revocable; the server only keeps a hash.Strictly necessaryUntil you sign out or revoke the device
    meCacheExtension storage. Cached copy of your account details and credit balance to show the popup quickly.FunctionalUntil you sign out
    activeRunExtension storage. State of the analysis in progress so it can resume if the popup is closed.FunctionalUntil the analysis is cleared
    pendingAutoAnalyzeExtension storage. Lets an analysis start automatically right after you sign in or top up.Functional3 minutes
    extractionConfigExtension storage. Cached configuration that tells the extension how to read supported profile pages.Strictly necessaryUntil refreshed
    pendingErrorLogsExtension storage. Queue of technical error reports (max 50) sent to us to fix bugs. Cleared once sent.FunctionalUntil sent
    localeExtension storage. Your language choice for the extension popup.FunctionalUntil cleared
    ci.signInContext, ci.rememberedAccounts, ci.pendingMagicLinkAuthExtension storage. Same purpose as the web storage entries of the same name, kept inside the extension.FunctionalAs above