Reference

naga138 Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account data explainedWallet records identifiedYour contact path
naga138 naga138 Privacy Policy For Your Account
CONTACT ROUTES

Get Help With Privacy Requests

A clear contact route matters when you want to ask about your personal data rather than a game or wallet balance. Use the support path attached to your account and include the phone number on the account, the subject of your request, and any relevant payment reference. We use those details to locate the right record without asking you to send a password or full wallet credentials.

Team online

Account data request

Ask us to confirm the personal data connected with your naga138 account. Include your registered phone number and we will use an account check before discussing records.

Wallet record question

For a DANA, OVO, GoPay or QRIS record, share the transaction reference and approximate date. We compare it with the account ledger while keeping wallet credentials out of the request.

Privacy contact path

When you need a correction, deletion request or clarification, use the account support route and state the exact change. We may request verification before altering a personal record.

HANDLING DETAILS

How We Manage Your Account Data

We handle account data in practical stages: collect only what helps us provide access or resolve a record, restrict internal access, and retain it for a defined operational or legal reason.

Account security

Before we discuss account records or change key details, we may compare your phone verification with the account profile. Never send us your password, wallet PIN or one-time code.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can be stored beside an account identifier. This lets us trace a receipt without retaining unnecessary wallet login details.

Device records

When you move from a mobile login to the lobby, we may record browser type, device signals and session time. These details support sign-in checks and help us investigate access problems.

Cookie choices

Cookies can remember a session preference and help us understand which policy pages load correctly. You can manage cookies through your browser settings, although some account functions may then need another sign-in.

Retention practice

We retain personal records while they serve account support, payment matching, security checks or a legal dispute. When a record no longer has one of those purposes, we assess it for removal.

Requesting changes

You can ask us to correct account data, explain a record, or consider deletion through support. We verify the requester first and may keep a limited transaction trace where a legal or dispute need remains.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions we expect you to ask before opening access from Indonesia. We keep the wording practical: what we collect, why a payment reference appears, how cookies work, and what to include when you contact us. If a request concerns eligibility or service access, the outcome depends on local law.

It covers account details, phone verification, device and browser records, cookies, lobby activity, payment references and support requests. It also explains retention, security checks and how you can ask about or correct your data.

We record a payment reference to match a DANA, OVO, GoPay or QRIS receipt with the correct account and investigate a pending status. We do not need your wallet PIN or sign-in code for that check.

Yes. Use the account support route, provide your registered phone number and request a data copy or explanation. We verify your identity before discussing personal records so another person cannot obtain them.

When you sign in on a phone, we may record browser type, device signals and session timing. These records help us identify unusual access and diagnose a failed lobby or account session.

You can request a correction or ask us to assess deletion through support. We first verify the account holder, then consider operational, payment, security and legal reasons for retaining a limited record.

Cookies can retain session preferences and help us see whether the Privacy Policy page loads properly. Browser controls let you manage them, but turning cookies off may require repeated sign-ins or affect account access.

The data practices described here apply to the account records we handle, while service access and eligibility depend on local law. If you are in Semarang or Makassar, check the current access position before continuing.