Reference

Privacy Policy For Your naga petir Account

The naga petir Privacy Policy shows how we handle the details connected with your account, including contact data, device signals and payment references from DANA, OVO, GoPay or…

Account dataCookie choicesWallet referencesRequest a change
Explore Our Lobby Read FAQ
naga petir Privacy Policy For Your naga petir Account
REQUEST SUPPORT

Get Privacy Help Beside Account Support

A clear contact route helps when you want to ask about personal data rather than a wallet status. Sign in and use the account support path shown near your cashier area, or send the request through the contact route displayed on naga petir. Include your registered phone number, the subject of your request and the relevant payment reference only when it helps us locate a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record. We may ask for an account step to confirm that the request comes from you.

Team online

Data access request

Ask us which account details we hold and why they are used. We may confirm your registered phone number and recent sign-in details before sending a response, so another person cannot obtain private account data through a simple name or payment reference.

Correction request

If your phone number, account name or contact detail is inaccurate, tell us what needs changing through the account support path. We compare the request with your account record before applying an update, including when the record is linked to a wallet status.

Deletion question

You can ask whether a particular detail may be removed. We assess the request against open account, security and payment records, then explain what can be deleted and what must remain for a stated operational or legal reason.

HANDLING YOUR DATA

How We Apply The Privacy Policy

We keep the policy practical by connecting each data use to an account action you can recognise.

Account details

We use the contact and identity details you provide to create, maintain and protect your account. Phone verification can be required before access, and we may use the registered number to match a support request with the correct account record.

Device signals

Browser type, device details, session timestamps and security events can help us detect an unusual login or repeated access attempt. These signals support account protection; they are not used as a substitute for your phone verification step.

Cookies

Cookies can keep your session active, remember selected settings and help us understand whether a page loads correctly. You can manage cookies through your browser settings, although removing them may affect sign-in continuity or the way the policy page displays.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may retain a reference, status and time rather than unnecessary wallet credentials. This lets support check a receipt or pending state while keeping the request tied to your account.

Security controls

We restrict account details to the operational people and systems that need them for access, support, payment matching or security checks. We may record failed sign-ins and verification events so we can investigate an account request without relying on an unverified message.

Retention and changes

We keep records only for as long as they support the stated account, security, payment or legal purpose. You can ask how a category is retained or request a correction through support; we explain any limit before making or declining a change.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the questions we expect before you open an account or ask about an existing one. They focus on account records, mobile access, cookies, local wallets and requests made through naga petir support. If your situation is not listed, send the specific question through the account contact route so we can check the relevant record.

You can read the current Privacy Policy on the /privacy-policy/ page before opening an account and whenever you need it later. We recommend checking this page after a policy update, especially if you use mobile access or connect DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

It covers details you submit for an account, phone verification records, sign-in timestamps, device and browser signals, support messages, cookie preferences and payment references. For wallet activity, the record may show a status or reference connected with DANA, OVO, GoPay or QRIS.

Phone verification helps us connect account access and privacy requests to the person who controls the registered number. It also gives support a practical ownership check when you ask about a login, a wallet status, a payment receipt or a change to account details.

Cookies can preserve a browser session, remember selected settings and help us identify loading or sign-in issues on your phone. You can adjust them in your browser. If you clear or block cookies, you may need to repeat the account access step.

Yes, you can ask what personal account data we hold and how it is used. Send the request through the account support route and include your registered phone number. We may verify ownership first, then explain the available data and any lawful restriction.

You can request a correction when an account detail is inaccurate, and you can ask whether a category may be removed. We check the request against account, security and payment needs. Some records may need to remain for a stated operational or legal purpose.

The policy describes our handling for accounts accessed in Indonesia, but account eligibility and some data duties depend on local law. If you are in Makassar or another Indonesian location, the same policy page applies while any access decision remains subject to local requirements.

Related Pages

naga petir Indonesia naga petir Casino Lightning Roulette About Us Account information