Who This Notice Covers
This document covers data processing for visitors to the dukatbet.org website. It doesn't cover the Dukat.bet operator's services, account registration, or payment processes—those are governed by Dukat.bet's own privacy notice, available on its official site.
dukatbet.org is a content site: you can read articles about licensing, security, and responsible gambling, but you can't register an account or submit financial data. Accordingly, the data we process is generally narrower in scope than that of an actual service platform.
What Data We Collect
Visiting the site generates a small amount of technical data automatically.
Cookies. dukatbet.org may use cookies to keep the site running and to measure traffic. Cookies are small text files stored by your browser that help us understand how visitors use the site.
Analytics data. For statistical purposes, we may collect anonymized or pseudonymized data, such as page-view counts, approximate visit duration, or referrer type. We analyze this data in aggregate, not to build individual profiles.
Contact data. If you email us, we store the name, email address, and message content you provide for as long as needed to answer your inquiry.
dukatbet.org doesn't collect or request sensitive data such as payment-card details or gambling-account information, since we don't operate that kind of service.
How We Use the Data
We use the data we collect primarily to run the site, keep it secure, and improve content quality.
Analytics data helps us understand which topics interest readers most, so we can prioritize which articles to update or expand.
We use contact data solely to respond to your inquiry, and we don't pass it on to third parties except where required by law.
dukatbet.org doesn't build personalized advertising profiles for marketing purposes.
Legal Basis and Data Retention
The legal basis for processing is generally legitimate interest (running, securing, and statistically analyzing the site), or, for contact requests, your consent when you send us a message.
We generally store analytics data in aggregate form for a limited time. We keep contact messages for as long as needed to close out the matter and allow follow-up, after which we delete or anonymize them.
Illustrative example (not dukatbet.org's actual internal procedure, purely for illustration): many content sites store analytics logs for 12–24 months before anonymizing or deleting them. We can confirm the exact retention period by email on request.
Your GDPR Rights
Under the European Union's General Data Protection Regulation (GDPR), you have the following rights regarding the data we process about you.
| Right | What it means |
|---|---|
| Access | You can request information about what data we hold on you |
| Rectification | You can request correction of inaccurate data |
| Erasure | You can request deletion of your data where there's no lawful basis for further processing |
| Restriction | You can request that processing be restricted in certain cases |
| Objection | You can object to processing based on legitimate interest |
| Portability | You can request a structured copy of the data you provided |
To exercise these rights, simply email the address listed on the contact page with a brief summary of your request.
Managing Cookies in Your Browser
Most browsers let you disable or delete cookies in the settings menu. If you disable cookies, some site features may not work correctly, but you'll still be able to read the content.
Note that dukatbet.org's cookie handling applies only to our own site. If you click through to Dukat.bet, the operator's own cookie practices apply there—see Dukat.bet's official notice for details.
Related Pages
The site's general terms of use are summarized on our terms of use page. You can read more about the editorial team's work and the site's purpose on the About page.
If you have a question about our data practices, or you'd like to exercise one of your GDPR rights, you'll find our details on the contact page.
If you'd rather understand how the Dukat.bet operator handles user data during account registration and the KYC process, see our KYC verification article.