Reference

Read the wahyu189 Privacy Policy first

The wahyu189 Privacy Policy tells you what we collect when you open an account, sign in through a mobile browser, use DANA or QRIS, and browse titles such…

Account dataWallet recordsDevice signalsCookie choices
wahyu189 Read the wahyu189 Privacy Policy first
CONTACT ROUTES

Ask support about a Privacy Policy request

A clear contact route matters when you need to understand a record or change an account detail.

Account support path Use the support route inside your account when your question concerns a sign-in record…
Wallet record check For a DANA, OVO, GoPay or QRIS question, include the payment reference and approximate…
Security concern If a mobile browser session looks unfamiliar, contact us through the account support path…
DATA HANDLING

Explore how we handle private account data

The Privacy Policy is practical: it connects each category of data with an account task you can recognise.

Account creation

When you open an account, we collect the contact and verification details needed to create a usable sign-in path. The Privacy Policy explains the purpose of each requested field, so you can distinguish required access data from optional browser preferences.

Wallet references

A DANA, OVO, GoPay or QRIS reference can be connected with an account transaction record, while the wallet password remains outside our support request. We use the reference to check status and resolve a receipt question without publishing payment credentials.

Mobile browser signals

When you move from login to a mobile lobby, we may record device and browser signals that help identify an unusual session. These signals support account protection around titles such as Aviator Mobile Play, but they are not a public profile.

Cookie controls

Cookies can retain a language choice, session preference or page setting. Our Privacy Policy describes their purpose, while your browser supplies controls to clear or restrict them. Removing some cookies may require you to repeat the account access step.

Retention requests

You may ask how long a category of data is kept or request deletion where that option is available. We first confirm the account connection, then assess security, transaction and legal needs before changing or removing a record.

Change of details

If your contact detail is wrong, send a Privacy Policy request through account support rather than opening a second account. We verify the request, update eligible fields and explain any record that must remain for account protection or legal duties.

Browse answers about Privacy Policy access

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover collected data, wallet records, cookies, corrections, deletion and contact steps. If your case involves an unusual sign-in or a payment reference from BCA, BRI, Mandiri or BNI, use the account support route so we can check the right record. Any access or eligibility decision depends on local law.

It covers account details, verification responses, wallet and transaction references, browser or device signals, cookies, support messages and retention. It also explains why we use each category, how we protect account access and which requests we can process where local law permits.

Yes. The Privacy Policy covers references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references to trace account status or a receipt question, while wallet passwords and security codes should never be sent through support.

Send the request through the account support path and identify the account step involved, such as sign-in or a payment receipt. We may verify your identity before responding, then provide the eligible data or explain why a record cannot be released.

You can ask us to correct eligible contact or account details through support. Do not create a second account to bypass a mismatch. We confirm the request against your account, update the permitted field and explain any verification record that must remain.

Cookies can remember session settings and selected page preferences, while device signals help us identify unusual access from a mobile browser. You can clear or restrict cookies in your browser, though doing so may require another login or preference selection.

You may request deletion of eligible data through account support. We check identity and assess whether the record is still needed for account security, a wallet receipt, transaction tracing or legal duties. Where local law permits, we remove or anonymise data that no longer has a valid purpose.

Use the support path connected with your account and describe the policy issue without including a password or wallet security code. Add a payment reference, device route or account step only when relevant, so we can locate the correct record and respond safely.