Reference

Privacy Policy for coop4d Accounts

coop4d Privacy Policy explains how we handle the account details, wallet records and device signals used when you access Sic Bo, Crash Games or onlinebingo.

Account dataWallet recordsDevice cookiesPolicy requests
coop4d Privacy Policy for coop4d Accounts
CONTACT ROUTE

Get Help With A Privacy Request

A clear contact path helps you ask about a record without explaining your whole account history.

Account identity Tell us the phone number or email attached to your coop4d account when you ask about personal data. We may request an account step before discussing records, so a private request is connected to the correct profile rather than answered from an unverified message.
Wallet reference For a DANA, OVO, GoPay or QRIS question, send the transaction reference and date through the account support path. We can use those details to locate a payment record while you keep your wallet PIN, password and one-time code private.
Policy correction If a contact detail or account record needs correction, explain what appears wrong and what it should say. We will assess the request against the account record and may ask for a verification step before changing data used for access or payment checks.
DATA CONTROLS

What We Do With Your Records

We separate practical account handling from unnecessary collection. Your phone verification supports account access, while wallet references help us trace DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Account records

We use your submitted contact details and phone verification result to connect the right person with the right account. This can include login history and account status needed to investigate access questions, but it does not make your wallet password visible to our support process.

Payment records

A payment selection creates operational records such as method, amount, reference and status. DANA, OVO, GoPay and QRIS checks help us match a cashier event to your account, while bank transfer and virtual account records support reconciliation without requesting your banking password.

Cookies

Cookies can remember session choices and help the mobile route return you to the correct account area. You can manage browser cookie settings on your device, although removing essential cookies may require you to sign in again before reaching the lobby.

Device signals

We may process browser, device and connection signals to maintain a session and spot access that does not match your account pattern. These signals can be relevant when you switch from a phone browser to desktop before opening Sic Bo or Crash Games.

Retention period

We keep account, payment and support records only for operational, dispute or legal needs that apply to the service. When a record is no longer needed for those purposes, our handling process can remove it, restrict it or separate it from active account use.

Your request

You can ask what personal data we hold, request a correction, or ask about deletion or restricted use where the applicable rules allow it. Send the request through account support with your identifying detail, and we will explain any verification or legal reason affecting the response.

Privacy Policy Answers For Your Account

The questions below address the points most often raised before account access: what we collect, how wallet records are matched, what cookies do and how to request a change. Each answer refers to the coop4d Privacy Policy rather than describing game or payment features on their own. If your situation is not covered, use the account support path and identify the record you want us to locate.

The coop4d Privacy Policy covers account details, phone verification, payment references, device signals, cookies, support requests and retention. It explains why we use each category, how it supports account or payment handling, and how you can ask about a record connected to your profile.

Phone verification helps us connect an access request with the account created under that contact detail. It can also reduce mistaken account matches during a DANA, OVO, GoPay or QRIS status check. We use the result for account handling, not as a request for your wallet PIN.

Yes. The Privacy Policy covers QRIS, DANA, OVO and GoPay references created when you use the cashier, along with bank transfer and virtual account records. We use method, reference, status and related account details to reconcile activity and respond to payment questions.

You can send an access request through the account support path and identify the email or phone number attached to your profile. We may verify your identity first, then explain which account, device, cookie or payment records can be disclosed under the rules that apply.

Describe the incorrect record and the correction you believe is needed through account support. Include the connected phone or email, but never send a password or wallet PIN. We may complete an account verification step before changing contact data used for access or payment checks.

Retention depends on the operational, dispute and legal reason for holding a record. Payment references may be needed for reconciliation, while device signals can support access checks. When those needs end, we can remove, restrict or separate the relevant data from active account use.

Yes. The Privacy Policy applies when you use a phone browser to sign in, move from the account page to the lobby, or open Fish Hunter and 1xjkt. Browser cookies and device signals may support that session, and your browser settings control non-essential cookie choices.