Reference

Open yykoin Privacy Policy With Clarity

yykoin Privacy Policy explains how we handle the details connected to your account, device and wallet activity before you open the lobby.

Account dataWallet referencesDevice choicesContact requests
yykoin Open yykoin Privacy Policy With Clarity
CONTACT YOUR WAY

Reach Support About Privacy Policy

A clear contact path helps when your Privacy Policy question concerns a phone number, wallet reference or device record. Tell us which account step created the concern, such as phone verification or a QRIS receipt check, and avoid sending a password in your message. We use the details you provide to locate the relevant record and explain the next step. If you are in Semarang or elsewhere in Indonesia, access still depends on local law. Our support route is for policy questions, correction requests and account-data concerns.

Team online

Account data request

Ask us to locate, correct or explain account details connected with your phone verification. Include the account contact you used and the specific record you question, such as a sign-in event or wallet reference, so we can reduce unnecessary back-and-forth.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, describe the payment reference and date shown in your account. We can explain how that reference is used for matching without asking you to share a wallet PIN or password.

Privacy contact route

Use our account support path when you want to ask about Privacy Policy access, retention or a data change. State whether you are using a mobile browser or desktop, because device context can help us identify the relevant account event.

HOW WE HANDLE DATA

Explore yykoin Privacy Policy Controls

We keep this Privacy Policy practical by tying each data use to an account action you can recognise.

Account collection

We may receive the phone number and verification result used when you create or enter your account. These details connect your access request to the correct account record. We ask you to keep the number current so a privacy response reaches the right account holder.

Device signals

A mobile browser or desktop session can create technical details such as sign-in time, browser type and security events. We use those signals to investigate unusual access and explain a record you ask about. They are not a request for your device contents.

Cookie choices

Cookies can keep a session working and remember selected page settings. You can manage cookie controls in your browser, although restricting them may affect account entry or require another verification step. Our Privacy Policy explains the purpose of cookies used around account pages.

Payment references

A DANA, OVO, GoPay or QRIS reference can be associated with an account action, while bank transfer and virtual account records may show a matching identifier. We use payment references for status checks and do not ask for your wallet PIN or banking password.

Retention choices

We retain account and transaction-related records only as needed for the stated account, security or legal purpose, subject to local requirements. You can ask why a record remains, whether correction is possible, and what happens to information after an account access request ends.

Security contact

If you notice an unfamiliar sign-in or suspect that account details are exposed, contact us through the policy support route promptly. Do not send a password, wallet PIN or full banking credential. We may ask for safe account identifiers before discussing a security event.

Find Answers About Privacy Policy

These Privacy Policy answers address the account questions we expect from people in Indonesia before they open access. They cover the data connected with phone verification, mobile and desktop sessions, cookies, wallet references, retention and requests for correction or removal. If your situation is not listed, contact our support path with a safe account identifier. Eligibility for access depends on local law, and we will explain the relevant policy route without asking for a password or wallet PIN.

The yykoin Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies and payment references. It explains why we use each category, how retention works, and how you can contact us about correction, removal or a question about your personal data.

We use the phone number and verification result to connect an account access request with the correct account record. If you ask about that data, tell us which phone contact is linked to your account. Never include a password or wallet PIN in the request.

Yes. Privacy Policy treatment includes payment references from DANA, OVO, GoPay and QRIS, along with bank transfer or virtual account identifiers. These references help match payment status to an account action. They do not require us to receive your private wallet PIN or banking password.

Where local law permits, you can ask what account data we hold or request a correction. Use the support route and identify the account contact plus the record in question, such as a phone verification result or device sign-in. We may verify ownership before responding.

When you use a mobile browser, we may record technical session details such as browser type, sign-in time and security events. Privacy Policy explains this device handling. We do not treat it as permission to inspect your photos, contacts or other unrelated device contents.

Retention depends on the purpose for keeping a record and on local requirements. Account, security and payment-related records may remain while they are needed for those purposes. You can contact us to ask why a specific record remains and whether removal is available.

Use our account support path and describe the policy issue in plain English, such as a cookie choice, wallet reference or unfamiliar sign-in. Include a safe account identifier and your device path if useful. We will not ask you to send a password or wallet PIN.