Cookies and browser storage
What BakeHQ stores on your device, and how to change it.
The current position
BakeHQ itself sets no cookies. Not for advertising, not for preferences, and not for consent — the consent decision deliberately is not a cookie, for the reason given below.
Analytics is enabled in this build. Nothing at all is stored until you decide: if you decline, or simply never answer, no measurement storage is created and no analytics code is loaded.
If you allow analytics, Google Analytics does set cookies. BakeHQ uses it as a measurement destination, and its tag is not loaded at all until you have allowed it. That is the honest position and it is why this page no longer says the site is cookie-free: it is, right up until you say yes.
What would be stored, if you allowed analytics
| Name | Type | Purpose | Retention |
|---|---|---|---|
bakehq.consent.analytics | Local storage | Remembers whether you allowed or declined analytics, so you are not asked again. | Until you clear your browser data |
bakehq.analytics.session | Session storage | A random, non-identifying value that lets a sequence of anonymous events be recognised as one visit. Created only after you allow analytics. | Deleted when you close the tab |
Neither of those two is a cookie. Both live in browser storage, which is never transmitted with a request, and neither identifies you.
The consent value deliberately is not a cookie: a consent cookie would be a cookie set before consent, which is the exact thing being consented to.
Third-party cookies
One third party is involved, and only after you allow analytics: Google Analytics. Its tag sets its own cookies, typically named _ga and _ga_<id>, which distinguish one browser from another so that repeat visits are not counted as new people.
Nothing is loaded before you agree. The tag is injected on the first event after consent is granted and never before, so a reader who declines — or who closes the banner without answering — never contacts Google at all. Advertising features, cross-site signals and personalisation are switched off explicitly.
BakeHQ loads no other third-party scripts, fonts, images or embeds. Its content security policy permits Google’s analytics hosts and nothing else beyond BakeHQ’s own origin, so no other third-party asset could load even if one were referenced by mistake.
Your choice
Your current choice: not yet chosen.
You can change this at any time, in either direction. The site behaves identically whichever you choose. See the privacy notice for what would be collected.