Privacy Policy

Last updated: 2026-11-20

This privacy policy describes how BrickHunter ("we", "us") collects, uses, stores, and shares personal data when you use our website and related services (the "Service"). It is written to meet the requirements of Regulation (EU) 2016/679 (the General Data Protection Regulation, "GDPR") and Hungarian Act CXII of 2011 on the Right of Informational Self-Determination and on Freedom of Information ("Infotv.").

By using the Service, you acknowledge that you have read this policy. Processing activities that rely on your consent only take place after you have given that consent.

1. Data controller

The data controller responsible for processing your personal data is:

  • Name: Geiger Tamás e.v. (sole proprietor)
  • Address: Váci út 83/A 2/208, 1044 Budapest, Hungary
  • Tax ID: HU60384649
  • Email: [email protected]

We have not appointed a Data Protection Officer, as we are not required to do so under Article 37 GDPR. For any data protection matter, you may contact us at the address above.

The competent supervisory authority for the controller is the Hungarian National Authority for Data Protection and Freedom of Information (Nemzeti Adatvédelmi és Információszabadság Hatóság, "NAIH"). Its contact details are listed in section 11.

2. Scope and legal bases of processing

Personal data is any information relating to an identified or identifiable natural person. The table below lists each processing activity we carry out, the categories of data involved, the purpose, the legal basis under Article 6(1) GDPR, and the retention period.

2.1 Account registration and management

  • Data: email address, name, hashed password, market of registration (home market), timezone, notification preferences, terms and privacy policy acceptance timestamps, optional profile-personalisation fields (shopping interests, buying motivation, year of birth — see section 2.14). If you sign in with Google or Facebook, we additionally store the provider user ID returned by that provider.
  • Purpose: to create and maintain your user account, authenticate you, enforce our Terms of Service, and record that you have accepted this policy.
  • Legal basis: performance of a contract between you and us — Art. 6(1)(b) GDPR.
  • Retention: for the lifetime of your account. When you request deletion, your account is retained for a 14-day grace period (see section 2.9) and then deleted.

2.2 Sign in with Google / Sign in with Facebook

  • Data: your Google or Facebook user ID, email address, name, and (if available) whether the email is verified.
  • Purpose: to let you authenticate using an external identity provider instead of a password.
  • Legal basis: performance of a contract — Art. 6(1)(b) GDPR. When you click the sign-in button you initiate the authentication flow, which is necessary to provide the Service.
  • Recipients: Google Ireland Limited and Meta Platforms Ireland Limited act as independent controllers for their own authentication services. See section 3.
  • Retention: the provider user ID is stored for as long as you keep your account linked to that provider, and deleted together with your account.
  • Linking to an existing account: when you sign in with Google or Facebook and an account with the same email address already exists, we link the two and send you an email about it, unless that account is already connected to a different Google or Facebook account: then nothing is linked, and you sign in the way you did before. With Google we do this only when Google vouches for the address, that is for a Gmail address or a Google Workspace account; for any other address you sign in with your password or the way you signed in before, because Google cannot confirm that the address still belongs to the owner of the Google account. If that account's email address had never been confirmed, we cannot know who created it, so the link removes its password, turns off marketing emails for it, makes its shared wishlists private (links shared earlier stop working) and signs out its other sessions and devices; its wishlist and settings are kept. The same applies when the password of such an unconfirmed account is reset with the reset link we email: marketing emails are turned off for it and its shared wishlists are made private, and because the link reached that inbox, the email address then counts as confirmed.
  • Connecting from your settings: while signed in, you can connect a Google or Facebook account to your account yourself, under Settings → Connected accounts or in the app, even if its email address differs from yours. To protect your account, this needs a confirmed email address and a sign-in within the last 15 minutes. We store the provider user ID as described above, refuse a provider account that is already connected to another account, and email you about every new connection. You can remove the connection in the same place (this needs a password on the account).
  • Sign-in scripts before you click: so that the sign-in options work without a delay, our pages load the providers' scripts before you choose one. Google's sign-in script (Google Identity Services) loads on every page of our websites while you are not signed in, once the page has loaded (on the sign-in and registration pages, at once), except the page where you accept our terms after a social sign-in. It may show Google's "One Tap" prompt, which offers to sign you in with a Google account your browser is signed in to; if you have signed in to our Service with that Google account before, the prompt can sign you in without a further click, but not after you sign out, until you next sign in with Google. Facebook's JavaScript SDK loads on the sign-in, registration, password-reset, email-verification and account-deletion pages, on the page where you accept our terms after a social sign-in, and on the page where you authorise our browser extension. In Settings → Connected accounts, a provider's script loads only when you click its Connect button.
  • What the providers receive: as with any request your browser makes, Google or Meta receives your IP address, your browser's user-agent string and the address of the page you are on, and your browser may also send cookies that Google or Meta has set on its own domains, depending on your browser settings. We receive nothing from the provider until you choose to sign in. In browsers that use FedCM (Federated Credential Management, such as Chrome), the browser shows Google's prompt itself; according to Google, FedCM lets sign-in work without third-party cookies. If you close the prompt, or after you sign out, Google's script may store a cookie on our domain, so that the prompt is not shown again for a while or does not sign you in again automatically (section 6 of the Cookie Policy). These scripts serve sign-in only, not analytics or advertising, and they load regardless of your choices in the consent banner.
  • Legal basis for loading the scripts: our legitimate interest in letting visitors sign in with Google or Facebook at once and in offering returning Google users the One Tap prompt — Art. 6(1)(f) GDPR. What the provider does with these request data is governed by its own privacy policy (section 3.3). You can object (section 5), and you can stop these requests yourself by blocking the scripts with a content blocker. Turning off third-party sign-in prompts in your browser settings, or Google Account sign-in prompts in your Google Account, hides Google's One Tap prompt but does not stop the script from loading. The rest of the Service, including sign-in with email and password, keeps working.

2.3 Wishlist, price alerts, and preferences

  • Data: product references you add to your wishlist, target prices, personal notes on wishlist items (optional, up to 500 characters), alert preferences (notify on any price drop, notify on back in stock), the market you were browsing when you added each item.
  • Purpose: to provide the wishlist and price-alert features you have requested.
  • Legal basis: performance of a contract — Art. 6(1)(b) GDPR.
  • Sharing a list (optional): each list is private until you turn on sharing for it. Sharing creates a link that cannot be guessed. Anyone you give the link to (and anyone they pass it on to) can see, without signing in, the list's name, the sets on it with their current best prices, and your first name as shown in the sharing dialog (taken from the name on your account). Your notes, target prices, alert settings, other lists and email address are not shown. The shared page tells search engines not to index it. Turning sharing off, or deleting the list, revokes the link at once; turning sharing on again creates a new link. While an account deletion is pending, the link shows the list as unavailable. Legal basis: performance of a contract (Art. 6(1)(b) GDPR), as you ask us to make the list available to the people you give the link to.
  • Retention: for as long as the entries remain in your wishlist, and until the account is deleted (entries are deleted together with the account). Each price alert we send is also stored in your in-app notification history (the notification bell on the website and the notification list in the app), which we keep for 12 months and then delete automatically, and in our alert log (which alert we sent about which set and shop, the prices and when), which we use to avoid sending you the same alert twice and to show your alert history, and keep for as long as your account exists.

