Reference

Indo Betting Guide Privacy Policy For Your Account

Indo Betting Guide Privacy Policy explains what we collect when you create an account, verify your phone, use DANA or QRIS, and contact us about your account.

Clear data purposesPhone verificationDANA and QRIS recordsAccount access requests
Indo Betting Guide Indo Betting Guide Privacy Policy For Your Account
ACCOUNT HELP

Get Privacy Help Through Your Account Path

A privacy request should not get lost beside a wallet question. Start from the support route linked to your account and state whether you need access, correction, deletion, or an explanation of a payment record. Include the phone number linked to your account, but never send a password or full payment credentials. From Denpasar or elsewhere in Indonesia, the same account help path lets us check identity before responding.

Team online

Account support route

Use the support link beside your account area to send a Privacy Policy request. We use the account phone number and request details to confirm that the request belongs to you.

Wallet record question

If a DANA, OVO, GoPay, or QRIS record needs clarification, tell us the rail and reference shown in your account. We can then narrow the search without requesting your secret wallet credentials.

Security concern

For an unfamiliar login or account detail, contact support through the signed-in account path as soon as possible. We may pause changes until phone verification confirms your identity.

SECURITY PRACTICE

Your Security Choices From Login Onward

Privacy depends on how data is handled after you leave the form. We separate account access, payment status, support requests, and security events so each team sees only what its task requires.

Collection purpose

We collect phone, account, device, and transaction details to create access, verify ownership, record wallet status, investigate security events, and answer requests connected with your account.

Cookie control

Cookies can keep a mobile or desktop session working and help us recognise security preferences. Clearing browser cookies may sign you out and require phone verification again.

Account security

Phone verification is an account step before access. We use it to reduce mistaken identity when you request a data copy, change account details, or question a payment record.

Payment separation

For DANA, QRIS, bank transfer, and virtual account activity, we keep the transaction reference and status needed for reconciliation rather than asking for your wallet password.

Retention period

We retain records while they support account operation, security checks, disputes, or legal duties. When those needs end, records are removed, restricted, or separated from active access.

Change request

You can ask us to correct account details, explain stored data, or consider deletion through the support path. Access and the result of a request depend on local law.

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. They cover phone verification, cookies, local payment records, requests for copies or changes, and the access wording that applies in Indonesia. If your situation is unusual, use the account support path so we can review the specific record.

It covers account, phone verification, device, cookie, support, and payment-status data connected with your use of Indo Betting Guide. It also explains purposes, retention, security controls, and request paths.

We use your phone number to create and verify account access, reduce mistaken identity, and confirm requests for copies, corrections, or deletion. We do not need your wallet password for this step.

Yes. The Privacy Policy covers the DANA or QRIS rail selected, transaction reference, status, and timing needed to match an account request. Sensitive wallet credentials should not be sent to support.

Cookies can keep a mobile or desktop session active and remember security preferences. Clearing them may sign you out, remove saved session data, and require phone verification when you access the account again.

You can ask through the signed-in account support path and describe the records you want, such as account details or payment status. We confirm identity first, and access depends on local law.

Send a correction request through account support, identify the inaccurate field, and provide the current detail. We may ask for phone verification before changing account data or linked payment status.

You can request deletion through the account support path. We assess the request against security, dispute, operating, and legal needs; where local law permits, eligible records can then be removed or restricted.