How We Handle Data

What data does this site collect?

For a page visit, demo click or partner-button click, the available site information names the action but not a personal-data inventory. The site is marked 18+ and may earn a commission when a partner button leads to an operator; neither fact identifies the data stored about a visitor.

This table separates confirmed parts of the journey from data practices that are not stated. The demo provides 100,000 Fun virtual credits with no cash value and no sign-up; demo credit rules explain that distinction. The site information does not identify a visitor account or named-profile system for reading guides.

Cookies, server logs and partner link clicks

If your browser opens the demo or a partner route, cookie settings and server-log fields are not specified here. The site information also leaves unanswered whether a click carries a referral identifier or what an operator records after the handoff.

A possible commission describes a commercial relationship, not the contents of a data transfer. It does not establish that personal information is shared, and it does not establish that no click record exists. Cookie names, purposes, analytics providers and deletion schedules are not listed in the site information.

Browser controls can show or limit some cookie permissions, but they do not show every record held by a server or operator. Before entering account details, make sure the page belongs to the operator you intended to use and read that operator's privacy information. The editorial method and scope set out the guide's focus on game information and user journeys, rather than operator data practices.

What happens to operator account data?

When you register or request a withdrawal, the operator handles account details and any KYC documents. Tower Rush has no separate player account, so login, sign-up, deposits and identity checks take place through a gaming operator that carries Galaxsys games.

Generic operator registration uses a mobile number or email address with a password, and many operators send a one-time code by SMS. Operators ask for identity documents for KYC before a withdrawal; payment methods and limits are set by each operator. These general steps do not establish the fields collected by a particular service or how long it keeps them.

The operator registration steps describe the general sign-up and identity-check flow, while operator terms and privacy information govern an individual account. Keep passwords and one-time codes private, and do not submit identity documents through a game screen or this editorial site. Fun credits in the demo are not account funds and have no cash value.

How to make a privacy enquiry

For a question about this site, use the editorial contact page and identify the page or partner-button action. The privacy contact route is for questions about the guide; operator account questions belong with the relevant operator.

1. Name the page or action, such as opening the demo or following a partner button.
2. Say what you want clarified, such as whether a cookie or server log is involved.
3. Leave out passwords, one-time codes, payment details and identity documents.

The editorial contact route is available for site-related enquiries. The available information does not state a separate privacy form, response period or deletion process. For an operator account, contact that operator through its own service and consult its privacy terms before sharing account information. This page describes the confirmed user journey and clearly marks where collection, sharing and storage details are not specified.