Reference

Privacy Policy for Your pw128 Account

Our Privacy Policy explains how we handle the account, wallet and device details you provide when you use pw128.

Account clarityWallet privacyDevice controlsLocal-law access
pw128 Privacy Policy for Your pw128 Account
PRIVACY HELP DESK

Get Help With a Privacy Request

A clear contact route matters when your account or wallet record needs attention. We keep privacy questions separate from game or cashier requests, while still giving you a practical path from the account area. Include the phone number or account detail connected to your request, and we can locate the relevant record without asking you to send a full payment credential. Your request may concern access, correction, deletion eligibility or cookie choices, and we will explain the next step.

Team online

Account privacy

Use the support path attached to your account when you need a copy of personal details, a correction to phone verification data or clarification about a login record.

Wallet record

For a DANA, OVO, GoPay or QRIS reference, share the receipt number and account contact only. We use those details to trace the record without requesting your wallet PIN.

Access questions

If privacy access is unclear, ask our support desk whether the request depends on local law. We can explain the available route before you send documents or change account details.

CONTROL YOUR RECORD

How We Handle Your Privacy Choices

We treat privacy as an account process you can inspect, not a hidden setting. Our controls cover collection, use, storage, cookies, security checks and requests to change personal details.

Data handling

We use account and contact details to provide access, answer support requests and connect an activity record to the right account. We do not need your wallet PIN to check a DANA or QRIS receipt.

Cookie choices

Cookies can keep a sign-in session active and remember selected site settings. Your browser controls can clear or restrict them, although some account functions may then require another sign-in.

Account security

Phone verification, sign-in events and device signals help us identify unusual account access. If a check interrupts your session, contact support from the account path and describe the device involved.

Retention context

We keep records only for the period needed for the stated account, support, security or legal purpose. The Privacy Policy explains why a particular record may remain after an account request.

Correction requests

You can ask us to correct inaccurate account details by naming the field and confirming the contact linked to it. We may verify ownership before changing phone, email or payment references.

Privacy contact

Send privacy questions through the support route shown beside your account area. Include a short request, such as access or deletion, and we will explain whether local law affects the response.

Privacy Policy Questions About pw128

These Privacy Policy answers focus on the account steps you are most likely to check before opening access. They cover the records connected to wallets, devices, cookies and support requests, with local-law wording where a privacy response may be limited.

It covers personal details connected to your account, phone verification, sign-in events, device signals, cookies, wallet references and support requests. It also explains our purposes for using those records, how retention works and how you can request access or correction.

Yes. The Privacy Policy covers references created when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use a receipt or transaction reference to match a payment status, and we do not ask for your wallet PIN.

Use the privacy contact route in your account support area and state that you want access to your personal record. Include the connected phone or email so we can locate it, then complete any ownership check needed before we respond.

You can ask us to correct inaccurate contact, phone verification or account details. Tell us which field is wrong and provide the account contact used for access. We may request confirmation before changing information that affects sign-in or wallet matching.

Cookies support sign-in continuity and selected site preferences. Your browser can clear or restrict them, but the lobby may ask you to sign in again or may not retain a setting. The Privacy Policy explains these functions and your available browser choices.

A request may depend on local law when it concerns account security, legal retention or another permitted restriction. We will explain the reason and the available contact route. You can ask support before submitting documents or requesting an account change.

Contact our support desk through the account privacy path and label the request as access, correction, deletion or cookie-related. Share only the details needed to locate your record. We will explain the next step and any identity check required.