Reference

Open yunani toto Privacy Policy Clearly

yunani toto Privacy Policy explains what we collect when you create an account, verify your phone, sign in from a mobile browser, or check a wallet status through…

Account dataWallet recordsCookie choicesPrivacy requests
yunani toto Open yunani toto Privacy Policy Clearly
CONTACT ROUTES

Ask About Privacy Through Account Support

A clear support path helps when you want to ask what a record means or request a change to your personal data. Sign in first when possible, open the support route near your account area, and include the phone number connected to your account without sending a wallet password or one-time code. We use the details you provide to locate the request and respond to the right account.

Team online

Policy questions

Use the support contact shown inside your account to ask which personal details we hold, why they are needed, and how the Privacy Policy applies to your request.

Account matching

Include your registered phone number and a short description of the issue. We may ask for an account step to confirm identity before discussing private records.

Wallet references

For DANA, OVO, GoPay or QRIS records, share the payment reference only through our support path. Never send your wallet password, PIN or verification code.

DATA PRACTICE

See How Your Privacy Requests Work

We keep the Privacy Policy practical: data is collected for a stated account, security or support purpose, then handled according to the type of record involved.

Data collected

We may receive your phone number, verification result, sign-in time, device details, support messages and payment references connected with DANA, OVO, GoPay, QRIS or bank transfer.

Cookie controls

Session cookies can keep your mobile browser connected after sign-in. Browser settings let you clear or restrict cookies, though some account steps may then need to be repeated.

Account security

Phone verification helps us match a privacy request to the right account. We do not need your wallet PIN or one-time code to explain a stored payment reference.

Record retention

We retain account, security and payment-status records only for the period needed for the stated purpose, account support and applicable legal duties where local law permits.

Who to contact

Our account support route handles questions about personal data, cookies and payment references. Sign in when possible so the request can be matched without exposing private details.

Request changes

Ask for access, correction or deletion by describing the record and using your registered phone number. We may verify account ownership before making a privacy change.

Find Privacy Policy Answers Before Signing In

These Privacy Policy answers focus on the account actions you are most likely to take from Indonesia: phone verification, mobile browser access, wallet references and support requests. Read them before opening an account, then use the policy page and account support route for a request that needs account-specific checking. Availability remains where local law permits.

It covers account details, phone verification, sign-in activity, device data, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account.

We use your phone number to create and identify the account, complete phone verification and match a privacy request. We do not need your wallet PIN or one-time code.

Yes. We may retain a reference and status for an account payment through DANA or QRIS, along with similar records for OVO, GoPay, bank transfer or virtual account.

Open the support contact shown in your account area and ask for a data copy. Include your registered phone number and enough detail to identify the request without sharing secret codes.

Yes. Send a correction request through account support, name the inaccurate field and provide your registered phone number. We may complete an ownership check before changing private account records.

A session cookie can keep your sign-in state while you move through account pages. You can clear or restrict cookies in browser settings, but some verification steps may repeat.

Access and eligibility depends on local law. We provide the policy where local law permits, and account support can explain how a request is handled for your location.