Reference

Open the nego777 Privacy Policy

The nego777 Privacy Policy explains how we handle your account details, phone verification, wallet records and device access from registration onward.

Account clarityWallet recordsPolicy access
nego777 Open the nego777 Privacy Policy
HELP WHEN NEEDED

Browse clear routes for privacy help

Privacy questions should have a practical route, especially when a phone verification step or wallet receipt needs checking. We keep account help close to the cashier path so you can identify the relevant transaction or access event before contacting us. Include your registered contact detail, the approximate time, and the payment rail involved; do not send a password or one-time security code. Our support team can explain which record is being checked, what request details are needed, and how a policy change request proceeds where local law permits.

Team online

Account request

Use the account help path when you want to ask what contact, verification or access records we hold. We can match your request to the registered account without asking you to disclose a password or one-time code.

Wallet record

For a DANA, OVO, GoPay or QRIS privacy query, include the receipt reference and payment status shown in your cashier history. We use those details to locate the relevant record without requesting unnecessary wallet credentials.

Policy change

Ask us to correct or clarify a personal detail through the same account support route. Describe the requested change and its reason; we may need an account step to confirm that the request comes from you.

DATA PRACTICE

Switch through our privacy controls

We handle privacy as an account process rather than a generic statement. Our records show how information enters through registration, phone verification, wallet activity or device access, while policy requests are connected…

Account details

We collect details needed to create and maintain your account, including contact information used for phone verification. If a detail changes, contact us through the account route so we can assess the correction against the relevant account record.

Payment history

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account action can create a payment record with status and receipt references. We use that information to resolve the specific transaction and do not ask for your wallet password.

Device signals

When you move from login to the lobby on a phone or desktop, technical signals such as browser or device details may support security checks. They help us examine unusual access without treating the device as your identity by itself.

Cookies

Cookies can help keep an account session working and help us understand whether a privacy notice has been shown. Your browser settings can control cookies, although changing them may affect account access or the way policy pages load.

Security steps

Phone verification is completed before account access, and we ask you to protect passwords and one-time codes. If an access event looks unfamiliar, contact account support with timing and device context rather than sharing security credentials.

Retention requests

We assess deletion, access and correction requests against the purpose of the record and any period that must remain. Send the request through account support, and we will explain the next step and any applicable limit where local law permits.

Ask about the nego777 Privacy Policy

These answers focus on the questions you may have before opening an account or checking a wallet record. The Privacy Policy explains how we connect registration, phone verification, device access and payment references without turning a privacy request into a request for your password. If your situation is specific, use the account support path with only the details needed to identify the issue.

It covers account details, phone verification, device and browser signals, cookies, payment records and requests concerning access, correction or retention. It applies to activity connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account records where local law permits.

We use payment status, receipt references and related account details to identify a transaction, check a stalled wallet status or respond to a privacy request. We do not need your wallet password or one-time code to examine a DANA, OVO, GoPay or QRIS record.

Yes. Send the requested correction through account support and describe the detail that needs changing. We may ask for an account verification step before making the change, because the request must be linked to the correct registered account.

Use the account support route and state that you want to know which personal records are held about your account. Include your registered contact detail and enough context to locate the account, but never include your password or one-time security code.

Yes. It explains that cookies may support an account session and record whether a privacy notice has been shown when you use a phone or desktop. Browser settings can restrict cookies, though account access or page behaviour may change as a result.

We retain records for the stated operational purpose or for a period required by applicable law. A request about retention is assessed against the record type, such as phone verification or a QRIS receipt, and we explain any reason the record must remain.

Use the account support path and identify the policy topic, such as cookies, device access, payment history or correction. Add the approximate time and relevant payment rail if needed. We will explain the request process and applicable position where local law permits.