Cookies, in plain terms

linkutm Cookie Policy

This page lists what linkutm.com actually loads in your browser, what each tool is for, and how your accept or reject choice is applied. It covers the marketing website. Our broader data practices are in the privacy policy.

Last updated: July 15, 2025

1. Your choice, and what it does

The first time you visit, a banner asks you to Continue or Reject. Until you choose, analytics are switched off.

  • Continue grants consent. Google Consent Mode is updated to granted, and PostHog is opted in.
  • Reject withholds consent. Google Consent Mode stays denied, and PostHog is opted out and captures nothing.

Your choice is stored in your browser's local storage under the key linkutm-cookie-consent so we do not ask again on every page. It is re-applied on each page load before our tag manager runs. The value stays on your device and is not sent to us as a cookie.

To change your mind, clear this site's local storage and cookies in your browser settings. The banner will appear again on your next visit and your new choice will apply.

2. An honest limit worth stating

Several tools below are loaded through Google Tag Manager rather than directly by our site code. For those, our site sends a consent signal, and the tag manager container is responsible for honouring it. We send denied by default and only send grantedafter you accept. We would rather tell you how the mechanism works than promise you an outcome we cannot show you on this page. If you want certainty, reject and also use your browser's tracking protection, or write to us at [email protected].

3. What we load

a. Google Tag Manager and Google Analytics 4

Google Tag Manager (container GTM-56TTDJWK) loads on every page and is the mechanism through which our other measurement tags are delivered. Google Analytics 4 runs through it and measures page views and general usage so we can see which pages are useful. GA4 sets cookies in your browser to distinguish visitors and sessions. For the specific cookie names and their lifetimes, see Google's own documentation, as these are set by Google and can change without a change on our side.

b. PostHog (product analytics)

PostHog is loaded directly by our site code and measures how the site is used: page views captured on navigation, and page-leave events. Person profiles are only created for identified users, not for anonymous visitors.

Session recording: we should be direct about this. Session replay is disabled by default, but for a random 10% sampleof visitors who have accepted, we start a session recording. That records your interactions with our marketing pages so we can see where the site is confusing. It applies only to visitors who accepted. If you reject, PostHog is opted out and no recording starts. For PostHog's cookie names and retention, see PostHog's documentation.

c. Intercom (support chat)

Intercom powers our support chat widget and is loaded through Google Tag Manager. It sets cookies to keep a conversation associated with you between visits so a reply from us reaches the right person. See Intercom's documentation for its cookie names and durations.

d. Albacross (B2B visitor identification)

This is the most privacy-significant tool on our site and it deserves a plain description rather than a euphemism. Albacross is loaded through Google Tag Manager. It takes the IP address of a visit and matches it against its own database to work out which company or organisation a visitor is coming from. Its purpose is to tell our sales and marketing team that a given business looked at our site, and which pages it looked at. It identifies organisations, not individuals by name, but it is de-anonymisation and we are not going to describe it as anything else. See Albacross's documentation for its cookie names and durations.

e. A traffic-source script

One further script, served from traffic-source-production-bc98.up.railway.app, is permitted by our content security policy and loaded through Google Tag Manager. Its name indicates it relates to attributing where visitors arrive from. It is not part of our site code, so rather than guess at its exact behaviour we are listing it here so you know it exists. If you want specifics, ask us at [email protected] and we will tell you what we find.

f. Strictly necessary

Your consent choice itself is stored locally, as described in section 1. It is required for us to remember that you rejected, so it is kept regardless of your choice.

4. Browser-level controls

Independently of our banner, every major browser lets you block or delete cookies and block third-party scripts. Those controls sit outside our site and will apply whatever we send. Blocking cookies may affect how parts of the site behave, such as the support chat.

5. Changes and contact

If we add or remove a tool, we will update this page and the "Last Updated" date above. Questions about anything listed here, or a request to see what we hold, go to [email protected].