Cookie Policy
Last updated: 12 October 2026
In short: nothing non-essential is stored on your device until you press Accept in the cookie bar at the bottom of the page. Pressing Reject, or simply ignoring the bar, means no analytics cookies are ever created. Your answer is remembered, so the bar does not keep asking, and the site works identically either way: nothing is withheld from you for saying no.
1. What cookies are
A cookie is a small text file a website asks your browser to store, so it
can recognize the browser on a later request. This policy also covers similar
technologies, such as localStorage, which store data in your
browser in the same way and are treated identically under Article 22.2 of
Spanish Law 34/2002 (LSSI-CE).
2. Cookies used on this site
2.1 Strictly necessary — always active
These are required for the site to work and to stay secure. Under Article 22.2 LSSI-CE they are exempt from the consent requirement, so they cannot be switched off from the cookie bar.
| Name | Provider | Purpose | Duration | Type |
|---|---|---|---|---|
__cf_bm |
Cloudflare, Inc. | Distinguishes real visitors from automated bots, so the service can block abuse without blocking people. | 30 minutes | Third party |
grm-consent |
This site | Remembers your answer to the cookie bar, so it stops asking. Holds
granted or denied and the date you chose,
nothing else. Stored in localStorage, not sent to any
server. |
24 months after an accept, 6 months after a reject, then the bar asks again | First party |
grm-ou-hidden |
This site | Remembers the games you chose to hide from “Your games got
bigger”, so they stay hidden on your next search. Holds a list of
Steam game IDs, nothing about you or your profile. Only created when you
hide a game. Stored in localStorage, not sent to any
server. |
Until you show the games again or clear your browser data | First party |
2.2 Analytics — only after you accept
These are set by Google Analytics 4 (loaded through Google Tag Manager) and by Microsoft Clarity, and are used to understand how many people use the tool, which parts of it they use, and where the interface confuses them. They are blocked until you consent and are removed again if you withdraw consent.
| Name | Provider | Purpose | Duration | Type |
|---|---|---|---|---|
_ga |
Assigns a random identifier to your browser so repeat visits can be counted as one visitor rather than several. | 2 years | Third party | |
_ga_5JK9BJZS23 |
Keeps the session state for this specific Analytics property. | 2 years | Third party | |
_clck |
Microsoft Clarity | Keeps a Clarity identifier for this browser, so several page views can be joined into one session. | 1 year | Third party |
_clsk |
Microsoft Clarity | Groups the page views of a single visit into one recording. | 1 day | Third party |
CLID, MUID, ANONCHK,
SM, MR |
Microsoft | Set on Microsoft’s own domains (clarity.ms,
c.bing.com) when Clarity loads, to identify a browser across
Microsoft services and to synchronize those identifiers. |
Up to 1 year | Third party |
What Microsoft Clarity records
Clarity produces heatmaps and session replays: an anonymized reconstruction of how a page was used — mouse movement, scrolling, clicks and rage clicks. It is used to find parts of the interface that confuse people, not to identify anyone. Text you type into fields is masked before it leaves your browser, so the Steam profile you enter is not readable in a recording. Clarity does not record other tabs, other sites, your screen, your camera or your microphone. Microsoft’s own explanation is in its Privacy Statement.
Clarity is loaded through Google Tag Manager on every page, but it reads the same Google Consent Mode signal that gates Google Analytics and does not record or set cookies until that signal is granted. If you reject, or have not yet chosen, Clarity stays inactive.
Google acts as a data processor for this analytics data. It may be transferred outside the European Economic Area under the European Commission’s Standard Contractual Clauses. Advertising features and Google Signals are switched off, so this data is not used to build advertising profiles. Google’s own explanation is available in its Privacy Policy.
2.3 reCAPTCHA on the contact form — only on that one page
The contact form is protected by Google reCAPTCHA v3, which works out whether a submission comes from a person or from a script. Without it the form becomes a spam relay within days.
reCAPTCHA sets cookies in the google.com domain and reads
signals about how the page was used. Two things limit it here:
- It runs on /contact only. No other page on this site loads it.
- The script is not fetched when that page opens. It is fetched the moment you click into the first field, so opening the page to read the email address contacts Google not at all.
This is treated as strictly necessary for a form that would otherwise be unusable, so it is not behind the cookie bar. If you would rather not involve Google, do not use the form: write to [email protected] instead, which reaches exactly the same inbox. Google’s handling is covered by its Privacy Policy and Terms of Service.
2.4 What this site does not use
There are no advertising cookies, no retargeting pixels, no social media trackers, no fingerprinting and no cross-site tracking of any kind.
3. How consent is handled
The cookie bar sits at the bottom of the page and does not block it. Until you press Accept, Google Consent Mode holds all analytics storage in a denied state, which means Google Tag Manager loads but Google Analytics and Microsoft Clarity are both prevented from writing anything to your browser. Scrolling, clicking elsewhere or carrying on using the site is never read as agreement: if you ignore the bar, nothing is stored and it asks again on your next page view. With the bar focused, the Esc key counts as Reject.
Both answers are remembered: an Accept for 24 months, a Reject for 6 months. After that the bar asks again, so an old answer is not assumed to still stand.
To know how many visitors accept, the bar also sends an anonymous count to our own server: only the words “shown”, “accept” or “reject”, added to a daily total. No cookie is set for this and nothing about you or your device is stored with it.
Reject is a single click on the same screen as Accept, the same size and weight, and there is no cookie wall: rejecting costs you no functionality whatsoever. Access to the site is never conditional on accepting.
Automated crawlers, such as search engine and AI indexing bots, are not shown the cookie bar. No analytics or session-replay tag is loaded for them either, so they are treated exactly as a rejection.
4. Changing or withdrawing your choice
You can change your mind at any time using the “Cookie settings” link in the footer of every page. Choosing Reject there un-remembers a prior Accept, signals Clarity to stop recording, and deletes the Google Analytics and Clarity cookies stored on this site, and your Reject is then remembered for 6 months. Cookies held on Microsoft’s own domains can only be removed through your browser settings, or by opting out at clarity.microsoft.com.
You can also delete or block cookies through your browser’s own settings. Instructions: Chrome, Firefox, Safari, Edge. Blocking the strictly necessary cookies may stop parts of the site working correctly.
5. Analytics that use no cookies at all
Separately from the above, the site records on its own server which recommendations get clicked, so the algorithm can be measured and improved. This uses no cookies and stores nothing on your device, so it is not governed by this policy and is unaffected by your cookie choice. It is described in full in the Privacy Policy, which also explains how to have that data deleted.
6. Changes to this policy
If the cookies used by the site change, this page is updated before the change takes effect, and the date at the top will reflect it.
7. Contact
Questions about this policy: use the contact form, or write to [email protected]. Identification details of the site owner are in the Legal Notice.