Reference

4P4P Privacy Policy: Your Data Choices

Our 4P4P Privacy Policy explains how we handle your account details, phone verification, device access and payment references for DANA, OVO, GoPay and QRIS.

Account dataWallet referencesCookie choicesRequest access
4P4P 4P4P Privacy Policy: Your Data Choices
CONTACT ROUTES

Where To Ask About Privacy

A direct privacy question should start from your signed-in account so we can match the request to the correct phone verification record.

Account privacy request Use the account support route to ask what personal details are connected with your…
Payment record question If a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference looks wrong…
Correction or deletion Ask us to correct outdated contact details or explain whether a deletion request can…
SECURITY PRACTICE

How We Handle Your Account Data

Privacy at 4P4P is tied to practical account steps rather than broad promises. We separate login credentials from payment references, use device signals to help identify unusual access and keep cookie controls…

Account security

Phone verification helps connect an account request to the right profile. We may use sign-in and device signals to identify unusual access, but you should still keep your password and wallet PIN private.

Payment references

For DANA, OVO, GoPay and QRIS activity, we handle payment status and reference details needed for account records. We do not ask you to place a wallet PIN inside a support message.

Cookies on devices

Cookies and similar device storage can remember a session, language choice or consent setting. Clearing them may sign you out or reset a preference, while the policy still explains how related records are handled.

Mobile access records

When you move from phone login to the lobby, device and connection signals may be recorded for security and service operation. The same approach can apply when opening Live Baccarat or Crash Games on mobile.

Retention periods

We keep personal data only for the period needed for account operation, security checks, support history or applicable legal duties. A deletion request may not remove records that must remain for those reasons.

Your data requests

You can ask for access, correction or clarification through the account support path. We may request enough account detail to verify the requester before sharing, changing or removing personal data.

Privacy Policy Questions For 4P4P

These Privacy Policy answers address the account, device and payment questions you may have before opening access. If your situation is not covered, contact us through the account support route with a clear subject and the relevant reference, while keeping passwords and wallet PINs out of your message.

It covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us connect account access and privacy requests to the correct profile. It also supports security checks when your sign-in device changes or an account detail needs correction.

Yes. When you use the mobile path from login to the lobby, we may handle device and connection signals for session operation and unusual-access checks. Clearing cookies can end the current session.

We use DANA and QRIS references to match payment status with your account record. We do not need your wallet PIN in a support request, and payment data remains subject to the retention rules described here.

You can contact us through the signed-in account support route and ask for access to personal data linked with your profile. We may verify your identity before responding, where local law permits.

You may ask us to correct inaccurate contact details or request deletion. We assess each request against account security, payment records and legal retention duties, so some records may need to remain.

We use the contact detail connected with your account or the support route you used to send the request. Include a clear subject and receipt reference when relevant, but never include your password or wallet PIN.