2.4 Push notification tokens

  • Data: Firebase Cloud Messaging (FCM) device tokens registered by your browser or by our mobile application; for each token, the platform (browser, Android or iOS), whether it is active, and when a notification was last delivered to it; for a token registered by the mobile application, the app sign-in it belongs to.
  • Purpose: to deliver browser and mobile push notifications you have opted in to (for example, price-drop alerts), and — on the mobile application — to send occasional silent background messages that refresh the home-screen wishlist widget when your wishlisted products' prices or availability change. Silent messages display no notification; they only prompt the app to refresh in the background and carry no personal data beyond a message-type marker.
  • Legal basis: your consent — Art. 6(1)(a) GDPR. You give consent in two steps: by accepting the browser or operating-system prompt, and by enabling push notifications in your account settings. If a browser already allows notifications from our site, signing in there with push notifications enabled in your account registers that browser for them without a new prompt; this also applies to a browser shared with someone who allowed notifications earlier. Logging out removes the browser's registration. You may withdraw consent at any time by disabling notifications in the Service or revoking the browser / OS permission.
  • Retention: active tokens are retained while you keep push notifications enabled. Tokens that become inactive (for example, when your browser revokes the subscription) are deleted 30 days after they were last seen active. A token registered by our mobile application is also deleted when you sign out of the app, and within two days after your app session expires (after 90 days without use). We keep at most 10 active tokens per account: when a new device or browser registers, the oldest active tokens beyond that number are deleted. All tokens are deleted when your account is deleted.
  • Push engagement records: when your browser shows a push notification from us, or you click it, we record which notification it was, the product and shop it was about, whether it was shown or clicked, and the time, linked to your account. We use these records to measure whether our alerts are useful, for example how many price-drop alerts are opened. They are only created for push notifications you have opted in to. The legal basis is our legitimate interest in measuring whether our alerts are useful (Art. 6(1)(f) GDPR); you can object at any time (section 5). They are deleted automatically within 90 days of being recorded, and at once if your account is deleted.

2.5 Transactional email

  • Data: your email address, name, and the content of the message (for example, a price-drop link, an email-verification link, or a password-reset link).
  • Purpose: to send emails that are strictly necessary to operate the Service — email verification, password reset, email-change confirmation, account-deletion confirmation, security alerts (a password was added to or changed on your account, a Google or Facebook account was linked to it, a scheduled account deletion was cancelled), a download link for the copy of your personal data you requested (see section 5), and price-alert notifications you have subscribed to.
  • Legal basis: performance of a contract — Art. 6(1)(b) GDPR.
  • Recipient: Sendinblue SAS (operating as Brevo) — see section 3.
  • Retention: for the duration of your account. Delivery metadata (opens, bounces) held at Brevo is retained according to Brevo's retention policy. When you request a password reset, we store your email address and a hash of the link's token. The link works for 60 minutes; the request is deleted when you use the link, within about two hours of the request at the latest, and at once when your account is deleted.

