Reference

toko22 Privacy Policy In Plain Terms

Clear account-data choices help you use toko22 with fewer surprises. Our Privacy Policy explains what we collect when you create an account, verify your phone, open Auto Roulette…

Account collectionWallet recordsCookie choicesPrivacy requests
toko22 toko22 Privacy Policy In Plain Terms
REQUEST ROUTES

Three Ways To Ask About Your Data

A direct request path matters when a wallet status, login record or account detail needs clarification.

Account privacy request Use the support route attached to your account when you want to ask what…
Wallet record check For a DANA, OVO, GoPay or QRIS question, include the payment reference and status…
Access and cookie help If browser storage affects sign-in or a privacy choice does not save, contact support…
HANDLING DETAILS

How We Handle Account Privacy

Privacy depends on practical handling, not just a page of promises. We separate account access from wallet references, limit internal access to service needs, and use your submitted details to respond to…

Account data

When you open an account, we record the details needed to identify it and send account messages. A clear phone verification step helps connect access to the correct account. If your phone number changes, request a correction through the account support route rather than creating duplicate details.

Wallet references

DANA, OVO, GoPay and QRIS activity can leave transaction references, status updates and timestamps in our service records. Bank transfer and virtual account requests can carry similar references. We use these details to match receipts, investigate status questions and protect account access.

Cookies and storage

Our site may use cookies or local browser storage to keep a session, remember a privacy choice and support the path from login to the lobby. On a mobile browser, clearing site data can remove that choice and require you to verify access again.

Device security

We may receive device, browser, IP and session signals when you sign in or switch between pages such as Madame Destiny Megaways and the account area. These signals help us spot unusual access. Never share your password, phone code or wallet PIN with support.

Retention approach

We keep personal and transaction records only for the period needed for account service, security checks, dispute handling and legal duties that apply where local law permits. When a record is no longer needed for those purposes, our processes address its removal or de-identification.

Changes and contact

You can ask us to correct inaccurate account details, explain a data use, or clarify a cookie choice through the privacy support route. Include a short description of the request and the affected account step; we may verify ownership before making a change.

Privacy Policy Questions For toko22

These answers address the privacy searches we hear most often before an account is opened or a wallet is connected. They focus on the records created by sign-in, phone verification, game activity, cookies and local payment references. If your question concerns a specific transaction, keep its reference ready when you contact us.

The toko22 Privacy Policy explains how we handle account details, phone verification, device signals, cookies, game activity and payment references. It also sets out retention, account-security controls and ways to request correction or clarification. Access or eligibility depends on local law.

We may collect the details you submit for account creation, your phone verification record, login and session events, device or browser signals, and support messages. If you use DANA, OVO, GoPay or QRIS, we can also receive transaction references, status and timestamps.

No wallet PIN or one-time verification code should be sent to us through support. Our records can contain a payment reference, status, amount and time for DANA or QRIS activity, while wallet credentials are handled through the relevant payment service rather than our support conversation.

Send a correction request through the privacy or account support route, describe the inaccurate field and identify the affected account step. We may ask you to complete phone verification before changing personal details, so a request is not applied to the wrong account.

The Privacy Policy covers cookies and local storage used for sessions, privacy choices and the path from mobile login to the lobby. Clearing browser data may remove a saved choice and require another account check. You can ask support about a cookie setting that does not save.

Retention depends on the purpose of each record, such as account service, security checks, dispute handling or legal duties where local law permits. Payment references from bank transfer, virtual account or local wallets are handled for the period needed for those purposes.

Use the support route available inside your account and label the request as a privacy question. Include the account phone number or transaction reference only through the requested secure field. Do not include a password, wallet PIN or one-time verification code in your message.