Reference

to388 Privacy Policy, Clearly Explained

Our Privacy Policy shows how to388 handles your account details, device signals and wallet records when you use the lobby.

Account clarityPayment privacyCookie choicesRequest access
to388 to388 Privacy Policy, Clearly Explained
HELP WITH PRIVACY

Get A Clear Route For Data Requests

A privacy question should not leave you guessing which account screen to use. We keep the policy contact route close to the login and cashier areas, so you can describe a data concern while the relevant account or payment record is visible. Include your registered phone number, request type and any receipt reference, but never send a password or wallet PIN.

Team online

Account access

If your phone verification or login record looks wrong, use the account support route and explain the exact step that failed. We can check the account reference without asking for your password.

Wallet records

For DANA, OVO, GoPay or QRIS questions, include the payment status and receipt reference shown in your cashier history. We use that detail to locate the relevant record.

Privacy request

Ask to access, correct or clarify personal data through our privacy contact path. We may verify account ownership before discussing records, protecting your details from an unrelated requester.

HOW WE HANDLE DATA

What Your Privacy Policy Covers

We treat privacy as an account process rather than a statement hidden away from the cashier.

Data we receive

We may receive your phone number, verification result, account activity and payment references such as a QRIS receipt.

Cookies and devices

Cookies and device signals can help keep your session connected while you move from login to casino pages.

Account protection

Phone verification is an account security step before access.

Storage period

We retain account and transaction records for as long as needed for the stated account, security and payment purposes, or…

Who to contact

Use the privacy contact route for questions about collection, cookies, retention or account records.

Corrections and changes

You can request a correction when an account detail is inaccurate, or ask how a record is used.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. We keep the wording practical: what we collect, how access works, what cookies do and which details to include when you contact us.

It covers account details, phone verification, device signals, cookies, payment references and support requests connected with your use of to388. It also explains retention, corrections and requests for access.

We use your phone number to create and identify the account, complete the verification step before access and connect a privacy request with the right account record.

Yes. It covers payment references and status details linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps, including receipt details needed for account support.

Where local law permits, you can request access to personal data connected with your account. Include your registered phone number and request details; we may verify ownership before replying.

Send a correction request through the privacy contact path and identify the inaccurate field. We may ask for account verification, then assess the change against payment and security records.

Cookies can keep a session connected between login and the lobby and help us recognise account activity. Clearing or restricting them may require you to repeat verification or login steps.

Yes. Requests and account access depend on local law. Where local law permits, we explain the processing purpose, available rights and any reason a payment record must remain stored.