Reference

Privacy Policy for Your 666menang Account

Our 666menang Privacy Policy explains what data we use when you open an account, complete phone verification, sign in from a mobile device, or connect DANA, OVO, GoPay…

ACCOUNT DATAWALLET RECORDSCOOKIE CHOICESLOCAL ACCESS
666menang Privacy Policy for Your 666menang Account
HELP WITH REQUESTS

Get Help With a Privacy Request

A clear contact path matters when you want to ask about your Privacy Policy rights or an account record.

Account privacy chat Use the support chat inside your signed-in account to ask what account data we hold, why a phone verification record appears, or how to request a correction. We may ask you to confirm the registered phone number before discussing private account details.
Wallet record check For a DANA, OVO, GoPay or QRIS record, send the transaction reference shown on your receipt through the account support route. We can compare the reference and status while keeping your wallet PIN, password and full security credentials out of the message.
Access and deletion request Ask the support team to explain a data access, correction or deletion request through the same account path. We first verify that you control the account, then confirm which records can be changed or retained under the Privacy Policy and local law.
CONTROL AND SECURITY

Controls Behind Your Account Data

Your Privacy Policy questions should lead to a specific action, not a vague promise. We separate account identifiers, wallet references, device signals and cookie choices so each request can be handled against…

Account ownership

Phone verification is used before we discuss private account records through support. If you sign in from a new phone or browser, device signals may be checked against recent account activity. Never share your password, wallet PIN or verification code with anyone contacting you.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match payment status with the correct account. We use the reference and status for reconciliation and support, rather than asking you to send a wallet PIN or full login secret.

Cookie choices

Cookies can remember a sign-in preference, support session continuity and help us understand whether a page is working on your device. You can control browser cookie settings, although removing necessary cookies may require you to verify your account again.

Device protection

We may record browser type, device signals, approximate session timing and sign-in events to identify unusual access. These checks support account security; they are not a substitute for your own password care. Sign out after using a shared phone or computer.

Retention approach

We keep account, support and transaction records only for as long as needed for the stated service, security checks, dispute handling or legal duties. When a record no longer has a valid purpose, our handling process moves it toward removal or de-identification.

Requesting changes

You can ask us to correct account data, explain a processing purpose, provide available records or close an account through the support chat in your account area. We verify ownership first and tell you if a record must remain for a legal or transaction reason.

Privacy Policy Questions for Indonesia

These Privacy Policy answers cover the questions we expect you to ask before opening an account or connecting a local wallet. Each answer points back to an account step, device setting or support route so you know what to do next. Where access or eligibility is discussed, it depends on local law.

The 666menang Privacy Policy covers account details, phone verification, wallet and bank references, device signals, cookies, support records, retention and requests to change or remove data. It also explains how we handle access questions where local law permits.

Phone verification helps connect an account to the person opening it and gives support a safer ownership check. We may ask for confirmation before discussing account data, wallet status or a Privacy Policy request, but you should never send your password or wallet PIN.

We may store the selected rail, transaction reference, amount, timestamp and status for DANA or QRIS. These records let us match a receipt when a wallet status stalls. We do not need your wallet PIN to investigate a payment record through support.

Yes. Open the support chat linked in your account area and ask for a data access or correction request. We confirm that you control the account, identify the relevant record, and explain any part that must remain under the Privacy Policy or local law.

Cookies can keep a session active, remember selected settings and help us detect whether a page works on your device. You can change browser cookie settings, but removing necessary cookies may sign you out or require phone verification when you return.

We retain account, transaction and support records for the period needed for service delivery, security checks, disputes or legal duties. The exact period can differ by record type. You can ask support to explain why a particular record is still retained.

Use the support chat shown inside your signed-in account and state that your request concerns the Privacy Policy. Include your registered phone number and, for a wallet query, the transaction reference. We verify ownership before discussing private records or processing a change.