2.6 Marketing email and audience segmentation

  • Data: we store you as a contact at Brevo with the following identity fields — email address, name, market, locale, timezone, registration date, email-verified flag, authentication provider (password / Google / Facebook) — and the following segmentation attributes derived from your activity on the Service: your consent states (marketing, email notifications, push notifications), your optional profile answers (shopping interests, buying motivation, year of birth — see section 2.14), activation signals (whether you have any wishlist items, number of wishlist items, the date of your first wishlist add, the last date you were active on the Service), the slugs of the top five LEGO themes present in your wishlist, up to twenty set numbers from your wishlist, the slugs of the top five themes among the products you have clicked out to shops in the last 30 days, the slugs of the top five themes among the products you have viewed in the last 30 days, and the total number of shop click-outs you made in the last 30 days. We never send user-generated free text (wishlist notes, category names), credentials, or provider-specific IDs (Google / Facebook IDs) to Brevo.
  • Purpose: to send you personalised messages about LEGO sets, price deals, and Service updates we believe are relevant to you, including a weekly selection of the best current offers from partner shops with which we have an affiliate relationship (we may receive a commission if you buy through these links), and occasional partner deal alerts — at most one per week — when a partner shop has the lowest price we track, well below the recommended retail price, on a popular set from a LEGO theme you have shown interest in through your wishlist, your click-outs or the themes you viewed in the last 30 days (we record the date of the last such alert on your account to enforce that limit); and to compute per-market audience segments (for example, opted-in users whose wishlist or recently-browsed themes overlap a specific LEGO theme) so that we can run partner-sponsored marketing campaigns from within Brevo without exposing any user data to partners.
  • Legal basis: your consent — Art. 6(1)(a) GDPR. We only add you to a marketing list and only send marketing email if you have explicitly opted in, either via the dedicated checkbox at registration or by turning on "Tailored deals & recommendations" in your account settings. You may withdraw consent at any time via the "unsubscribe" link in every marketing email or from your account settings. A withdrawal in your account settings removes you from every market list at Brevo immediately; a withdrawal registered at Brevo (for example your mailbox provider's one-click unsubscribe, or a spam report) is applied to your account within a day, as is a block Brevo places on your address because mail to it bounces permanently. We then delete every contact attribute we stored at Brevo and keep only your email address there, marked as not consenting (see Retention). Turning marketing on, at registration or in your account settings, lifts any block Brevo placed on your address, but only once your email address is verified: if you turn it on before confirming your address, we lift the block when you confirm it. Until then we send you no marketing email. To keep that consent, we record when you last turned marketing on, when you last changed your email address while it was on (we then also lift any block Brevo placed on the new address), and when Brevo confirmed it, so an older withdrawal Brevo still shows does not switch off your newer consent. Withdrawal does not affect the lawfulness of processing carried out before the withdrawal.
  • Recipient: Sendinblue SAS (Brevo) — see section 3.
  • Retention: contact attributes are retained at Brevo until you withdraw consent or delete your account. Event data (workflow triggers such as user_registered, wishlist_add, price_drop_notified) are retained at Brevo according to Brevo's 90-day default event-retention period. When you delete your account (section 2.9), your Brevo contact is removed at the end of the 14-day grace period; Brevo's event history decays separately on the schedule above. Once consent is withdrawn while the account still exists, Brevo keeps only your email address, marked as not consenting, solely to ensure we do not email you again; if you never opted in, we keep no contact for you at Brevo, unless Brevo itself has blocked your address.
  • Prize draws: from time to time a market runs a prize draw (sweepstake), announced on its /sweepstakes page together with its own official rules (prize, period, conditions). Every registered user whose home market is that market and who meets the published conditions by the end of the draw takes part automatically; marketing consent is not required, and turning it on or off does not change your chances. To decide who takes part, we check your home market, your registration date, whether your email address is verified, whether your account is scheduled for deletion, the number of products on your wishlist (and when you added them) and, for draws reserved for app users, whether you have the BrickHunter mobile app installed (see section 2.18). After the draw closes, we export the email address, name, market and wishlist size of the users who take part to a file stored on our own servers, use it only to run the draw and contact the winners, and delete it once the draw is complete, and in any case 90 days after the export at the latest. Legal basis: our legitimate interest in running prize draws for our members and rewarding those who use the Service — Art. 6(1)(f) GDPR. Taking part costs you nothing and needs no action from you, and the draw uses only data we already hold for your account. You may object at any time by writing to [email protected]: we then record that you do not take part in that draw, and this does not affect your account.

2.7 Outbound click tracking

  • Data: for every click on a link or button that takes you to a shop, we log: product ID, shop ID, market ID, referring user ID (if logged in), the address of the shop page the link leads to, the address of our page you clicked from (without its parameters, so tracking parameters such as ad click IDs are never stored), a keyed HMAC-SHA256 hash of your IP address, user-agent string, Accept-Language header, the GA4 client ID and session ID associated with your visit (only if you have accepted analytics cookies), a SHA-256 hash of your email address used as the GA4 user ID (if logged in and only if you have accepted analytics cookies), whether the click looks automated, whether your browser runs JavaScript, the time between opening the product page and the click, whether you used the shortcut to the cheapest offer, and a timestamp.
  • Purpose: to measure which offers are most useful, to provide aggregated shop and product performance reports, to detect fraudulent or automated traffic, and to reconcile outbound traffic with our retailer partners.
  • Legal basis: our legitimate interest in running and improving the Service and preventing abuse — Art. 6(1)(f) GDPR. The data we store is not directly identifying (the click record never contains your IP address in plain text — only a keyed hash).
  • Retention: aggregated shop statistics are retained indefinitely, because they do not identify you. The GDPR-relevant fields attached to each click record - the hashed IP, user agent, Accept-Language header, GA4 client ID, GA4 session ID, GA4 user ID (the email hash), and (if any) the link to your user account - are removed after 12 months, so that only non-identifying statistics remain. If you delete your account before that point, these fields are removed immediately from the click records linked to your account.

2.8 Session cookies and authentication

  • Data: a session identifier stored in the brickhunter-session cookie, and — while the session is active — the user you are logged in as, your active market, a keyed HMAC-SHA256 hash of your IP address (not the IP itself), your user agent and, if you are not signed in, whether you have already clicked through to a shop on that market website during the session, so that the click-through events we send (sections 2.12 and 2.13) can tell a first click-through from a repeat one.
  • Purpose: to keep you logged in, to protect against session-hijacking, and to display the correct market.
  • Legal basis: performance of a contract — Art. 6(1)(b) GDPR. Session cookies are strictly necessary for the Service and do not require a consent banner.
  • Retention: the session cookie expires 120 minutes after your last activity, or sooner if you log out. Session records are garbage-collected automatically afterwards. If you tick "Remember me" when signing in, a remember_web_* cookie keeps you signed in for 30 days, also after the session has expired; it is deleted when you sign out and stops working when you change your password or use "Sign out on all devices" (see section 8).

2.9 Account deletion

  • Data: your account email, the scheduled deletion date.
  • Purpose: to let you exercise your right to erasure. When you request deletion, your account is marked with a scheduled deletion date 14 days in the future and a verification email is sent. You can also request deletion without signing in, on our account deletion page: we email you a confirmation link, and you confirm with your password or, if your account has no password because you sign in only with Google or Facebook, with the emailed link alone and a confirmation button. During the grace period you can cancel the deletion from your account settings or in the app; signing in does not cancel it. We email you whenever a scheduled deletion is cancelled, so that you notice if someone else cancelled it. At the end of that period, the account is processed.
  • Legal basis: compliance with a legal obligation under Art. 17 GDPR — Art. 6(1)(c) GDPR. The 14-day grace period is a legitimate-interest measure (Art. 6(1)(f)) to let you cancel an accidental or unauthorised deletion request.
  • What is deleted: your user record, your wishlists (their items and the lists themselves), your alerts log entries, your in-app notification history, your device tokens, your push engagement records, your theme-level browsing history (section 2.15), all API tokens, your sign-in sessions, your single sign-on tokens, any pending browser-extension authorization codes (section 2.16), any pending password reset request, any record that you do not take part in a prize draw (section 2.6), the link between your account and your app installations, and any copy of your data prepared for download (section 5). In the clicks table, personal identifiers (hashed IP, user agent, Accept-Language header, GA IDs, and link to your user ID) are removed — the click events themselves remain as anonymous shop statistics.
  • Google Analytics: the analytics data linked to your account in Google Analytics 4 (the events stored under the GA4 user ID described in section 2.12, a hash of your email address) is held by Google, not by us. When your account is erased, we ask Google, through its user deletion function, to delete that data. Google carries out the request on its own schedule. The request covers the GA4 user ID of the email address your account has when it is erased, so it does not cover events stored under an earlier address (before an email change), nor analytics data that was never linked to your account.
  • If you did not cancel it yourself: write to us from your account's email address. We then end every session and sign-in on your account, replace your password with one nobody knows (and, if needed, remove the link to your Google or Facebook account), make your shared wishlists private, turn marketing emails off (you can opt in again in Settings), cancel any pending email address change, and email you a link to set a new password, and, if you ask, schedule the deletion again or carry it out at once. We keep a record of these steps (your user ID, the steps taken, the date and our support reference, with no email address or other contact details) to document the incident, as Art. 33(5) GDPR requires (Art. 6(1)(c) GDPR), and delete it automatically after 24 months.
  • Backups: we back up our database once a day, so that we can restore the Service after a technical failure. Each backup is kept for 14 days on the server that runs the Service (DigitalOcean, Frankfurt data center, see section 3.1), where only the operator can access it, and is then deleted. Data deleted from the Service, including the data of an erased account, therefore remains in the backups made before the deletion until they are deleted, at the latest 14 days after the deletion.
  • Retention: the account record is deleted on the scheduled date. See section 2.7 regarding anonymised click data.

2.10 Customer support communication

  • Data: your email address and the content of the messages you send to us.
  • Purpose: to reply to your support requests, complaints, or data-subject requests.
  • Legal basis: performance of a contract — Art. 6(1)(b) GDPR for service-related requests; compliance with a legal obligation — Art. 6(1)(c) GDPR for data-subject requests we must answer under Chapter III GDPR.
  • Retention: 3 years from the last message, to evidence that we answered within the legally required timeframes. Data-subject requests we have acted on are retained for 3 years to evidence compliance.

2.11 Security and access logging

  • Data (application and API logs): server application logs containing request metadata (URL, HTTP status, timing), error stack traces, and — for rate-limit decisions and abuse detection — keyed HMAC-SHA256 hashes of IP addresses. Where a logged action concerns an email address (for example an email address change or a failed request to our email service provider), we log a keyed hash of the address, never the address itself. For requests to our mobile-app and browser-extension API (paths under /api/), we additionally keep a per-request access log recording the HTTP method, endpoint, status code, response time, the API client and installation identifiers, the authenticated user ID (only when the request is authenticated), the user-agent string, and the same keyed hash of the IP address. For every push notification we send, we also log its delivery outcome: the notification type, whether it was sent to browsers or to mobile devices, your user ID, how many of your registered devices received it, the error codes Firebase Cloud Messaging returned for those that did not, and the internal record numbers of the affected device tokens (never the tokens themselves). Apart from the web server logs described below, which are deleted after at most 15 days, we never store IP addresses in plain text.
  • Data (web server access and error logs): for every request to our websites, our web server logs the time, requested host and URL (with access tokens and signatures removed), HTTP method and status, response size and time, the referring website (domain only), user-agent string, the country Cloudflare derived from the connection, the Cloudflare request ID, and your IP address in plain text. Error messages from the web server also record the IP address of the request that caused them. Daily summaries of these logs (request counts per path, status code and IP address; slowest requests; blocked requests) are generated for security review.
  • Data (failed background tasks): some tasks, such as sending an email, run in the background. If one fails for good, we keep a record of it with the error message and the task's data, so that we can find the cause and run it again. Such a record can contain your email address. Task data that includes an email address, a signed link or a token is stored encrypted; the error message is not.
  • Data (browser security reports): when your browser blocks or flags content on one of our pages under our Content Security Policy, it may send us a report. We keep the address of the page (without its query string or fragment, which can contain campaign or click identifiers), the address of the blocked resource and of the referring page (shortened the same way) and the policy rule involved, merged with identical reports into one entry with a count. We store no IP address, account or other identifier with these reports.
  • Purpose: to detect, investigate and stop security incidents, attacks and abuse (for example brute-force login, credential stuffing, scanning, scraping, denial-of-service, rate-limit evasion against the API, or attempts to bypass our CDN), to monitor API error rates and service reliability, and to diagnose errors and outages. Reviews of these logs are carried out with the help of an AI assistant (Anthropic's Claude) under our supervision, with read-only access.
  • Legal basis: our legitimate interest in ensuring network and information security and in operating a reliable service — Art. 6(1)(f) GDPR, see Recital 49 GDPR. In the application and API logs, IP addresses are stored only as keyed hashes; where a request is authenticated, the access-log entry may be linked to your account through your user ID solely for the purpose of investigating abuse of that account, and a push delivery entry is linked to it solely to find out why a notification did not reach your devices. Plain IP addresses appear only in the web server logs, which are kept for at most 15 days and are readable only by us and a read-only analysis account.
  • Recipients: Cloudflare, Inc., through whose network every request to our websites passes, and Anthropic, which provides the AI assistant used for log reviews — see sections 3.1 and 3.6.
  • Retention: 14 days for application logs (including push delivery logs), API access logs and records of failed background tasks, at most 15 days for web server access and error logs, 14 days for the daily summaries, and 14 days after the last identical report for browser security reports, after which they are deleted automatically.

2.12 Web analytics (Google Analytics 4, Microsoft Clarity)

  • Data (with analytics consent): GA4 client ID (stored in the brickhunter_client_id cookie), GA4 session ID, page views, events (searches, wishlist actions, outbound clicks, etc.), approximate location derived from IP (the IP itself is not stored by GA4 in identifiable form — Google truncates it before storage), device and browser details.
  • Data (without analytics consent): no Google Analytics cookies (_ga, _ga_*) are set or read, and no persistent user or device identifier is transmitted. Google Analytics runs in Google Consent Mode v2 in advanced mode (see Google's documentation): a cookieless "ping" is sent to Google containing only the timestamp, the user-agent string, the referrer URL, a boolean consent state, a flag indicating whether the current or a prior page contained ad-click information in the URL (such as a gclid / dclid), and a random number generated on each page load. Google states that the IP address received as part of the network request is not stored or logged. Google uses these signals solely to produce aggregated, modelled reports — no individual user profile is built from them.
  • Server-side events: when you click through to a shop, our server reports the click to GA4 as a conversion event (purchase) using the Measurement Protocol. If you have accepted analytics cookies, the event carries your GA4 client ID and session ID from the brickhunter_client_id and brickhunter_session_id cookies, so GA4 counts it as part of your visit. If you have not, the event is sent with a random identifier generated for that event alone, which is not linked to you or to your browser, without a session ID and with the advertising consent signals set to denied; in that case no GA4 identifier is stored with the click either (see section 2.7).
  • User-identifying signals (only with marketing consent): when you are signed in and have granted marketing consent, the server-side event additionally carries a SHA-256 hash of your email — both as the GA4 user_id (for cross-device attribution) and in the user_data.sha256_email_address field, which Google uses, together with its own signed-in users' data, to improve audience reports, conversion attribution, and ads-measurement accuracy. Only the SHA-256 hash is sent; the plaintext email never leaves our servers, and the hash cannot be reversed by Google. If you are not signed in, or if you have not granted marketing consent, no user-identifying hash is sent in either field.
  • Microsoft Clarity (only with analytics consent): once you accept analytics cookies, Google Tag Manager also loads Microsoft Clarity, which records how our pages are used so that we can watch session replays, view heatmaps and find usability problems. Clarity collects your interactions with the page (page views, clicks and taps, scrolling, mouse movement, text selection, window resizing), the structure of the pages as they are displayed, the names of events such as searches, wishlist actions, sign-ins and registrations, technical errors and performance data, and device and browser details. It links them with a pseudonymous identifier: Clarity's own user ID, stored in the _clck cookie, and, as custom identifiers, the GA4 client ID (which Clarity hashes in your browser before sending it) and the GA4 session ID of your visit. Like any server your browser contacts, Microsoft also receives your IP address, from which Clarity determines your approximate location. Clarity masks what you type or select in form fields and drop-down menus in your browser, so it never reaches Microsoft; in addition, we use Clarity's strict masking mode, which also masks all text on the page: recordings show the page layout and your interactions, not the text. We pass your consent choice on to Clarity. Clarity also uses Microsoft's own cookies on Microsoft domains (such as MUID), which, according to Microsoft, are used for advertising, site analytics and other operational purposes (see the Cookie Policy). Without analytics consent, Clarity is not loaded at all.
  • Purpose: to understand how the Service is used and improve it; with Microsoft Clarity, also to find usability problems through session replays and heatmaps.
  • Legal basis: your consent — Art. 6(1)(a) GDPR. You may grant, reject, or change your choice at any time via the consent banner or the cookie-settings link in the site footer.
  • Recipients: Google Ireland Limited and Microsoft Ireland Operations Limited - see section 3.
  • Retention: GA4 retains event-level data for 14 months by default. Microsoft keeps Clarity session replay data for 30 days, and click and heatmap data, as well as recordings we label or mark as favourites, for 9 months, after which it is deleted. Our own cookies brickhunter_client_id (up to 24 months) and brickhunter_session_id (30 minutes) are used for GA4 correlation; our website's script sets them only after you accept analytics cookies, immediately and without reloading the page, and never otherwise.
  • Email link tracking: outbound 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 email it originated from. The UTM parameters themselves describe the email type and subject — not the recipient — and do not set or read any cookies on their own. When you click such a link, GA4 records the visit subject to the same consent-based behaviour described above: with analytics consent the visit is attached to your GA4 client ID, without analytics consent only the cookieless modelled signal is sent.

2.13 Advertising (Google Ads, Meta Ads, ChatGPT Ads)

  • Data (with marketing consent): conversion events, page views, and interactions you make while on the Service, sent to Google Ads, the Meta (Facebook) Pixel, the Meta Conversions API, and the OpenAI Measurement Pixel for measurement and remarketing. Depending on the platform's behaviour, this may include your IP address, cookie identifiers, and a hashed version of your email (for Google's Enhanced Conversions, Meta's Advanced Matching, and OpenAI's automatic advanced matching).
  • Data (without marketing consent):
    • Google Ads continues to run in Google Consent Mode v2 advanced mode. No Google Ads cookies (_gcl_*) are set or read, and any gclid / dclid identifiers are redacted from the outgoing network requests. Cookieless pings with the same minimal signals described in section 2.12 are still sent to Google, and are used solely for aggregate conversion modelling (to estimate, at an aggregate level, conversions that would otherwise have been measured with consent). No individual user is tracked, profiled, or retargeted.
    • Meta Pixel does not implement an equivalent consent-mode mechanism. When you deny the marketing category, the Meta Pixel is not loaded and does not fire at all — no request is made to Meta from the Service in that case, apart from loading the Facebook sign-in SDK on the pages listed in section 2.2, which serves sign-in, not advertising.
    • OpenAI Measurement Pixel does not implement a consent-mode mechanism either. When you deny the marketing category, it is not loaded and does not fire at all, and no request is made to OpenAI from the Service.
  • ChatGPT Ads measurement (OpenAI Measurement Pixel): when you have granted marketing consent, Google Tag Manager loads OpenAI's Measurement Pixel, which measures visits and conversions resulting from our ads in ChatGPT. The pixel stores two identifiers in first-party cookies on our domain: the ad-click identifier that OpenAI adds to the link (the oppref parameter) when you click one of our ads in ChatGPT, and a randomly generated identifier for your browser (see the Cookie Policy). It sends OpenAI the name and details of the event (such as a page view or a conversion), the address of our website, a timestamp, these identifiers, and, as with any request your browser makes, your IP address and browser user-agent. The pixel also uses OpenAI's automatic advanced matching, which OpenAI does not let us switch off: it detects customer information present on our pages, such as an email address you enter in a sign-in or registration form, and sends OpenAI only a SHA-256 hash of it, computed in your browser, which OpenAI uses to match conversions to ad interactions. The plaintext value is not sent, but the hash is still personal data.
  • Server-side conversion events (Meta Conversions API): when you have granted marketing consent, conversion-relevant events (specifically: outbound clicks to partner shops) are also sent to Meta from our server using the Meta Conversions API. The server-side event carries: a SHA-256 hash of your email if you are signed in (em), your IP address (client_ip_address, transmitted to Meta over TLS — Meta hashes it on receipt and does not retain the plaintext), your browser user-agent (client_user_agent), and the values of the _fbp and _fbc cookies if your browser has them. Meta uses these signals together with the browser-side Pixel signals to improve ad measurement, attribution, and audience matching despite browser-level tracking limitations (third-party cookie blocking, ad-blockers). The server event is only dispatched when you have granted marketing consent — without that consent, no server event is sent. If you are signed out, the em field is omitted.
  • Purpose: to measure the effectiveness of our advertising campaigns and, when you have given marketing consent, to show you relevant ads on third-party platforms.
  • Legal basis: your consent — Art. 6(1)(a) GDPR. Tag firing is controlled through Google Tag Manager according to your choices in the consent banner. You may withdraw consent at any time via the cookie-settings link.
  • Recipients: Google Ireland Limited, Meta Platforms Ireland Limited, and OpenAI Ireland Limited - see section 3.
  • Retention: governed by the third-party platform's retention policies. We do not store advertising identifiers on our own servers.
  • Up-to-date third-party information: Google maintains an up-to-date list of cookies used by its advertising products at business.safety.google/adscookies. Meta publishes the current list of cookies it sets at facebook.com/privacy/policies/cookies. OpenAI publishes its cookie policy at openai.com/policies/cookie-policy. These pages take precedence over the cookie names listed in sections 2 and 3 of our Cookie Policy if they diverge.

2.14 Profile personalisation

  • Data: your answers to three voluntary onboarding questions — who you typically shop for (yourself, children, extended family, friends/acquaintances), what matters most to you when you buy (lowest price, best value for money), and your year of birth. All three questions are optional and individually skippable; no answer is required to use the Service. We collect year of birth only, never an exact date, and use it solely to place users into broad age bands for targeting and for our aggregate usage statistics (section 2.20). We also store an internal timestamp for each question recording when you last engaged with it.
  • Purpose: to personalise the on-site experience and — once you have given explicit marketing consent (section 2.6) — to inform partner-coupon targeting via Brevo.
  • Legal basis: our legitimate interest in personalising the on-site experience — Art. 6(1)(f) GDPR — for the on-site use; your consent under Art. 6(1)(a) GDPR for the Brevo-based marketing use, which is only activated if you have opted into marketing email.
  • Retention: for the lifetime of your account. These fields are deleted together with your account at the end of the deletion grace period (section 2.9). You may clear or change any of the three answers at any time from your account settings.

2.15 Aggregated browsing history (theme-level)

  • Data: while you are logged in and you have turned on "Tailored deals & recommendations" (see section 2.6), we log a theme-level record for each LEGO product-detail page you visit — specifically: your user ID, the LEGO theme ID of the product you viewed, the market on which you viewed it, and a timestamp. We do not log the individual product, the price you saw, the shop you clicked through to (click-outs are a separate processing activity — section 2.7), nor anything about the page layout or your scroll/interaction behaviour. We skip known bot traffic.
  • Purpose: to determine, at a theme level, which parts of the LEGO catalogue are currently of interest to you, so that the weekly product-lifecycle digests (newly-announced sets, newly available to preorder or buy, entering "Retiring soon") and other marketing messages described in section 2.6, including partner deal alerts, can be filtered or prioritised around themes you actually engage with.
  • Legal basis: your consent — Art. 6(1)(a) GDPR. No theme-view record is written unless you are logged in AND you have explicitly opted into marketing. Turning marketing off stops further theme-view logging immediately; existing theme-view records expire on their own schedule below. Anonymous visitors and logged-in users who have not opted in never have theme-view records created.
  • Retention: 90 days. Theme-view records older than 90 days are deleted automatically by a scheduled daily job. The 90-day window matches the 30-day recency window used in your Brevo segmentation attributes (see section 2.6) with a buffer for operational reprocessing. On account deletion, all of your theme-view records are removed together with your account.

2.16 Browser extension authorization

  • Data: when you sign into the BrickHunter browser extension (Chrome or Firefox companion), we record an OAuth 2.0 authorization code bound to your user account, the extension's registered redirect URI, the PKCE code challenge, the market you selected during the consent step (optional, for telemetry), and timestamps for issue / expiry / consumption. The code is hashed at rest with HMAC-SHA256 and is single-use with a 60-second lifetime. After successful exchange we issue you a long-lived API access token labelled "extension" attached to your account, identical in nature to the access tokens issued to our mobile app.
  • Purpose: to let the extension act on your behalf — read and modify your wishlist, receive price-drop alerts, and identify products you are viewing on partner shop pages — without you having to enter your password again. Authorization codes themselves are operational artefacts; only the resulting access token is retained.
  • Legal basis: performance of the contract — Art. 6(1)(b) GDPR. The extension cannot function on your account without an access token.
  • Retention: authorization codes expire after 60 seconds and can no longer be used after that. An automated cleanup job that runs every hour deletes a code once it is more than 5 minutes past its expiry, so a code is deleted at the latest about 65 minutes after it expires. Access tokens persist until you revoke them (extension logout, "Log out everywhere" from settings, password reset, or account deletion) or until 90 days after their last use; expired tokens are deleted by a daily cleanup job. All extension-issued tokens are revoked together with the rest of your tokens on account deletion.

2.17 Google CSS service applications

  • Data: if you apply for our free Google Comparison Shopping Service (CSS) on the /css page, we collect your full name, company name, business email address, and one or more Google Merchant Center account IDs, together with the locale and market you applied from and the timestamp on which you accepted the CSS Service Terms of Service. If you separately choose to grant us a user role on your Google Merchant Center account, that grant is made and managed inside Google Merchant Center, not stored by us; granting it is optional.
  • Purpose: to receive and evaluate your application, to associate your Merchant Center account with our CSS, and to contact you about the CSS service (including a confirmation email). Application details are also sent to our internal CSS mailbox so we can act on them.
  • Legal basis: the taking of steps at your request prior to, and the performance of, the free CSS service arrangement — Art. 6(1)(b) GDPR — together with our legitimate interest in evaluating and administering applications for a service we offer free of charge — Art. 6(1)(f) GDPR.
  • Recipient: the confirmation email is delivered via Sendinblue SAS (Brevo) — see section 3.2. Applications are not shared with any other third party. Note that this application is a business-to-business relationship separate from any personal user account you may hold.
  • Retention: application records are retained for as long as your account is associated with our CSS and for a reasonable period afterwards to evidence the arrangement; applications that do not proceed are deleted within 24 months.

2.18 Mobile application

Our mobile application (BrickHunter) processes the same account data as the website, plus the following mobile-specific data:

  • Device identifier. A per-installation identifier (Identifier for Vendor on iOS, or an equivalent app-scoped identifier on Android) secures API access (installation token) and prevents abuse. Legal basis: legitimate interest (Art. 6(1)(f) GDPR) in securing the Service.

  • Account link. When you use the app while signed in, we record which account last signed in on that installation. We use this to contact you about the app, for example to tell you about an urgent update, and to check whether you are eligible for promotions reserved for app users, such as prize draws. We only send you promotional messages if you have agreed to receive marketing. The link stays after you sign out, is replaced when another account signs in on the installation, and is removed when your account is deleted. Legal basis: legitimate interest (Art. 6(1)(f) GDPR) in keeping the app secure and up to date and in running promotions reserved for app users.

  • Push notification token. If you enable notifications, a Firebase Cloud Messaging (FCM) device token is registered with us to deliver the price-drop and target-price alerts you configured. We also use this token to send silent background messages that keep the home-screen wishlist widget up to date: these display no notification, wake the app only to refresh the widget in the background, and carry no personal data beyond a message-type marker. You can disable notifications at any time in the app or your device settings, which removes the token. Legal basis: performance of the service you requested (Art. 6(1)(b)) / your consent to notifications.

  • Camera (barcode scanner). When you use the barcode scanner, the camera image is processed on your device only to decode the EAN/GTIN. No image is stored or transmitted; only the decoded number is sent to look up the matching set. Legal basis: performance of the service (Art. 6(1)(b)).

  • Biometric unlock. If you enable biometric unlock, authentication is performed by your device's operating system (Face ID / Touch ID / fingerprint / passcode). We never receive or store your biometric data — it never leaves your device. Legal basis: your consent to enable the feature.

  • Diagnostics. We use Firebase Crashlytics and Firebase Performance Monitoring to collect crash reports and performance data so we can fix defects. A crash report contains the error and its stack trace, short technical notes the app records before the error (for example which request to our server failed), the time of the crash, the app version, your device model, operating system version, memory and storage, whether the device is rooted, and random identifiers that Firebase creates for the installation and the app session. It does not contain your name, email address, user ID or account credentials. Crashlytics keeps crash reports for 90 days. Legal basis: legitimate interest in a stable Service.

  • Google Play statistics and reviews. If you installed the app from Google Play, Google gives us, as the app's developer, data about the app's stability (crash and freeze rates, and crash reports collected from Android devices) and aggregated figures on installs, uninstalls and ratings. These contain no name, account or contact details. If you publish a review of the app on Google Play, we also receive the review: your star rating, the review text, the Google Play name shown with it, the language, the app version, your device model and Android version. We use this data to find and fix defects and to improve the app. We do not copy reviewers' names out of Google Play; our internal release reports quote at most short passages of review text, without the reviewer's name. Google operates Google Play and publishes reviews as an independent controller under its own privacy policy (policies.google.com/privacy). Legal basis: our legitimate interest in a stable, well-functioning app (Art. 6(1)(f) GDPR).

  • AI-assisted review. We review crash reports and the Google Play data and reviews described above with the help of an AI assistant (Anthropic's Claude), under our supervision and with read-only access, to find defects and to judge whether a new app version is stable. See section 3.6.

  • Analytics. We use Firebase Analytics, in the same GA4 property as the website, gated by the Analytics choice on the in-app consent screen (see section 5 of the Cookie Policy). Analytics is denied by default until you choose to allow it.

    • With analytics consent: Firebase Analytics stores an identifier on your device (the app-instance ID) and records the screens you view and what you do in the app (for example searches, the sets you open, wishlist additions and clicks through to a shop), together with app and device details. While you are signed in and have allowed analytics, the app also sets a SHA-256 hash of your email address as the GA4 user ID, the same value the website uses (section 2.12), so that your use of the app and of the website is counted as one user. Only the hash is sent, never the email address itself. The app removes the user ID when you sign out or withdraw analytics consent.
    • Without analytics consent: Firebase Analytics runs in Google Consent Mode v2 advanced mode, as on the website (section 2.12). It does not store, read or send the app-instance ID, and no user ID is set. It sends only minimal cookieless signals, which Google uses solely for aggregate modelling and from which it builds no individual user profile.

    Legal basis: your consent (Art. 6(1)(a)).

  • Firebase (processor). Firebase Cloud Messaging, Analytics, Crashlytics, Performance Monitoring, and Remote Config are provided by Google Ireland Limited as our processor. See section 3 (Recipients of data) for its role and privacy policy.

  • Advertising and app-install measurement (Meta App Events SDK). The app integrates Meta's App Events SDK so that we can measure and optimise our Meta (Facebook / Instagram) app-install advertising campaigns and attribute installs and conversions to them. This SDK is denied by default and collects nothing until you both (a) grant the in-app Advertising consent — the same Consent Mode v2 choice described in the Cookie Policy, which is denied by default — and (b), on iOS, allow tracking in Apple's system App Tracking Transparency (ATT) prompt. Only after that consent does the SDK transmit the following to Meta:

    • App events: app install and activation; product content views; searches (the search term itself is never sent to Meta); wishlist additions; account registrations (only the sign-up method — email, Google, or Facebook — never your email address); and purchases recorded when you click out to a partner shop (the offer value, the currency, and the LEGO set number as the content identifier).
    • Your device advertising identifier — the IDFA on iOS (only if you allow tracking in the ATT prompt) or the Google Advertising ID (GAID) on Android.
    • Technical data the SDK attaches to each event — your IP address, app and device information, and an anonymous, Meta app-scoped identifier.

    The content identifiers we send are LEGO set numbers, which are not personal data. The app does not send your hashed email address or phone number to Meta — Meta "Advanced Matching" is disabled in the app. Legal basis: your consent — Art. 6(1)(a) GDPR. You may withdraw consent at any time in the app's consent settings and, on iOS, by turning off tracking for the app in your system privacy settings; the SDK then stops collecting. Meta Platforms Ireland Ltd. is the recipient and transfers this data to Meta Platforms Inc. in the United States under the safeguards described in section 4. See section 3.4.

  • Apple SKAdNetwork (iOS only). On iOS, install attribution additionally uses Apple's SKAdNetwork, which reports campaign performance to Meta in a privacy-preserving, aggregated form that contains no user-level data. SKAdNetwork operates at the operating-system level and does not identify you.

Apart from the Meta App Events SDK described above — which is off by default and runs only after you opt in — no mobile data is used for cross-app advertising tracking. Because that SDK can, with your permission, measure app-install advertising across apps, the app shows Apple's App Tracking Transparency prompt on iOS. If you choose "Ask App Not to Track" there, or leave the in-app Advertising consent denied, no advertising identifier is collected and Meta app-event tracking stays off.

2.19 Partner quote requests

  • Data: if you request a quote on the /partners page, we collect your full name, company name, business email address, shop website and your optional message, together with the locale and market you sent the request from.
  • Purpose: to answer your request and to discuss a possible partnership with you. The details are sent by email to our internal mailbox so we can act on them.
  • Legal basis: the taking of steps at your request prior to entering into a contract — Art. 6(1)(b) GDPR — together with our legitimate interest in answering business enquiries — Art. 6(1)(f) GDPR.
  • Recipient: the email is delivered via Sendinblue SAS (Brevo) — see section 3.2. Requests are not shared with any other third party. Note that this request is a business-to-business relationship separate from any personal user account you may hold.
  • Retention: requests are kept in our mailbox for as long as we are in contact with you and, if a partnership follows, for as long as it lasts and a reasonable period afterwards to evidence the arrangement; requests that do not proceed are deleted within 24 months.

2.20 Usage statistics

  • Data: the date (day only, no time of day) of your most recent signed-in visit — on the website, in the mobile app or in the browser extension. To produce aggregate statistics, we count accounts by the account data described in sections 2.1–2.4, 2.9, 2.14 and 2.18: home market, registration date, sign-in method (password, Google, Facebook), whether your email address is verified, your notification and marketing-email settings, whether push notifications can reach one of your devices, whether your account is scheduled for deletion, your age band derived from your year of birth, whether you use the mobile app, and the number of sets and price alerts on your wishlist.
  • Purpose: to follow how the Service grows and how actively it is used, and to report aggregate figures (for example, how many users a market has and how many of them were active in the last 30 days) to partner shops and in reports about the Service.
  • Legal basis: our legitimate interest in measuring and developing the Service and in presenting it to business partners — Art. 6(1)(f) GDPR.
  • Recipients: the statistics we share contain only totals per market and day, never data about an individual user.
  • Retention: the last-visit date is kept for the lifetime of your account and deleted together with it (section 2.9). The daily totals are not personal data and are kept without a time limit.

3. Recipients of data (subprocessors)

We share personal data only with the processors and independent services listed below, each of which provides an appropriate level of data protection. Data is never sold to third parties.

3.1 Hosting infrastructure

  • Laravel Holdings Inc. — 60 Broad Street, 24th Floor, #1559, New York, NY 10004, USA. Provides the server management platform ("Laravel Forge") through which we operate the Service. Role: processor. Terms: laravel.com/legal/forge-terms. Trust Center: trust.laravel.com.
  • DigitalOcean, LLC — 105 Edgeview Drive, Suite 425, Broomfield, CO 80021, USA. Operates the underlying virtual server on which the Service runs. The server is located in the Frankfurt (Germany) data center. Role: processor. DPA: digitalocean.com/legal/data-processing-agreement. Privacy policy: digitalocean.com/legal/privacy-policy.
  • Cloudflare, Inc. — 101 Townsend Street, San Francisco, CA 94107, USA. Every request to our websites passes through Cloudflare's network, which provides content delivery (CDN), a web application firewall (WAF), and TLS encryption. In doing so, Cloudflare processes your IP address and request data (such as the requested URL, the user-agent string, and the country derived from your connection). Role: processor. Transfer safeguard: the EU–U.S. Data Privacy Framework (Cloudflare is self-certified), with Standard Contractual Clauses as a fallback, as set out in Cloudflare's DPA. DPA: cloudflare.com/cloudflare-customer-dpa. Privacy policy: cloudflare.com/privacypolicy.

3.2 Email delivery

  • Sendinblue SAS (Brevo) — 17 rue Salneuve, 75017 Paris, France. Delivers transactional email, and — if you have opted into marketing — stores your contact record with the segmentation attributes listed in section 2.6, manages your membership in our per-market contact lists, receives server-side workflow-trigger events (such as registration, email verification, wishlist add, price-drop notified, the three weekly product-lifecycle digest triggers: newly-announced sets, newly available to preorder or buy, entering "Retiring soon"; the weekly partner offers digest; and partner deal alerts), and sends the resulting marketing messages. Role: processor. Data is processed within the European Union. Privacy policy: brevo.com/legal/privacypolicy. DPO: [email protected].

3.3 Identity providers

  • Google Ireland Limited — Gordon House, Barrow Street, Dublin 4, Ireland. Provides "Sign in with Google". Role: independent controller for the authentication flow, processor for information returned to us. Privacy policy: policies.google.com/privacy.
  • Meta Platforms Ireland Limited — Merrion Road, Dublin 4, D04 X2K5, Ireland. Provides "Sign in with Facebook". Role: independent controller for the authentication flow, processor for information returned to us. Privacy policy: facebook.com/privacy/policy.

3.4 Analytics and advertising

  • Google Ireland Limited — as above. Provides Google Analytics 4, Google Tag Manager, and Google Ads. Role: processor for Google Analytics; joint/independent controller for Google Ads, depending on the product. Consent Mode v2 documentation: support.google.com/analytics/answer/9976101. Up-to-date information on cookies used by Google advertising products: business.safety.google/adscookies.
  • Meta Platforms Ireland Limited — as above. Provides the Meta (Facebook) Pixel, the Meta Conversions API, and Meta Ads on the website, and — in our mobile application — the Meta App Events SDK used, subject to your in-app Advertising consent and (on iOS) the App Tracking Transparency prompt, to measure and optimise app-install advertising (see section 2.18). Role: joint controller with us (per CJEU case C-40/17, Fashion ID) for the Pixel and the Conversions API, since both transmit user-identifying signals to Meta for the same advertising purposes; recipient of the app-event data collected by the App Events SDK. Data collected in the app is transferred to Meta Platforms Inc. in the United States (see section 4). Joint-controller information is made available through Meta's Business Tools Terms. Meta's data policy: facebook.com/privacy/policy. Up-to-date information on cookies used by Meta: facebook.com/privacy/policies/cookies.
  • OpenAI Ireland Limited - 1st Floor, The Liffey Trust Centre, 117-126 Sheriff Street Upper, Dublin 1, D01 YC43, Ireland. Provides ChatGPT Ads and the OpenAI Measurement Pixel on the website (see section 2.13). Our advertising contract is with OpenAI OpCo, LLC (USA), but under OpenAI's Ad Tools Data Processing Addendum (openai.com/policies/ad-tools-dpa), data from the EEA and Switzerland is processed by OpenAI Ireland Limited, and data from the United Kingdom by OpenAI OpCo, LLC under the UK Standard Contractual Clauses. Role: independent controller for the data received through the pixel, under OpenAI's Conversion Terms (openai.com/policies/conversion-terms) and the Ad Tools Data Processing Addendum. Transfer safeguard: OpenAI Ireland Limited uses a valid transfer mechanism for any onward transfer to a country outside the EEA without an adequate level of protection, such as to OpenAI's affiliates in the United States. Privacy policy: openai.com/policies/eu-privacy-policy. Cookie policy: openai.com/policies/cookie-policy.
  • Microsoft Ireland Operations Limited - One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, Ireland. Provides Microsoft Clarity on the website (see section 2.12). According to Microsoft, Clarity customers in the EU contract with Microsoft Ireland Operations Limited, and Clarity operates with Microsoft as a data controller. Role: independent controller for the data it receives through Clarity, under the Clarity terms of use (clarity.microsoft.com/terms) and the Microsoft Privacy Statement (microsoft.com/privacy/privacystatement). The data is stored in Microsoft's Azure cloud. Transfer safeguard: Microsoft Ireland Operations Limited transfers data to Microsoft Corporation in the United States under Standard Contractual Clauses, and Microsoft states that it complies with the EU-U.S. Data Privacy Framework. Microsoft's information on Clarity's data handling: learn.microsoft.com/clarity/faq. Clarity cookies: learn.microsoft.com/clarity/setup-and-installation/clarity-cookies.

3.5 Push notifications, mobile analytics, and diagnostics

  • Google Ireland Limited — as above. Provides Firebase Cloud Messaging (browser and mobile push delivery), and — for our mobile application — Firebase Analytics (the same GA4 property as the website), Crashlytics, Performance Monitoring, and Remote Config. Role: processor. Privacy policy: firebase.google.com/support/privacy. Analytics collection in the app is governed by Consent Mode v2 exactly as on the website.

3.6 AI-assisted operations

  • Anthropic Ireland, Limited — 6th Floor, South Bank House, Barrow Street, Dublin 4, D04 TR29, Ireland. Provides the AI assistant (Claude) that we use, under our supervision, to review our server and application logs for security incidents, errors, and service-reliability problems (section 2.11), and our mobile app's crash reports, Google Play statistics and app reviews (section 2.18). Log excerpts processed this way may contain the data described in section 2.11, including IP addresses; crash reports and reviews contain the data described in section 2.18. We use Claude in two ways:

    • Automated log triage, which sends excerpts of our application logs and operational data to Anthropic through its API. Role: processor, under Anthropic's DPA (anthropic.com/legal/data-processing-addendum). Anthropic does not use this data to train its models.
    • Security and stability reviews, in which the assistant reads our server logs, crash reports and Google Play data through read-only accounts. These run on an individual Claude subscription under Anthropic's consumer terms; for this processing, Anthropic acts as an independent controller under its own privacy policy. We have turned off the use of our conversations for model training; with that setting, Anthropic keeps the data for 30 days, except for content flagged for a safety review.

    Transfer safeguard: data may be processed in the United States by Anthropic, PBC (548 Market St, PMB 90375, San Francisco, CA 94104, USA) under Standard Contractual Clauses. Privacy policy: anthropic.com/legal/privacy.

4. International data transfers

Personal data processed by us is stored primarily on servers located in the European Union (Frankfurt, Germany). Some of the recipients listed in section 3 are established in, or transfer data to, countries outside the European Economic Area (in particular, the United States).

For any such transfer, we rely on one or more of the following safeguards under Chapter V GDPR:

  • The European Commission's Standard Contractual Clauses (Decision (EU) 2021/914), incorporated into each provider's Data Processing Agreement.
  • The EU–U.S. Data Privacy Framework adequacy decision of 10 July 2023, where the recipient is self-certified under that framework.

You may request a copy of the applicable safeguards by emailing us.

5. Your rights under the GDPR

You have the following rights in respect of your personal data:

  • Right of access (Art. 15) — to obtain confirmation whether we process personal data about you and, if so, a copy of that data.
  • Right to rectification (Art. 16) — to have inaccurate personal data corrected or completed.
  • Right to erasure / "right to be forgotten" (Art. 17) — to have your personal data deleted, subject to the limits in Art. 17(3). You can trigger erasure yourself at any time from your account settings.
  • Right to restriction of processing (Art. 18) — to request that we limit processing in specified situations.
  • Right to data portability (Art. 20) — to receive your personal data in a structured, commonly used, machine-readable format, and to transmit it to another controller.
  • Right to object (Art. 21) — to object to processing that relies on our legitimate interest (sign-in scripts loaded before you click in section 2.2, push engagement records in section 2.4, prize draws in section 2.6, section 2.7, 2.9 grace-period, 2.11).
  • Right to withdraw consent (Art. 7(3)) — where processing is based on consent (sections 2.4, 2.6, 2.12, 2.13, and the consent-based mobile processing in section 2.18), you may withdraw it at any time. Withdrawal does not affect the lawfulness of processing that took place before withdrawal.
  • Right not to be subject to automated individual decision-making (Art. 22) — we do not make decisions about you based solely on automated processing that produce legal or similarly significant effects.
  • Right to lodge a complaint with a supervisory authority (Art. 77) — see section 11.

How to exercise your rights

Email us at [email protected] from the email address associated with your account, or use the relevant action in your account settings. We will answer within 30 days of receiving a clear request. If the request is complex, we may extend this period by a further two months and will inform you of the extension within the first 30 days. Exercising your rights is free of charge; we may charge a reasonable fee or refuse the request only if it is manifestly unfounded or excessive (Art. 12(5) GDPR).

A copy of your data (access and portability, Art. 15 and 20 GDPR). You can request a copy of your personal data in your account settings on the website or in the BrickHunter mobile app, once your email address is verified. We prepare the copy as a JSON file, a structured, machine-readable format, and email a download link to your account's email address. The link is valid for 72 hours and works only after you sign in to your account. We keep only your newest copy, for at most 4 days: the file is deleted when you request a new copy, when your account is deleted, and in any case within 4 days. The file leaves out secrets such as your password and sign-in tokens, values we store only as hashes, and short-lived sign-in records (web sessions and one-time sign-in codes). You can ask for these, or for a full copy, by email as described above.

To protect you, we may ask you to verify your identity before we answer — typically by confirming you can act on the account.

6. Cookies

The Service uses cookies and similar technologies. Cookies fall into three categories — strictly necessary, analytics, and marketing — and each category is subject to your choices in the consent banner. The processing activities behind the analytics and marketing cookies, including their purposes, legal bases, and retention periods, are described in sections 2.12 and 2.13 above. The sign-in scripts of Google and Facebook, which load regardless of these choices, are described in section 2.2.

For the full list of cookies we set and read, their durations, and how to change your choices at any time, see our separate Cookie Policy.

7. Data-breach procedure

If a personal-data breach occurs that is likely to result in a risk to your rights and freedoms, we will notify the competent supervisory authority (NAIH) without undue delay and, where feasible, within 72 hours of becoming aware of the breach, as required by Article 33 GDPR. If the breach is likely to result in a high risk to your rights and freedoms, we will also notify you directly without undue delay, pursuant to Article 34 GDPR. We maintain an internal register of all breaches, regardless of notification requirement.

8. Data security

We take appropriate technical and organisational measures to protect your personal data against unauthorised access, loss, alteration, or disclosure, in line with Article 32 GDPR. These include:

  • HTTPS with HTTP Strict Transport Security (HSTS) on all domains.
  • Passwords stored as bcrypt hashes — plain-text passwords are never stored or logged.
  • A password change or reset, an email-address change, removing a Google or Facebook link, a scheduled account deletion and the "Sign out on all devices" option end every other session, "remember me" login, app sign-in and cross-domain sign-in of the account. Adding a first password to an account created with Google or Facebook requires a recent sign-in, and we email you whenever a password is added or changed. We also email you when a scheduled account deletion is cancelled.
  • IP addresses stored only as keyed HMAC-SHA256 hashes in our application database; web server logs containing plain IP addresses are kept for at most 15 days and are readable only by the operator and a read-only analysis account.
  • API tokens and installation tokens stored only as HMAC-SHA256 hashes.
  • Session cookies marked Secure, HttpOnly, and SameSite=Lax.
  • Server-side CSRF protection on all state-changing web requests, and rate limiting of web and API requests per app installation, per authenticated user and, where neither is available, per keyed hash of the IP address.
  • Brute-force protection on login: failed attempts are counted per account (not per spelling of the address) and per network or app installation, and the hourly limit per account is shared by the website and the app.
  • Regular security updates to the server operating system and application dependencies.
  • Access to the production environment restricted to the controller; all third-party processors listed in section 3 have signed a Data Processing Agreement or accepted equivalent contractual terms.
  • Application logs rotated and deleted after 14 days.
  • Daily database backups kept on the server that runs the Service, accessible only to the operator, and deleted after 14 days (see section 2.9).

9. Children

The Service is not directed at children. If you are under 16 years old, you must not use the Service or create an account without the consent of your parent or legal guardian, as required by Article 8 GDPR and Hungarian Infotv. § 6(3). If we become aware that we have collected personal data from a child without proper authorisation, we will delete it without delay.

10. Automated decision-making and profiling

We do not carry out automated decision-making that produces legal or similarly significant effects on you within the meaning of Article 22 GDPR. We do use aggregated, non-individual profiling to display modelled advertising (Google Ads, Meta Ads) and to prioritise products in listings; this profiling never produces a decision with a legal effect and is always subject to your consent (see section 2.13).

11. Legal remedies

If you believe that our processing of your personal data infringes the GDPR or Hungarian data-protection law, you have the right to:

  1. Contact us first at [email protected] — we will investigate and respond within 30 days.
  2. Lodge a complaint with the supervisory authority:
    • Hungarian National Authority for Data Protection and Freedom of Information (NAIH)
    • Address: 1055 Budapest, Falk Miksa utca 9–11, Hungary
    • Postal address: 1363 Budapest, P.O. Box 9
    • Phone: +36 (1) 391-1400
    • Email: [email protected]
    • Website: naih.hu
    • You may also lodge your complaint with the supervisory authority of the EU Member State where you habitually reside, work, or where the alleged infringement occurred.
  3. Seek a judicial remedy before the competent court of your habitual residence or of the controller's habitual residence (Hungarian courts, for claims against us), pursuant to Articles 78–79 GDPR.

12. Changes to this policy

We may update this privacy policy from time to time to reflect changes in the Service, in applicable law, or in our processors. When we make material changes, we will update the "Last updated" date at the top of this page and, where the change affects a processing activity based on your consent, ask for renewed consent. We recommend reviewing this page periodically.

13. Contact

For any question about this privacy policy or about your personal data, please contact:

  • Email: [email protected]
  • Postal address: Geiger Tamás e.v., Váci út 83/A 2/208, 1044 Budapest, Hungary