Reference

Open oyuki88 Privacy Policy Before Access

oyuki88 Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and contact our support team.

Account clarityWallet recordsCookie choicesRequest access
oyuki88 Open oyuki88 Privacy Policy Before Access
CONTACT YOUR WAY

Contact Support About Privacy Policy

A clear contact route helps you resolve a Privacy Policy question without sharing more than necessary. Tell us the account email or phone number connected to your request, describe the data issue, and include only the payment reference needed for checking. We respond through the support channel shown on our site during the published support hours. For account safety, we may ask you to confirm ownership before discussing records or changing contact details.

Team online

Account requests

Use the support contact shown on our site to ask for a copy, correction or explanation of account data. Include your registered phone or email, but never send a wallet PIN or password. We may verify ownership before releasing account details.

Wallet questions

If a DANA, OVO, GoPay or QRIS receipt is connected to the wrong account record, send the reference and approximate time through support. We use those details to locate the transaction without asking for your wallet login credentials.

Security concerns

Report an unfamiliar sign-in, device event or account message through the listed support channel as soon as possible. We can review the account activity, confirm your identity and explain which Privacy Policy records relate to the security check.

HOW WE HANDLE DATA

Explore Privacy Policy Controls For Your Account

We apply the Privacy Policy to the account journey from phone verification through wallet status checks and support contact.

Account details

We may handle your name, contact details, verification results and account settings to create and maintain access. Phone verification helps us distinguish your request from an unrelated person. We use these details for the stated account purpose rather than asking for unnecessary wallet credentials.

Device activity

Sign-in time, browser type, device markers and security events can help us identify unusual access. These records support account protection when you switch from a mobile browser to desktop. We use them to investigate a specific event, not to request your device password.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create references, amounts and status results in our records. These details help match a receipt to your account and resolve a stalled cashier step. Wallet PINs remain outside our requested support information.

Cookies

Cookies and similar browser storage can remember session settings, support account access and help us understand whether a page loads correctly. You can manage browser cookie controls, although blocking some storage may require you to sign in again or repeat a verification step.

Retention

We retain account, security and transaction records only for the period needed for the purpose described in the Privacy Policy, account protection and applicable obligations. When a record no longer needs to remain, we remove it or separate it from direct account identifiers where suitable.

Your requests

You may contact us to ask what personal data we hold, request a correction, question its use or ask about deletion where applicable. State the request clearly and provide an account contact for verification. We explain any limit before taking action on your records.

Check Privacy Policy Answers Before Access

These Privacy Policy answers cover the questions we expect you to have before opening an oyuki88 account or using a local wallet. They explain the practical path for account data, cookies, payment references, security events and contact requests. If your situation is not listed, use the support route and share only the minimum details needed to identify your request.

It covers account details, phone verification, sign-in activity, device records, cookies, support messages and payment references. It also explains why we use each category, how records support account security, and how you can ask about access, correction or deletion where applicable.

Phone verification helps us confirm that the person requesting account access or account changes is connected to the registered contact. It also helps with security checks when sign-in activity changes. We do not ask you to provide a DANA, OVO or GoPay PIN.

Yes. When you use DANA, OVO, GoPay or QRIS, we may retain transaction references, status results and related account details needed to match a payment step. These records help us investigate receipt questions without requesting your private wallet password.

Contact us through the support channel listed on the site and state whether you want access, correction or another Privacy Policy request. Include your registered email or phone number. We may verify account ownership before discussing personal records or changing them.

We may use cookies or browser storage for session access, preferences and technical checks. This applies when you sign in through a mobile browser or desktop browser. Your browser settings can limit cookies, but you may need to sign in or verify again.

Retention depends on the purpose of the record, account security needs and applicable obligations. Transaction references may remain while a payment question or account matter requires them. You can ask support why a category is retained and what request path applies.

Contact support using the channel listed on our site and describe the unfamiliar event, approximate time and affected device. Do not send a password or wallet PIN. We may verify ownership, review security records and explain the relevant Privacy Policy handling.