Reference

name666 Privacy Policy For Your Account

The name666 Privacy Policy explains what account, device and wallet details we use when you open our lobby on mobile or desktop.

Account dataWallet statusMobile accessPolicy requests
name666 name666 Privacy Policy For Your Account
CONTACT PATHS

Where To Ask About Your Privacy Policy

A direct support path matters when you want to know what we hold about your account or wallet activity. Start from account help beside the cashier path, then describe the request using the phone number or payment reference connected to your account. We can use that detail to find the right record without asking for a wallet password. The same route can help when login status stalls on a mobile browser in Jakarta.

Team online

Account data request

Ask account help what personal details are linked to your name666 account, why a field is needed, or how to request a correction. Include your verified phone number so we can distinguish your request from an unrelated account without exposing account data in an open message.

Wallet record check

For a DANA, OVO, GoPay or QRIS question, send the payment reference and date through the account-help route. We use the receipt or status reference to trace the record, while you should keep wallet passwords, one-time codes and full security credentials out of the message.

Access concern

If your policy page or account page does not load, tell us whether you are using a mobile browser or desktop and what access step stopped. We can check the account path, explain the next privacy request step and apply local-law wording where eligibility is relevant.

HANDLING DETAILS

How We Handle Data Around Your Lobby

Our privacy work follows the account actions you can recognise: sign-in, phone verification, wallet status checks, policy requests and contact with support.

Account records

We use the account details you provide to create access, complete phone verification and respond to a Privacy Policy request. If you ask us to correct a field, we may compare it with the verified account route before changing the record, helping prevent another person from acting on your account.

Cookie choices

Cookies and similar browser storage can help keep your sign-in path, language preference and policy page state working on a mobile browser. You can clear browser storage through your device settings, but doing so may require you to complete phone verification again before account access resumes.

Wallet matching

A DANA, OVO, GoPay or QRIS reference may be retained with the related account event so we can check a receipt or status question. For bank transfer and virtual account requests, the transfer reference serves the same narrow purpose: matching the payment record to your account inquiry.

Account security

Phone verification is an account step, not a request for your wallet password. We use sign-in and verification signals to help identify unusual access, and we ask you to keep one-time codes private. If your device is shared, sign out and clear the browser session after checking the lobby.

Retention checks

We retain account and payment records for the period needed to provide access, resolve a receipt or status issue, meet a valid legal request and protect the service from misuse. When a record no longer serves one of those purposes, our handling follows the applicable retention process.

Change requests

You can ask about access, correction or deletion of personal data through account help. Tell us the request type and the verified phone number linked to your account. We may ask for an additional account check before acting, and we explain any limit that depends on local law.

Privacy Policy Questions About name666

These Privacy Policy answers cover the account and payment questions you are most likely to ask before opening access. We keep the answers tied to real steps: phone verification, mobile browsing, wallet references and account help. If your request concerns a specific record, use the contact path above and avoid sending passwords or one-time codes.

The name666 Privacy Policy covers account details, phone verification, browser storage, lobby access records, payment references and messages sent through account help. It explains why we use those details, how we protect the account path, how long records may be kept and how you can request access or correction.

Phone verification helps connect an account request to the correct account and reduces the chance of another person changing its details. We do not need your DANA, OVO or GoPay password for this step. Keep verification codes private and contact account help if access stalls.

Yes. The Privacy Policy covers DANA and QRIS references used to check a receipt or payment status connected to your account. OVO, GoPay, bank transfer and virtual account references can serve the same matching purpose. We ask you to share the reference, not a wallet password.

You can ask account help for the personal details linked to your name666 account. Include the verified phone number and describe the records you want checked. We may complete an account check before responding, and the response path can depend on local law and the nature of the request.

Send a correction request through account help with the field you believe is wrong and the verified phone number connected to your account. We compare the request with account records before making a change. If a correction cannot be made, we explain the reason and any local-law limit.

Yes. The Privacy Policy applies when you use a mobile browser to sign in, complete phone verification, open the lobby or contact account help. Browser storage may keep the access path working. Clearing it can sign you out and may require verification again on your next visit.

You can request deletion through account help and state which account details you want reviewed. We first verify the request and then check whether records are still needed for access, payment status, security or a valid legal requirement. Any restriction depends on local law and is explained to you.