Reference

naga5000 Privacy Policy for Your Account

naga5000 Privacy Policy explains how we collect account details, phone verification records and payment references when you use DANA, OVO, GoPay, QRIS or bank transfer.

Account dataWallet recordsCookie choicesSecurity checks

Explore Our Lobby Read FAQ

Open the Policy Before Account Access

naga5000 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy applies when you create an account, complete phone verification, sign in, contact support or use payment routes connected with the lobby. We may handle your account identifier, contact details, device signals, login events, wallet status and transaction references so we can provide the

1
requested service and investigate unusual activity. DANA, OVO, GoPay and QRIS may return confirmation or reference data; bank transfer and virtual account records can include the sending bank and reconciliation reference. We use this material for account administration, security, support and legal duties. Access to naga5000
2
and related processing depends on local law. Please read the current policy before opening an account, and contact us if a section is unclear.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Browse Help for Privacy Requests

Privacy questions should reach the same account path that handles login and wallet status, so we can connect your request with the correct record. Include your account identifier, the email or phone number linked to it, and a short description of the change you want. Never send a password, one-time code or full payment credential in a support message.

Team online

Account help

Use the signed-in account help route for access, correction or deletion requests. We may ask you to complete a phone verification step before discussing personal records.

Payment records

For a DANA, OVO, GoPay, QRIS or bank transfer query, provide the payment date and reference only. We use those details to locate the relevant wallet or reconciliation record.

Security concern

If you suspect an unfamiliar login, contact account support promptly and describe the device or time shown. We can check login events and guide the next account-security step.

HANDLING PRACTICES

Explore How We Handle Your Data

We separate ordinary account administration from security checks and payment reconciliation, using each data type for a defined operational reason.

Account creation

When you open an account, we collect the details needed to create your profile and send account notices. Phone verification helps connect access requests with the correct account.

Device signals

Login time, browser type and device signals can help us identify unusual access. These checks support account protection and are not used to read unrelated content on your device.

Cookie controls

Cookies may preserve a session, language choice or page setting. You can remove or restrict them in your browser, while necessary session controls may stop working as expected.

Wallet matching

Payment references help match a DANA, OVO, GoPay, QRIS, virtual account or bank transfer event with your account. We do not need your wallet password for this check.

Retention period

We keep account, support and transaction records for the period needed for service continuity, fraud checks, disputes and applicable legal duties, then remove or anonymise them when appropriate.

Your request

You may ask us to access, correct or remove eligible personal data through account support. We verify the requester first and explain if a record must remain for a legal or security reason.

Check Common Privacy Policy Questions

These answers address the privacy searches we hear most often before an account is opened. If your situation involves a particular wallet reference, device event or account change, use the support route above and we will match the request to the relevant record.

It covers data used for account creation, phone verification, login security, cookie operation, support, wallet reconciliation and legal record keeping when you access the service where local law permits.

We may collect your account details, contact information, phone verification result, login events, device signals, support messages and payment references connected with DANA, OVO, GoPay, QRIS or bank transfer.

Phone verification helps us connect an access request with the correct account and identify unusual login activity. It can also be required before we discuss a personal data request.

Yes. The Privacy Policy covers cookies and similar session controls used on mobile browsers and desktop browsers. You can manage them in device or browser settings, though some account functions may change.

You can ask for access or correction through account support. Include your account identifier, complete the requested identity check and specify the record. We will explain any lawful reason for retaining or limiting data.

Retention depends on the purpose and applicable legal duties. DANA, OVO, GoPay, QRIS, virtual account and bank transfer references may remain for reconciliation, security, disputes and required records.

Contact account support promptly through the signed-in help route, describe the date, device or payment reference and avoid sending passwords or one-time codes. We can check the related security or wallet record.

naga5000 Privacy Policy for Your Account

Browse Help for Privacy Requests

Account help

Payment records

Security concern

Explore How We Handle Your Data

Account creation

Device signals

Cookie controls

Wallet matching

Retention period

Your request

Check Common Privacy Policy Questions

01 What does the naga5000 Privacy Policy cover?

02 What personal data does naga5000 collect?

03 Why is phone verification needed for account access?

04 Does the Privacy Policy cover cookies on mobile?

05 Can I request a copy or correction of my data?

06 How long does naga5000 keep payment records?

07 How do I report an unfamiliar login or wallet event?

Related Pages