Reference

topan33 Privacy Policy For Your Account Data

Our Privacy Policy explains what we collect when you create an account, sign in from a phone, browse Blackjack or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice accessCookie choices
topan33 topan33 Privacy Policy For Your Account Data
REQUEST HELP DIRECTLY

Three Ways To Ask About Your Data

A clear request path helps when your login or wallet status stalls. From your account area, use the support route beside the cashier path and describe the record you want checked. Include your registered phone number, the relevant payment reference and whether the request concerns access, correction or deletion. We use those account details to locate the right record without asking you to send a wallet password.

Team online

Account request

Use the support link inside your signed-in account to ask for a copy, correction or status check concerning personal data tied to your phone verification.

Payment record

For DANA, OVO, GoPay or QRIS questions, share the transaction reference and date shown in your receipt so we can match the correct wallet event.

Access concern

If a device sign-in looks unfamiliar, state the device path and time in your request. We can check security records and explain the next account step.

SIX CONTROL POINTS

Six Data Controls Behind Account Access

We handle this Privacy Policy through practical controls rather than broad promises. Account creation, phone verification, wallet references and device activity each serve a defined purpose.

Collection

We collect account fields, phone verification status, device signals and activity records such as opening Madame Destiny, using only what supports access, security and account service.

Cookies

Cookies can remember sign-in preferences and measure account-area activity. Your browser controls can limit them, although some account functions may then require another sign-in.

Account security

We compare sign-in details, device behaviour and verification events to identify unusual access. Never send us your password or DANA, OVO, GoPay or QRIS secret.

Retention

We retain records for the account, security, dispute or legal purpose that requires them. When that purpose ends, deletion or anonymisation is considered where permitted.

Your contact route

Send privacy questions through the signed-in support path near the cashier area. Your registered phone number and request type help us locate the right account record.

Policy changes

If this Privacy Policy changes, we will place the updated wording in the policy area. Check it before opening Blackjack or continuing through your account path.

Privacy Policy Answers For DANA And QRIS

These Privacy Policy answers address the account and wallet questions we hear most often. They explain what you can request, how device and payment records are used, and where local law affects access. For a case-specific answer, use the support path in your signed-in account and include the relevant reference.

It covers account details, phone verification, device signals, cookies, game activity, wallet references and support requests connected with your topan33 account and its account area.

Phone verification links the account to the contact detail you provide and helps us check sign-in requests. We also use its status when responding to an access or correction request.

Yes. We may receive a DANA or QRIS transaction reference, amount status and timing needed to match the wallet event. We do not require your wallet password.

Where local law permits, you can request access or correction through the signed-in support route. Include your registered phone number and the specific record so we can verify the account.

Cookies may remember sign-in preferences and record basic account-area activity. You can adjust browser controls, but limiting cookies may require repeated sign-in during your mobile device path.

We keep records for the account, security, dispute or legal purpose that applies. When that purpose ends, deletion or anonymisation is considered, subject to local requirements.

Yes. Access or eligibility depends on local law. Where local law permits, we can process requests for access, correction or deletion after confirming the account and request scope.