Tower Rush Privacy Policy

tower-rush-politika

Personal information may be involved when Tower Rush is opened, when game-related features are used or when an account is created with an online casino. This Privacy Policy explains the main categories of information, why they may be needed and what choices are available. Tower Rush is developed by Galaxsys, while casino operators manage registration, account balances, deposits and withdrawals. Each organisation handles information relating to the services it provides.

Information Collected

Information Type	Examples	Purpose
Technical details	IP address, browser type, device information and request time	Loading content, maintaining connections and checking technical errors
Cookies and preferences	Session identifiers and saved settings	Remembering selected options and supporting available features
Voluntary contact details	Name, email address and the content of a message	Responding when a contact option is used
Game information	Session events, selected stake and completed results	Running the game and recording activity where supported
Casino account details	Contact information, account credentials and verification records	Creating and managing a casino account
Payment information	Transaction amount, reference and payment method	Processing deposits, withdrawals and related checks

Not every service requests or stores all these details. A technical session identifier is different from an identity document, and a game result is different from a bank transaction. Personal information should be supplied only when it is necessary for a chosen service. Passwords, wallet PINs and one-time verification codes should never be shared through an unsolicited message.

How Information Is Used

Information is used according to the function being accessed. Ordinary technical data may support page delivery and help identify failed requests. Details submitted through a contact option are relevant to the enquiry. Information provided to a casino supports its account and payment procedures. Common purposes include:

Providing access: Loading Tower Rush information, maintaining a working session and displaying supported game features.
Remembering choices: Keeping available language, privacy or session preferences where the relevant setting is enabled.
Checking performance: Identifying connection problems, errors and unusual activity when technical records or monitoring tools are in use.
Answering enquiries: Using the information included in a message to understand and respond to the request.
Managing casino activity: Registering players, confirming identity, recording transactions and handling withdrawals under the operator’s own conditions.

These purposes do not mean that every type of information is used for every activity. A person reading about a feature does not automatically need to provide the information required to open a casino account.

Cookies and Preferences

Cookies are small pieces of information that a browser can store between visits. Similar functions may use browser storage or technical identifiers. They can help retain a session, remember selected preferences or measure how a feature performs. Some functions require technical storage, while optional analytics and promotional tracking depend on the tools being used. Browser settings provide several ways to manage this information:

Review permissions. Check any available cookie controls and examine the privacy settings in the browser.
Clear or restrict storage. Remove saved cookies or block selected categories. Some session preferences may be lost, and certain features may need to be loaded again.
Check casino preferences separately. When Tower Rush is opened through a casino account, the operator may offer its own cookie and communication settings.

Deleting cookies does not necessarily remove records already stored by another service, such as a casino payment history. Browser controls and requests concerning account records are different actions. The settings available also vary by browser and device.

Casino Accounts and Payments

Galaxsys develops the Tower Rush game, including its floor-building mechanics, multipliers and bonus features. A casino offering the game manages its players’ profiles and financial transactions. Using a casino account may therefore involve information that is not required to read about Tower Rush or try an available demo.

Registration can involve a name, contact details, date of birth and login credentials. Before a withdrawal, an operator may request identity verification or confirmation that the payment method belongs to the account holder. The scope of those checks depends on the operator’s procedures.

For players using PKR, a deposit may pass through a bank, card provider or mobile wallet such as Easypaisa or JazzCash. The payment service can process the amount, reference number and payment details needed for that transfer. The casino may hold a corresponding record in the account history. Its rules determine available methods, account limits and withdrawal requirements.

A successful Cash Out in Tower Rush records an in-game payout. It does not by itself transfer money to a bank or wallet. Information required for a later withdrawal is managed through the operator’s payment process. Casino account holders should read the operator’s privacy terms before providing documents or financial details.

Sharing Information

Different services may take part in delivering a game session or completing a payment. Their roles should be understood separately. A technical provider may handle connection data, while a casino and its payment partner handle account and transaction information. Identity verification may involve an additional authorised service.

Opening an external casino link can pass ordinary connection information and, in some cases, a referral or campaign identifier. That is not the same as providing a bank password or identity document. Information entered after a casino opens is handled under the receiving operator’s policies.

Personal data should only be used or shared for an identified purpose and under applicable requirements. The information handled by Galaxsys as a game developer should not be confused with the full customer records held by individual casinos. Payment details, player verification and marketing choices may be governed by separate notices from the organisations responsible for them.

Storage and Security

Information does not always need to be kept for the same length of time. Temporary session details can expire when they are no longer needed. Technical records may be retained to investigate errors or protect a service. Casino account and transaction records may be kept for longer where operational or record-keeping requirements apply.

Removing information from a browser does not automatically erase records held by a casino or payment provider. A request to remove personal data should be directed to the organisation that stores it. Some records may need to remain available for an existing transaction, dispute or other applicable obligation.

Security measures vary by service. Access controls, protected connections, software updates and checks for suspicious activity are examples of measures that can reduce risks. They do not make online information completely immune to loss or unauthorised access.

Users can also reduce avoidable risks by choosing strong, unique passwords, keeping devices updated and signing out on shared devices. Verification codes and wallet PINs should be kept private. Unexpected requests for personal documents or payment details should be checked with the relevant provider before anything is submitted.

Privacy Choices

Questions about personal information are best addressed to the organisation holding it. The appropriate contact depends on whether the request concerns a browser preference, a message sent through a contact option or an account maintained by a casino. Depending on the service and applicable rules, available requests may include:

Access to information: Asking what personal details are held and why they are used.
Correction: Updating inaccurate contact, account or verification details.
Deletion or restriction: Requesting that information be removed or its use limited where such an option applies.
Communication preferences: Changing available marketing choices, cookie settings or optional notifications.

A provider may ask for identity confirmation before releasing or changing sensitive information. Some requests cannot be completed immediately if records are still needed to process a payment or meet another obligation. For casino registration, deposits, withdrawals and account closure, the operator’s published support and privacy channels are the appropriate point of contact.

Updates and Questions

Privacy information may change when game access, technical features or account procedures change. The current version should be reviewed when using a new service or providing personal details for the first time. A new Tower Rush release does not automatically change the payment or privacy rules of every casino offering the game.

Questions about casino account data, payment history or identity verification should be sent to the relevant operator. Questions about a separate payment transaction may also need to be addressed to the payment provider. Requests should include enough detail to identify the issue without disclosing passwords, one-time codes or other unnecessary confidential information. Information about spending limits, session control and support options is available under Responsible Gambling.