Reference

wak5000 Privacy Policy And Your Account

The wak5000 Privacy Policy explains what we collect when you open an account, enter the lobby, use DANA or QRIS, and contact our support team.

Clear data purposesWallet record contextAccount access controlsPolicy contact route
wak5000 wak5000 Privacy Policy And Your Account
HELP WITH PRIVACY

Get Help With A Data Request

A clear support path helps you ask about the Privacy Policy without sending sensitive details into the wrong channel. Start from the account help route beside the cashier area, describe the record you want checked, and include the account step or payment reference that explains your request. We may ask you to confirm account ownership before discussing personal data. This protects your details whether you are contacting us from a phone in Surabaya or from a desktop elsewhere in Indonesia.

Team online

Account help

Use the account help route when you want to ask how your phone verification, login record or profile details are used under our Privacy Policy. We may request an account identifier before confirming any personal-data detail.

Cashier context

If your request concerns DANA, OVO, GoPay or QRIS, mention the wallet status or receipt reference shown near the cashier path. We use that context to locate the relevant record without asking you to resend a wallet password.

Access concern

For an unfamiliar login or device session, tell us which account step looked unexpected and when it occurred. We can use the sign-in record to investigate access and explain the related Privacy Policy handling.

DATA HANDLING

How We Handle Account Privacy

Privacy work is connected to ordinary account operations: phone verification before access, wallet matching during a payment check, and device signals when a session needs protection.

Account details

We use the details you provide during account creation to identify your account and complete the required phone verification step. If a detail changes, contact us through account help so we can assess a correction request before changing the account record.

Payment references

A cashier check may contain a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference. We use the reference to match status and receipts, while your wallet credentials remain outside the information we ask you to share with support.

Cookies

Cookies and similar browser storage can keep a session active, remember basic preferences and help us identify a broken login path. You can manage browser storage through your device settings, although removing it may require another sign-in.

Device security

Technical signals such as browser type, device details and session timing can help us investigate an unfamiliar access attempt. If you see a sign-in you do not recognise, secure your account and contact us with the affected account step.

Retention purpose

We keep personal records for the period needed to operate the account, resolve payment or security questions, and meet duties that apply where access is permitted. When a record no longer serves those purposes, our handling follows the applicable retention process.

Change requests

You can ask us to check, correct or explain personal data through the support route. State the account detail involved and the action requested. We may verify ownership first, then confirm what can be changed under the Privacy Policy and local rules.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account and wallet questions we expect from Indonesian customers before they continue to the lobby. Each answer points back to a practical account step, from phone verification to a receipt check, so you know what to include when asking for help.

The wak5000 Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It explains why each category is used for account operation, security or cashier checks, and applies where local law permits.

Phone verification helps connect an account to the person completing the access step and helps us investigate login problems. We record the verification status rather than asking you to place a wallet password in support messages. Access depends on local law.

Yes. The Privacy Policy covers payment references created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account references. We use them to match a receipt or status question with the correct account.

Use the account help route and state the profile detail you want checked, corrected or explained. Include your account identifier when requested, but do not send a wallet password. We may verify ownership before assessing the request under applicable rules.

It does. Cookies and browser storage can support a live session, basic preferences and diagnosis of a failed login. You can remove or manage them in your phone or desktop browser settings, though doing so may require another account sign-in.

We keep records while they are needed for account operation, security checks, payment questions or duties that apply to permitted access. The retention period can differ by record type. You can ask support which policy purpose relates to a particular record.

Yes. Device and session details can help us identify an unfamiliar login or diagnose access from a mobile browser. Contact account help with the relevant time and account step, and we can explain the related handling after confirming ownership.