Reference

Privacy Policy for Your pkj4d Account

pkj4d Privacy Policy explains what we collect when you create an account, verify your phone, enter the lobby, or connect DANA, OVO, GoPay, or QRIS.

Account dataWallet recordsCookie choicesAccess requests
pkj4d Privacy Policy for Your pkj4d Account
CONTACT ROUTES

Get Privacy Policy Help Through Your Account

A clear support path helps when you cannot identify a wallet record or want to ask about the Privacy Policy. Start from the support link in your account area and include the phone number attached to your account, the relevant date, and the payment reference if your question concerns DANA or QRIS. We use those details to locate the correct record without asking you to send a password. Your request can cover access, correction, deletion, cookies, retention, or account security.

Team online

Data request

Use the account support path to ask what personal data we hold. Include your verified phone number and the subject of your request, so we can match the enquiry to the correct account without exposing another person’s records.

Wallet query

For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account question, provide the transaction reference and date. We check the stored status record and explain which payment details are connected to your account.

Security concern

If a login or phone verification event looks unfamiliar, use the same support route and describe the device and time shown in your account. We can review the access trail and guide the next account-security step.

DATA PRACTICES

Inside pkj4d Privacy Policy Controls

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

Account details

We may hold your phone number, verification state, login events, device signals, and support messages. These fields let us confirm that a Privacy Policy request comes from the person connected with the account.

Cookie settings

Cookies can keep your session active and help us understand page loading or navigation. You can adjust cookie controls in your browser, although disabling certain cookies may require another login or affect account-area access.

Payment matching

A wallet or bank record may include a reference, amount status, time, and selected rail. We use this narrow transaction context to match DANA, QRIS, OVO, GoPay, or bank activity to your account query.

Device security

When you move from phone login to the lobby, we may record device and session signals for protection. An unfamiliar event can trigger an account check before access continues, without requiring your password in support messages.

Retention choices

We remove or anonymise eligible records when the stated need ends, subject to a lawful reason to keep them. A request about a Live Baccarat Diamond or Capsa Susun VIP Table record follows the same retention assessment.

Change requests

To correct a phone detail, ask about stored data, or request deletion, send the request through account support. We may verify your account first, then confirm what can be changed under local rules.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet is connected. We describe the account step, the records created by local payment rails, and the route for requesting action. If a question depends on eligibility or a retention duty, the answer remains subject to local law and the facts linked to your account.

It covers account details, phone verification, login and device signals, cookies, support messages, and payment references. It also explains how we use records connected with DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity.

Phone verification connects account access with the number you provide and helps us respond to a data request safely. We may compare the verification state with login events before discussing records from your account or wallet activity.

Open the support link inside your account and ask for access to your personal data. Include your verified phone number and a clear request subject. We may complete an identity check before sharing records linked to your account.

Yes. We may retain payment references, status results, timestamps, and account links for DANA and QRIS, as well as OVO, GoPay, bank transfer, and virtual account activity. We use them to match a transaction question and protect account access.

Send a correction or deletion request through the account support path. We first verify the request, then assess the record. Where local law permits, eligible data can be changed or removed; records required for security or lawful duties may remain.

Cookies can preserve a login session and help us understand whether pages load correctly on your phone or desktop. Browser settings let you manage them. Turning off certain cookies may lead to another login or limit account-area functions.

We retain records for the period needed for account access, payment matching, security, support, or a lawful duty. When that need ends, we remove or anonymise eligible material. A specific retention answer requires checking the record and applicable local law.