DEVELOPMENT DRAFT — OPERATOR REVIEW REQUIRED
Cookie Policy
This is a test website. Use synthetic details only. Unconfirmed business details appear in square brackets. These documents must be completed and reviewed before public launch.
Version 2026-10-13.2 · 13 October 2026
Your choice
Accept All, Reject All and Manage Preferences are available with equal prominence. Analytics and marketing start off. Rejecting optional storage does not prevent registration. Cookie Settings lets you change your choice later. An updated consent version, expiry, invalid record or unavailable browser storage causes optional processing to remain off until a new choice is successfully saved.
Storage used by this implementation
- pac_consent_v1 — first-party local storage, not an HTTP cookie. Stores essential/analytics/marketing choices, policy version, choice time and expiry. It remembers your preference for 180 days in that browser. It is not linked to your application and is not copied into a server-side visitor log. An expired value is no longer honoured and is replaced when you choose again. Clearing site storage removes it.
- _ga and _ga_* — optional first-party Google Analytics cookies, only if a valid Measurement ID is enabled and you accept analytics. They distinguish visits and maintain measurement state. Configured lifetime: up to 180 days, without renewal on each visit. Actual storage must be checked with the operator's configured Google property before launch.
- WordPress login cookies — required for administrators who sign in, including wordpress_test_cookie, wordpress_sec_* and wordpress_logged_in_*. These are not required to submit a public cleaner registration. Lifetimes depend on login/Remember Me settings; confirm them when auditing administrator sessions.
Google and advertising
Google Analytics status: not enabled. Basic Consent Mode blocks the Google library entirely until analytics consent. Rejecting analytics sends no analytics event or cookieless consent ping from this implementation. Google advertising storage, advertising user data and ad personalisation remain denied; Google signals and ad personalisation are disabled in the tag configuration. No advertising service is connected, even if you select Marketing.
Analytics is excluded from customer enquiry, registration and confirmation pages. Changing analytics to off disables measurement, removes accessible Google Analytics cookies and refreshes the page to unload its code. Events already sent before withdrawal cannot be recalled by a browser preference change.
Other providers and browsers
Cloudflare serves the site and may use security storage if security features are enabled. No Cloudflare cookie was observed in the sampled unauthenticated HTTP responses; provider configuration and challenge flows still need checking. No payment, video, map, remote font or CAPTCHA integration was found in the current custom site. New integrations require an updated inventory and appropriate consent controls.
Browser controls can clear storage or block it. If preference storage is blocked, this implementation keeps optional analytics off. Cookies are distinct from promotional email/text preferences; manage those through our contact route.