Cookie Policy
and Consent

• Strictly necessary. Page navigation, security protections, and display rendering – the foundational layer the Site depends on to function. Always active. Not subject to your consent choices. Blocking at browser level causes the Site to malfunction.
• Analytics and performance. Aggregate statistics about reader engagement with Tower Rush content: which articles hold sustained attention, how long visits to individual pages last, and what external sources bring readers here. All output is statistical across all visitors combined. No individual is identified, tracked, or profiled.
• Affiliate referral. Records the moment a reader navigates from this Site to a partner casino. A click identifier and a timestamp – nothing else. No personal data captured. No activity on the casino platform tracked after the reader leaves this Site.
• Preference and consent. Stores your consent selections so they apply consistently on return visits to this Site.

How Consent Works

First visit: a banner offers three options – accept all non-essential cookies; decline all; or open a preference panel to choose by category. Browse without selecting and only necessary cookies run. We do not treat inaction as consent.

Your preference is stored in a preference cookie. Clear your browser cookies and the record goes with them; the banner reappears on your next visit. Any new non-essential category we introduce will always require fresh consent before it activates.

The preference panel is technically real. Declining a category genuinely stops those cookies from being placed – not a display change, a technical restriction. Accepting analytics while declining affiliate referral tracking is a supported, working configuration.

Once the affiliate referral cookie fires and you navigate to a casino, our data visibility ends entirely. We cannot see your Tower Rush sessions: the tower heights you reached, which bonus mechanics activated, how many manual cashout attempts you made, or your account balance. Tower Rush has no auto-cashout feature – which means there is no automated cashout event of any kind for any tracking system to capture, even hypothetically. The affiliate cookie records the click when you left this Site. Everything inside any Tower Rush session – every Frozen Floor activation, every Temple Floor level, every Triple Build window, every crash – happens on Galaxsys’s technology on casino infrastructure and is completely outside our data visibility.

Primarily Google Analytics under its own data processing agreement with us. No advertising networks, retargeting services, data brokers, or behavioral profiling tools are permitted to place cookies on this Site or receive visitor data from us. Nothing deployed here supports behavioral advertising, cross-site user tracking, or interest-based profiling.

No live data connection exists between this Site and any casino platform. The affiliate referral cookie records one event: the click at the moment of navigation. After that, all Tower Rush activity – the tower climbing, the bonus mechanics activating, every manual cashout decision, every crash, your account balance – is processed by Galaxsys’s technology on casino infrastructure. Completely inaccessible to this Site.

Tower Rush’s Manual-Only Design and What It Means Here

Tower Rush requires a live manual cashout every round. There is no auto-cashout feature, no pre-configured exit target, no automated mechanism of any kind in the game structure. From the perspective of what cookies on this Site can observe, this means there is no automated cashout event to record – the category of event simply does not exist for this game. The affiliate tracking cookie captures one data point per casino visit: the initial click. For specific session information – tower heights, bonus mechanic activations, cashout timing, round outcomes – the casino that hosted those sessions is the only contact with the relevant data, not this Site.

The three bonus mechanics (Frozen Floor, Temple Floor, Triple Build) each alter the risk profile within the rounds where they appear, but none of them generates any data observable from outside the casino’s own infrastructure. All game event data, including every bonus mechanic activation and every cashout action, runs on casino infrastructure and is invisible to this Site.

Google Analytics in our configuration anonymizes IP addresses before any data is stored. The output we access is aggregate content engagement statistics across all visitors combined – not records associated with specific readers or specific sessions.

Three options: the on-site preference panel (accessible from the footer at any time) for category-level control over non-essential cookies without affecting necessary cookies; your browser’s own cookie settings for all-site management; and Google’s Analytics opt-out extension at tools.google.com/dlpage/gaoptout for Analytics specifically.

Browser paths: Chrome – Settings, Privacy and security, Cookies and other site data. Firefox – Settings, Privacy & Security. Safari – Preferences, Privacy. Edge – Settings, Cookies and site permissions.

Declining non-essential cookies does not restrict access to Tower Rush content or casino comparison material on this Site. It may reduce some personalization and means we cannot attribute any subsequent casino registration to a referral from this Site. Category-level control means you are not forced into all-or-nothing choices.

Blocking Necessary Cookies

Blocking all cookies at browser level including necessary ones typically breaks the consent tool because the preference record cannot be saved. The banner usually reappears every visit. Using the on-site preference panel for category-level management avoids this while still giving you genuine control over non-essential cookies.

Where a cookie processes data qualifying as personal data under applicable law, our Data Handling Notice governs: the legal basis, the retention period, and your rights. Analytics cookies anonymize IP addresses before storage. Affiliate referral cookies hold click events and timestamps, not personal identifiers. We review third-party practices periodically and update this page when practices change materially.

We update this page when cookie practices change materially. Current version always published here with a new effective date.