Wildies and Your Data: What We Collect and Why
Account data, transaction records and verification documents: those three categories cover what an account with us involves, each kept for a stated purpose and each subject to a retention period we publish as a number.
Two principles govern the rest: we collect for a purpose already named, and we keep for a period already stated, so a player can always trace both.
Information an Account Carries
The categories are few and concrete, each tied to a function of the account:
- Account data from registration, the details that identify the account holder.
- Transaction records of deposits, wagers and payouts, which also appear to the player as game and payment history.
- Verification documents where the first payout or a 10,000 EUR deposit total triggers the check, a photo ID, proof of address and sometimes proof of payment-method ownership.
- Support correspondence with live chat and email, kept so a conversation continues without repeating itself.
How Changes to This Policy Reach You
Where a change appears first
Material changes appear in the policy itself, with the date line at the end updated so a returning reader sees at a glance whether anything moved since the last visit.
When changes take effect
A change governs from its publication onward, and continued use of the account after that point reads as acceptance; significant changes to purpose or retention are worth a fresh look at the table of periods.
How Long Information Is Kept
| Data type | Retention | Why it is kept |
|---|---|---|
| Account data | For the life of the account | Operating the account and its access |
| Transaction records | After closure, for the legally required period | Payment records and dispute handling |
| Verification documents | For the required retention after review | Proof that identity stood confirmed |
| Support messages | With the account history | Continuity of unanswered questions |
Your Rights Over the Data
- A request for access asks what the account holds, answered through our live chat and email support routes.
- A correction request fixes inaccuracy in account data, the same route, without a new identity check where the record already stands verified.
- A deletion request covers what the retention table does not legally require us to keep, applied at the account level.
- A complaint about data handling travels the same support route and is answered in writing.
How Each Type Is Used
Account data serves access and identification, transaction records serve the money flow and its history, verification documents serve the payout gate, and support correspondence serves the conversation itself. Marketing does not run on documents, and nothing collected for a stated purpose changes purpose silently: a new purpose arrives with a new statement in this policy, not with a quiet reuse. We treat the retention table as the short contract of the policy, and the date line records when that contract last moved.
Last updated: 19 November 2026
