Reference

Privacy Policy for your account data

Your account record, cookie choices, and DANA, OVO, GoPay, or QRIS wallet traces are covered here before you open an account.

DANA record handlingCookie choicesAccount data requestsDevice sign-in checks
costum4d Privacy Policy for your account data
POLICY CONTACT

Privacy requests by chat or email

Clear contact paths make privacy requests faster to sort. Use live chat for account-level questions, email us when you need a written response, or open the in-account form if you want us to link your request to your username. We may ask you to verify your mobile number before we discuss wallet records or device activity, because those records can expose private account history.

Team online

Live chat

Chat is open every day from 10:00 to 22:00 WIB, and you can ask how this Privacy Policy applies to your account, login records, wallet entries, or cookie choices before you continue.

Privacy email

Send written requests to [email protected] with your username, registered mobile number, and the data request you want us to check. We reply with the next account verification step when needed.

Account form

After sign-in, head to Account > Help > Privacy Request and choose access, correction, deletion, or cookie question. This route attaches your request to the active account session for cleaner handling.

DATA HANDLING

Cookie data for VIP Baccarat sessions

Privacy controls work only when the account record is accurate. We separate data used for sign-in, wallet matching, game-session checks, cookies, and support messages so each team sees only what it needs.

Account basics

We collect the details needed to create and protect your account, such as mobile number, username, login time, and basic profile fields. We do not ask for unrelated documents during the account opening step.

Wallet logs

DANA, OVO, GoPay, and QRIS records may include status, time, amount, and reference code. We use them to match funds, trace disputed wallet lines, and answer your payment privacy questions.

Cookie choices

Cookies help remember language, session state, and security checks around areas such as VIP Baccarat or Monopoly Live. You can clear browser cookies, though we may need a fresh sign-in afterward.

Device checks

When a new device or browser appears, we may log the device type, IP range, and sign-in time. Open Account > Security > Devices if you want us to check an unfamiliar session.

Retention timing

We keep account, wallet, security, and support records only while needed for service use, dispute handling, fraud checks, or legal duties. When a record is no longer needed, we remove or anonymise it.

Change requests

You can ask us to correct profile data, close unused account details, or explain why a record remains. We verify your mobile number before changing data tied to wallet or security history.

Privacy Policy questions from Indonesia accounts

Your privacy questions usually come up when you open an account, add a wallet, change devices, or ask support to check a transaction. These answers explain what we collect, why we collect it, how to contact us, and how to ask for access, correction, or deletion. We keep each answer tied to the Privacy Policy so you can decide whether to continue with a clear view of the data flow.

We collect account details such as username, registered mobile number, sign-in time, and security markers. If you add DANA, OVO, GoPay, or QRIS records, we also store payment references needed for wallet matching.

Cookies keep your session active, remember basic preferences, and help us check account safety while you move between slots, live tables, or sportsbook pages. You can clear cookies in your browser, then sign in again.

Yes. Send a request through Account > Help > Privacy Request or email [email protected]. We verify your registered mobile number first, then prepare the account, wallet, cookie, and support records we can share.

We use wallet data to match deposits, trace payout questions, and resolve duplicate or failed references. Access is limited to account, payment, security, and support roles that need the record for a clear task.

You can ask support to correct profile data linked to your account. We may require OTP verification, recent wallet reference checks, or a short account question before changing data that protects sign-in access.

We keep records while needed for account service, security checks, payment tracing, dispute handling, or legal duties. When the reason ends, we remove the record, reduce it, or anonymise it where practical.

Yes. Access and eligibility depend on local law and are available only where local law permits. We may use location, device, and account signals to help apply those rules to your session.