Type by type: what data arises here and what does not
| Data | Created on d-ucat.bet? | Where it is actually processed |
|---|---|---|
| Card number, IBAN, crypto wallet address | no | in the Dukat.bet cashier, if you pay there |
| Username, password, balance | no | in your Dukat.bet account |
| ID card, address card, selfie | no | in Dukat.bet’s verification process |
| Visit statistics | yes, aggregated | Google Analytics 4 |
| Emails you send us | only if you write | in the editorial mailbox |
The site has no registration, login, newsletter, forms or comment section. You cannot pay for anything here either.
This is not modesty; it simply follows from how the site is built.
Who is responsible for this site
The d-ucat.bet editorial team, reachable by mail at Štefánikova 2, 811 05 Bratislava, in the Slovak Republic. Privacy questions also go to info@d-ucat.bet – we have not appointed a separate data protection officer, because the range of data we handle is this narrow.
We have no data link whatsoever with Dukat.bet: we receive no data from them and pass none to them.
Visit measurement: GA4 cookies, no cookie banner
Traffic is measured by Google Analytics 4: which page is opened, on what device, roughly from which country and from where the visitor came. We see aggregated reports from this and cannot identify individual readers.
GA4 places cookies in your browser. The site does not currently show a cookie consent banner, so if you would rather stay out of the statistics, you can block cookies in your browser settings or install Google’s browser add-on that disables Analytics. The site stays fully readable without measurement.
A few of our links to Dukat.bet carry UTM parameters. All Dukat.bet learns from them is that the visit came from d-ucat.bet – not your name or your email address.
Once you click through, Dukat.bet’s rules apply
As soon as you land on dukat.bet, all data is handled under their privacy policy (as read on 14 October 2026). Section 7 of that policy says data is kept for the whole duration of the relationship and for three years afterwards. Section 10 says advertising pixels require consent, which has to be given via a cookie banner.
You can ask about your own data at dpo@dukat.bet (section 12). How to protect your card and wallet details in practice is shown on our transaction protection page, while Dukat.bet’s own verification and security rules are summarised on the security and KYC page.
Your rights and where to complain
Under Regulation (EU) 2016/679, the GDPR, you are entitled to find out which of your data we process, to have it corrected or erased, to have processing restricted, and to object to it. Requests go to info@d-ucat.bet.
GA4 data often cannot be tied to a specific person. If so, we say it straight out.
With our editorial office in Bratislava, we fall under Slovakia’s supervisory authority for personal data, Úrad na ochranu osobných údajov SR. Readers living in Hungary may equally lodge a complaint with NAIH, the Hungarian data protection authority.
Before you send us anything
If you write to us, your message and address are used only to reply and to follow up the correction; nobody else receives them, and we do not hold on to them once the matter is closed.
Do not send ID copies, bank statements, card photos or passwords – we need none of them. How to structure a message is covered on the contact page, and who we are on the about page.