Policy

Cookie policy

How we use cookies and the options you have to manage your cookie preferences.

This is a translation for your convenience. The Dutch text is legally binding; in the event of any difference, the Dutch version prevails.

Talensa Cookie Policy

Version: 2.1 — Effective from: 2026-10-31

1. Scope

This Cookie Policy applies to the Talensa website. In this statement we explain which cookies and similar technologies we use and why.

2. What are cookies?

Cookies are small text files that are placed on your device when you visit a website. They are used to remember information about your preferences and actions on the website. Cookies can be placed by the website you visit ("first-party cookies") or by third parties ("third-party cookies"). Similar techniques include storage in your browser (localStorage and sessionStorage) and tags that send a request to another service.

3. Your consent

On your first visit, we ask which cookies you allow. We always place strictly necessary cookies. We place analytics and marketing cookies only if you give your consent. You can change your choice at any time via "Cookie settings" at the bottom of every page. If you withdraw your consent, the measurements stop and we delete the analytics identifiers that we placed ourselves.

Google Tag Manager loads the third-party tags. It does not place any cookies itself and passes your choice on to those tags (Google Consent Mode).

Without consent, we report technical errors on the website to Sentry so that we can fix malfunctions: the error message, the page (without the rest of the link), browser and device. Sentry does not place any cookies for this and does not store any IP address on our behalf; it does not track your behavior on the website.

4. What data do we process with your consent?

4.1 Session and visitor data

  • Visitor ID: unique pseudonymous identifier (cookie, valid for 1 year)
  • Session ID: session identifier (expires after 30 minutes of inactivity)
  • First and last time of visit

If you later log in to the Talensa platform, we may link your previous website visits to your account via the Visitor ID.

4.2 Page and referral data

  • Pages visited (URL) and page title
  • First page of the visit
  • Referrer (referring page)
  • UTM parameters: utm_source, utm_medium, utm_campaign, utm_content, utm_term, utm_id
  • Only if you also consented to marketing cookies: the ad click ID from the link through which you arrived (gclid, gbraid, wbraid, msclkid, fbclid), so that we can see which ad led to a demo or contact

4.3 Device and browser data

  • User agent
  • Device type (desktop, tablet, mobile)
  • Browser (Chrome, Firefox, Safari, Edge and the like)
  • Country and city, as derived by our hosting provider during your visit; we do not store the IP address itself

4.4 Interaction data

  • Page views and navigation
  • Clicks on buttons and links to a demo, contact or the platform
  • Which parts of a page you view and for how long

4.5 PostHog

We use PostHog (EU-hosted) for:

  • Session recordings (recordings of your visit to the website)
  • Heatmaps (visualization of click behavior)
  • Rage click detection (detection of frustration clicks)
  • PostHog distinct_id and session_id (pseudonymous identifiers)

Session recordings capture mouse movements, scrolling behavior and clicks. Everything you type into a form is masked and not recorded.

4.6 Google Analytics

We use Google Analytics to gain insight into how the website is used, such as page views and referral sources.

4.7 LinkedIn Insight Tag

With the LinkedIn Insight Tag we measure the effectiveness of our advertisements on LinkedIn, for example how many demos a campaign generates, and we can reach website visitors again through LinkedIn ads.

4.8 Google Ads

With Google Ads we measure which ads on Google lead to a visit or demo, and we can reach website visitors again through Google.

5. Which cookies do we use?

5.1 Strictly necessary (always)

  • Cookie preferences (localStorage, talensa_cookie_consent_v1): stores your choice in the cookie banner
  • Cloudflare (including __cf_bm): protects the contact form and the demo scheduler against abuse by bots

5.2 Analytics (with consent)

  • talensa_visitor_id (cookie, 1 year): pseudonymous visitor identifier
  • Session storage (sessionStorage): Session ID and time of last activity
  • PostHog (including ph_* cookies and localStorage): session recordings, heatmaps and analytics
  • Google Analytics (including _ga and _ga_*): website analytics

5.3 Marketing (with consent)

  • LinkedIn Insight Tag (including li_gc, li_sugr, bcookie, lidc, UserMatchHistory): campaign measurement and audiences for LinkedIn ads
  • Google Ads (including _gcl_au, test_cookie, IDE): campaign measurement and remarketing via Google

6. Where is data stored?

  • PostHog: EU-hosted (session recordings and analytics)
  • Supabase: EU-hosted (session and event data in our own database)
  • Sentry: EU-hosted (website error reports, for a maximum of 90 days)
  • Google and LinkedIn: under their own terms; they may process data outside the EU

We do not store IP addresses in our own database as part of our website tracking, and we do not forward them to other services to look up a location.

7. Managing your cookie preferences

You can manage your cookie preferences in several ways:

  • Via "Cookie settings" at the bottom of every page: here you change your choice per category or withdraw your consent
  • Via your browser: you can manage cookies through your browser settings
  • By deleting cookies and site data: this also resets your saved choice, and we will ask for your consent again on your next visit

Instructions for commonly used browsers:

8. Retention period

  • Session storage: until you close the tab, or after 30 minutes of inactivity
  • Visitor ID cookie: 1 year
  • Cookie preferences: 12 months; after that we ask for your choice again, and also earlier if we add a new category or service
  • Record of your choice: to be able to demonstrate which choice you made, we keep every choice (including a refusal) together with a random code for your browser, the version of this policy, the selected categories and the time, without IP address; 25 months
  • Session recordings (PostHog): in accordance with PostHog's retention policy
  • Session and event data (own database): 14 months after your last activity. If you contact us through the contact form, a demo booking or the generator, we keep the origin of that visit (landing page, referrer, UTM parameters) with your contact details for as long as we keep them, up to 2 years after the last contact; we do not keep the individual page views and interactions

9. Updates to our cookie policy

We may update this cookie policy from time to time. The version and the effective date are shown at the top of this page.

10. Contact

If you have any questions about our cookie policy, please contact us at: