Reference

Privacy Policy For Your tokyo55 Account

Auto Roulette, Royal Fishing and the mobile lobby are connected to an account record, so our Privacy Policy explains what we collect before you open those pages.

Account clarityWallet dataMobile privacyPolicy access
tokyo55 Privacy Policy For Your tokyo55 Account
PRIVACY SUPPORT PATH

Get Privacy Help Beside Account Support

A privacy question should not leave you guessing about the next step. From your account page, use the displayed support path and include the email or phone linked to your tokyo55 account, the subject of your request and any relevant payment reference. We use that limited context to locate the correct record without asking for a wallet password or full payment credentials.

Team online

Account access

If your phone verification does not open the account, contact us through the support path shown after login. Tell us which device you used and whether the issue affects your personal data request or ordinary sign-in.

Wallet status

For a DANA, OVO, GoPay or QRIS privacy question, share the transaction reference and selected rail rather than secret wallet credentials. We can use that reference to separate payment status from the rest of your account record.

Policy requests

To ask for a copy, correction or removal of eligible account data, use the policy contact route on our site. We may verify the account holder through the registered phone before changing or releasing records.

DATA HANDLING PRACTICE

Your Account Data And Device Controls

We apply the Privacy Policy to the practical points you meet while using the account: sign-in, phone verification, wallet selection, mobile browsing and support.

Account records

We collect the details needed to open and maintain your account, such as contact information, verification status and selected settings. These records let us connect a request to the correct account instead of exposing another person’s details.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can produce payment references, amounts and status markers. Our Privacy Policy treats these as account-linked transaction data, not as permission to request your private wallet login.

Mobile sessions

When you open the lobby in a mobile browser, we may process session, browser and device signals needed to keep the account page working. These signals can help identify repeated access attempts without storing the contents of your personal device.

Cookies

Cookies can retain a sign-in session, language choice or acknowledgement that you opened the Privacy Policy. Browser controls let you clear or block them, but clearing session cookies may sign you out or require phone verification again.

Security checks

We may compare sign-in timing, device signals and account changes when access looks unusual. A request involving Auto Roulette, age138 or another lobby page does not bypass these checks; account protection remains tied to your verified sign-in.

Retention and changes

We retain account and payment records for the operational, dispute and legal periods that apply to the service, then remove or restrict them when appropriate. You can ask what is held, request a correction or contact us about an eligible deletion.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the account questions you may search before choosing a wallet or signing in from Indonesia. They explain how we connect personal details, device activity and payment references, plus the route for asking us to check or change a record. If a request depends on eligibility or access, it depends on local law and the applicable account conditions.

It covers account details, phone verification, device and browser signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security checks and how you can request access or correction.

We use the phone number connected to your account for phone verification, sign-in recovery and account ownership checks. It can help us confirm that a privacy request comes from the right account holder, but you should never send a wallet password through a support message.

Yes. A QRIS receipt or DANA, OVO or GoPay reference can show the selected rail, transaction status and account connection needed for reconciliation. The policy does not give us your private wallet password, and we ask for a reference instead of secret credentials.

Use the privacy contact route displayed on the site and identify your account with its registered phone or email. State that you want a copy of your account data. We may complete an ownership check before releasing records, and the request depends on local law.

You can ask us to correct an inaccurate name, phone number, email address or account setting through the displayed support path. Include the incorrect field and the replacement value. We may ask for phone verification before changing the record or linking a payment reference.

We keep payment references and account records for the periods needed to operate the account, resolve disputes and meet applicable legal requirements. After that, we remove or restrict them when appropriate. The exact period can depend on the record type and local law.

Start with the policy contact route or support path shown on your account page. Include your registered contact detail, request type and relevant reference, such as a QRIS receipt. Do not send wallet passwords. Eligibility for a requested action depends on local law.