Reference

Open pgking6 Privacy Policy Details

pgking6 Privacy Policy explains what we collect when you create an account, verify your phone, sign in from a mobile device, and use wallet records such as DANA…

ACCOUNT DATACOOKIE CHOICESLOCAL ACCESSREQUEST PATH
Explore Our Lobby Read FAQ
pgking6 Open pgking6 Privacy Policy Details
REQUEST SUPPORT

Contact Us About Privacy Requests

A clear contact route helps you resolve a data question without sending sensitive details through an unsuitable channel. Start with the account help route when your request concerns phone verification, a wallet reference, or a sign-in record. For a copy, correction, deletion query, or cookie concern, describe the request and include the account identifier we can use to locate it. We may ask for an account check before changing data, so another person cannot act on your behalf.

Team online

Account Help Route

Use account help when a phone verification record, login event, or wallet status appears unfamiliar. We use the details you provide to locate the relevant account record, confirm that you are the account holder, and keep the request attached to the correct case.

Privacy Request Form

For access, correction, deletion, or cookie questions, submit a privacy request through the available contact path. Tell us which data period or account action concerns you, such as a QRIS reference or device sign-in, so we can assess the request accurately.

Payment Data Check

If a DANA, OVO, GoPay, bank transfer, or virtual account reference is involved, share the transaction date and status rather than a password or full secret credential. We compare the reference with account records before discussing the related data.

DATA PRACTICES

Browse pgking6 Data Handling Steps

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

Account Details

We collect the details needed to create and maintain your account, including contact data and phone verification status. If you request a correction, we compare your request with the account record before changing it, helping prevent an unauthorised alteration.

Device Signals

A mobile browser or another device may provide session, browser, and security signals when you sign in. We use these signals to recognise unusual access around the account, not to request your device password or private wallet credential.

Cookie Controls

Cookies can remember a session choice, language setting, or security state on your browser. You can clear or restrict cookies through browser controls, although some account functions may then require another sign-in or verification step.

Payment References

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity can create references, status values, timestamps, and amounts. We use those records to match account events and resolve status questions without collecting your wallet password.

Retention Steps

We retain account and support records only while they serve the stated account, security, dispute, or legal purpose. When a retention need ends, records are removed, anonymised, or restricted according to the process that applies to that data.

Change Requests

You can ask to access, correct, or delete eligible data through the privacy contact path. Include your account identifier and the requested change; we may verify your identity first and explain if a legal or security reason limits the request.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers address the account and device questions we expect from Indonesian customers before they open an account. They cover wallet references, cookies, access requests, retention, and the identity check used to protect your records. If your case is not listed, use the privacy contact path and describe the account action involved.

The pgking6 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages, payment references, security records, retention, and your available data requests. It also explains why we use each category and how to contact us about access or correction.

Yes. Our Privacy Policy covers references linked to DANA, QRIS, OVO, GoPay, bank transfer, and virtual account activity. We may handle status, amount, timestamp, and reference data so an account event can be matched or checked, but we do not ask for your wallet password.

When you complete phone verification, we record the contact detail, verification state, and related account event. A device or browser may also provide session and security signals. These records help protect account access and respond when you question an unfamiliar sign-in.

Use the privacy request path and state that you want access to your data. Include your account identifier and describe the relevant area, such as a device sign-in or QRIS reference. We may complete an identity check before providing records to the correct account holder.

You can request a correction or deletion of eligible data through the contact path described in this Privacy Policy. Tell us what appears wrong or what you want removed. We assess the request against account, security, dispute, and legal needs before confirming the result.

We keep each category only while it supports the stated account, security, support, dispute, or legal purpose. The period can differ by record type, so a payment reference may follow a different retention need from a cookie choice. Ask through the privacy path for case-specific detail.

The Privacy Policy applies to data created when you access the account from a supported mobile browser or other device in Indonesia. Eligibility and access depend on local law. You can still ask about cookies, device signals, account data, or correction where local law permits.

Related Pages

pgking6 Indonesia Serie A Match Bet About Us FAQ Access guide