Reference

yongtoto Privacy Policy Explained

yongtoto Privacy Policy sets out what we collect when you open an account, sign in, use the lobby or contact support.

Account dataWallet referencesCookie choicesAccess requests
yongtoto yongtoto Privacy Policy Explained
CONTACT ROUTES

Ask About Your Privacy Policy

A direct support route helps when you want to ask about the Privacy Policy, check an account record or request a correction. Start from the support path connected to your account and include the email or phone detail used during account access, without sending a password or wallet PIN. We can then match the request to the right account record and explain the next step. The same route can help when a DANA receipt, QRIS reference or sign-in record needs clarification.

Team online

Account request

Use the support path beside your account area to ask what personal details we hold or why a particular record appears. Include your registered contact detail and the subject of your request so we can direct the Privacy Policy question accurately.

Correction request

If your name, phone detail or contact record is outdated, tell us which field needs attention and why. We may ask you to complete the clear phone verification step before changing account data, helping us avoid edits by another person.

Payment record

For a DANA, OVO, GoPay or QRIS reference, share the transaction date, amount shown in your account and reference code only. We use those details to locate the record; never send a wallet PIN, password or full banking login.

HANDLING DETAILS

Six Ways We Handle Your Data

Privacy work is practical: we separate account access, payment references, device signals and support correspondence so each record has a defined purpose.

Account details

We collect the contact and identity details needed to create your account and keep its access path clear. When you open the account, review each field before submitting it, because accurate details make later verification and correction requests easier to match.

Phone verification

Before account access or a sensitive change, we may use the phone verification step linked to your account. This helps us distinguish your request from an unauthorised attempt and limits disclosure of account details to the person who can verify access.

Device signals

Your browser and device can provide sign-in time, session and security signals. We use these details to identify unusual access patterns, support an interrupted login and investigate a request without asking you to reveal your password.

Cookies

Cookies can keep your session active and remember selected page settings. You can manage cookie controls in your browser, although restricting necessary cookies may affect sign-in continuity or the way a Privacy Policy request is submitted.

Retention

We keep account, payment-reference and support records only for operational, dispute-handling or legal reasons that apply to the record. When a purpose ends, we review whether the data should be removed, anonymised or kept for a documented reason.

Your request

You may ask about access, correction or deletion where local law permits. Send the request through our account support route with enough detail to identify the record; we may verify your phone or contact detail before responding.

Privacy Policy Questions You Can Search

These Privacy Policy answers address the account and payment questions we expect you to ask before opening access. They explain why records appear, how to request a change and what to do when you use a mobile device in Indonesia. If your situation is not covered, use the support route linked to your account and mention the exact record or page involved. Access and eligibility depends on local law, so we may need to explain a location-specific result.

The yongtoto Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention and how to request access or correction where local law permits.

Phone verification helps us confirm that the person requesting account access or a data change can use the contact detail attached to the account. It reduces accidental disclosure and supports a clear correction path. We will not ask you to provide a password or wallet PIN.

Yes. The Privacy Policy covers payment references created when you use DANA, QRIS, OVO, GoPay, bank transfer or a virtual account. We use the reference, status and related account details to identify a transaction or resolve a support question, not to request your private wallet credentials.

Open the support route connected to your account and ask for an access request under the Privacy Policy. State your registered contact detail and the records you want checked. We may complete phone verification before releasing account-linked data, and access depends on local law.

You can ask us to correct an inaccurate name, phone detail or contact record through account support. Tell us which field is wrong and provide the updated detail. We may verify your phone before making a change so another person cannot alter your account.

We keep each record while it supports account operation, payment-reference checks, dispute handling or a legal requirement. We then review whether continued retention is necessary. The exact period can depend on the record and applicable law, and you can ask support about a specific category.

You may request deletion through the support route where local law permits. We first identify the relevant account and may verify your contact detail. Some records can need continued retention for account, dispute or legal reasons, so support will explain what can be removed.