Reference

tokyojitu Privacy Policy For Indonesian Accounts

The tokyojitu Privacy Policy explains how we handle your account, device and wallet records when you access Live Roulette, Sportsbook or payment tools from Indonesia.

Account dataDevice choicesWallet recordsPolicy requests
tokyojitu tokyojitu Privacy Policy For Indonesian Accounts
PRIVACY CONTACT

Get Privacy Help Beside Account Access

A clear contact route matters when a phone verification record or wallet reference looks wrong. We keep privacy questions close to the account help path, so you can explain the issue without reposting sensitive payment details in a public channel. When you contact us, include your account identifier and the request you want handled; access remains subject to local law.

Team online

Account access

Use the account support route shown after sign-in when you need to ask about phone verification, a stored contact detail or an access record connected with your tokyojitu account.

Wallet status

For DANA, OVO, GoPay or QRIS questions, share the payment reference through the wallet support path rather than sending a full wallet password or private security code.

Policy requests

Ask for a copy, correction or retention explanation through the privacy contact path in your account area; describe the exact record so we can route the request correctly.

DATA PRACTICES

Keep Device And Wallet Data Clear

We treat privacy as an account operation, not a decorative page. Our controls connect the records needed for sign-in, phone verification, payment status and security checks while separating those purposes from unnecessary…

Purpose-based use

We use account and phone details to create access, confirm a sign-in and respond to account questions. Payment references from DANA or QRIS help us match status without asking you to disclose a wallet password.

Cookies and sessions

Cookies and similar session records can keep your sign-in path working across a mobile browser or desktop visit. They may also help us detect an unexpected device change during account access.

Account security

Phone verification and sign-in records help us identify account activity that needs checking. Never send a password, one-time code or wallet security code when asking our support route for help.

Retention choices

We retain records for the period needed for account support, payment reconciliation, security checks or applicable legal duties. A retention request can be assessed when you identify the relevant account record.

Policy changes

If our Privacy Policy changes, we place the updated wording on this policy page and show the effective wording there. Check this page before opening a new account or changing wallet details.

Correction requests

You can ask us to correct an inaccurate name, contact detail or account reference. Include the affected field and your account identifier, while keeping DANA, OVO and GoPay security codes private.

Privacy Policy Answers For Your Account

These questions address the records Indonesian account holders most often ask about, from phone verification and QRIS receipts to cookies, retention and correction requests. Each answer refers back to the tokyojitu Privacy Policy and the account contact path used for a specific request.

It covers account details, phone verification, device and session records, payment references, support requests, cookies and retention. It also explains how you can request access or correction where local law permits.

We use the verification status to support account access and help identify unusual sign-in activity. The record is not a request for your one-time code, which you should keep private.

Yes. The policy includes payment status and reference details connected with DANA, OVO, GoPay and QRIS, along with bank transfer or virtual account references used for account reconciliation.

You can submit a request through the privacy contact path shown in your account area. Identify the account and record category, and we will assess the request under applicable local requirements.

Use the privacy request route and name the inaccurate field, such as a contact detail or account reference. Do not include passwords, wallet PINs or one-time codes in your message.

Cookies and session records can maintain your sign-in path and help recognise an unexpected device change. Your browser settings provide controls, although changing them may affect account access.

Yes. Access, correction and retention requests depend on local law. We assess each request against the applicable requirement and may need account details to confirm which record you mean.