Reference

Your pixel138 Privacy Policy, Clearly Set Out

Your pixel138 Privacy Policy explains what we collect when you open an account, use a mobile browser in Yogyakarta, or check DANA and QRIS status.

Account dataWallet recordsCookie choicesAccess requests
pixel138 Your pixel138 Privacy Policy, Clearly Set Out
CONTACT PATHS

Get Privacy Help Near Your Account

A clear contact path helps when a Privacy Policy question is tied to a real account step.

Account help Send a Privacy Policy request through your signed-in account path when you need a copy of account data, a correction to your phone detail, or help understanding a security check. We may ask you to confirm account ownership before replying.
Wallet records For DANA, OVO, GoPay or QRIS data questions, include the payment date, rail name and receipt reference. We use those details to locate the relevant wallet record without asking you to share your wallet PIN or full secret credentials.
Access concerns If a Privacy Policy request cannot be completed because your account is locked or your phone verification is pending, contact support through the available account path. We can explain the next identity step and the data needed for a lawful response.
HANDLING DETAILS

What We Do With Your Account Data

Privacy depends on practical handling, not broad promises. We separate account, device, cookie and payment records so a request about a mobile session does not automatically expose wallet details.

Account collection

When you open an account, we collect the details needed for access and phone verification. We may also retain messages you send about account support so we can connect a Privacy Policy request with the correct account record.

Device signals

A mobile browser or desktop session can create device, browser and sign-in records used to protect account access. These signals help us investigate unusual activity around Live Baccarat Elite or Football Goal Rush without treating game use as a separate identity.

Cookie controls

Cookies can keep your account path working and help us understand whether a page request succeeded. Your browser settings can limit some cookies, although changing them may affect sign-in, saved preferences or the way a Privacy Policy request is submitted.

Wallet matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may be matched with an account reference and payment receipt. We use that link to check status and resolve disputes, rather than requesting your wallet password.

Security checks

Before changing phone details, exposing account records or handling a deletion request, we may ask for an account step that confirms you are the right person. Never send a password, wallet PIN or one-time code in a support message.

Retention requests

We keep records only for the operational, security or legal period that applies to their purpose. Ask us which category a record belongs to, request a correction, or ask whether removal is available; access depends on local law and verification.

Privacy Policy Answers for pixel138

These Privacy Policy answers address the searches we expect before you open an account or send a data request. Each reply stays focused on the records created by account access, mobile browsing, game activity and local payment checks. Where a request concerns another person, a protected record or a legal retention period, we may need more context before acting.

The pixel138 Privacy Policy covers account and phone details, device and browser signals, cookies, support messages and payment records connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security checks, access requests and correction or removal questions.

We use your phone number for account access and a clear verification step. It can help us connect a support request to the correct account and identify an access attempt. If you ask to change it, we may request an account check before updating the record.

Yes. The Privacy Policy covers records created when you use a mobile browser or desktop path, including browser settings, sign-in events and cookie choices. These details help us keep account access secure while you move between the lobby, Fishing War Mobile Play and wallet status.

We may link a DANA or QRIS payment reference, receipt detail and status result to your account so we can identify the correct transaction. We do not need your wallet PIN for that check. OVO, GoPay, bank transfer and virtual account records follow the same account-matching purpose.

You can contact us through the signed-in account path and ask for the data connected with your account. State the records you want, such as phone, cookie, device or payment data. We may verify your identity first, and access depends on local law and retention duties.

Send a correction request through account support with the record category and the accurate replacement detail. For a phone number or wallet reference, we may require verification before changing it. We will explain if a record must remain unchanged for security or legal reasons.

Retention depends on why the record exists, such as account security, payment reconciliation, support history or a legal requirement. Ask us about a particular category rather than assuming every record follows one period. We can explain the applicable basis and whether a removal request is available.