Reference

power666 Privacy Policy For Indonesia

power666 Privacy Policy explains how we collect, use and protect the details you provide when opening an account, signing in or contacting support.

Clear data purposesWallet record controlsSupport request path
power666 power666 Privacy Policy For Indonesia
CONTACT THE TEAM

Privacy Help Beside Your Account Path

A direct privacy request helps us identify the correct record without making you repeat your account history.

Account privacy request Ask us to explain how a specific account detail is used or stored. Include your registered contact detail and the subject of your Privacy Policy question so we can locate the relevant record without requesting unnecessary personal data.
Wallet record check If a DANA, OVO, GoPay or QRIS reference appears unclear, send the transaction reference through the account support path. We compare the record with your account activity and explain what status data we hold for that payment event.
Access and correction You can ask us to correct an account detail that no longer matches your records. We may request an account step before making a change, because confirming the requester protects your sign-in and prevents another person from altering the profile.
DATA HANDLING

Inside power666 Privacy Controls

We keep this Privacy Policy practical by linking each data use to an account action, security need or support request.

Account details

We use the contact and profile details you enter to create your account, confirm an account step and respond to requests. Clear details help us match a privacy question with the correct record without combining it with another account.

Cookies and sessions

Necessary cookies can keep your selected settings and sign-in session working as you move between the lobby and account pages. You can manage browser cookie controls, though disabling necessary cookies may interrupt access to account or wallet status screens.

Device signals

We may record browser, device and sign-in signals to protect your session and investigate unusual access. On mobile, these details help us understand a failed path from login to the lobby without reading unrelated content stored on your device.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account actions can create references showing the selected rail and processing status. We use those references to reconcile an account event, respond to a receipt question and maintain an accurate transaction record.

Retention decisions

We retain personal data only for the period connected to its stated purpose, account security, dispute handling or a lawful operational need. When a record is no longer needed for those reasons, our handling follows the deletion or restriction process available for that data.

Your requests

You may contact us to ask about access, correction, deletion, restriction or the purpose of a data use. We confirm the requester's account connection before responding, then explain any limit that depends on local law or an active security requirement.

Privacy Policy Answers For power666

These Privacy Policy answers address the account questions we expect when you check power666 before opening an account. They explain the data connected with sign-in, local wallets, device access and support. If your situation is not covered, send a focused request through the account support path and we will identify the relevant record.

The Privacy Policy covers details you submit for an account, sign-in and support, plus device signals, cookies and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains purposes, retention and request options where local law permits.

We store the transaction details needed to match a DANA or QRIS action with your account, such as a reference and processing status. We do not need unrelated wallet content for that purpose. The same approach applies to OVO, GoPay and other listed payment rails.

Use the support path available after sign-in and state that you are making a Privacy Policy data request. Include your registered contact detail and the record or purpose you want checked. We may confirm an account step before sharing information connected with your profile.

Yes, you can ask us to correct an account detail that is inaccurate or outdated. Send the request through account support and identify the field clearly. We confirm your connection to the account before changing it, which protects your profile from an unauthorised edit.

Device and sign-in details help us protect your session, investigate unusual access and diagnose a failed mobile path from login to the lobby. We use these signals for those operational reasons rather than to inspect unrelated device content. Access remains subject to local law.

We keep payment references for the period needed to reconcile an account event, answer a status or receipt question, handle a dispute or meet a lawful operational need. When that purpose ends, the record follows our deletion or restriction process under the Privacy Policy.

You can request deletion or restriction through the account support path. We review which records can be removed and explain any data that must remain for account security, dispute handling or another lawful need. The outcome depends on local law and the purpose attached to each record.