Reference

Open pgwin138 Privacy Policy Clearly

pgwin138 Privacy Policy sets out how we handle your account details, wallet records and device data when you use our Indonesia service.

ACCOUNT DATACOOKIE CHOICESLOCAL WALLET RECORDSCONTACT PATH
pgwin138 Open pgwin138 Privacy Policy Clearly
CONTACT ROUTES

Reach Us Through Your Account Path

A clear contact route helps you raise a privacy question without searching through unrelated pages.

Login privacy request Start from the contact link beside the login path when you need a copy, correction or explanation of account data. We may ask you to complete phone verification before discussing records, which helps prevent another person from receiving your details.
Wallet record question For a DANA, OVO, GoPay or QRIS reference that looks incorrect, send the date, amount reference and account phone number through the account support route. Do not send your wallet PIN or password; we only need enough detail to trace the record.
Access and deletion request Ask us to change or remove eligible data through the same account contact path. We first confirm account ownership, then explain what can be changed, what must remain for a stated service reason and when the requested action has been completed.
HANDLING DETAILS

Check Our Data Handling Steps

We keep this policy practical by connecting each data use to an account action you can recognise.

Account collection

We collect details you enter during account creation and phone verification, then connect them to the account record needed for access. We do not ask for your DANA, OVO, GoPay or QRIS PIN, and you should never include that secret in a support request.

Cookie choices

Cookies can remember selections and help pages work across a mobile browser or desktop session. Your browser controls available cookie settings. If you clear them, some preferences may need to be selected again, while the core account record remains separate from those browser files.

Login security

Phone verification is used before account access and may be repeated when a security check requires it. We record login and device signals to investigate unusual attempts, protect your account and distinguish a genuine access request from activity that needs closer checking.

Payment references

We retain the reference needed to match a wallet or bank transfer status with your account. For a virtual account, BCA, BRI, Mandiri or BNI transfer, the reference supports reconciliation without requiring us to store your banking password.

Retention checks

We keep data while it serves the account, security, payment tracing or support purpose described in this policy. When that purpose ends, we assess whether the record can be removed, shortened or kept only where a stated operational need still applies.

Change requests

You can ask us to correct account details, explain a data use or request removal of eligible records. We confirm ownership through the account path, assess the request against this policy and reply with the action taken or the reason a record must remain.

Ask About pgwin138 Privacy Policy

These answers address the privacy searches we hear most often before someone opens an account. We keep the wording tied to actual account steps, wallet references, cookies and contact requests, so you can decide what to send and where to ask. If your situation is not covered, use the privacy contact route connected to your login page.

The pgwin138 Privacy Policy covers account details, phone verification, login and device signals, cookie choices, payment references and support requests. It explains why we use each category, how we protect access and how you can ask us to correct, explain or remove eligible data.

No. We use transaction references and status details to connect DANA or QRIS activity with the correct account, but your wallet PIN is not needed for that process. Never include a PIN, password or secret code when you contact us about a payment record.

Use the privacy contact link beside the login path and ask for an account data copy. We may require phone verification before releasing records. Include your account phone number and the exact request, but leave out wallet credentials and any password.

Yes. Send a correction request through the signed-in account contact path, or use the contact link shown when login is unavailable. We confirm ownership, update eligible details and tell you what changed. Some payment or security records may need to remain for their stated purpose.

Cookies may remember your choices and help the mobile or desktop page function during a session. Your browser provides the available controls. Clearing cookies can remove saved preferences, but it does not automatically delete your account record or payment reference.

We use phone verification before account access, monitor login and device signals for unusual activity and restrict internal data access to the work that requires it. If you suspect an incorrect login record, contact us through the account privacy path so we can check it.

The policy is written for supported Indonesia access, while eligibility and access depends on local law. If local rules affect your account or data request, we will explain the applicable route. You can still contact us to ask which policy process applies to your case.