Reference

Privacy Policy for Your toke33 Account

toke33 Privacy Policy explains what we collect when you open an account, use the mobile lobby, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
Explore Home Lobby Read FAQ
toke33 Privacy Policy for Your toke33 Account
HELP WITH YOUR RECORDS

Get Privacy Policy Help From Account Support

A clear support path matters when your account record or wallet status needs attention. From the signed-in account area, send a request about personal data, cookie choices, phone verification, or a payment reference. In Jakarta and across Indonesia, the same route keeps your request attached to the correct account instead of asking you to repeat private details in an open channel. We may ask for account checks before discussing records.

Team online

Account request

Use the support route inside your signed-in account to ask about collected data, a correction, or a copy of records. We check the account and phone verification details before sharing anything connected with your profile.

Wallet status

If DANA, OVO, GoPay or QRIS shows a payment status you do not recognise, include the displayed reference and date in your private support request. We use that context to locate the relevant record without requesting your wallet password.

Access concern

When a sign-in or data request stalls, contact us from the account support path and describe the device route you used, such as mobile browser or desktop. We can then separate an access issue from a privacy request.

OUR DATA PRACTICE

What We Do With Account Data

We keep the Privacy Policy practical by tying each data use to an account action. Phone verification helps us connect the right person to the right sign-in, while device and security signals…

Account details

We use the details you provide during account creation and phone verification to create your profile, return you to the right signed-in session, and answer requests about data held under that account.

Device signals

A mobile browser or desktop sign-in can produce security signals such as session and device context. We use these signals to help identify unusual access, protect your account, and investigate an access question.

Cookies

Cookies can keep essential session settings available while you move from login to the lobby. Where choices are offered, you can adjust non-essential cookie preferences through the site controls rather than changing your wallet settings.

Payment records

A DANA, OVO, GoPay or QRIS status may be linked with an account reference, while bank transfer and virtual account records help us answer cashier-status questions. We do not ask for your wallet password through support.

Retention

We retain account, security, support and payment records only as long as needed for the stated account purpose, dispute handling, security checks, or a legal duty that applies where local law permits.

Your request

You can ask us to access, correct, or remove eligible personal data through the signed-in support route. We confirm ownership first, explain any record that must remain, and respond using the contact path attached to your account.

Privacy Policy Answers For toke33

These Privacy Policy answers focus on the questions you may have before opening an account or connecting an Indonesian wallet. We explain the practical route for access, correction, cookies, payment records, and account security without asking you to publish private details. If your situation is not covered here, use the signed-in support path and include only the account context needed to locate your request.

It covers data collected when you open an account, verify your phone, sign in, use the mobile or desktop lobby, contact support, or connect DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. It also explains cookies, security use, retention, and available data requests.

We may hold the account details you submit, phone verification status, sign-in and device signals, support messages, and payment-status references. We use them for account access, security, cashier-status questions, and policy requests. We do not need your wallet password to investigate a payment reference.

Sign in and use the account support route to request access to eligible records. Tell us which account contact and time period the request concerns. We confirm ownership before responding, because sending account data to an unverified requester could expose your private details.

Yes, you can ask us to correct eligible account details through signed-in support. Include the field that needs attention and the reason for the change, but do not send a wallet password. We may retain the original record where security, dispute handling, or local law requires it.

Payment flows can provide a status, reference, amount, and account-linking context so we can identify a cashier event. We use that record to answer your request and protect the account. OVO, GoPay, bank transfer, and virtual account records follow the same policy approach.

Yes. Necessary cookies can keep your signed-in session and required site settings working as you move from a mobile browser to the lobby. Where cookie controls are available, you can adjust non-essential choices there. Changing cookies does not change your account or wallet records.

You can submit a deletion request through the signed-in support path where local law permits. We first verify ownership and identify the records involved. Some account, payment, security, or support records may need to remain for a stated legal, dispute, or protection purpose.

Related Pages

toke33 Indonesia bet364 FAQ About Us wbola