What we actually store on your device, and why. Plain language, no dark patterns.
We use only strictly-necessary technical storage. No marketing cookies. No advertising cookies. No retargeting pixels. No cross-site tracking. Our two analytics tools — Plausible Analytics and Vercel Analytics — are both cookie-free by design.
GDPR + ePrivacy don't require opt-in consent for strictly-necessary storage, but we list it here for transparency.
One localStorage entry called cgh-cookie-consent-v1 — set when you click "Got it" on the cookie notice. Its only purpose is to stop the notice from re-appearing every time you load a page. No personal data is stored. The value is the literal string "dismissed". You can delete it from your browser's Application/Storage panel at any time and the notice reappears on the next visit.
Nothing else. We do not set any cookies in the cookie jar (the .com / .org type), and we do not write anything else to localStorage, sessionStorage or IndexedDB on our pages.
Google Analytics, Google Tag Manager, Facebook Pixel, TikTok Pixel, LinkedIn Insight, Twitter/X pixel, Bing UET, or any other ad-tech tracker. Not loaded, not embedded, not present in the markup.
Cross-site tracking cookies. Browser fingerprinting. Session replay tools (Hotjar, FullStory, LogRocket, etc.). Affiliate-network tracking on this site itself — when affiliate links are eventually wired up, the operator's tracking happens on their site after you click through, not on ours.
Profile-building or audience-segmentation infrastructure. We don't build a profile of who you are, what you read, or what you've clicked.
We run two analytics tools side-by-side, neither of which uses cookies. Plausible Analytics tracks aggregate page-view counts (URL, referrer, country derived from IP — not stored per-user). Vercel Analytics tracks page views plus basic device/region metadata for performance monitoring (Largest Contentful Paint, Cumulative Layout Shift, etc.); it uses no cookies and no cross-site identifiers.
Both tools aggregate data server-side and never associate measurements with an individual visitor across sessions. Neither builds a profile, neither shares identifiers with third parties.
If you'd still rather not be counted in aggregate stats, any standard ad-blocker or content-blocker (uBlock Origin, Brave Shields, Safari Intelligent Tracking Prevention) will block both without affecting page functionality.
When we add operator-specific affiliate links (currently we don't have any active), the click handoff happens on the operator's domain — not ours. The affiliate tracker is set by the operator's own infrastructure on their site after the redirect. We get a credit attribution; we don't get a per-user identifier.
Until those links are live, this section is informational only. When they go live we'll update this page with the specific affiliate networks involved.
If we ever introduce non-essential cookies (advertising, retargeting, third-party analytics with cookies, etc.), the cookie notice on the site will be upgraded to a proper opt-in flow with categorised preferences. You'll have to actively accept those categories — silence does not equal consent under GDPR + ePrivacy.
Until that happens, the current notice is purely informational and the dismissal is for the notice itself, not for any cookie.
All GDPR rights apply (access, rectification, erasure, restriction, portability, objection, complaint to a supervisory authority). Since we hold practically no personal data on individual visitors — no account, no cookie, no profile — most of those rights are trivially satisfied. If you want a full data-access request, contact us via the editorial address on the contact page and we'll respond within the 30-day GDPR window.
Browser settings → Site data → cryptogamblinghub.org → Clear. That removes the dismissal flag in localStorage. The cookie notice will reappear on your next visit, which is the only effect.
Privacy-extensions (uBlock Origin, Brave Shields, Safari ITP) won't break anything on this site. Plausible analytics will be blocked, the cookie notice will still work, and all content will remain accessible.
