Legal · Cookies

Cookie Policy

LAST UPDATED · 20 MAY 2026

A plain-language list of every cookie we and our infrastructure providers set on this site, what each is for, and how to turn them off. There is no advertising or analytics tracking here — and that is intentional.

01What cookies are

Cookies are tiny text files a website stores on your device. They let the site recognise you between page loads, keep you signed in, and protect against automated abuse. "Cookies" in this policy also covers similar storage mechanisms — local storage, session storage, and pixel tags — used for the same purposes.

We split cookies into two groups: strictly necessary (the site doesn't work without them) and functional (comfort and security improvements). We do not use advertising, tracking, or analytics cookies. We do not embed third-party social pixels.

02Cookies we use

The exact cookie names below come from the libraries we use; some are set only after you sign in or only on protected endpoints.

NameSet byPurposeDurationCategory
__clientClerkIdentifies your signed-in session.SessionStrictly necessary
__sessionClerkShort-lived JWT used to authenticate API requests.~1 hourStrictly necessary
__clerk_db_jwtClerkStores Clerk session metadata.1 yearStrictly necessary
__cf_bmCloudflareBot-management cookie. Distinguishes humans from bots to block scraping/abuse.~30 minutesStrictly necessary
cf_clearanceCloudflareConfirms you passed a security challenge. Only set if you trigger one.~30 daysStrictly necessary
_cfuvidCloudflareHelps Cloudflare rate-limit fairly across a shared IP.SessionStrictly necessary
tcgi_currencyTCGinvestRemembers your currency preference (EUR/USD).1 yearFunctional
tcgi_themeTCGinvestRemembers your colour theme preference.1 yearFunctional

Cookie names and durations can change when our authentication or security providers update their libraries. We will keep this page current; the "Last updated" date at the top reflects the latest revision.

03Why there is no cookie banner

Under the EU ePrivacy Directive (and Maltese implementation of it), consent banners are required for cookies that are not strictly necessary — primarily analytics, advertising and cross-site tracking. We don't set any of those, so we are not legally required to interrupt your visit with a consent modal. Strictly necessary and clearly-described functional cookies are permitted on the basis of providing the requested service.

If we add analytics or any non-essential cookies in the future, we will introduce a granular consent banner at that point and will not place those cookies until you opt in.

04Third-party cookies

We embed services from a small number of partners, each of which may set their own cookies on pages where their functionality appears:

None of these partners use cookies set on TCGinvest to track you across unrelated websites, and none are used for advertising profiling.

05Local storage and similar

In addition to cookies, we use your browser's local and session storage to keep small bits of state across page loads — none of this data leaves your device:

  • tcgi_currency — your selected currency (EUR/USD).
  • tcgi_recent — recently viewed cards, to power the "Recently viewed" rail.
  • tcgi_watchlist_anon — if you are signed out, a local-only copy of your watchlist additions. Cleared on sign-in (merged into your account) or by clearing site data.

06Managing and deleting cookies

You can clear, block, or accept-on-a-per-site basis any cookie set by us or our providers, directly from your browser:

Blocking strictly necessary cookies will break parts of the site — most obviously sign-in. Blocking functional cookies will reset your preferences each visit. Nothing else will break.

07Changes to this policy

We update this Cookie Policy when we add or remove a provider, or when a provider changes the cookies it sets. The "Last updated" date at the top of the page always reflects the current version. For wider privacy questions, see our Privacy Policy.

Questions or a cookie-related data request? Email [email protected]. We aim to respond within a few working days; the statutory deadline under the GDPR is 30 days.