Reference

yykoin Legal: What Your Account Covers

yykoin Legal explains how account access, identity checks, wallet records and policy requests work before you enter the lobby.

Account termsPrivacy choicesLocal-law accessPayment records
yykoin yykoin Legal: What Your Account Covers
HELP WITH POLICY

Where to ask about a Legal issue

A clear contact route matters when a Legal question affects your account or payment record. We keep policy questions separate from game questions, so you can explain whether the issue concerns identity…

Account policy request Use the account help path when you need a clause explained, an account detail checked, or a request linked to your phone verification. We match the response to the account record rather than asking you to send payment details in an open message.
Wallet record question For DANA, OVO, GoPay or QRIS questions, tell us which wallet or reference needs attention. We check the payment status and receipt trail connected with your account, then explain what the Legal terms allow us to do next.
Privacy contact path Ask through support when you want to know what account data is held, why a check was requested, or how to request a permitted change. We keep the request attached to your account so the response reaches the right person.
SIX ACCOUNT CONTROLS

Six controls behind our Legal process

Legal handling is practical: we record the account events needed to operate the service, protect payment trails and respond to requests.

Data purpose

We use account details to create access, complete phone verification, connect payment records and answer policy requests. The purpose should match the account action involved, so a DANA receipt question does not require unrelated personal details.

Cookie choices

Cookies can support sign-in continuity and page settings on your phone, tablet or desktop. Your browser controls remain available, while some account functions may need a working session cookie to keep your Legal request connected.

Account security

Phone verification helps us distinguish the account holder from an unauthorised request. Keep your sign-in details private and contact support if your access path changes; we may ask account questions before discussing wallet or identity records.

Payment records

For QRIS, bank transfer and virtual account activity, we retain the reference needed to match a receipt with the account event. This helps us explain a status without treating an unverified screenshot as final payment evidence.

Retention timing

We retain records for the period needed for account operation, payment reconciliation, security checks and policy duties. When a record is no longer needed for those purposes, handling follows the applicable retention rule rather than an informal deletion promise.

Change requests

You can ask us to correct account details or clarify how a record is used through the account support path. Include the relevant account contact and request type; we verify ownership before making a change to protected data.

Legal answers before you open an account

These Legal answers cover the questions we expect before account creation: who may access the service, what verification means, how payment records are handled and where to ask for a change. Read them alongside the full policy wording. If your situation is not covered, send a focused request through the account support path before you continue.

Access depends on local law. You are responsible for checking whether the service is permitted where you are located before opening an account. We may also require accurate account details and phone verification before account access, and we can explain the relevant policy clause through support.

Phone verification connects the account to a contact method and helps us identify the account holder when a policy, privacy or wallet request arrives. It can also be needed before discussing protected records, including DANA, OVO, GoPay or QRIS activity.

We keep the payment reference needed to match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity with your account. That record supports status checks and reconciliation. We use it for the account purpose involved, not as a substitute for identity verification.

Yes, you can request a correction through the account support path. Tell us which account detail is wrong and provide the contact linked to your account. We verify ownership before changing protected data, and we explain if a record must remain for a stated Legal purpose.

Cookies can keep your session active and remember page choices on a phone, tablet or desktop. You can manage them in your browser. If a required session cookie is blocked, a policy request or account action may not stay connected until you allow the relevant setting.

We retain records while they are needed for account operation, payment reconciliation, security checks and applicable policy duties. The period can differ by record type. When the purpose ends, we handle the record under the relevant retention rule rather than promising immediate removal.

Use the account support path and state whether your request concerns access, privacy, phone verification, a payment receipt or account data. Include your account contact, but do not send wallet credentials in an open message. We will direct the request to the appropriate policy response.