Cookie Policy
Cookie Use and Management Policy

A cookie is a small text file a website places on your device when you visit. Your browser stores it locally and may return it on later visits to the same site, letting the site recall settings or recognize returning users. Cookies hold data only; they cannot execute code, access other files on your device, or install software of any kind. Throughout this Policy, “cookies” also covers browser local storage and pixel tags where the specific distinction is not relevant.

Your first visit triggers a consent banner offering three options: accept all non-essential cookies, decline all, or open a preference panel to choose by category. Browsing without making a selection means only necessary cookies run – we do not treat inaction as consent for non-essential cookies.

Your choice is stored in a preference cookie. Clearing all cookies from your browser removes this record, so the banner reappears on your next visit. Any new non-essential cookie category we introduce always requires fresh consent before it is activated.

The preference panel is technically functional, not cosmetic. Declining a category genuinely prevents those cookies from being placed on your device. Category-level choices are fully supported: accepting analytics while declining affiliate referral tracking is a valid, working configuration, as is any other mix.

The only third party involved is currently and principally Google Analytics, operating under its own data processing agreement with us. No advertising networks, retargeting services, data brokers, or comparable third parties are permitted to place cookies on this Site or to receive visitor data from it. Nothing deployed here supports behavioural advertising, cross-site user tracking, or interest-based profiling of any kind.

Once an affiliate referral cookie is set and you navigate to a casino, our data visibility ends entirely. No live data connection of any kind exists between this Site and any casino platform. The affiliate referral cookie records one click event at the moment of navigation. After that, your entire Tower Rush session – the tower heights reached, the bonus mechanic activations, the cashout decisions made, the account balance – is processed by Galaxsys’s technology on casino infrastructure and is completely inaccessible to this Site.

The Data Visibility Boundary

Unlike crash games that offer an auto-cashout setting, Tower Rush requires a live manual cashout decision every single round. There is no pre-configured exit target, no automated cashout mechanism, and no timer-based exit setting within the game. From the perspective of what this Site’s cookies can observe, this means there is no automated cashout event of any kind to record, even in principle. The affiliate tracking cookie captures one event: the click that brought you to the casino. Questions about specific Tower Rush session outcomes, multiplier heights, bonus activations, or cashout decisions go to the casino that hosted those sessions.

Google Analytics in our configuration anonymizes IP addresses before any data is stored. The analytical output we access consists of aggregate engagement statistics across all visitors combined – not records linked to individual readers. We do not use this to identify, profile, or track any specific reader.

Three options are available for managing cookies on this Site. The first is the on-site preference panel, accessible on your first visit and always through the link in the Site footer, giving category-level control over non-essential cookies. The second is your browser’s own privacy settings, which manage cookies across every site you visit. The third applies specifically to Google Analytics: Google’s Analytics opt-out browser extension, published at tools.google.com/dlpage/gaoptout.

Each browser files these controls in a slightly different place. In Chrome, go to Settings, then Privacy and security, then Cookies and other site data. In Firefox, go to Settings, then Privacy & Security. In Safari, go to Preferences, then Privacy. In Microsoft Edge, go to Settings, then Cookies and site permissions.

Declining non-essential cookies does not restrict access to any Tower Rush content or casino comparison material on this Site. It may affect some personalization features, and it means that if you subsequently register at a partner casino we cannot attribute that registration to a referral from this Site for commission purposes. We accept this as the appropriate consequence of respecting user preferences.

Control is exercised category by category through the preference panel rather than as a single all-or-nothing switch, so you are never forced into taking or refusing everything at once.

Category-level control means accepting analytics while declining affiliate referral tracking is a fully supported combination, and you decide exactly which non-essential categories run.

A Note on Blocking Necessary Cookies

Blocking all cookies at browser level, including necessary ones, typically causes the consent tool to malfunction, because the preference cookie that saves your choice cannot be stored. The most common result is the consent banner reappearing on every visit rather than recognizing your prior selection. Using the on-site preference panel for category-level management avoids this problem while still providing genuine control over non-essential cookies.

Where a cookie on this Site processes data that qualifies as personal data under applicable law, our Privacy Policy governs that processing, including the applicable legal basis, the retention period, and the rights available to you. Analytics cookies anonymize IP addresses before any data is stored, while affiliate referral cookies hold click events and timestamps and no personal identifiers at all.

We review the practices of third-party tools periodically and update this Policy whenever those practices change materially, so that the description here continues to match what actually runs on the Site.

We update this Policy whenever our use of cookies changes in any material way, including when we change the third-party tools we integrate or when an integrated tool changes its own data handling practices. The current version is always published on this page, carrying a new effective date.