Reference

Privacy Policy For Your bom666 Account

The bom666 Privacy Policy explains how we handle the details you provide when opening an account, signing in on mobile, or checking DANA, OVO, GoPay and QRIS status.

Account clarityWallet data controlsMobile access recordsRequest a change
Browse Our Lobby Read FAQ
bom666 Privacy Policy For Your bom666 Account
CONTACT YOUR WAY

Get Policy Help Before Changing Details

If you want to understand the Privacy Policy before opening an account, our support path keeps the request tied to the right record. Tell us whether your question concerns phone verification, a sign-in device, a wallet reference or a correction to account data. We use the account and receipt details you provide to locate the relevant event, while asking only for what is needed to respond. Access remains subject to local law, and we explain the next step when a request needs identity confirmation.

Team online

Account data request

Ask us to explain the account details held for you, including phone verification and sign-in records. We may request an account identifier before replying so we do not disclose private details to the wrong person.

Wallet reference check

For DANA, OVO, GoPay or QRIS questions, include the payment reference and approximate time shown in your receipt. We use those details to check status without asking you to send a wallet password or security code.

Correction support

If your contact detail or account record is incorrect, contact our support desk through the account help path. We verify the request, record the change, and tell you if another step is required before the record is updated.

DATA CARE DETAILS

See The Controls Behind Your Privacy Policy

We keep the Privacy Policy practical by connecting each data practice to an account action you can recognise.

Data collection

We collect details you submit for account access, such as contact information and phone verification data. We also receive event data from sign-ins, device use, support messages and payment references needed to connect an account action with its status.

Cookie choices

Cookies can remember sign-in settings and help us understand whether a page request works on your device. You can manage cookies through your browser settings, although disabling some cookies may require you to repeat account or security steps.

Account security

We use phone verification and sign-in event checks to help protect account access. Never send us a password, wallet PIN or one-time security code in a support message; our process does not require those secrets for a policy request.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a payment record with your account. We use the reference for status and reconciliation, rather than treating wallet details as general profile content.

Retention timing

We retain account, security, payment and support records only while they serve an operational, safety or legal purpose. When a record no longer needs to be kept, we remove it or separate it from direct account identifiers where our process allows.

Your requests

You can ask for access to your personal data, correction of an inaccurate record, or clarification of a retention decision. We may confirm account ownership first, then explain the result and any restriction that depends on local law.

Answers About bom666 Privacy Policy

These Privacy Policy answers address the questions we expect you to ask before creating an account or connecting a wallet. We keep the wording tied to actual bom666 actions, from phone verification and mobile sign-in to payment references and requests for account access. If your situation is not covered, use the support path and include only the details needed to identify your request.

It covers account details, phone verification, sign-in and device events, cookie activity, payment references, support messages, retention and requests to access or correct your data. It also explains how access is handled where local law permits and when a request depends on local law.

Phone verification connects your account to a confirmed contact step and helps us check account access. We retain the verification record for security and account support purposes, not as a wallet password. If the record is inaccurate, you can request a correction through support.

Yes. When you use DANA, OVO, GoPay or QRIS, we may keep a payment reference, amount status and timing needed to match the transaction with your account. We use this record for reconciliation and support, and do not ask for your wallet PIN.

We may record device and browser details, sign-in time, security events and cookie settings that help us recognise an account session. These records help investigate access issues on mobile or desktop. Browser controls can limit cookies, but some account steps may then repeat.

Contact our support desk through the account help path and state that you are requesting access under the Privacy Policy. Include your account identifier and the category you want checked, such as phone verification, device events or payment references. We confirm ownership before responding.

You can request correction of inaccurate account details and ask how deletion applies to your record. Some security, payment or legal records may need retention for a defined purpose, so we explain the outcome rather than removing a record that depends on local law.

The policy is available for your account questions, but access and eligibility decisions depend on local law. Where local law permits, we handle requests through the stated support path, verify account ownership and explain any restriction affecting data access, correction or retention.

Related Pages

bom666 Indonesia bolampo bom666 Casino Access guide fantasy88