Reference

Privacy Policy For Your pol4d Account

pol4d Privacy Policy explains how we collect, use and protect the details connected to your account, wallet activity and lobby access.

Account dataWallet recordsCookie choicesSecurity steps
Explore Our Lobby Read FAQ
pol4d Privacy Policy For Your pol4d Account
HELP WITH PRIVACY

Get Policy Help Beside Your Account

A clear contact route helps you ask what we hold, why we use it, or how to request a correction. Start from the account help path when your question concerns sign-in, phone verification or a wallet receipt; that context lets us match the request to the right account record. We may ask for account details needed to confirm your identity, but you should not send a password or one-time security code. We handle privacy questions as policy requests, not as general lobby enquiries.

Team online

Account data request

Use the account help path to ask which personal details are connected to your pol4d account. We may verify your phone before discussing records, so the request reaches the account holder rather than another person.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks incorrect, include the payment date and account identifier through support. We use those details to locate the receipt or status record without asking for your wallet PIN.

Policy change request

Ask us to correct outdated details or explain a retention question through the same support route. We review the request against your account and reply with the next step, including any identity check needed before a change.

DATA CONTROL LAYERS

What Your Privacy Policy Covers

Privacy controls follow the account journey rather than sitting apart from it. When you sign in, we record technical details needed to keep the session working on your device and to detect…

Account details

We handle details such as your account identifier and verified phone status to provide sign-in and account assistance. Phone verification is an account step, and we use it to help distinguish your request from an unverified third-party enquiry.

Device sessions

A mobile or desktop session can create technical records such as browser, device and sign-in timing details. These records help us investigate access issues and unusual activity without treating your device data as a public profile.

Cookies

Cookies can keep your session active and remember necessary preferences while you move through the lobby. Your browser controls some cookie settings, but disabling required cookies may interrupt sign-in or the account path.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment status to the correct account. We use the reference for reconciliation and support, not as a request for your wallet password.

Security handling

We limit account assistance until the relevant identity details are checked, especially after a phone verification event or unfamiliar sign-in. Never send us a password, wallet PIN or one-time code when asking about Privacy Policy.

Retention requests

We retain personal and transaction records only for the period needed for account operation, security, support and applicable requirements. You can ask what remains stored, request a correction, or ask whether deletion is available for a specific record.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions we receive most often from people using pol4d in Indonesia. They explain what to send, what we use, and where local requirements may affect a request. If your situation is not covered, use the account help path with only the details needed to identify the issue.

The pol4d Privacy Policy covers account details, phone verification, device sessions, cookies, support messages and payment references. It explains why we use those records for sign-in, security, reconciliation and account assistance, along with how you can ask about correction, deletion or retention.

Phone verification helps us confirm that an account request comes from the account holder. We use the verified status when handling sign-in assistance or a data request, and we do not need your password, wallet PIN or one-time code to discuss the policy.

Yes. The Privacy Policy includes operational references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account routes. We use these references to match a payment status, investigate a receipt question and support the correct account.

You can ask for details linked to your pol4d account through the account help path. We may verify your phone or another account detail before responding, because releasing records requires us to distinguish your request from an enquiry made by someone else.

Send a correction request through support and identify the account detail that is outdated. Include only the information needed to locate your account. We assess the request against the available record and may complete an identity check before changing account data.

We keep records for the time needed to operate the account, investigate security events, reconcile DANA, OVO, GoPay, QRIS or bank activity, and meet applicable requirements. The exact period can differ by record type, so ask support about a specific item.

You can ask whether deletion is available for a particular personal record. We assess the request against account security, transaction reconciliation and applicable requirements. Where local law permits, we explain the available action; some records may need to remain stored for a defined purpose.

Related Pages

pol4d Indonesia Access guide About Us Account information pol4d Casino