Reference

unyil89 Privacy Policy For Your Account

The unyil89 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and your wallet.

Account dataWallet recordsCookie choicesSecurity steps
unyil89 unyil89 Privacy Policy For Your Account
REQUEST HELP DIRECTLY

Three Ways To Ask About Privacy

A privacy question should not leave you guessing which account route to use. We keep requests connected to the same account details used for phone verification, so we can check identity before discussing personal data. Whether your question follows a QRIS receipt, an OVO wallet status or a mobile login, describe the issue clearly and include only the details needed to locate it. Our support path is intended for access questions, data requests and corrections, not for collecting extra personal details.

Team online

Account data request

Ask us to identify the personal data linked to your account and explain its use. Include your account contact detail and the request type, but do not send a wallet PIN or full payment credential through the message.

Payment record query

If a DANA, GoPay, QRIS or bank transfer record looks incorrect, send the reference shown in your account. We can use that reference to check status without asking you to disclose an unrelated password or security code.

Correction or deletion

Contact us when an account detail needs correction or you want to ask about removal. We first confirm the account step connected to the request, then explain any records that must remain for security, payment reconciliation or legal duties.

DATA HANDLING DETAIL

Six Privacy Checks We Keep Visible

Privacy is handled through practical account controls rather than vague promises. We separate login and payment-status checks, limit staff access to the details needed for a support task, and use session controls…

Account collection

When you open an account, we collect the details needed for account setup and phone verification. We use those details to connect your login with account activity, rather than asking you to repeat personal data at every lobby step.

Wallet matching

A DANA, OVO, GoPay or QRIS event creates a payment-status record. We use the reference and amount shown by the transaction flow to match the account, investigate a missing receipt and reduce duplicate processing.

Cookie controls

Cookies can keep a session active, remember a selected language or help us understand whether a page loads correctly. You can adjust browser cookie settings, although disabling some cookies may require another login or affect account access.

Session security

We treat an unfamiliar device, repeated failed login or changed session as a security signal. We may ask for account confirmation before discussing data, changing a contact detail or connecting a new mobile session.

Retention choices

We retain account, support and payment records only as long as needed for the stated service purpose, security checks and applicable duties. A deletion request does not automatically remove records that must support a payment or account dispute.

Policy requests

To ask for access, correction or deletion, contact the support path with your account contact detail and a clear request. We may verify ownership first, then reply with the action available and any reason a record must remain.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the searches we hear most often before an account is opened. They explain how unyil89 treats payment references, mobile sessions, cookies, account requests and access conditions for people in Indonesia. If your situation is not covered, use the privacy contact path above and describe the specific account step or transaction record involved. We will keep the response focused on your request and ask for only the verification needed to protect your data.

The Privacy Policy covers account details, phone verification, login sessions, cookies, support messages and payment-status records. That includes references connected with DANA, OVO, GoPay, QRIS, virtual account and bank transfer activity when those options are used on your account.

Phone verification helps us confirm that the person requesting account access or a data change controls the registered contact detail. It also helps us protect payment records and support conversations from being discussed with someone who cannot verify the account.

Yes. The Privacy Policy covers the payment reference, status and account connection created when you use DANA or QRIS. We use those details to investigate receipt issues and match activity, but you should not send a wallet PIN, password or full security code.

Send a privacy request through the account support path and identify the registered contact detail. State that you want a copy of your account data. We may verify ownership before responding, then explain the available records and the format used for the reply.

Yes. Tell us which account detail is incorrect and provide the corrected value through the privacy contact path. We may ask for phone verification before making a change, especially when the detail affects login, wallet matching or account security.

We keep account, payment and support records for the period needed for the stated service purpose, security checks and applicable duties. If you request deletion, we explain which records can be removed and which must remain for reconciliation or dispute handling.

Yes. Account access and service availability depend on local law. The Privacy Policy still explains how we handle data for an eligible account, including cookies, payment references, device sessions and requests to access, correct or delete personal details.