Tracking and Analytics Disclosure

Last updated: 15 May 2026

This document provides an operational disclosure of tracking and analytics implementations identified in current public web properties. It is intended to support legal transparency and implementation governance.

1. Scope

Reviewed properties:

www.efficientether.co.uk (main marketing website)
forge_site (EtherApps Forge web property)
Etherinsights-site
etherassist-platform docs site
status page web frontend

2. Site-by-Site Tracking Inventory

Property	Tools Observed	Identifiers / Notes	Consent Behavior (as implemented)
www.efficientether.co.uk	Google Analytics, Microsoft Clarity	GA `G-PY6RD3J33G`; Clarity project id configured via `NUXT_PUBLIC_MICROSOFT_CLARITY_PROJECT_ID` build env	Cookie banner present. Default consent state is `denied`; both analytics tools load only after the visitor clicks Accept all. Consent is reversible from the footer Cookie preferences link.
forge_site	Google Analytics, Microsoft Clarity, HubSpot	GA `G-BMKKPQ381K`; Clarity `t72vjgku3a`; HubSpot portal `146295643`	Cookie consent banner controls analytics/tracking enablement via local consent state.
Etherinsights-site	Google Analytics, Microsoft Clarity, HubSpot, LinkedIn Insight	GA plugin `G-91EL2SHTL7`; additional homepage GA `G-44TW9LRM14`; Clarity `q6ptf8ik01`; HubSpot `146295643`; LinkedIn partner ID `5668002`	Cookie banner present; however legacy homepage-injected scripts are separately implemented and should be aligned to central consent controls.
etherassist-platform docs	Cookie consent component references GA/Clarity controls	No explicit GA/Clarity IDs identified in docs-site config at review time.	Consent storage key and privacy link are configured in docs site config.
status frontend	No first-party analytics/tracking scripts identified in frontend code at review time	Footer includes external links only.	No site cookie banner implementation identified in frontend code at review time.

3. Governance Requirements

All non-essential tracking must be gated by explicit consent where required by law.
All production tracking IDs should be documented in one authoritative location and kept in sync with deployed code.
Changes to tracking vendors or IDs should trigger legal disclosure updates and release notes.
Legacy script injections should be migrated to one consent-aware initialization path.
Consent withdrawal must be as easy as consent acceptance, including post-visit preference changes.
Engineering releases must include pre-consent script checks in QA evidence for each public site.

4. Open Remediation Items

Etherinsights homepage legacy script path: consolidate to central consent-aware initialization before next release.
Status frontend: if analytics is introduced, deploy a banner/control flow before enabling any non-essential tracking.
All sites: maintain quarterly evidence of cookie and tag scans against this disclosure and Cookie Policy.

5. Change Notice

This disclosure reflects implementation evidence reviewed on 3 March 2026. It may change as codebases evolve. Material changes should be republished through legal.efficientether.co.uk.