Reference

nama666 Privacy Policy For Indonesia

The nama666 Privacy Policy explains what we collect when you create an account, verify your phone, enter the casino lobby and use DANA, OVO, GoPay or QRIS.

Clear data purposesCookie choicesAccount securityContact request path
nama666 nama666 Privacy Policy For Indonesia
CONTACT ROUTES

Get Privacy Help Through Your Account

A clear contact route helps when you want to ask about personal data rather than a wallet status. We handle privacy questions through the support path available after you sign in, so we can match the request with the correct account and avoid sending account details to the wrong person. Include the email or phone detail connected to your account, the subject of your request and any relevant receipt reference. We may ask for an account step, such as phone verification, before discussing private records.

Team online

Account support

Use the support path after sign-in for a Privacy Policy question, data access request or correction request. We check the account connection before sharing personal details, which helps keep your request attached to the right nama666 profile.

Payment record help

If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, include the payment reference and date. We use those details to locate the relevant status without asking for your wallet password or banking login.

Access assistance

When you cannot reach the account support route, use the contact option displayed on the nama666 site and explain the access problem. Do not send a password, wallet PIN or one-time code; we will request only details needed to verify the request.

DATA PRACTICES

Six Practical Privacy Controls

We apply the Privacy Policy to the real account actions you take, from opening access on a phone to checking a wallet status beside the lobby.

Account details

We use the name, contact detail and other fields you submit to create and maintain your account.

Wallet references

DANA, OVO, GoPay and QRIS may return a transaction reference or status, while bank transfer and virtual account activity can…

Device signals

A phone or desktop browser can provide technical signals such as browser type, operating system, language and approximate network details.

Cookies

Cookies can remember a session, preserve selected settings and help us understand whether pages load correctly.

Retention

We retain account, payment and support records only for as long as needed for the stated purpose, security checks, dispute…

Your requests

You can ask us to provide available personal data, correct an inaccurate detail, explain a processing purpose or delete eligible…

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or continuing from a phone in Indonesia. We describe the data path in plain terms, including payment references, cookies, account verification and contact steps. If your situation is specific, use the support route connected to your signed-in account and include only the details needed to identify the request.

The Privacy Policy treats your phone number and verification result as account-access data. We use them to confirm control of the contact route and protect the profile from mistaken or unusual sign-ins. We do not need your one-time code in a support message.

No wallet password or PIN is needed for our account records. When you use DANA, OVO, GoPay or QRIS, we may receive a reference, amount and status from the payment flow so we can match the action to your profile and answer a receipt question.

For a bank transfer or virtual account, we may retain the reference, receiving-bank status, amount and related account identifier. These details help reconcile the transaction and resolve a support request. They are handled as payment records, not as permission to access your BCA, BRI, Mandiri or BNI account.

Yes, you can ask for available personal data or request correction of an inaccurate detail through account support. Include the contact detail linked to your profile and describe the item clearly. We may complete an identity check before responding to protect the account holder.

Cookies can keep a sign-in session active, remember selected settings and show whether pages work correctly on your phone or desktop. Browser controls let you remove or restrict them. Necessary cookies may still be required for phone verification, account access and the lobby path.

Retention depends on the purpose of the record, security needs, dispute handling and applicable legal duties. We do not promise one period for every record. When the reason ends, we remove, anonymise or restrict the data according to our internal handling process.

Use the contact option displayed on the nama666 site and explain that your question concerns privacy or account access. Do not include a password, wallet PIN or one-time code. We may ask for limited identifying details before discussing a private account record.