Reference

tukul777 Privacy Policy, Clearly Explained

Our Privacy Policy explains what we collect when you open an account, verify your phone, browse on mobile, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice choicesContact route
tukul777 tukul777 Privacy Policy, Clearly Explained
CONTACT THE POLICY DESK

Three Ways to Ask About Your Data

A clear contact path matters when your account record, wallet reference, or device detail needs attention. We keep Privacy Policy questions separate from game choices, so your request can focus on personal data, cookie settings, access history, or a correction. Start from the account support route, include the email or phone detail attached to your account, and describe the exact change you want us to check.

Team online

Account access request

Use the support path from the login area to ask for the personal data connected with your account. Include your registered phone detail so we can distinguish your request from another account.

Wallet record question

If a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference appears unfamiliar, send the receipt or status detail through support. We use it to trace the relevant account record.

Privacy change request

Ask us to correct an account detail, explain a cookie setting, or clarify retention by naming the data involved. We may request account checks before changing or disclosing anything.

SIX DATA SAFEGUARDS

What Our Privacy Process Covers

Our handling process follows the same account steps you see in practice: phone verification, login checks, wallet matching, and support confirmation.

Account details

We use contact and verification details to create, protect, and locate your account. Phone verification before access helps us connect a request to the correct record without relying only on a display name.

Wallet references

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference can appear in account records. We use those references for reconciliation, receipt checks, and support replies about a specific transaction.

Cookies and devices

Cookies and device signals help remember sessions, detect unusual login behaviour, and keep the mobile path consistent from login to the lobby. You can ask support which setting or signal concerns you.

Account security

We may compare login details, phone verification status, and device activity when protecting account access. If a security check interrupts your session, contact support rather than sending account credentials in a message.

Retention approach

We retain records for the period needed for account operation, wallet reconciliation, security checks, dispute handling, or applicable requirements. When a record is no longer needed, our process addresses its removal or separation.

Correction route

You can request access, correction, or clarification through the support route. Tell us the field or record involved, such as a phone detail or QRIS reference, and we will explain the next account check.

Privacy Policy Answers for Your Account

These Privacy Policy answers cover the questions we expect before you open an account or ask about an existing record. Each reply points to a practical step, from phone verification and cookie choices to wallet references and correction requests. If your situation is unusual, use the support route and describe the specific data involved.

It covers account details, phone verification, login and device signals, cookies, wallet references, support messages, retention, and requests to access or correct personal data connected with your account.

Phone verification helps us confirm account ownership before access and before handling a data request. It also helps separate your records from another account with a similar name or device.

Yes. The policy covers references linked to DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity. We use these references to match receipts, status checks, and account support requests.

Use the support route from the login area and ask for an account data access request. Include your registered phone detail and the records you want us to locate, such as device or wallet references.

Yes. Send a correction request through support and identify the field that needs attention. We may verify your account first, then explain whether the change can be made and when it will appear.

Cookies and device signals can support session continuity, security checks, and the mobile path from login to the lobby. Ask support about a particular cookie or setting if you want its purpose clarified.

Retention varies by the record's purpose, including security, wallet reconciliation, dispute handling, account history, and local requirements. We can explain the reason for keeping a specific record when you contact support.