Reference

poker369 Privacy Policy for Your Account

poker369 Privacy Policy explains how we handle your account details, device signals, cookies, and payment records when you use our service.

Account dataDevice settingsWallet recordsCookie choices
Explore Our Lobby Read FAQ
poker369 poker369 Privacy Policy for Your Account
PRIVACY HELP

Check Privacy Help Through Your Account

A clear contact route matters when you want to ask about a stored detail, correct a phone number, or understand a wallet reference. From your account help area, send the relevant account step and payment reference rather than sharing a password or full wallet credential. Our support route is designed to keep privacy requests separate from lobby activity, including when a QRIS status needs checking. We answer requests through the contact path shown on the site, subject to identity checks.

Team online

Account help path

Use the account help link when you want to ask about profile data, phone verification, cookies, or a Privacy Policy request. Include the email or phone connected to your account so we can identify the correct record without requesting your password.

Payment status request

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account questions, send the transaction reference shown in your cashier history. We use that reference to locate the relevant record and avoid asking for complete wallet credentials.

Correction request

If your name, phone number, or contact detail needs changing, ask through the support route connected to your account. We may ask for a phone verification step before making a correction, helping prevent another person from changing your profile.

DATA PRACTICES

Browse Our Data Handling Commitments

We handle Privacy Policy requests through practical account controls rather than vague promises. Your sign-in record, device details, cookie settings, and wallet references serve different purposes, so we assess each request against…

Account security

Phone verification can be required before account access or a profile change. We use the step to reduce mistaken identity and protect details connected with your sign-in, without asking you to send a password through support.

Device signals

We may record device type, browser version, IP address, and session events to recognise a returning sign-in and investigate unusual access. These signals help us protect the account path rather than describe your private activity outside our service.

Cookie choices

Cookies can keep a session active, remember a selected setting, and help us understand whether a page loads correctly. Your browser controls can remove or restrict them, although some account steps may then require another sign-in.

Payment records

A wallet or bank reference lets us match a payment status with the correct account. For DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri, or BNI records, we use the relevant reference instead of requesting a full bank credential.

Retention choices

We keep account and transaction records for the period needed for service operation, security checks, disputes, or legal duties. When a retention reason ends, we delete, restrict, or de-identify the record according to the applicable request.

Request handling

You can ask for access, correction, deletion, restriction, or clarification through the account support route. We first confirm that you control the account, then explain the next step and any reason a request cannot be completed.

Find Answers About Privacy Policy

These Privacy Policy answers address the searches we hear most often from people preparing to open an account in Indonesia. We explain which details are collected, how payment references are used, how to reach us, and what happens when you ask for a change. If your question concerns access or eligibility, the answer depends on local law.

The poker369 Privacy Policy covers account details, phone verification, device and session signals, cookies, payment references, support requests, and retention. It explains why each category is used and how you can ask for access, correction, restriction, deletion, or clarification where local law permits.

We do not need your wallet password to match a payment. Our records may contain a transaction reference, status, amount, time, and account connection from DANA, OVO, GoPay, or QRIS. Never send a wallet password through account support or any policy request.

Open the account help path and ask for a copy of the data connected with your account. Include the phone number or email used at sign-in. We may complete phone verification first, then explain the format, scope, and timing of the response.

Yes, you can request a correction through the account support route. Tell us which detail is wrong and provide the account contact used during access. We may ask for a verification step before changing a phone number or other profile record.

Cookies can remember session settings and help pages load with the selected account state. You can restrict them in your browser, but sign-in may be required again and some account steps may not work as intended until necessary cookies are allowed.

We retain records while they are needed for account operation, security checks, payment disputes, support history, or legal duties. After the relevant need ends, we delete, restrict, or de-identify records. A Privacy Policy request can ask which retention reason applies.

Use the contact route shown inside your account help area and describe the Privacy Policy request clearly. You can ask about access, correction, deletion, restriction, cookies, or payment records. We verify account control before discussing details or changing a record.

Related Pages

poker369 Indonesia La Liga Mix Parlay poker369 Casino VIP Baccarat Circle About Us