Cookie Policy

Last updated: 2026-11-20

This Cookie Policy describes the cookies and similar technologies used on the BrickHunter website ("the Service"), what they do, how long they last, and how you can change your choices. Our mobile application does not use cookies; storage, analytics, and advertising consent in the app are covered in section 5. It forms part of our Privacy Policy; for the purposes, legal bases, and retention periods behind the processing activities that rely on these cookies, please refer to sections 2.2, 2.12 and 2.13 of the Privacy Policy.

What are cookies?

Cookies are small text files that a website places on your device when you visit it. Similar technologies include localStorage, pixels, and browser databases (IndexedDB). We use the word "cookies" below to cover all of them.

When you are signed in, the pages that offer browser push notifications load the Firebase Cloud Messaging script, which keeps its data in IndexedDB databases on your device: firebase-heartbeat-database (the days on which the script contacted Firebase) and, once you turn on push notifications, firebase-installations-database (a random Firebase installation ID) and firebase-messaging-database (your browser's push subscription and its notification token). They are needed for the push notifications you asked for (Privacy Policy section 2.4), are not used for analytics or advertising, and stay in your browser until you delete its data for our website.

Categories of cookies we use

The cookies on the Service fall into three categories, reflected in our consent banner: strictly necessary, analytics, and marketing. Strictly-necessary cookies are always active because the Service cannot run without them. Analytics and marketing cookies are only set when you have given the corresponding consent in the banner, except as described in section 4 below (Google Consent Mode v2 cookieless pings). The cookies of the sign-in providers (section 6) do not depend on the banner.

1. Strictly necessary cookies

These cookies are required for the Service to function. They cannot be switched off.

| Cookie | Purpose | Duration | | --- | --- | --- | | brickhunter-session | Authentication and session state | 120 minutes from last activity | | XSRF-TOKEN | Protection against cross-site request forgery | 120 minutes from last activity | | remember_web_* | Set only when you tick "Remember me" when signing in: keeps you signed in after the session has expired. Deleted when you sign out; stops working when you change your password or use "Sign out on all devices" | 30 days | | bh_js | Detects whether JavaScript is enabled | 24 hours | | brickhunter-consent-settings | Stores your cookie consent choices | 12 months | | bh_sweepstake_dismissed | Remembers that you closed the sweepstake banner, so it is not shown again during that sweepstake | Until the sweepstake ends | | sso-probed | Records that we have already checked whether you are signed in on our other market websites (single sign-on), so you are not redirected again | 120 minutes | | sso-anchor | Set on brickhunter.net when you sign in: lets our other market websites sign you in automatically (single sign-on). Stops working when you change your password or sign out on all devices | 30 days | | sso-anchor-pending | Set on brickhunter.net for a few minutes while you sign in, so the single sign-on cookie is only set in the browser you signed in with | 5 minutes | | __cf_bm | Set by Cloudflare, our CDN and security provider, when its bot protection evaluates your request; helps tell real visitors apart from automated traffic | Expires after 30 minutes of inactivity | | cf_clearance | Set by Cloudflare after your browser passes a security check, so you are not checked again | 30 minutes |

The two Cloudflare cookies are set only when Cloudflare's bot protection evaluates a request or asks for an additional security check. Cloudflare's up-to-date list of the cookies it may set: developers.cloudflare.com/fundamentals/reference/policies-compliances/cloudflare-cookies.

2. Analytics cookies

These cookies are set only after you accept the "analytics" category in the consent banner.

| Cookie | Set by | Purpose | Duration | | --- | --- | --- | --- | | brickhunter_client_id | Our website's script, on our domain | Stores your GA4 client ID so that our server can link the click-through events it sends to GA4 (Privacy Policy section 2.12) to your visit | Up to 24 months | | brickhunter_session_id | Our website's script, on our domain | Stores the current GA4 session ID for the same server-side events | 30 minutes | | _ga, _ga_* | Google Analytics 4 | Distinguishes users and sessions | Up to 24 months | | _clck | Microsoft Clarity, on our domain | Keeps the Clarity user ID and settings, so that your visits are attributed to the same pseudonymous user | 1 year | | _clsk | Microsoft Clarity, on our domain | Connects the pages you view into a single Clarity session recording | 1 day | | Microsoft cookies MUID, CLID, ANONCHK, MR, SM | Microsoft, on Microsoft's own domains | MUID identifies your browser across Microsoft websites and, according to Microsoft, is used for advertising, site analytics and other operational purposes; CLID records when Clarity first saw your browser on any website that uses Clarity; ANONCHK, MR and SM are technical flags for MUID (whether to refresh it, its synchronisation across Microsoft domains, and whether it is passed on to an advertising cookie, which never happens with Clarity) | See Microsoft's privacy statement |

If you reject the analytics category, none of the cookies above are set: our website's script stores no GA4 client ID or session ID, and Microsoft Clarity is not loaded. If you accept it, our script sets brickhunter_client_id and brickhunter_session_id at once, without reloading the page. Without analytics consent, Google Analytics runs in Google Consent Mode v2 advanced mode - see section 4.

The Microsoft Clarity cookie names above reflect Microsoft's documentation at the time of writing. For the authoritative, always-up-to-date list, see Microsoft's page at learn.microsoft.com/clarity/setup-and-installation/clarity-cookies and the Microsoft Privacy Statement at microsoft.com/privacy/privacystatement.

Links inside our transactional emails (password reset, email verification, price-drop alerts, account-deletion notifications, etc.) carry standard UTM query parameters (utm_source, utm_medium, utm_campaign, utm_content) so that GA4 can attribute the resulting visit to the originating email. These query parameters do not set or read any cookies on their own — they only feed into the GA4 attribution model already described above and operate under the same consent rules.

3. Marketing cookies

These cookies and pixels are loaded only after you accept the "marketing" category in the consent banner.

| Cookie / pixel | Set by | Purpose | Duration | | --- | --- | --- | --- | | Google Ads cookies (e.g. _gcl_au, _gcl_aw) | Google Ads | Conversion measurement and remarketing | Up to 90 days | | Meta Pixel cookies (e.g. _fbp) | Meta | Conversion measurement and remarketing | Up to 90 days | | __oppref | OpenAI Measurement Pixel, on our domain | Stores the ad-click identifier from a ChatGPT ad you clicked, so that later conversions can be attributed to it | 30 days | | __obref | OpenAI Measurement Pixel, on our domain | Randomly generated identifier for your browser, used for conversion measurement | 12 months | | __oaiq_consent cookie and oaiq_consent (localStorage) | OpenAI Measurement Pixel, on our domain | Stores the pixel's consent state | Cookie: 30 days; localStorage: until deleted | | OpenAI cookies (e.g. oai-did, oai-sc, __cf_bm) | OpenAI, on OpenAI's own domains | Device identification and security on OpenAI's services; your browser may send or receive them when the pixel contacts OpenAI's servers | See OpenAI's cookie policy |

The OpenAI Measurement Pixel also sets a short-lived technical cookie (__oaiq_domain_probe) to find out which domain it can store its cookies on, and deletes it immediately.

The cookie names above reflect what we have observed at the time of writing. For the authoritative, always-up-to-date list, see Google's page at business.safety.google/adscookies, Meta's page at facebook.com/privacy/policies/cookies, and OpenAI's page at openai.com/policies/cookie-policy.

4. How to change your consent

When you first visit one of our websites, the first screen of the consent banner offers three choices: accept all cookies, reject all cookies except the strictly necessary ones, or open the settings and choose category by category. Rejecting takes a single click, just like accepting. You can change your choice at any time via the "Cookie settings" link in the footer of every page, on each of our market websites and on brickhunter.net, or by deleting the brickhunter-consent-settings cookie (section 1) from your browser, after which the banner appears again. Your choices are enforced through Google Tag Manager as follows:

  • Google Analytics and Google Ads run under Google Consent Mode v2 in advanced mode (Google documentation). Google tags are loaded on the page, but when you have not granted the corresponding consent they run without setting or reading cookies and send only minimal cookieless signals (timestamp, user-agent, referrer, boolean consent state, ad-click-presence flag, a random per-page-load number). Google uses those signals exclusively for aggregate modelling and does not build an individual user profile from them.
  • Microsoft Clarity is loaded only after you accept the analytics category, and we pass your consent choice on to it. When you reject analytics, Clarity is not loaded at all. If you withdraw a consent you gave earlier, Clarity stops loading, but the cookies it has already set stay in your browser until they expire or you delete them; they are no longer used.
  • The Meta (Facebook) Pixel has no consent-mode equivalent. When you deny the marketing category, the Meta Pixel is not loaded and does not fire at all.
  • The OpenAI Measurement Pixel (ChatGPT Ads) has no consent-mode equivalent either. When you deny the marketing category, it is not loaded and does not fire at all. If you withdraw a consent you gave earlier, the pixel stops loading, but the cookies it has already set stay in your browser until they expire or you delete them; they are no longer used.
  • Other marketing and analytics scripts (if added in the future) will only execute after the corresponding consent has been granted.

You can also configure your browser to block or delete cookies. Please note that blocking strictly-necessary cookies will break core Service features such as login.

5. Mobile app consent

Our mobile application does not use cookies. Instead, Firebase Analytics stores a small amount of data on your device to measure how the app is used. This storage is controlled by an in-app consent screen — the mobile equivalent of the consent banner on this website — using Google Consent Mode v2.

Analytics and advertising storage are denied by default, and you can change your choice at any time in the app's privacy settings. As on this website (section 4), the app uses Consent Mode v2 in advanced mode. While the Analytics choice is denied, Firebase Analytics does not store, read or send the identifier it would otherwise keep on your device (the app-instance ID) and sends only minimal cookieless signals, which Google uses solely for aggregate modelling and from which it builds no individual user profile. Once you allow analytics, Firebase Analytics stores that identifier on your device and measures how you use the app.

The in-app consent screen has a separate Advertising choice — the mobile equivalent of the marketing-cookie category on this website. It is also denied by default. When you grant it, it enables the Google/Firebase advertising signals and the Meta App Events SDK, which measures our Meta app-install advertising (see section 2.18 of the Privacy Policy). On iOS, the Meta SDK additionally requires you to allow tracking in Apple's App Tracking Transparency prompt. If you deny the Advertising choice — or, on iOS, ask the app not to track — the Meta App Events SDK collects nothing. You can change either choice at any time in the app's privacy settings and, on iOS, in your system Tracking setting.

6. Sign-in providers (Google and Facebook)

Our pages load Google's sign-in script while you are not signed in, and some pages, such as sign-in and registration, load Facebook's JavaScript SDK, so that "Sign in with Google" and "Sign in with Facebook" work without a delay. Section 2.2 of the Privacy Policy lists the pages, what the providers receive and the legal basis. These scripts belong to the sign-in function, not to analytics or advertising, so they load regardless of your choices in the consent banner.

| Cookie | Purpose | Duration | | --- | --- | --- | | g_state | Set on our domain by Google's sign-in script when you close the "One Tap" prompt, so that the prompt is not shown again for a while | Determined by Google |

In browsers that use FedCM (such as Chrome), the browser may apply its own pause instead. After you sign out, Google's script also records in a cookie that it should not sign you in again automatically; Google's reference does not name that cookie. Google's script sets these cookies only for the sign-in function itself (to remember that the prompt was closed or that this browser was signed out), so they are strictly necessary for that function and are set without asking for your consent. When the scripts contact Google's or Facebook's servers, your browser may send the cookies that Google or Meta has set on its own domains, depending on your browser settings; we do not read those cookies. Google describes its cookies at policies.google.com/technologies/cookies, Meta at facebook.com/privacy/policies/cookies. To stop these requests, block the scripts with a content blocker; turning off third-party sign-in prompts in your browser only hides Google's One Tap prompt. Sign-in with email and password keeps working.

7. Questions

For any question about this Cookie Policy, contact us at [email protected]. For broader questions about how we process your personal data, see our Privacy Policy.