What the website uses
This website uses an essential cookie to remember your privacy choice and short-lived functional cookies to confirm a saved enquiry. It also uses tab-local session storage for a retry token, confirmation reference and a denial-only safety marker. These values are for the requested form and privacy controls; they are not advertising identifiers and do not contain your entered contact details or message.
The automatic page-request counter uses no cookie or browser identifier. Optional first-party analytics uses a limited device signature without adding another analytics cookie, but still relies on the signed preference cookie to verify your grant. Google Analytics 4 uses the external-analytics choice and Microsoft Clarity uses the separate session-recording choice. The advertising choice can govern consent-gated Meta Pixel, Google Ads, Microsoft UET, LinkedIn Insight Tag, X Pixel and Reddit Pixel integrations. Google Tag Manager may deliver a named integration only when its required public identifier and reviewed tag are configured and enabled; naming a supported provider does not prove that it received a visit or conversion. Optional media has its own choice.
Fonts and brand artwork are served from our own website. This does not make the whole site cookie-free: Cloudflare security services and YouTube videos you choose to load can process technical data and use cookies or similar storage.
The privacy-choice cookie
After you save a choice, __Host-lgm_privacy is set by this website for up to 180 days. Its signed random references, notice version and expiry are used to verify the corresponding server-side choice. It is Secure, HttpOnly and SameSite=Lax on the live HTTPS site, restricted to this host and unavailable to page JavaScript. Local development uses lgm_privacy without Secure.
Rejection is remembered as well as acceptance. Earlier first-party analytics or media grants retain their original scope and do not authorize new external analytics, recordings or advertising. Privacy choices in the footer lets you review and change the settings. Without a valid choice, optional features remain off. You can still read ordinary pages and submit an enquiry.
The cookie is not used for advertising. The corresponding choice and limited security evidence are described in the Privacy notice. Optional first-party analytics records can be associated with an enquiry or newsletter request you later submit from that browser. The choice does not accept every policy or permit undisclosed future tracking.
Functional session storage and confirmation cookies
The tab-local key lgm.enquiry.attempt.v1 keeps a signed random token so a submission can be retried without creating another accepted enquiry. After confirmed acceptance, that token is cleared and lgm.enquiry.confirmation.v1 holds a random confirmation locator and expiry for the thank-you page. These keys contain no entered name, email, phone number or project message.
A confirmation cookie whose name begins __Host-lgm_enquiry_ carries a protected proof for the saved enquiry. It is HttpOnly, Secure, host-only and SameSite=Lax on the live HTTPS site, and lasts 15 minutes. A recognised retry may renew it. The locator in session storage cannot confirm an enquiry without the corresponding cookie. Local development uses the lgm_enquiry_ prefix.
The __Host-lgm_enquiry_context cookie is a short-lived, shared proof that the contact page was opened in an eligible context. The __Host-lgm_enquiry_restricted marker prevents conversion measurement after a sensitive or unrecognised context. Both expire within 30 minutes. They contain no form content and are not unique tracking identities. They cannot grant optional consent.
The lgm-tracking-paused session-storage value is a denial-only marker. It keeps optional features off if a privacy change fails or needs a safe reload. It contains no visitor identifier and cannot grant permission. A successful, confirmed new choice can clear it. Session storage is managed by the browser for the tab; browser restore or clearing settings can affect its lifetime.
Functional form and confirmation values are not placed in page URLs, advertising payloads or public reporting. Their server records are retained for up to 30 days after acceptance, separately from the enquiry and privacy-choice evidence.
Forms and Cloudflare security
The contact form uses Cloudflare Turnstile, which processes browser and security signals and returns a token for server verification. Its optional pre-clearance feature is disabled on this site. Other Cloudflare security controls may still use security cookies when needed.
The newsletter form does not use a CAPTCHA. Both forms have server-side checks to limit abuse. Enquiries, subscription requests and withdrawal preferences are database records, not browser cookies. Their handling and retention are explained in the Privacy notice.
Videos load only when you choose
Some guides include a YouTube video option. No YouTube player, thumbnail or preconnection loads until you allow optional video media in Privacy choices and then press Load video. You can read the guide and use its sources without loading the video.
After you choose to load it, an embedded player connects through youtube-nocookie.com. Google or YouTube then receives technical information such as your IP address and device or browser details. Privacy-enhanced mode limits some uses of viewing information; it does not guarantee no data collection, cookies or storage. The provider's terms and privacy practices apply.
X and Instagram references are plain links, not automatically loaded embeds. Opening an external link takes you to that provider's website and its own controls. The separate YouTube link also remains available if you prefer to watch there.
Your controls and future changes
Your browser can block or clear cookies and other storage. Blocking security scripts may stop a form from working, and blocking functional storage can limit retry or thank-you confirmation. You can email support@lucidgrowthmedia.com instead. Clearing storage does not erase an enquiry or withdraw a newsletter request; use the relevant contact or preference route.
Privacy choices lets you allow or reject first-party analytics and YouTube media independently. Any genuinely enabled external analytics, recording or advertising purposes have their own controls. Rejecting optional features leaves essential functions and the separate identifier-free page-request counter operating; it does not secretly permit device identification or optional advertising.
A failed save leaves optional features off in that tab and asks you to retry. A denial-only session marker can preserve this protection through reload. The earlier server choice or another browser may still retain its last valid setting. Browser privacy signals or blocked scripts can also prevent optional features from running.
Optional Google Analytics cookies
After external-analytics permission on an eligible page, Google Analytics may set _ga and _ga_* first-party cookies to distinguish browsers and sessions. We configure the maximum 25-month cookie lifetime offered in Google Analytics, renewed relative to the most recent permitted visit. Browsers can enforce a shorter limit and users can clear cookies at any time. Browser settings can shorten this. These cookies are separate from our signed privacy-choice cookie and the optional first-party device signature.
Google Analytics receives the technical connection and permitted event data described in our Privacy notice. The property uses 14-month event/user retention with activity reset enabled; cookie lifetime and report retention are different settings. Google Tag Manager delivers the reviewed tags. Google Analytics does not load before external-analytics permission. Other enabled tags require their own purpose. Rejection or withdrawal removes supported first-party vendor cookies and stops future tag loading.
The recording and advertising integrations have separate controls. An earlier advertising-measurement choice does not silently authorize the new retargeting scope: that scope requires a fresh choice under this notice. Our 180-day preference-cookie lifetime is separate from a provider cookie or report retention period.
Adding or changing tracking tools
Google Analytics 4 uses the external-analytics choice and Microsoft Clarity uses the separate session-recording choice. The advertising choice can govern consent-gated Meta Pixel, Google Ads, Microsoft UET, LinkedIn Insight Tag, X Pixel and Reddit Pixel integrations. Google Tag Manager may deliver a named integration only when its required public identifier and reviewed tag are configured and enabled; naming a supported provider does not prove that it received a visit or conversion. Optional media has its own choice.
Before enabling a provider, the tracking inventory and notices must identify its actual purposes, data, storage, retention and controls, with relevant provider information. Newly introduced optional recipients or purposes do not inherit an old first-party or media grant. A policy update alone is not consent.
Refusing optional features must be as straightforward as accepting them. A later withdrawal stops future optional collection; it cannot recall data a provider already received. Legally required choice evidence may remain. Security storage must not be repurposed for advertising, and cookieless technology must not be used to bypass an explicit choice.
Recording and advertising storage
After recording permission, Clarity can use _clck and _clsk to recognise a browser and group session activity. Microsoft controls their technical lifetimes. Its playback and extended-data retention limits are described in the Privacy notice. We do not enable Clarity advertising storage.
After advertising permission, a configured Meta Pixel, Google Ads tag, Microsoft UET tag, LinkedIn Insight Tag, X Pixel or Reddit Pixel may use provider-managed browser identifiers for permitted page and conversion events. Each sitewide or accepted-enquiry path remains independently off until its required public identifier and reviewed tag are configured. A named integration or eligible source event is not evidence that its provider received, matched or reported the event. Cookie blocking can reduce matching accuracy even when a request reaches a provider.
Longer provider-cookie settings do not extend the lifetime of your 180-day privacy choice or authorise collection after rejection. Changing a choice replaces the active document, removes supported first-party vendor cookies and prevents loading unapproved tools. We cannot directly erase another provider’s third-party cookies; its controls and your browser settings remain available.