Leadwave Web Studio

    Cookie Policy

    How we use cookies and similar technologies

    Legal

    Last updated: 20 November 2026 · Website: https://leadwave.uk

    1About this policy

    This Cookie Policy explains how Shanuda Abadeir trading as Leadwave Web Studio uses cookies and similar browser technologies on leadwave.uk. Read it alongside our Privacy Policy. Contact sales@leadwave.uk for questions.

    2What are cookies and similar technologies?

    Cookies are small pieces of information stored by a website or service on your browser. Similar technologies include browser local storage and scripts that access information on your device. They may help secure the website, remember settings, support forms and chat, or measure use. UK PECR rules can apply to these technologies, not just traditional cookies.

    3Categories we use or may use

    • Strictly necessary/security: support site delivery, security and protection against automated abuse. These generally do not require consent where genuinely necessary.
    • Functional preferences: remember a chosen display setting such as light/dark theme. Whether an exemption applies depends on how the feature is implemented and whether it was requested by the visitor.
    • Chat, booking and CRM tools: GoHighLevel/LeadConnector widgets may use cookies or browser storage when loaded or used. Their actual operation must be tested, including when chat opens and a booking is made.
    • Analytics/advertising: a previous review did not identify Google Analytics or Meta Pixel on the site. This is not a guarantee that no analytics or advertising technology is currently installed. If non-essential tracking is used, we will obtain the required consent before it runs.

    4Currently identified technologies

    TechnologyProviderPurposeApprox. durationStatus
    __cf_bmCloudflareBot management and website securityApprox. 30 minutesPreviously observed; reconfirm live
    Light/dark theme preference (browser local storage)Leadwave websiteRemembers display preferenceUntil changed or storage clearedPreviously observed; reconfirm live
    LeadConnector chat/booking storageHighLevel / LeadConnectorSupports chat and booking functionalityTo be confirmedRequires live audit

    This table describes known or potentially used technologies; it is not yet a complete verified live inventory. We will update it with any additional cookie names, providers, purposes and durations identified during testing.

    5Consent and your choices

    Where consent is legally required for non-essential cookies or comparable technologies, we will ask for it before setting or accessing them and provide a way to refuse or withdraw consent as easily as it was given. We will not treat continued browsing as consent. If the site uses only genuinely exempt technologies, a non-essential-cookie banner may not be required.

    You can also manage cookies and site storage through your browser settings. Blocking some technologies may affect chat, booking or other functions. Browser controls do not replace our obligation to obtain consent where required.

    Implementation note: A link to the actual cookie-preference control will be added here once one is deployed. We do not claim a preference centre exists unless it does.

    6Third-party services

    Some technologies are operated by Cloudflare or GoHighLevel/LeadConnector. Those providers may process technical information according to their roles and applicable privacy terms. Using WhatsApp or other external links may take you to a service with its own privacy and cookie practices.

    7Updates and contact

    We may update this policy when our website technologies change. Questions: sales@leadwave.uk. Controller: Shanuda Abadeir trading as Leadwave Web Studio, Bluebell Croft, Houghton Regis, LU5 6SB.

    Before publishing: Run a fresh desktop/mobile browser audit in a clean session, before and after opening chat, booking and submitting forms. Record actual cookie names, storage keys, providers, lifetimes, purposes and whether any non-essential script runs before consent. Implement and test consent/refusal/withdrawal where required, then replace provisional table entries and remove this note.