Cookie Policy
Last updated: 2026-09-23
Overview
This Cookie Policy explains how BixBuz uses cookies and similar storage on our websites.
Essential cookies and local storage
Essential technologies are required for the service and are not used for optional analytics. Examples from the current product:
Supabase Auth session cookies used to keep you signed in.
Theme preference in localStorage.
Cookie consent choice in localStorage key bixbuz_cookie_consent.
Draft listing wizard progress in localStorage while composing a listing.
These remain functional even if you reject non-essential cookies.
The essential items by name: bixbuz-theme (theme preference), bixbuz_submit and bixbuz_submit_edit_<listingId> (listing wizard draft), bixbuz_cookie_consent (storage of the consent decision), login_redirect (the post-sign-in return path, 300 seconds), and the Supabase Auth session cookie (sb-<project-ref>-auth-token).
The exact type, purpose and expiry of each essential item are listed in the table by name below.
Analytics and measurement (consent required)
Only after you accept analytics/measurement consent do we load:
Plausible analytics script (configured via configured domain).
Google Analytics 4 (measurement ID present in the application layout, gated by consent).
A/B experiment cookies named bx_ab_* (assigned only after analytics consent; cleared when you reject non-essential cookies).
You can Accept all, Reject non-essential, open Settings, or reopen Cookie settings later from the footer.
The Google Analytics 4 measurement ID is G-Y40FXCBPB3; the measurement cookies (_ga, _ga_<ID>, _gid, _gat) are created only after consent.
Plausible measures page views without cookies by default, which is why it is listed as cookie-free measurement rather than as a cookie; the measurement script does not load before consent.
The Chatwoot live chat (self-hosted at chat.bixbuz.co.uk) is consent-based too: the widget does not load before consent and only then writes its own cookie (visitor id, conversation state).
A/B experiment cookies (bx_ab_<experimentId>) expire after 30 days; no experiment is currently active in live traffic, so no such cookie is created.
Sign-up and purchase conversion de-duplication uses the bixbuz_analytics_signup_<analyticsId> and bixbuz_analytics_purchase_<session_id> localStorage keys; these are likewise created only after consent.
Cookies and local storage – table by name
The table below lists, by name, the cookies and browser storage BixBuz uses. Essential items are required for the service and keep working after you reject non-essential cookies; consent-based items are created only after you accept analytics consent.
bixbuz_cookie_consent (localStorage) - stores your consent decision - essential - no expiry until you clear browser storage.
bixbuz-theme (localStorage) - light/dark theme preference - essential - no expiry.
bixbuz_submit (localStorage) - listing wizard draft for a new listing - essential - no expiry; cleared when the draft is saved successfully.
bixbuz_submit_edit_<listingId> (localStorage) - listing wizard draft when editing a listing - essential - no expiry.
login_redirect (cookie and sessionStorage) - the path to return to after sign-in - essential - 300 seconds for the cookie, until the browser tab closes for sessionStorage.
sb-<project-ref>-auth-token (cookie, Supabase Auth) - keeps you signed in - essential - for the lifetime of the Supabase Auth session.
bixbuz_analytics_signup_<analyticsId> (localStorage) - de-duplicates the sign-up conversion - consent-based - no expiry; created only after consent.
bixbuz_analytics_purchase_<session_id> (localStorage) - de-duplicates the purchase conversion - consent-based - no expiry; created only after consent.
bx_ab_<experimentId> (cookie) - A/B experiment variant - consent-based - 30 days. No experiment is currently active, so no such cookie is created in live traffic; the policy documents them in advance and rejecting non-essential cookies clears any existing ones.
_ga, _ga_<ID>, _gid, _gat (cookie, Google Analytics 4) - usage measurement - consent-based - the GA4 default lifetimes: _ga and _ga_<ID> 2 years, _gid 24 hours, _gat 1 minute.
Chatwoot visitor id and conversation state (cookie, self-hosted Chatwoot at chat.bixbuz.co.uk) - live chat and support - consent-based - follows the Chatwoot configuration; the widget loads only after analytics consent.
Plausible - sets no cookie - web analytics - consent-based (the measurement script loads only after consent) - no expiry because no cookie is created.
Consent is stored in browser localStorage while cookies live per host, so each of the eight domains (bixbuz.hu, bixbuz.eu, bixbuz.co.uk, bixbuz.de, bixbuz.at, bixbuz.ch, bixbuz.nl, bixbuz.ro) keeps its own consent state.
You give consent with the banner controls Accept all, Reject non-essential and Settings, and can change or withdraw it at any time with the Cookie settings control in the footer; on rejection the GA and bx_ab_* cookies and any queued analytics events are cleared.
How to manage consent
Use the on-site Cookie settings control (footer) to change or revoke analytics consent.
You can also clear site data in your browser. Essential features may set fresh essential storage after reload.
Consent applies per domain: the eight domains (bixbuz.hu, bixbuz.eu, bixbuz.co.uk, bixbuz.de, bixbuz.at, bixbuz.ch, bixbuz.nl, bixbuz.ro) keep separate storage, so a decision taken on one of them does not carry over to another and has to be made on each domain.
Effect of withdrawal: the analytics scripts (Plausible, GA4, Chatwoot) do not load, and the GA and bx_ab_* cookies plus any queued analytics events are cleared; essential storage keeps working unchanged.
More information
See the Privacy Policy for controller identity, processors, retention and your rights.
Cross-references to the Privacy Policy: the data controller is in the Data controller section, the processors and the legal basis for international transfers are in the Processors and international transfers section, retention periods are in the Retention and deletion section, and request handling is in the Your rights section.
In the Categories of personal data section, local storage and cookies are described by reference to this policy.