Reference

imbagacor Privacy Policy for Your Account

imbagacor Privacy Policy explains what we collect when you open an account, verify your phone, browse Andar Bahar or Wild West Gold, and use DANA or QRIS.

Clear data purposesWallet record contextAccount access controlsRequest-based updates
imbagacor imbagacor Privacy Policy for Your Account
PRIVACY SUPPORT

Get Privacy Help Near Account Access

A clear contact route matters when your account record or wallet reference needs attention. Open the account support path and tell us whether your request concerns phone verification, a DANA receipt, QRIS status or a device session. We use the details you provide to locate the right record, and we ask you to avoid sending passwords or full wallet credentials. Where local law permits, our support team can explain the next privacy step.

Team online

Account request

Use the account support path for access, correction or deletion questions. Include your account contact detail and the specific record involved so we can check identity before discussing private data.

Wallet record

For DANA, OVO, GoPay or QRIS concerns, share the transaction reference rather than wallet credentials. We can compare the reference with the account record and explain what data remains stored.

Device session

If a mobile browser session looks unfamiliar, tell us the device path and approximate time. We can review the security event, ask for phone verification and help protect account access.

DATA CONTROL

What Your Privacy Choices Cover

We keep this policy practical by connecting each privacy choice to an account action. Phone verification helps us distinguish your account from an unknown sign-in, while session records help us investigate unusual…

Data handling

We use account, device and wallet-reference data for the stated account, security and record-matching purposes. Browsing Andar Bahar or Dota 2 may create activity records connected to your account session.

Cookie choices

Cookies can keep a mobile sign-in session connected and help flag unusual access. You can adjust cookie controls in your browser settings, then sign in again if the account path asks for it.

Account security

Phone verification is checked before account access, and security events may be reviewed when a device changes. Never place your password, one-time code or full wallet credentials in a request.

Retention period

We retain selected account and payment-reference records for security checks, dispute handling and legal duties. Retention can differ by record type, and deletion may be limited where a duty still applies.

Who to contact

Our account support route handles privacy questions about your profile, device session or wallet reference. State the request clearly, and we will ask for enough detail to verify ownership without requesting your password.

Request changes

Where local law permits, you can request access, correction or deletion of eligible personal data. We may confirm your phone verification first, then explain the result and any record that must remain.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. We explain the account step, device path and request route in plain English, with local examples such as DANA, QRIS and mobile access. If a question involves eligibility, access depends on local law and the answer may require a location-specific check.

It covers account details, phone verification, device and browser events, cookies, lobby activity records and wallet references from DANA, OVO, GoPay, QRIS, virtual account and bank transfer use.

Phone verification helps us confirm account ownership before access and before discussing private records. It can also help us investigate an unfamiliar mobile session without asking you to share a password.

Yes. The policy can cover account-linked activity such as opening Fish Hunter, Super Bingo or Crash Games. We use that record for account functions, security checks and applicable record duties.

We retain the wallet reference, amount and status needed to match an account record. We do not need your wallet password, and you should send only the transaction reference when requesting help.

Where local law permits, you can ask for access to eligible records or request a correction. Use the account support path, identify the account contact detail and complete any ownership check we require.

Retention depends on the record and its purpose. Security, dispute and legal records may remain after a session ends, while other details may be removed when they are no longer needed.

Yes. It covers the mobile browser path from phone verification to the lobby, including cookies, device type and security events. Access remains subject to local law and available account controls.