Reference

bettor365 Privacy Policy For Your Account

Our Privacy Policy explains what bettor365 collects when you open an account, verify your phone, browse Sic Bo or Mega Fishing, and use DANA or QRIS.

Clear data purposesIndonesia account contextWallet record clarityDirect privacy requests
bettor365 bettor365 Privacy Policy For Your Account
CONTACT ROUTES

Privacy Help Beside Your Account

A clear contact path matters when you want to ask about the Privacy Policy or a record attached to your account.

Account privacy request Ask us to locate the personal data connected with your account. Include your registered phone number and the subject of your request, such as a verification record or sign-in history, so we can check the correct account before replying.
Wallet record question If a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account entry looks unfamiliar, send the reference and date through our support route. We use those details to trace the record without asking you to share a wallet password.
Access and cookie help Tell us when a cookie choice, device change, or phone verification step affects access to your privacy settings. We can explain which browser or account detail is relevant and direct the request to the right internal check.
DATA PRACTICES

How bettor365 Handles Privacy Requests

We keep this policy practical: the data you create through an account step, wallet reference, device session, or support conversation should have a stated operational reason.

Account data

When you open an account, we use the submitted phone number and verification result to identify the account and manage sign-in. We do not need your password in a privacy request, and you should never place it in a support message.

Payment references

A DANA, QRIS, OVO, GoPay, bank transfer, or virtual account reference helps us reconcile a cashier event. We use the reference, amount status, and timing for that purpose, while wallet credentials remain outside a privacy request.

Device signals

Your browser, device type, sign-in time, and related access signals can be recorded to identify unusual account activity. These signals help us protect the account path on mobile and desktop without turning a device detail into a public profile.

Cookies

Cookies can remember a session choice or help us understand whether a page request is working. You can adjust cookie controls in your browser; changing them may affect saved preferences, and our support route can explain the resulting account behaviour.

Retention checks

We keep personal records for the time needed to operate the stated purpose, answer a dispute, protect an account, or meet a legal duty. When a record no longer has a valid purpose, our handling process considers removal or de-identification.

Change requests

To request correction, access, deletion where available, or clarification, contact support from the account-linked route. State the record and action you want; we may verify account ownership before changing or disclosing anything.

Privacy Policy Questions For Indonesia

These answers address the privacy searches we hear most often before an account is opened. They explain how the Privacy Policy relates to phone verification, local wallet records, cookies, device access, and requests for changes. If your situation involves a particular transaction or account event, use the support route with a reference rather than posting sensitive details publicly.

The Privacy Policy covers account details, phone verification, sign-in and device signals, cookie choices, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. It explains why we use each category and how you can ask about an eligible record.

Phone verification links an account request to a reachable account detail and helps us check ownership during access or privacy requests. We record the verification result and related account event for these purposes; access remains where local law permits.

Yes. The Privacy Policy covers references connected with QRIS, DANA, OVO, and GoPay, as well as bank transfer and virtual account records. We use those references to reconcile status and answer disputes, not to request your wallet password or PIN.

Contact our on-site support route from the account-linked path and name the data you want corrected, accessed, or removed where available. Include a relevant date or reference, but never send a password. We may check account ownership before acting.

Cookies may retain a session choice or help us identify whether a page request works correctly. You can change browser cookie controls at any time. The Privacy Policy treats those settings separately from account data, and some saved preferences may no longer remain.

We keep a record for the time needed for its stated purpose, account administration, security checks, dispute handling, or a legal duty. Retention can differ by record type. Ask support about a specific phone, payment reference, or device event for a more precise response.

You can ask through our support route for the personal data connected with your account, including verification status, device events, cookie choices, or payment references. Provide your registered phone number and request subject so we can verify the correct account before replying.