500k.io is built to need almost no cookies. Specifically, we do not use marketing or tracking cookies.

What we set

CookiePurposeTypeDuration
themeStores light/dark theme preference if you toggle it.Functional1 year
_ga, _ga_*Google Analytics 4 — anonymized analytics. IP anonymized, Google Signals off, no ad personalization, no remarketing.Analytics2 years
_clck, _clskMicrosoft Clarity — anonymized heatmaps and session recordings (when enabled).Analytics1 year
cf_*Cloudflare bot management + DDoS protection. Set by Cloudflare on edge.Strictly necessary30 min – 30 days

What we don't set

  • Marketing cookies (Facebook Pixel, LinkedIn Insight, ad-network pixels, etc.).
  • Cross-site tracking cookies.
  • Google Ads or remarketing cookies — Google Signals is disabled in our GA4 config.

About our GA4 setup

Google Analytics 4 is configured for analytics-only use, not advertising. Specifically:

  • IP anonymization is enabled.
  • Google Signals (cross-device measurement using Google account data) is off.
  • Ad personalization signals are off.
  • No user-id is collected.
  • Data retention is set to 14 months (the GA4 maximum without identifying users).

This configuration aligns with the CNIL's guidelines for analytics-only use of GA4 in the EU. If you'd prefer not to be measured at all, browser-level tracking blockers (uBlock Origin, Brave's shields, Safari ITP) work fine on this site.

Third-party content

Embedded media (YouTube, Twitter) may set their own cookies if you click them. Our embeds use privacy-enhanced modes by default (youtube-nocookie.com, etc.). If you choose to interact with embedded content, the third party's cookie policy applies.

Future changes

If we ever add a cookie that requires consent, we'll add a banner and update this page. Material changes will be emailed to subscribers.