KlarBond Cookie and Browser Storage Notice
Effective date: 29 June 2026
This notice explains how KlarBond Ltd uses cookies, local storage, session storage, tags and similar technologies on the KlarBond public website and, where relevant, the KlarBond logged-in application.
1. What these technologies are
Cookies are small files stored by a browser. Local storage and session storage allow a website or application to store information in the browser. Tags and scripts may read information from a device or send website and application events to a service provider.
These technologies may be used to operate the service, authenticate users, remember a setting selected by a user, protect security or—where the user has consented—measure website use.
2. Our approach
KlarBond uses:
- necessary technologies to authenticate users, protect accounts, maintain requested sessions and provide core service functions;
- user-requested preference technologies to remember a setting or interface choice selected by the user; and
- optional site-improvement or measurement technologies only after the required consent.
KlarBond uses Meta Pixel only for optional campaign measurement after marketing consent. We do not use browser technologies for LinkedIn or Hotjar advertising pixels in the reviewed configuration.
3. Public website technologies
| Name | Type | Purpose | Duration | Consent position |
|---|---|---|---|---|
| `klarbond_cookie_consent` | Cookie or local storage | Remembers cookie choice | Up to 180 days | Necessary |
| `klarbond_visitor` | Cookie or local storage | Recognises a returning browser and supports return-visit/counting when analytics or site-improvement use is allowed | Up to 180 days | Optional |
| `klarbond.landing.locale` | Local storage | Remembers landing-page language preference | Until cleared or changed | User-requested preference |
| Google Tag Manager container `GTM-WWJTR75Q` | Tag container | Manages approved public-website tags | Depends on the enabled tag | Optional tags remain blocked until consent unless the tag is strictly necessary |
| Google tag / GA4 configuration `G-CBRKC8Q16K` | Google tag / GA4 config, loaded through GTM | Initialises the Google Analytics 4 destination for optional site measurement | Google Analytics cookies may last up to 2 years by default unless configured shorter | Optional analytics/site measurement |
| GA4 event `page_view` to `G-CBRKC8Q16K` | Google Analytics 4 event, loaded through GTM | Measures page views after consent | Depends on Google Analytics identifiers and configuration | Optional analytics/site measurement |
| GA4 event `generate_lead` to `G-CBRKC8Q16K` | Google Analytics 4 event, loaded through GTM | Measures submitted or triggered lead-generation events after consent | Depends on Google Analytics identifiers and configuration | Optional campaign/lead measurement |
| Meta Pixel `1014729200934579` | Meta Pixel JavaScript tag | Measures page views and campaign funnel events after marketing consent | Depends on Meta Pixel identifiers and configuration | Optional campaign measurement |
No GA4 measurement ID or Google Ads ID is embedded directly in the reviewed code. The Google Analytics 4 destination `G-CBRKC8Q16K` runs through Google Tag Manager. Meta Pixel ID `1014729200934579` is embedded in the landing app and loads only after marketing consent. No Google Ads, LinkedIn or Hotjar tag was identified in the reviewed configuration.
4. Logged-in application technologies
| Name | Type | Purpose | Duration | Consent position |
|---|---|---|---|---|
| `klarbond.auth.session` | Browser storage / session mechanism | Maintains logged-in application authentication session | Until expired or cleared | Necessary |
| `klarbond.auth.session.override` | Session storage | Tab-session mirror of authentication session | Browser-tab session | Necessary |
| `klarbond.auth.remembered-login` | Local storage or cookie | Remembers a login identifier selected by the user | Until cleared | Optional preference |
| `klarbond.auth.oauth` | Session storage | OAuth state, code verifier and return path | Browser-tab session; removed after callback | Necessary |
| `klarbond.activity.skipIgnoreConfirm` | Local storage | Remembers user's choice to skip a confirmation prompt | Until cleared or the preference is changed | User-requested preference |
| `klarbond.activity.skipAcceptConfirm` | Local storage | Remembers user's choice to skip a confirmation prompt | Until cleared or the preference is changed | User-requested preference |
| `klarbond.realtime.clientId` | Local storage | Maintains realtime WebSocket client identifier for service operation | Until cleared | Necessary |
| `klarbond.documentLibraryRailPinned` | Local storage | Remembers whether the user pinned the document-library navigation rail | Until cleared or the preference is changed | User-requested preference |
Google Tag Manager must not be enabled in the logged-in application unless every non-exempt tag is subject to the same prior-consent and withdrawal controls described in this notice.
5. Staff back-office technology
| Name | Type | Purpose | Duration | Consent position |
|---|---|---|---|---|
| `backoffice.auth.session` | Session storage | Maintains an authenticated KlarBond staff back-office session | Browser-tab session | Necessary |
6. Application telemetry
KlarBond may use application performance, reliability, fault-diagnosis or security telemetry for the logged-in application or staff back office. This notice does not treat AWS CloudWatch RUM or another application telemetry tool as an active public-website cookie or tag.
Before KlarBond onboards users to a logged-in application configuration that uses AWS CloudWatch RUM or a similar browser telemetry tool, KlarBond will confirm whether it stores or accesses information on the user's device and will update this notice and consent controls where required.
If AWS CloudWatch RUM is enabled with cookies disabled and without non-exempt browser storage, it will be treated as application telemetry rather than optional public-site analytics. If browser storage, advertising, profiling or non-essential measurement is enabled, it will be assessed and controlled before use.
7. Google tags
The reviewed public-site GTM configuration contains the following Google tags:
| Tag | Type | Destination | Trigger | Purpose | Consent category |
|---|---|---|---|---|---|
| Google tag config | Google tag / GA4 configuration | `G-CBRKC8Q16K` | `gtm.init` | Initialises Google Analytics 4 measurement | Optional analytics/site measurement |
| GA4 event | `page_view` | `G-CBRKC8Q16K` | `klarbond_page_view` | Measures page views after consent | Optional analytics/site measurement |
| GA4 event | `generate_lead` | `G-CBRKC8Q16K` | `generate_lead` | Measures lead-generation events after consent | Optional campaign/lead measurement |
Google Analytics 4 JavaScript tags may set or read first-party analytics cookies such as `_ga` and `_ga_<container-id>` where analytics storage is allowed. For KlarBond's current GA4 destination, this may include `_ga` and `_ga_CBRKC8Q16K`. Google states that GA4 cookies have a default expiration of up to 2 years unless configured otherwise.
KlarBond must update this notice or the cookie-settings interface before enabling a materially different GTM tag, destination, trigger, purpose, cookie or storage item.
8. Meta Pixel
The reviewed public-site Meta Pixel configuration contains:
| Tag | Type | Destination | Trigger | Purpose | Consent category |
|---|---|---|---|---|---|
| Meta Pixel base code | Meta Pixel JavaScript tag | `1014729200934579` | Marketing consent grant | Initialises Meta Pixel for campaign measurement | Optional campaign measurement |
| Meta Pixel event | `PageView` | `1014729200934579` | Initial marketing consent grant and route changes after consent | Measures page views after marketing consent | Optional campaign measurement |
| Meta Pixel custom event | `ScoreCardInitView` | `1014729200934579` | Scorecard page opens after marketing consent | Measures scorecard page entry | Optional campaign measurement |
| Meta Pixel custom event | `ScorecardStart` | `1014729200934579` | User starts the scorecard after marketing consent | Measures scorecard starts | Optional campaign measurement |
| Meta Pixel custom event | `ScorecardEnd` | `1014729200934579` | User completes the last scorecard question after marketing consent | Measures completed scorecard questions | Optional campaign measurement |
| Meta Pixel custom event | `ScorecardRequested` | `1014729200934579` | Scorecard report request is saved after marketing consent | Measures scorecard report requests | Optional campaign measurement |
| Meta Pixel custom event | `ScorecardReportView` | `1014729200934579` | Scorecard report opens successfully after marketing consent | Measures scorecard report views | Optional campaign measurement |
| Meta Pixel custom event | `RequestAccess` | `1014729200934579` | Early-access request is saved after marketing consent | Measures early-access requests | Optional campaign measurement |
The static no-JavaScript Meta image pixel is not used because it cannot be gated by the runtime cookie-consent control.
9. Consent controls
For optional technologies, KlarBond's consent interface:
- offers Accept and Reject choices with comparable prominence;
- leaves optional technologies disabled by default;
- prevents optional tags and storage from operating before consent;
- permits separate choices where materially different optional purposes are used;
- remembers the user's choice; and
- provides a persistent Cookie Settings control through which consent can be withdrawn as easily as it was given.
When consent is withdrawn, KlarBond stops future optional use and removes KlarBond-controlled optional identifiers where technically possible. Third-party identifiers may also need to be removed through browser settings where KlarBond cannot delete them directly.
Necessary technologies cannot be disabled through the cookie controls because the requested service cannot operate securely without them.
10. Browser controls
A user can delete or block cookies and browser storage through browser settings. Blocking necessary technologies may prevent authentication or other core functions.
Browser settings do not replace KlarBond's obligation to obtain consent before using a non-exempt technology.
11. Changes
KlarBond will review its website, application, GTM container and browser-storage inventory regularly. This notice will be updated before a materially different optional technology or purpose is enabled, and fresh consent will be requested where required.
12. Contact
KlarBond Ltd
Company number: 17300261
ICO registration number: ZC182066
Registered office: 5th Floor, 167–169 Great Portland Street, London, W1W 5PF, United Kingdom
Privacy contact: privacy@klarbond.com