Reference

yoi4d Privacy Policy For Your Account

yoi4d Privacy Policy explains how we use account details while you move from phone verification to Super Sic Bo, Rocket Crash or the wider lobby.

ACCOUNT DATAWALLET RECORDSCOOKIE CHOICESCONTACT STEPS
yoi4d yoi4d Privacy Policy For Your Account
CONTACT ROUTES

Where Privacy Questions Meet Wallet Help

A clear contact route helps when you want to ask what data we hold or why a wallet status is attached to your account.

ACCOUNT SUPPORT PATH Use the support contact shown after login to ask for a copy, correction or…
CASHIER STATUS CHECK If a DANA or QRIS record looks unfamiliar, provide its reference and status from…
DEVICE ACCESS HELP When mobile browser access shows an unexpected login prompt, tell us the device type…
DATA PRACTICES

Account Security From Login To Wallet

We keep this policy practical by linking each data use to an account action you can recognise.

DATA COLLECTION

We collect registration details, phone verification results, login events, device signals, support messages and payment references when those details are…

COOKIE CONTROL

Cookies can keep a selected language, session state or account setting available during your visit.

ACCOUNT SAFETY

Phone verification is checked before account access, while login and device signals help us investigate unusual entry.

RETENTION PERIOD

We retain account, payment and support records for operational checks, disputes and legal requirements.

YOUR REQUESTS

You can ask us to access, correct or clarify personal data connected with your account.

POLICY CHANGES

If this Privacy Policy changes, we will place the revised wording on this page and show the effective date.

Privacy Policy Questions For yoi4d

These answers focus on the privacy questions that arise before you open an account or check a wallet record. We keep the wording tied to real account steps, including phone verification, mobile browser access, cookies and payment references from Indonesian rails.

It covers registration details, phone verification, login and device signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account.

We use your phone number to create and verify the account before access. It also helps us match a privacy request or wallet-status question with the correct account.

Yes. We may retain transaction references, status and timing connected with DANA or QRIS so we can match a payment, investigate a discrepancy and answer an account request.

Open the support path inside your signed-in account and ask for access to your data. Provide the registered phone number and enough detail for us to verify the request.

Yes. Send a correction request through the account support path, identify the field that is wrong and complete the requested account check before we change the record.

Cookies can retain session and setting details on your phone. Clearing them may sign you out or trigger phone verification again when you return through the mobile browser.

Yes, access and eligibility depends on local law. We apply this policy where local law permits, and you should check the rules that apply to your location before opening an account.