https://casino.tymoshenko.com.ua/en/glossary/gdpr/ If you play with a UA casino or are considering registration, knowing how to request a personal data export matters. A data export shows what the operator holds about you: ID checks, deposits, game history and marketing flags.
This guide explains the practical steps to get that export and what to expect from a Ukrainian operator. It is written for English-speaking players who want clear, usable procedures before signing up, claiming bonuses or making larger deposits.
When and why you might request your export
Players ask for a data export for several sensible reasons. You might want to verify the accuracy of KYC documents, check transaction records for tax or budgeting, or confirm that an account closure removed marketing consent. If you live in the EU or the UK, GDPR gives you rights when a site targets you or processes your data in those territories. For background on the framework, see .
What a standard data export contains
| Type of data | Typical contents | File format | Why it matters |
|---|---|---|---|
| Personal details | Name, email, date of birth, address | CSV / PDF | Confirms identity and contact info |
| Account activity | Login timestamps, IPs, game sessions | CSV / JSON | Useful for dispute resolution |
| Financial records | Deposits, withdrawals, balances, payment refs | CSV / PDF | Essential for audits and chargebacks |
| KYC documents | ID scans, selfie checks, proof of address | PDF / image files | Shows what the operator verified |
| Preferences & marketing | Consents, promo history, contact choices | CSV / PDF | Helps manage opt-outs |
Step-by-step: how to make a clear DSAR
- Check the privacy policy first: find the data controller name and the published DSAR procedure. Many casinos have a dedicated email address or web form.
- Prepare identity proof: a scan of a passport or ID and a recent utility bill commonly required. Use the secure channel the casino specifies.
- Write a concise request: state you are exercising your GDPR right of access, ask for a full data export, and specify the preferred format (e.g. machine-readable CSV or JSON).
- Include account details: your username, registered email, and any account ID to speed lookup. Avoid sharing extra personal data in the request body beyond what’s necessary.
- Set a deadline politely: GDPR gives one month in most cases. Ask for acknowledgement within 7 days and the full dataset within one month.
- Follow up in writing: if you get no response, send a polite reminder and keep copies of all correspondence.
- Escalate if needed: if the operator refuses without valid reason, you can complain to the relevant supervisory authority (see regulatory notes below).
Regulatory context and points of caution
GDPR applies to businesses offering services to EU residents, even if the operator is based in Ukraine. That said, not all UA casinos target EU or UK players; jurisdiction matters. Licensed operators under regulators like the UKGC or recognised EU authorities generally have clearer procedures and stronger enforcement. If a casino lacks a licence or avoids clear contact points, exercise caution before sharing sensitive ID documents.
Also be mindful of identity verification: always use the casino’s secure upload channel (encrypted form or verified email). Never post ID scans on forums or send them via unencrypted chat. For disputes over withheld data, UK players can contact the ICO; EU players should use their national data protection authority. Keep records of your requests and responses; they are useful evidence if you need to escalate.
Key takeaways
Requesting a data export from a UA casino is a straightforward process if you follow the privacy policy, provide minimal identity proof, and state the formats you prefer. Allow the operator up to a month, keep copies of all communications, and escalate to the relevant authority if necessary. Finally, always play responsibly: check licences and age limits (18+/21+ depending on jurisdiction) and use self-exclusion tools if gambling becomes a concern.