Reference

pangeran911 Privacy Policy for Your Account

Our Privacy Policy explains what pangeran911 collects when you create an account, sign in, use Live Baccarat or check DANA, OVO, GoPay and QRIS status.

Account dataWallet recordsCookie choicesSupport requests
pangeran911 pangeran911 Privacy Policy for Your Account
CONTACT DATA CARE

Three Ways to Ask About Privacy

A clear contact path matters when your account record or wallet reference needs attention. We keep privacy requests close to the account support route, so you can identify the relevant login, payment reference or device event without sending unnecessary details. If you are in Jakarta or elsewhere in Indonesia, use the same account-based path to ask about access, correction, deletion eligibility or a question about this Privacy Policy.

Team online

Account support

Use the support route after signing in and include the email or phone number attached to your account. We can locate the request more accurately without asking you to share a password.

Wallet reference

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, provide the transaction reference and date. Leave out wallet PINs, one-time codes and full login credentials.

Access request

Ask for a copy, correction or clarification by naming the Privacy Policy issue. We may request an account verification step before discussing personal records linked to your identity.

SIX DATA CONTROLS

What We Do With Your Records

We treat account data as operational material rather than a reason to collect more than needed. Our Privacy Policy connects each handling step to account access, security, payment matching or support.

Account details

We use your submitted contact details to create the account, send access messages and connect phone verification with the correct profile. Keep your details current so a privacy request can be matched safely.

Device signals

Login time, browser type and device signals can help us identify unusual access. On mobile, these checks support the path from phone verification to the lobby without exposing your password to support.

Cookie settings

Cookies can remember session choices and help pages load with the right account state. You can manage browser cookie controls, although switching them off may interrupt sign-in or account request forms.

Payment references

DANA, OVO, GoPay and QRIS references help match wallet activity, while bank transfer and virtual account references support reconciliation. We do not need your wallet PIN or one-time code for that match.

Security checks

Before we discuss personal records or change account details, we may ask you to complete phone or account verification. This step reduces the chance of disclosing data to the wrong person.

Record retention

We retain account, security and transaction records only for operational, dispute-handling or legal needs described in the Privacy Policy. When a record is no longer needed, handling follows our retention process.

Privacy Policy Questions for pangeran911

These answers address the searches we hear most often about the pangeran911 Privacy Policy. They cover account creation, mobile access, wallet references, cookies and requests for personal data, while the full policy remains the place to check the applicable wording for your account.

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

Phone verification helps connect access to the correct account and supports security checks before we discuss personal records. We may use the result to prevent an unrelated person from changing account details.

Yes. The Privacy Policy includes browser and device signals created when you sign in from a phone. These signals help maintain a session and identify unusual access without requiring your wallet PIN.

You can send a request through the account support route asking for a copy or explanation of personal data. We may verify your account first, and the response depends on applicable legal requirements.

Use account support and identify the profile detail that needs correction, such as a phone number or email address. We may ask for verification before changing information linked to account access.

We use transaction references, dates and status details to match a wallet request with your account. Do not send a PIN, one-time code or complete wallet credentials in a support message.

Retention depends on the type of record and the operational, dispute-handling or legal reason for keeping it. Account support can explain the applicable request path after verifying the account.