Reference

bet388 bet Privacy Policy for Your Account

Our Privacy Policy explains what bet388 bet collects when you open an account, verify your phone and move between casino, sports and wallet screens.

Account clarityWallet data contextCookie choicesRequest access
bet388 bet bet388 bet Privacy Policy for Your Account
CONTACT YOUR WAY

Privacy Questions Reach Our Support Team

A clear contact path helps when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record. Start from the support contact shown in your signed-in account and include the email or phone detail connected to your profile. We may ask for an account step or transaction reference so we discuss the right record without exposing private data. Do not send a password, wallet PIN or full banking credentials.

Team online

Account request

Use the support contact inside your account to ask what personal data is linked to your profile. Include your account identifier and the specific Privacy Policy question, while keeping your password and wallet PIN out of the message.

Wallet record

For a DANA, OVO, GoPay or QRIS reference, share the date, rail name and visible transaction code only. We use those details to locate the payment record and avoid asking you to reveal a banking password or private wallet credential.

Access concern

If a phone verification or sign-in event looks unfamiliar, contact us through the account support route and describe the device and time shown. We can review the relevant access record and explain which security step is needed next.

DATA HANDLING

Six Practical Privacy Commitments

We handle privacy through visible account actions rather than vague promises. The records connected with your login, phone verification, wallet status and lobby activity are used for defined operational purposes.

Account details

We collect details needed to create and identify your account, such as contact data and the account identifier shown after registration. Phone verification helps connect a sign-in request with your profile before account access is completed.

Device signals

Login time, browser or mobile device details and security signals may be recorded to spot unusual access. These records help us examine a concern without relying only on the location or appearance of a single session.

Payment references

A cashier record can show DANA, OVO, GoPay, QRIS, bank transfer or virtual account references. We use the reference and status to reconcile your account activity, not to request your wallet PIN or bank login.

Cookies

Cookies and similar storage can remember a session, preserve language or help us understand which policy page was opened. You can manage browser storage through your device settings, although removing it may require another sign-in.

Retention

We keep records only for the period needed for account operation, security checks, dispute handling or an applicable legal requirement. When a record is no longer needed, our process removes it or separates it from direct account identification.

Change requests

You can ask us to access, correct or clarify personal data through the support contact linked to your account. Tell us which record is involved; we may verify ownership before changing details or sharing a copy.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers address the account questions we expect before you continue with bet388 bet. They explain the practical link between your phone verification, device session, local wallet reference and account records. If your question is not covered, use the support contact shown after sign-in and describe the exact data or event you want us to check.

The bet388 bet Privacy Policy covers account and contact details, phone verification, login events, device signals, cookie records and payment references. It can also cover activity connected with casino or sports areas when that activity is required to answer a request, protect an account or reconcile a transaction.

Phone verification helps us match a sign-in request with the correct account before access is completed. We retain the related event so we can examine account-security questions, including an unfamiliar mobile session, without asking you to share a password.

Yes. The Privacy Policy includes payment references and status connected with DANA, OVO, GoPay and QRIS. We may also record bank transfer or virtual account details needed to match activity, but you should not send a wallet PIN, banking password or full credentials.

You can contact us through the support route shown in your signed-in account and request access, clarification or correction. State the account detail or payment reference involved. We may verify ownership first, and some records may remain where an applicable legal requirement requires retention.

Cookies can keep your session active, remember a selected language and show that a Privacy Policy page was opened. Browser or device settings let you remove them. After removal, you may need to sign in again and some account controls may not behave as expected.

The same Privacy Policy applies whether you sign in through a mobile browser or desktop browser. Device and login signals may be recorded for security as you move from account access to Live Roulette Wheel or Football Betting Live, subject to local law.

We describe access for Indonesia and handle account records connected with Indonesian payment rails and activity. Availability and eligibility depend on local law. If you need a location-specific answer, contact us from your account and mention the region shown during access.