Let us start with what we do not handle
There is no registration on the site, no sign-in and no payment interface. We do not ask for your name, date of birth, document number or card details, because none of our functions would need them.
Nor do we run gaming accounts. Balances, deposit histories, bonus status and documents uploaded for verification arise solely at the operator and stay there, under its own data handling rules.
What does arise here is traffic and technical in nature: cookies, aggregated statistics and server-side log entries. The sections that follow describe those three categories.
Cookies in your browser
Cookies are small text files stored by your browser. Some of them are needed for the site to work, for instance to remember settings or to stop a notice you have already accepted from reappearing on every load.
Others serve a statistical purpose and help us understand how a visit unfolds: which page you arrive on, how long you stay, where you click next. We look at these in aggregate, without identifying individual readers.
Managing cookies stays in your hands. You can block or delete them in the settings of every common browser, and you can also change your consent in the notice shown on the site. After switching off statistical cookies the articles remain just as readable; at most a few convenience settings will not be retained.
Traffic statistics
We follow how widely articles are read through aggregated statistics. From this we can see which slot reviews attract more interest, on which page many readers stop reading, and what kind of device the traffic arrives from.
This data is useful in aggregate form, not person by person. We do not attach names or email addresses to it, and we do not build reader profiles from it for advertising purposes.
The aim is practical: the editorial running order and the structure of the texts depend on it. If a longer explanation of a mechanic is consistently abandoned halfway through on mobile, we rewrite it. We have written more about that approach on the about us page.
Server-side logs
Every website's server keeps logs, and this site is no exception. A log entry typically contains the IP address, the time of the request, the address of the page requested, the browser type and the status code of the response.
These entries arise automatically and we do not use them for marketing. Their role is operational and defensive: troubleshooting, load analysis, and filtering out abusive and automated traffic. We have written in more detail about technical protection on the security page.
The table below sums up the three categories of data.
| Data category | How it arises | What we use it for | How long we keep it |
|---|---|---|---|
| Functional cookies | stored by your browser | remembering settings | until the cookie expires or is deleted |
| Statistical cookies | on the basis of consent | aggregated readership | until the cookie expires or consent is withdrawn |
| Traffic statistics | collected by the measurement code | content decisions | in aggregate, for a limited period |
| Server logs | automatically, by the server | operational security, troubleshooting | for the usual operational period |
| Incoming emails | you send them | replying and handling the matter | for a reasonable period after the matter is closed |
If you write to us
We use the contents of a message sent to the editorial team to reply to you and for nothing else. We do not put your email address on a newsletter and we do not pass it to third parties for advertising.
Please do not send unnecessary personal data: we have no need for a password, a card number or a copy of an identity document in any matter. If something of that kind does arrive, we delete it and let the sender know.
The contact details for correspondence and a description of who handles what can be found on the contact page. Data handling related to accounts, deposits and withdrawals is governed by the operator's own notice, not by this document.
Your rights
Under European data protection rules you may generally request access to the data held about you, its correction or erasure, ask for the processing to be restricted, and object to the processing. Where the basis is consent, typically with statistical cookies, you may withdraw that consent at any time; doing so does not affect the lawfulness of processing carried out beforehand.
Since we do not maintain user accounts, most requests first require identifying which category of data is involved. For cookies this is quickest to settle in your own browser, and for correspondence it is enough to reference the earlier message.
We receive requests of this kind at redakcia@ducatbet.bet. Please indicate in the subject line that it concerns data handling, and describe briefly what you would like. The option of turning to the supervisory authority is open to you in every case.
This notice may change if the operation of the site or the measurement tools it uses change. We show the date of the current version at the foot of the page, and we have written about the risks that come with gambling and the ways of limiting them on the responsible gaming page.