Privacy Policy
By Elena Vance · Updated
Buttons lead to the partner casino
This site keeps no account data.
This privacy page separates confirmed site routes from details that remain unknown. A click opens the free demo, and partner buttons route to operators; available facts leave cookie use, server logs and data retention unspecified. Check the operator notice before sharing account or payment details.
What data is collected when the demo opens?
One click opens the free demo, but the available facts leave the site’s data collection and retention details unspecified. The Galaxsys demo uses Fun credits with no cash value and requires no sign-up. Those game conditions do not establish what technical information the site may process when a visitor opens a page or starts play.
| Activity | Confirmed detail | Privacy detail not established |
|---|---|---|
| Demo use | The demo opens after a click and uses Fun credits | Whether demo activity is stored |
| Account on this site | Tower Rush has no game account of its own | Whether the site receives operator account details |
| Partner link clicks | Buttons route through a partner link to an operator; the site may earn a commission | Whether clicks are logged, what fields are involved, or how long records remain |
| Cookies | No cookie settings are documented in the available facts | Whether cookies are used or how visitors can manage them |
| Server logs | No log policy is specified | Whether logs are kept, their contents, or retention period |
| Operator records | Operators manage account access and payment steps | Each operator’s specific collection, use and storage practices |
The free demo details explain the Fun credit conditions, not technical storage on this site. No claim about anonymous browsing, analytics, device identifiers or deletion periods can be established from the available information.
What happens when a partner link opens?
A partner button routes to an operator, while the information available here leaves the handling of partner link clicks unspecified. The site may earn a commission from that route. Commission arrangements alone do not establish whether personal details pass to an operator or whether a click record is retained.
Operators manage their own accounts and payment processes. Their general sign-in flow uses a mobile number or email with a password, and many operators send a one-time code by SMS. Operators may request identity documents for KYC before a withdrawal. These are operator processes, not Tower Rush account features.
Before submitting personal or payment details, identify the company that will hold the account and read its privacy notice. The operator registration steps describe the general account flow, but they do not establish any particular operator’s privacy practices. Payment methods and limits also depend on the operator.
How can readers check privacy before sharing details?
Use these three checks before entering account details at an operator:
- Confirm that the privacy notice belongs to the operator that will hold the account, rather than to the game or this site.
- Look for the information collected, including account details and identity documents, and check the stated purposes, recipients and retention terms.
- Use the operator’s own published contact route for questions about account data, KYC documents, payment information or a data request.
Demo play and operator account use are separate activities. The demo needs no sign-up and uses Fun credits with no cash value; deposits, withdrawals and account records belong to an operator’s real-mode service. The available facts do not establish how any specific operator handles those records.
Where is the privacy contact?
For a question about this site, the Contact page is the stated editorial route. No separate privacy contact details are specified here, so use the editorial contact page for a site-related question. For account information or KYC documents submitted to an operator, contact that operator through its own published route.
The editorial method explains the scope of this site’s content, not its technical storage settings. The available information leaves cookie controls, server-log practices and retention periods unresolved; contact the relevant organisation for details about its own records.