Reference

kopi4d Privacy Policy And Your Account

The kopi4d Privacy Policy explains what we collect when you open an account, sign in from a phone, or check DANA and QRIS status.

Account dataWallet statusDevice choicesPrivacy requests
kopi4d kopi4d Privacy Policy And Your Account
CONTACT THE DESK

Privacy Help Beside Your Account

A clear contact route matters when a Privacy Policy question involves your own account record.

Account privacy request Ask about the data attached to your account through the signed-in support path. We may ask for the verified phone step or another account detail so we can confirm that the request comes from you before discussing stored records.
Wallet record check For a DANA, OVO, GoPay or QRIS privacy question, include the payment reference and date shown in your cashier history. We can use that context to separate your record from another transaction without requesting your wallet password.
Correction request If your account data is inaccurate, tell us which field needs attention and why. Our support path can route a correction request to the team handling account records, while access or eligibility still depends on local law.
HOW WE HANDLE DATA

Live Blackjack Salon And Data Controls

Privacy controls follow the same account path whether you browse Live Blackjack Salon, Dragon Tower Mobile Play or Liga 1 Mix Parlay from a mobile browser.

Data collected

We may collect your phone verification result, account identifiers, device signals, session events and payment references. If you contact support about a receipt, the message and attached context can become part of the account record used to resolve that request.

Cookie choices

Our pages may use cookies or browser storage for sign-in continuity, language preferences and session measurement. You can clear or restrict them in your browser, but doing so may require another account check when you return from a mobile device.

Account security

We use phone verification, session controls and device signals to reduce unauthorised account access. Never send us a password, wallet PIN or one-time code in a support message; our privacy team does not need those secrets to handle a request.

Payment records

A DANA or QRIS status check can require a reference, amount and time from your account history. Bank transfer and virtual account records may be retained with the related BCA, BRI, Mandiri or BNI reference for reconciliation.

Retention period

We keep account, support and payment records only for the period needed for account operation, dispute handling, security checks or legal duties. When a record is no longer needed, our retention process removes it or separates it from direct account identifiers.

Change or deletion

You can ask us to correct, access or delete eligible personal data through the privacy request path. We may retain limited records where local law permits or requires it, and we will explain any restriction connected with your request.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the searches we expect from someone deciding whether to open a kopi4d account from Indonesia. They cover phone verification, mobile browsing, local wallet references, cookies, deletion requests and the route for asking about personal data. If your question involves eligibility, access depends on local law.

It covers account details, phone verification, device signals, cookies, support messages and payment references connected with your use of the service. It also explains why we use those records, how long they may remain available and how you can request access or changes.

Phone verification helps us connect an account request with the person seeking access and reduces mistaken or unauthorised sign-ins. We record the verification result rather than asking you to place a password or wallet PIN inside a privacy request.

Yes. The Privacy Policy covers payment references and status details created when you use DANA, OVO, GoPay or QRIS. These records help us match a receipt or pending status with your account, while wallet passwords and PINs should never be sent to support.

We may receive browser, device, connection and session signals when you sign in or move between account pages. These signals help protect the session and diagnose an account issue on mobile or desktop; they are handled as part of the account security process.

You can ask us to delete eligible personal data through the privacy request path, along with any relevant account identifier. Some account, payment or support records may need to remain where local law permits or requires retention, and we will explain that limitation.

Use the signed-in support path and state which account field is incorrect, such as a phone detail or profile entry. Include enough account context for verification, but do not send a password, wallet PIN or one-time code with the correction request.

Cookies and browser storage can retain sign-in preferences and session behaviour, so clearing them may lead to another account check on your next visit. You can manage these settings in your browser, while some account functions may require selected storage to operate.