This Cookie Notice explains how GoBLAM uses cookies, local storage, session storage, pixels, tags, SDKs, and similar technologies. The Privacy Notice explains how GoBLAM processes personal data created or collected through those technologies.

GoBLAM updates this Cookie Notice when it materially changes tracking tools, analytics tools, advertising platforms, checkout tools, security signals, or cookie categories.

Strictly necessary technologies are required to provide services you request or to keep GoBLAM secure. They may support login, authentication, account security, routing, locale selection, CSRF protection, consent storage, checkout continuity, live Contest operation, and service availability.

Strictly necessary technologies may be used without opt-in consent where they are required to provide a requested service, comply with legal requirements, or maintain security and integrity.

Preference technologies remember choices such as language, locale, display settings, and consent preferences. They help keep the GoBLAM experience consistent across visits and devices where supported.

Analytics technologies measure usage, errors, performance, funnels, product quality, and feature behavior. GoBLAM minimizes personal data in analytics and avoids collecting raw payment, payout, identity, or support evidence through analytics tools.

Optional analytics cookies and detailed analytics events run only after valid consent where required. Where configured, Google Advanced Consent Mode may send cookieless page views and confirmed account-creation or Contest-registration signals when optional analytics is rejected. Those limited signals omit Customer and Contest identifiers, advertising click identifiers, arbitrary query parameters, and detailed workflow diagnostics.

GoBLAM may use privacy-minimised first-party experiments to compare whether a page treatment improves the service. These experiments use an experiment-specific random identifier and variant. After an authenticated outcome, a one-way pseudonymous key scoped to that experiment version prevents duplicate or mixed Customer outcomes. The record does not create a reusable cross-experiment visitor profile and remains separate from optional third-party analytics.

Advertising cookies, pixels, tags, and conversion tools may support campaign attribution, conversion measurement, retargeting, and ad optimization when configured, legally permitted, and allowed by your consent settings where consent is required.

Campaign tracking must not misrepresent purchase, prize, or Contest behavior. Advertising audiences must avoid sensitive, underage, restricted-jurisdiction, or legally inappropriate targeting.

Security cookies and similar signals may help protect accounts, Contests, Ticket Bundle purchases, Prize Payouts, and service integrity. Security signals may include device or browser fingerprints, hashed identifiers, IP-derived risk data, proxy indicators, hosting indicators, and abuse-prevention context.

Security and risk signals are described at a level intended to provide transparency without exposing anti-abuse methods. Raw IP addresses and raw user agents are minimized, hashed, or access-restricted where reasonably practicable.

• Customer authentication storage, including player_token in local storage: keeps signed-in customer sessions and protects account access until sign-out, expiry, or manual deletion.
• Locale storage, including the PARAGLIDE_LOCALE cookie where used: remembers language or locale choices.
• Consent preference storage, including goblam_cookie_consent in local storage and a first-party cookie retained for up to 180 days: records consent version, separate optional analytics and advertising category choices, and decision timestamp so browser and server-side tags enforce the same choices.
• Client preference storage, including goblam_client_preference in local storage when selected: remembers whether the customer prefers Steam or GeForce NOW launch guidance.
• Live Contest session storage, including goblam:live:* keys: caches live leaderboard, rank trend, and rating trend data for the current browser session.
• First-party attribution storage, including goblam_signup_attribution in local storage where advertising consent allows it: records UTM parameters, gclid, fbclid, rdt_cid, landing path, referrer, and capture time for signup attribution.
• First-party experiment storage, including versioned goblam_exp_homepage_positioning cookies retained for up to 30 days: keeps one random experiment-specific identifier, the assigned homepage variant, and whether assignment was randomized or forced by a code-reviewed URL selector. Existing assignments remain sticky and are not replaced by a later force URL. The identifier is not passed to client component properties. GoBLAM records the exposure, bounded UTM source, medium, campaign and content values where present, and whether a later account creation or Contest registration is confirmed. After an authenticated outcome, the record also contains a one-way pseudonymous deduplication key derived from the Customer ID and scoped to this experiment version; it does not contain the raw Customer ID. It does not store raw IP addresses, user agents, page URLs, advertising click identifiers, or a reusable cross-experiment visitor profile in this experiment record. Enrollment-level records are deleted no later than 90 days after the experiment assignment window ends; aggregate decisions may be retained.
• Google Analytics 4 and Advanced Consent Mode, where configured: when optional analytics is rejected, may receive cookieless page views containing a normalized page path and minimal confirmed account-creation or Contest-registration events, together with ordinary request metadata such as timestamp, browser or user-agent information, site origin, and approximate network-derived location. GoBLAM replaces identifiers in dynamic page paths and omits page titles, campaign values, advertising click identifiers, Customer and Contest identifiers, and detailed workflow events from those limited signals. When analytics consent is granted, Google Analytics may also use _ga and related cookies and receive page titles, allow-listed campaign parameters, and additional interaction data. GoBLAM does not send arbitrary page query strings in its GA4 page-view events.
• Microsoft Clarity, where configured: may use _clck and _clsk cookies and record session replays and heatmaps covering page paths, clicks, scrolling, mouse movement, device and browser information, and approximate location to show how the site is used. Clarity masks form input and text content by default.
• Google Ads tags and Advanced Consent Mode, where configured: when optional advertising is rejected, may receive redacted cookieless account-creation and Contest-registration conversion signals without advertising click identifiers, transaction identifiers, Customer data, or enhanced-conversion user data. When advertising consent is granted, Google Ads may also use Google tag storage such as _gcl_* cookies, campaign attribution, transaction identifiers, and enabled enhanced-conversion data.
• Meta Pixel and Meta Conversions API, where configured and allowed by your consent settings where required: may use _fbp and _fbc cookies, event IDs, page URLs, IP address, user agent, and limited allowed event data for advertising attribution and conversion measurement.
• Reddit Pixel and Reddit Conversions API, where configured and allowed by your advertising consent setting: may use the _rdt_uuid cookie and a first-party goblam_reddit_click_id cookie retained for up to 28 days, conversion IDs, page URLs, IP address, user agent, and limited event data for advertising attribution and conversion measurement.
• Security and risk signals: help detect duplicate accounts, proxy abuse, fraud, eligibility evasion, and service misuse.

GoBLAM reviews provider names, storage names, cookie names, purposes, durations, and first-party or third-party status when tracking tools change.

Where required, Customers can accept all, reject non-essential technologies, and manage categories. Refusing non-essential technologies does not block core service access unless GoBLAM confirms a lawful feature-specific reason.

You can change cookie preferences from the Cookie preferences control in the footer. Revoking consent stops future consent-dependent tracking as soon as reasonably practicable, but it does not affect processing that occurred before revocation or the limited cookieless measurement described below.

Rejecting optional analytics prevents analytics cookies, experiment dimensions, and detailed Google Analytics events, but Google Advanced Consent Mode may still send the limited cookieless page views and confirmed events described above. Rejecting optional advertising prevents advertising cookies, attribution storage, enhanced-conversion user data, and all Meta and Reddit measurement, while Google may receive the redacted cookieless conversion signals described above. These choices do not disable the privacy-minimised first-party experiment, which is used to assess and improve GoBLAM without a reusable third-party visitor profile.

Browser and device settings may also allow you to block, delete, or limit cookies and similar technologies. Blocking strictly necessary technologies may prevent parts of GoBLAM from working correctly.

GoBLAM may keep consent records containing version, timestamp, categories, decision state, and limited context needed to demonstrate the choice. Consent controls are intended to avoid dark patterns, bundled consent, pre-ticked choices, or misleading button hierarchy.