Reference

toko22 Privacy Policy For Your Account

Our Privacy Policy explains how toko22 handles your account details, wallet activity and device signals while you access Live Roulette, Aztec Gems or Football Betting.

Account clarityWallet contextDevice controlsContact path
toko22 toko22 Privacy Policy For Your Account
CONTACT ROUTES

Privacy Help Beside Account Support

A clear contact route helps when a Privacy Policy question affects your account or wallet record. Start from the account help path and include the email or phone linked to your account, the date of the issue and a payment reference if relevant. We use those details to find the right record without asking you to disclose a password. Your request may concern access, correction, deletion, cookies or a transaction record.

Team online

Account help

Use the account help path for a Privacy Policy request tied to phone verification, login history or a detail that looks incorrect on your account.

Wallet status

For DANA, OVO, GoPay or QRIS records, include the payment reference and date so we can separate your request from another wallet status check.

Data request

Ask us to access, correct or remove eligible personal data through support. We may verify account ownership before changing records or disclosing account details.

DATA PRACTICES

How We Handle Your Privacy Choices

The practical controls below describe how we handle the data connected with your account. We separate account security checks from ordinary lobby activity, keep wallet references for reconciliation, and use retention periods…

Account details

We use your submitted account details and phone verification result to identify the account you are asking about. This helps us avoid sending private records to the wrong person.

Device signals

Browser, device and session signals can help us detect unusual access around Live Roulette or Aviator. They support account protection and are not a substitute for your password.

Cookies

Cookies and similar storage can keep a session working, remember selected settings and help us understand sign-in errors. You can manage browser storage through your device settings.

Wallet records

Payment references from DANA, QRIS, bank transfer or a virtual account help us match a status query. We do not need your wallet password to investigate a receipt.

Retention

We retain account, security and transaction records only for the operational or legal period connected with their purpose. When that period ends, records are removed or de-identified where suitable.

Change requests

To request a correction, access copy or eligible removal, contact us through account help with your linked phone or email. We may ask for an account step before processing.

Privacy Policy Answers For toko22

These answers address the Privacy Policy searches we hear most often before account access. They cover the data used for verification, wallet reconciliation, device security and requests made through support. If your situation is different, send the account reference and describe the record you want us to check.

The toko22 Privacy Policy explains how we collect, use, protect and retain account, device, cookie, support and payment-reference data when you access our services where local law permits.

We may collect your account contact details, phone verification result, sign-in and device signals, support messages, cookie preferences and references linked to DANA, OVO, GoPay, QRIS or bank transfer.

Phone verification helps us confirm account ownership before access or a data request. It also gives support a safer account step when you ask us to change contact details or wallet records.

Yes. The Privacy Policy covers payment references and status information used to reconcile DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity; it does not require your wallet password.

Use the account help path and state whether you want access, correction or eligible removal. Include your linked phone or email, then complete any ownership check we request.

Retention depends on the purpose of each record and any applicable legal requirement. Account security and transaction references may remain while needed for those purposes, then are removed or de-identified where suitable.

Yes. Contact us through account help with the device or browser involved. We can explain session cookies and security signals, while your browser settings provide controls for stored cookies.