Last production scan: 2 August 2026. HedgeLens uses a consent-first setup. Anonymous requests to the homepage, contact page and XML sitemap returned no HTTP Set-Cookie header, and the scan found no active Google Analytics, Meta Pixel or Hotjar code.
Current first-party preference
| Name | Provider | Purpose | Duration | Category |
|---|---|---|---|---|
hl_analytics |
HedgeLens | Records whether analytics was accepted or rejected so the banner can respect the choice. | 180 days | Necessary preference |
The preference is created only after you make a choice. Rejecting analytics stores “no”; accepting stores “yes”. Optional analytics code is not currently configured on the public site.
WordPress administration
WordPress may set login, session, security and interface-preference cookies for authorised administrators who sign in. These are not intended for ordinary public visitors and are necessary for restricted site administration.
Analytics
If HedgeLens later configures consent-based analytics, it will remain blocked until you choose “Accept analytics”. Before activation we will update this policy with the provider, cookie names, purposes and durations and repeat the production scan.
Retailer and affiliate destinations
A normal link does not allow HedgeLens to set cookies on the retailer’s website. After you follow a clearly labelled retailer or affiliate link, the destination may set its own cookies or referral identifiers under its own notice. You should review the destination’s controls.
Managing your choice
You can reject optional analytics in the banner. You can also remove the hl_analytics preference using your browser’s site-data controls; the choice banner will then appear again. Blocking all cookies may affect administrator login or saved preferences but should not prevent reading public editorial pages.
Updates
We rescan after material changes to analytics, advertising, embedded media, fonts, consent tools or plugins. Questions can be sent to hello@hedgelens.co.uk.