Reference

wahyu138 Privacy Policy

wahyu138 keeps your account, wallet references and device details within a clear Privacy Policy, so you know what we collect before opening the lobby.

Clear data purposesWallet record handlingYour request optionsLocal access wording
wahyu138 wahyu138 Privacy Policy
HELP WITH DATA

Ask About Your Privacy Policy

A direct support path helps when your account record, wallet status or Privacy Policy request needs a closer look. Sign in first when you can, then use the account support route beside the cashier area so we can connect your question to the correct phone verification and transaction record. You can ask us to explain a data field, correct an account detail or clarify how long a record is kept.

Team online

Account data questions

Use the support path inside your account when you want to ask what phone, login or verification details we hold. Including your registered phone number helps us locate the correct record, while we avoid asking you to send a wallet PIN or full payment credential.

Wallet record checks

For a DANA, OVO, GoPay or QRIS question, include the transaction reference and approximate time shown in your receipt. We use those details to check the account record and explain the status without requesting your private wallet password.

Correction requests

If your phone detail, account name or device record appears wrong, tell us which field needs attention through the account support route. We may ask for an account step or verification response before changing personal data, protecting the record from an outside request.

DATA HANDLING

What We Do With Your Account Data

Privacy works best when each account step has a defined reason. We use the details created during registration, login, payment checking and support contact to operate access and respond to requests.

Registration details

We use your registered phone number and account details to create one identifiable account and complete phone verification before access. This reduces duplicate records and lets us connect a DANA, OVO, GoPay, QRIS or bank reference to the correct account.

Device and browser signals

When you move from login to the lobby on a phone or desktop, we may record browser type, device signals, IP-related access data and session times. These details help us detect unusual sign-ins and investigate why an account step did not complete.

Cookies and sessions

Cookies and similar session tools help keep your signed-in path connected while you move between account pages and the cashier. You can manage cookies through your browser settings, although limiting them may interrupt login, verification or the return to the lobby.

Account security

We use phone verification, login records and account status checks to reduce unauthorised access. We do not need your DANA PIN, OVO PIN, GoPay PIN or bank password for a Privacy Policy request, and you should never place those credentials in support messages.

Record retention

We keep account, payment-reference and support records for as long as needed for account operation, security checks, dispute handling and legal duties that apply where local law permits. Retention can differ by record type, and we can explain the reason for a stored field.

Changes and requests

If you want a copy, correction or explanation of personal data connected with your account, contact us through the signed-in support route. We may verify your phone before acting, then record the request and update this Privacy Policy when a material handling change occurs.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the searches we hear around account records, wallet references, device access and contact requests. We keep the wording practical so you can understand what happens before you open an account or return to the lobby from a phone in Indonesia.

The wahyu138 Privacy Policy covers account details, phone verification, login and device signals, cookies, payment references, support messages, retention and requests connected to your account. It explains why we use each category and how to contact us when you need a correction or clarification.

No. Our Privacy Policy concerns transaction references, receipt details and payment status, not your DANA PIN, OVO PIN, GoPay PIN or bank password. When checking a QRIS or transfer record, send only the reference needed to match the payment with your account.

We use device and browser signals to connect a login session, identify unusual account activity and diagnose a failed verification step. A phone returning to the lobby and a desktop opening the same account may create different technical records under the Privacy Policy.

Sign in and use the account support route beside the cashier, then state whether you want a copy, correction or explanation. Include the registered phone number and the relevant field, but do not send a wallet PIN. We may verify account ownership before processing the request.

We retain account, payment-reference and support records for the period needed for service operation, security, dispute handling and legal duties where local law permits. The period can differ between a phone verification record, a QRIS receipt reference and a support conversation.

You can adjust cookies through your phone or desktop browser controls. Some session cookies connect login, phone verification and the move back to the lobby, so blocking them may require you to repeat an account step or may prevent a page from working correctly.

Access and eligibility depend on local law, and this Privacy Policy applies where local law permits. If you are unsure whether access is available from your location, contact us through the account support route before submitting personal details or payment references.