Reference

toko88 Privacy Policy for Your Account

Our Privacy Policy explains how toko88 handles the account details, device signals and wallet records connected with your access.

Clear data purposesWallet record contextAccount access choicesPhone verification details
toko88 toko88 Privacy Policy for Your Account
POLICY HELP

Get Policy Help Through Account Support

A clear contact path matters when a privacy request meets a login or wallet question. From your account help route, tell us which record concerns you, such as a phone verification entry, DANA receipt or QRIS status. We may ask for account details needed to locate the request, while avoiding unnecessary payment credentials.

Team online

Account access request

Ask us to locate or explain account data through account help. Include your registered phone detail and the request type so we can check identity before sharing anything.

Wallet record question

For DANA, OVO, GoPay or QRIS records, send the payment reference and approximate date through support. We use those details to match the entry without asking for a wallet password.

Correction request

If your phone, account name or contact detail is inaccurate, identify the field through the support path. We check the account first, then record the requested correction under this Privacy Policy.

SECURITY PRACTICE

Keep Control Of Account Data

We treat privacy as an operating task rather than a footer link. The controls below describe how we handle data while you move from phone verification to the lobby, return on a…

Account data

We use your account identifier, phone verification result and login history to connect access with the correct account. We do not need unrelated personal details to provide this account path.

Cookie choices

Cookies or similar browser storage can remember a session and selected settings. On a mobile browser, clearing site storage may sign you out and remove those saved choices.

Security checks

When account access or a wallet status looks unusual, we may compare login, device and verification records. This helps us protect account data without requesting your wallet password.

Retention timing

We keep account, support and payment references only while they serve account operation, security or legal needs. Afterward, we delete, separate or reduce the record where practical.

Data access

You can ask what eligible account data we hold and why it is used. Where local law permits, we assess the request after checking your account identity.

Policy changes

If this Privacy Policy changes, we place the updated wording on this page. You can return through the policy link near account access and ask support about a specific change.

Privacy Policy Answers For toko88 Accounts

These Privacy Policy answers address the searches we hear most often before account access. They cover wallet references, mobile browsing, identity checks, retention and requests for a copy or correction, with access handled where local law permits.

It covers account details, phone verification, login and device records, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use the verification result to connect account access with the correct phone detail, reduce mistaken access and investigate account requests. We do not use it as a substitute for your wallet password.

Yes. The policy covers session storage, device signals and login records created when you reach the lobby through a mobile browser. Clearing browser storage can sign you out and remove saved settings.

We use DANA and QRIS references to match a payment action with your account, check a receipt or resolve status questions. We ask for a reference, not your wallet password.

You can contact us through account help with your registered phone detail and the data request. We verify the account first, then assess access where local law permits.

Send the field that needs correction through the policy support path, such as a phone or account detail. We check identity, update eligible records and keep the request linked to the account.

Retention depends on the purpose: account operation, security, payment status or legal need. When that purpose ends, we delete, separate or reduce the record where practical and permitted.