How Fugu Casino treats member data
Last updated: 9 October 2026.
This policy explains how Galaktika N.V., the operator of Fugu Casino and referred to here as we, collects and uses the personal data of members. It covers the browser site, the iOS and Android apps, live chat and the support channels. Questions about it go to [email protected].
Who is responsible for member data
Galaktika N.V., registered in Curaçao under number 140803 and operating Fugu Casino under the Curaçao licence OGL/2024/169/0146, decides why and how the data described here is used. Card payments are processed through Unionstar Limited of Cyprus, which receives the payment details needed for a card transaction and applies its own policy to them.
What we collect and when
| Moment | Data | Use |
|---|---|---|
| Registration | Email address, password, full name, date of birth, address, phone number | Creating the account, confirming contacts, age check |
| Verification | Government ID, proof of address, confirmation of the payment method, sometimes a selfie | Identity and ownership checks before payouts |
| Deposit and withdrawal | Payment method, amount, currency (EUR, USD or crypto), transaction time | Processing and tracing payments |
| Play | Games played, stakes, bonus status, VIP tier | Wagering calculation, rakeback, daily limits |
| Support | Chat and email text, Telegram messages, call notes | Answering and recording requests |
We do not ask for documents at registration. They are requested at the first withdrawal, when total deposits pass €2,000 or a single withdrawal exceeds €1,250, and a source-of-funds question may be added from €10,000.
Purposes and the legal basis for each
| Purpose | Data involved | Legal basis, in general terms |
|---|---|---|
| Creating and running the account | Registration data, play data | Performance of the agreement with the member |
| Checking age and identity | Registration data, verification documents | Legal obligations that apply to an operator of this kind |
| Processing deposits and payouts | Payment and transaction data | Performance of the agreement with the member |
| Preventing fraud and unclear ownership of payment methods | Documents, transaction history | Our legitimate interest in protecting the service and its members |
| Answering requests and complaints | Support records | Performance of the agreement and our legitimate interest in service quality |
| Limits and self-exclusion | Limit and exclusion records | The member’s own request, and the protection of the member |
The legal basis depends on the law that applies to the member, so the table states it in general terms. A member who wants to know which basis applies to a particular use can ask at [email protected].
Who else receives data
Payment providers receive the data needed to carry out a transaction: card networks, e-wallet services, banks, exchanges and blockchain networks. Their handling of data is governed by their own policies, which differ from this one. Support conversations on Telegram pass through that messenger. To find out which provider handles a particular payment, write to [email protected].
What each payment route involves
A bank card payment involves the card network and the issuing bank, which see the amount, the time and the merchant. An e-wallet payment such as Skrill, Neteller, MiFinity, Jeton or Revolut involves the wallet provider, which sees the same details together with its own account data. A voucher such as Paysafecard or Flexepin shows the voucher provider that a deposit was made. Apple Pay and Google Pay pass the payment through the phone’s wallet. Exchange routes through Binance or Bybit and cryptocurrency transfers are recorded on the exchange or on a public blockchain, where the wallet address and amount remain visible to anyone who looks. We record the amount, currency, method and time on our side in every case.
Verification documents in detail
A government ID is used to read the name and date of birth, which are compared with the profile. Proof of address is used to check the residence entered in the profile. The confirmation of the payment method shows that the card, wallet or bank account belongs to the account holder. A selfie, when requested, is compared with the photograph on the ID. The review target is up to 48 hours, and the documents are used for that review and for the questions that arise from it. The date of birth in the profile is compared with the identity document, which is how the 18+ rule of the service is applied.
Rights and how to use them
A member may ask what data we hold, ask for a wrong detail to be corrected, or ask for deletion, by writing to [email protected] from the email address of the account and naming the request. Where a payout or a verification is open, records connected with it are kept until it is closed, and we say so in the reply. A request concerning a limit or self-exclusion record is answered the same way.
Records connected with limits and exclusion
When a member asks for a deposit, loss or bet limit, or for self-exclusion, we record the request, its date and the limit agreed. The record is needed so that the limit is applied correctly and can be explained later. A member who wants a limit changed or the record explained writes to [email protected].
Communication with members
We write to members from the support address and answer in live chat, Telegram and email. Messages about an account, a payout or a document request are service messages, and they contain only what is needed to identify the request. Members should not send full card numbers, passwords or one-time codes in chat or by email: documents are uploaded in the account, and support never needs a password.
Retention while an account is active
Registration data, verification documents and transaction records are kept while the account is open and while a payout, a bonus or a document check is unresolved. Support records are kept for the life of the request. A member who closes the account through support should say so in writing, so that the request can be handled together with any open payout.