Reference

toke88 Privacy Policy For Your Account

toke88 Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account clarityWallet dataCookie choicesContact path
toke88 toke88 Privacy Policy For Your Account
CONTACT YOUR WAY

Privacy Questions Near The Wallet Path

A clear contact route helps you act on your Privacy Policy rights without searching through unrelated pages. Send a request through the account support channel when you need to correct a phone number, ask why a device signal was recorded, or question a wallet reference. Include your account identifier and the date of the event, but do not send a password or full payment credentials. We handle requests during our listed support hours and may ask for an account step to confirm that the request comes from you.

Team online

Account support

Use the signed-in support path for a Privacy Policy request about your name, phone verification, login history or account access. We can match the request to the right account record while keeping your password and full wallet credentials out of the conversation.

Payment receipt help

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the receipt number and transaction date through support. We use those details to locate the payment record, check its status and explain what information is retained for reconciliation.

Device access help

Contact us when a phone, browser or sign-in event looks unfamiliar. We may ask you to confirm the recent account step, then explain the device data connected with that event and help you secure access without requesting your password.

DATA HANDLING

What We Keep And Why

Privacy Policy choices are easier when each data use has a practical reason. We separate account operation, security checks, payment matching and cookie controls so you can ask about one area without…

Account records

We use your submitted account details and phone verification status to create, maintain and protect access. If you request a correction, we compare the requested change with the account step already on file before updating the relevant record.

Cookie controls

Cookies and similar browser storage can remember a session, support security checks and show whether a page loads correctly on your device. You can manage available cookie controls in your browser, although turning some off may affect sign-in or saved preferences.

Device signals

A mobile browser or desktop session may provide language, browser, operating-system and security-event details. We use these signals to detect unusual access and troubleshoot account pages, not to request unrelated content from your device.

Payment references

DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri, BNI, bank transfer and virtual account activity can create reference data. We use the reference, amount status and date to match a receipt, investigate a delay and answer a payment-data request.

Retention periods

We keep account, security and payment records for the period needed to operate the account, resolve disputes, investigate misuse or meet a legal request. Ask support which category applies to your record and whether deletion or restriction is available.

Your requests

You can ask for access, correction, deletion where available, restriction, objection to a particular use or an explanation of our data handling. We may verify your identity through the account path before responding, so another person cannot change your records.

Privacy Policy Answers For Indonesia

These Privacy Policy questions cover the practical points you may check before opening or using a toke88 account. We answer them in plain terms, with examples from phone verification, mobile access and Indonesian wallet references. If your situation is not listed, use the account support path and describe the specific record or event you want us to check. Availability depends on local law.

The toke88 Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains why we use each category, how long records may remain and how you can request access, correction, deletion where available or other handling changes.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account records. We use these references to match receipts, check payment status and answer account questions; we do not need your wallet password for that process.

When you sign in from a mobile browser or desktop, we may collect browser type, operating system, language, session details and security events. The Privacy Policy describes this data as technical information used to keep access working, identify unusual sign-ins and resolve account problems.

Send a data-access request through the signed-in account support path. State that you are asking under the Privacy Policy and identify the record category, such as phone verification, login history or QRIS receipt references. We may confirm your account step before releasing the applicable data.

You can ask us to correct inaccurate account details or request deletion where available under the applicable rules. Contact support with the specific field or record. We may retain security, dispute or payment information for the required period, even when another record can be changed.

Account access and data rights can differ by location, so our Privacy Policy states that access depends on local law and is offered where local law permits. This wording applies in Indonesia and helps us handle requests according to the rules relevant to your location.

Use the account support channel and describe the concern in direct terms, such as an unfamiliar device event, an incorrect GoPay reference or a cookie question. Include your account identifier and event date, but never send your password or complete wallet credentials.