Privacy Policy for Readers of This Service

4 Fields the Server Logs Record

The server logs record 4 fields and nothing more: IP address, requested URL, user agent and timestamp. The host provides them for security and error diagnosis, and every identifying detail stays out of them.

Nothing is sold. Server logs here stay unsold and unmerged with anything else. They feed no profile, they stay inside this one site, and the pages ship without an analytics script, so a tracking pixel is simply absent.

In Short, What We Hold About You

Here's the honest summary: it's a web server log and that's all. There's no account, no newsletter and no advertising identifier, so there's very little to hand over even when you ask.

You'll still get a straight answer to a data request. If the log has already been discarded, the reply says exactly that, because an empty answer beats an invented one.

Accounts

None

Cookies this site sets

0

Analytics scripts

None

Server log fields

4 (IP, URL, user agent, time)

Own images

100%, served from this domain

Policy dates

26 Sep 2026 / 27 Sep 2026

What Should You Do Before You Start Reading?

Two steps are worth taking before you start, and both are available inside your own browser. Browse the range of privacy settings your browser offers, then explore the operator policy for any casino you intend to visit.

1. Check the privacy settings your browser already applies to this site.
2. Read the operator policy that takes over once a redirect hands you across.
3. Note the date of your visit if you plan to ask what the server kept.

According to the host, an access log lives only as long as current security work needs it, and all 19 pages here are dated. Doing this in advance matters, because a request arriving days later can only be answered honestly.

What Those Logs Leave Out

Every identifying detail is missing from those server logs: name, email address, payment record and gambling history are absent, because none of that is ever gathered here. That is a real limitation of what a data request here can return.

An operator account is a separate world with separate records. We can see a click leaving Tower Rush by Galaxsys and nothing after it.

Cookies, Local Storage and Logs

Cookies here number zero right now, and none are set by this site at all. Cookies stay absent from this policy for a simple reason: the site sets none, so the logs are the only record here. The 2 scripts each page loads rewrite the affiliate button address and add small conveniences such as copy link and back to top.

Neither script sends data anywhere, and the pages ship free of advertising tags. Our methodology for this site keeps the front end static, so a page offers nothing for a tracker to attach to.

Anything else a reader sees is ordinary browser behaviour. Anything a browser keeps on its own, such as a collapsed menu state, stays on the device, and the browser settings clear it at any time.

Affiliate Redirects Beside the Logs

Beside the logs sits one third party. Affiliate redirects are the only outside traffic in play, and this site runs them. Links to licensed casino and betting operators may pass through an affiliate redirect that records the click for commission accounting, and the terms of use explain that arrangement in full.

Once a reader lands on an operator or a regulator site, that site's own policy takes over. 1xBet and 1win each publish their own, and they answer to their own regulator instead of to the editors.

Which Types of Data a Redirect Passes?

The redirect provides a click record and nothing more. It includes no name, no email address and no payment detail, because this service collects none of them from you.

An operator supplies its own tracking once you arrive, and they answer for it under their own regulator. Compared to this site, other casinos collect a great deal, so their notice is the one worth reading. Their privacy policy governs everything after that moment, so you should read it before you register.

The weakness of this arrangement is visibility: the editors cannot see what an operator stores about you, and that limitation is stated instead of glossed over.

Third-Party Software and Embedded Content

No third-party software loads. Embedded content of that kind is absent from every page here. Widgets of that kind appear nowhere on Tower Rush by Galaxsys. Pages carry no video players, social widgets or advertising scripts, so loading a page contacts no other server.

According to the file record, every screenshot here is an original captured in recorded demo sessions of the client published by Galaxsys, part of the Digitain Group, and served from this domain. The testing method page explains where those frames come from.

How Long the Logs Are Kept

The logs go quickly. Retention of the current set belongs to the host, not to us. The hosting provider offers a fixed retention window, and it exists for security and error diagnosis instead of for analytics. They are discarded afterwards, and every log stays inside that single system for the 19 pages this site serves.

Retention sits with the hosting provider, and the window will be named here once that provider is chosen; inventing a figure would be worse than the gap. So write while a log still exists if you intend to ask about a specific visit.

Reader Rights over Those Logs

Reader rights over the current logs follow the same law that applies to any small publisher in the European Union, the European Economic Area and the United Kingdom. A reader may ask what data, if any, the server holds about their visits, and may request its deletion.

Write to the editors through the contact page, name the approximate date and time of your visit, and the request is checked against whatever logs survive. To verify the answer, the editors read the host log directly. However, a log already discarded cannot be produced, and the reply says exactly that.

What Is Left Behind by a Deposit?

The complete list of what a deposit leaves here is empty. A deposit, a withdrawal or a bonus claim happens entirely inside an operator account under its own regulation, so none of it reaches this service. The about page sets out who is responsible for Tower Rush by Galaxsys.

The responsible gambling page explains that this site holds no gambling account data whatsoever, which is also why this desk cannot help with an operator balance.

Terms This Policy Uses

Access log

The line a web server writes for each request, holding an IP address, a URL, a user agent and a timestamp.

Affiliate redirect

A short link that records a click for commission accounting before sending the reader to the operator.

Local storage

A small store inside the browser itself, cleared from the browser settings and never read by this site.

Data request

A message asking what the server holds about a visit, answered against whichever logs still exist.

Does This Site Set Any Cookie?

This site sets no cookie of its own, and the pages load no analytics script, so a reader has nothing here to opt out of and nothing to clear afterwards.

An operator is a different matter once you leave. Their cookies, their tags and their retention rules take over the instant you land there.

Recap: This Policy Compared with an Operator

If you want a one-line answer, the operator policy is the better one to read. This one is short. Compared with an operator, this policy is short: the server logs 4 fields, the site sets 0 cookies, embedded content is absent, affiliate redirects record a click, retention belongs to the host, and a reader may ask what survives. That short list is the whole of the record.

This policy was first published on 26 Sep 2026 and changes only when the technical setup behind Tower Rush by Galaxsys changes; the current wording dates from 27 Sep 2026. Because no accounts exist here, a change reaches readers through this page instead of by email.