Cookie Policy
Last updated: 10 November 2026
Purpose
This notice explains cookies and similar technologies on the hilighter marketing website (www.hilighter.io). It supplements the Privacy Policy. The hilighter application (app.hilighter.io) may use additional necessary session and security technologies; those are disclosed separately when audited.
Technology categories
Strictly necessary. Session, sign-in, anti-abuse controls, essential preferences and security. These may operate without consent only where a lawful exemption applies.
Analytics and user experience. Google Analytics 4 and Microsoft Clarity provide audience statistics and session/interaction analytics respectively. They operate only after consent where required.
Tag management. Google Tag Manager orchestrates tags; it does not itself justify activating marketing or analytics tags before consent.
Company identification (Leadfeeder / Dealfront). The marketing Site may load the Leadfeeder tracker. With Consent Mode enabled, company identification can run without the _lfa cookie until analytics are accepted; after Accept, Leadfeeder may set visitor cookies listed in the inventory below.
Bot protection (marketing Site). Forms on www.hilighter.io use a self-hosted Cap proof-of-work check when enabled. Cap may set short-lived necessary tokens; it is not loaded from a third-party CDN.
Bot protection (application). The hilighter application may use Google reCAPTCHA or equivalent anti-abuse tools. Necessity, disclosure and transfers are assessed for that context.
Other services. LinkedIn login/import is user-initiated. Brandfetch may fetch company logos. Google Search Console and Bing Webmaster Tools are webmaster services, not necessarily visitor-set browser cookies.
Your choices
For non-essential trackers, Accept and Decline are equally accessible on the banner. Preferences can also be changed at any time through Cookie Settings. Choices are remembered for up to one year. Refusal does not block essential service.
Verified cookie inventory (www.hilighter.io)
Audited on the marketing Site. Durations are approximate. Non-essential analytics and Leadfeeder cookies are set only after analytics consent, except that the Leadfeeder script may load cookieless for company identification when Consent Mode is enabled.
| Name | Category | Duration | Purpose |
|---|---|---|---|
| hilighter-cookie-consent | Necessary | 1 year | Stores whether a cookie choice was made |
| analytics-consent | Necessary | 1 year | Stores analytics Accept / Decline |
| hilighter-theme | Necessary | Persistent (localStorage) | Light / dark preference |
| hilighter-locale | Necessary | Persistent (localStorage) | Language choice from the switcher |
| _ga | Analytics | 1 year | Google Analytics visitor distinction |
| ga* | Analytics | 1 year | Google Analytics session state |
| _gid | Analytics | 1 day | Google Analytics visitor distinction |
| _clck | Analytics | 1 year | Microsoft Clarity browser ID |
| _clsk | Analytics | 1 day | Microsoft Clarity session grouping |
| _lfa | Analytics | 1 year | Leadfeeder visitor ID (after Accept) |
| _lfa_consent | Analytics | Up to 2 years | Leadfeeder Consent Mode status |
| _lfa_test_cookie_stored | Analytics | Session | Leadfeeder cookie support check |
Google Tag Manager loads only after analytics Accept and does not set its own cookies. Form fields are masked in Clarity recordings. Cap anti-spam widgets may set necessary tokens when a form is used.
Questions: contact@hilighter.io.