Our sources
The main source is the Privacy Policy on the official Dukat.bet website. For comparison we also opened the FAQ page and the AML/KYC Policy, as they address document retention differently. We read all the texts on 8 October 2026.
The documents are available in English and Hungarian; we quote the English text. The Privacy Policy explicitly refers to the principles of the GDPR, Regulation (EU) 2016/679.
Where the document is silent, we say so plainly. We do not fill gaps with guesses.
What the document states: overview with check dates
| Fact | What the source says | Source | Checked |
|---|---|---|---|
| Data collected | first name and surname, address, contact details, email, payment details, username; a passport scan may be requested for verification | Privacy Policy | 8 October 2026 |
| Collected automatically | browser type, IP address, referring website | Privacy Policy | 8 October 2026 |
| Purposes | identity verification, payments, service delivery, communication, website optimisation, offers, paying out winnings, dispute resolution, legal compliance | Privacy Policy | 8 October 2026 |
| Onward transfer | to affiliated companies and business partners regardless of country; to authorities where required by law | Privacy Policy | 8 October 2026 |
| FAQ claim | data is ‘never shared with third parties’ | FAQ | 8 October 2026 |
| Your rights | access, rectification or erasure, restriction of processing, portability, information on retention period, complaint | Privacy Policy | 8 October 2026 |
| Data request | email to dpo@dukat.bet with a passport copy; response time not stated | Privacy Policy | 8 October 2026 |
| Fee and refusal | reasonable fee for repeated requests; manifestly excessive requests may be refused | Privacy Policy | 8 October 2026 |
| Data breach | supervisory authority within 72 hours; the user immediately if there is a high risk | Privacy Policy | 8 October 2026 |
| Retention | for the duration of the relationship and 3 years after it ends | Privacy Policy | 8 October 2026 |
| Verification documents | at least 5 years | AML/KYC Policy | 8 October 2026 |
| Encryption | stated as used; type and version not given | Privacy Policy | 8 October 2026 |
| Cookies | essential, functional and advertising; Facebook, Google and Reddit pixels only with consent | Privacy Policy | 8 October 2026 |
Don't mix up the two retention periods. Three years after the relationship ends applies to ordinary data under the Privacy Policy. Five years is the minimum for identity verification documents under the AML/KYC Policy – a different category under a different document. What exactly is checked during verification is covered in our article on KYC and security.
Where the FAQ and the Privacy Policy contradict each other
The FAQ page claims that data is never shared with third parties. The Privacy Policy goes into more detail: it allows data to be passed to affiliated companies and business partners, regardless of the country where they are based, and to authorities where the law requires it.
The more detailed wording, the Privacy Policy, is the binding one. The FAQ reads more like simplified marketing copy.
The sober conclusion for you: assume your data may travel beyond a single company. The document does not list who the ‘business partners’ are. If you want to know, that is a legitimate question to put in a request to dpo@dukat.bet.
How to request your data
The procedure under the Privacy Policy is simple, if not entirely convenient:
- Email dpo@dukat.bet from the address registered on your account.
- State what you want: access to a copy of your data, rectification, erasure, restriction of processing or transfer in a structured, machine-readable format.
- Attach a copy of your passport – the document explicitly requires it. You can write ‘for data request purposes only’ and the date across the copy.
- Keep the sent email and every reply.
The Privacy Policy gives no response deadline. Under the GDPR, a controller normally has one month to respond, and should not drag its feet. If nothing happens, that gives you grounds to chase.
For repeated requests the operator may charge a reasonable fee. Manifestly excessive requests may be refused.
Erasure has one limit: under the AML/KYC Policy, identity verification documents are kept for at least 5 years, so the operator will not delete them on request. According to the Privacy Policy, you also unsubscribe from marketing messages by emailing dpo@dukat.bet.
The browser padlock: a thirty-second check
The Privacy Policy says the operator uses encryption but not which kind. It mentions neither SSL nor TLS, nor a protocol version, so we add nothing. You can still check the connection yourself (this is a general method, not information from the documents):
- The address bar must show https:// and the exact domain dukat.bet – no extra letters, hyphens or a different ending.
- Click the icon left of the address (a padlock or settings icon). The browser shows whether the connection is secure and who the certificate was issued to.
- If the browser reports a certificate error or an ‘insecure connection’, enter nothing and close the page.
The padlock confirms only encrypted transfer between you and the server. It says nothing about who runs the site or how it handles data.
Copycat sites with look-alike domains often have a valid padlock too, so the address counts, not the icon. How to guard against fraudulent login links is described in our article on login protection.
Where to turn when no reply comes
Your first point of contact is always the operator, at dpo@dukat.bet. If no reply arrives or you disagree with it, you can complain to a supervisory authority.
In this context the Privacy Policy names the European Data Protection Supervisor, an EU body that mainly oversees the Union's own institutions. For an ordinary user it is more practical to go to your national data protection authority (e.g. NAIH in Hungary or the Slovak Office for Personal Data Protection) – under the GDPR you can turn to the supervisory authority in the country where you live. Attach a copy of your request and the full correspondence.
Disputes over withdrawals or a blocked account are a separate matter and fall outside data protection. They follow the complaints procedure in the Terms & Conditions; for payments, see our page on safe payments.