Reference

tokyo777 Privacy Policy In Plain English

tokyo777 Privacy Policy explains how we collect, use and protect the details connected with your account, including phone verification and wallet records.

Account dataWallet recordsCookie choicesAccess requests
tokyo777 tokyo777 Privacy Policy In Plain English
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact route matters when you want to understand a record or change an account detail.

Account support Use the support path connected to your tokyo777 account to ask which personal details…
Cashier enquiry For a DANA, OVO, GoPay or QRIS receipt, start from the cashier support path…
Access issue If your account cannot open on a mobile browser, use the available contact route…
DATA PRACTICES

How We Handle Account Privacy

Privacy work is part of each account step, from phone verification to a wallet status check.

Collection at entry

When you open an account, we collect the details needed for the account path, including your phone number and verification…

Payment matching

A DANA, OVO, GoPay or QRIS payment can create a reference, timestamp and status linked to your account.

Cookie controls

Cookies and similar browser storage can remember sign-in state, help keep the account path working and show whether a page…

Account protection

We use phone verification and account checks to reduce unauthorised access.

Retention reasons

We keep records only for as long as needed for the stated account, security, payment reconciliation or legal purpose.

Your change request

You can ask us to correct an account field, explain a data use, provide a copy of relevant records or…

Privacy Policy Questions From Indonesia

These answers address the privacy searches we expect before an account is opened. They cover the records created by phone verification, the wallet paths used in Indonesia, browser cookies, account access and requests sent to our support route. If your question concerns a specific receipt or sign-in, keep its reference ready but never send a password or one-time code.

We use your phone number for the account path, phone verification and account-support checks. It can help us identify the relevant account when you ask about a correction or access issue. We do not ask you to place a password or one-time code in a support message.

Yes. The Privacy Policy covers payment references and status records created when you use DANA, OVO, GoPay or QRIS. We use those details to match a receipt, investigate a stalled cashier status and respond to your account question, subject to local legal requirements.

A bank transfer or virtual account reference helps us connect a payment status with the correct account and resolve a receipt enquiry. We may retain that record for reconciliation, security or a legal purpose after the original support conversation has ended, where local law permits.

Use the account-support route and state whether you want a copy, an explanation or a correction. Include the account phone number or reference needed for verification, but not your password. We check the requester's identity before discussing private records or changing an account field.

You can adjust cookie settings in your mobile or desktop browser. Some cookies help preserve sign-in state and save privacy choices, so disabling them may require you to repeat an account step or may prevent a page from working as intended.

The same Privacy Policy applies when you sign in from Bandung, whether you use a phone browser or desktop browser. Device and sign-in records can be created for security and troubleshooting. Account access depends on local law, and we use the data for the stated purposes.

Change your account credential, avoid sharing any one-time code, and contact support through the account route. Tell us the sign-in time, device path and any affected DANA, OVO, GoPay or QRIS reference. We can then check the relevant security and payment records.