Reference

nusa188 Privacy Policy for Your Account

Our Privacy Policy explains how nusa188 handles the account, wallet and device data connected with your access.

Account dataWallet recordsDevice securityPolicy requests

Open Privacy Policy Before Wallet Access

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

This Privacy Policy covers data you provide during account creation, including your contact details and phone verification status, plus records created when you use account services. A DANA, OVO, GoPay or QRIS transaction can create a reference, amount, time and status record so we can match

1
a wallet event to your account. Bank transfer and virtual account records may include the selected rail, reference number and confirmation result. We also receive technical details such as device type, browser settings, IP address and session events when you sign in. We use these details
2
for account access, security checks, support responses and legal duties where local law permits. The policy applies to nusa188 services reached through supported web browsers, and the current policy page is the place to check changes before you continue.

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

REQUEST HELP

Check Privacy Support Through Your Account

A clear request path matters when a wallet record or login detail looks unfamiliar. Use the support route linked from your account area and state that your request concerns the Privacy Policy; include the relevant date, device path and transaction reference, but do not send a full password or wallet PIN. We use the details you provide to locate the right record and respond to your request.

Team online

Account access route

If phone verification or a sign-in record needs checking, open the account support route and identify the email or phone detail attached to your account.

Wallet record request

For DANA, OVO, GoPay, QRIS or bank transfer data, share the transaction date and reference so we can check the stored status without requesting your wallet PIN.

Privacy change path

Ask through the policy request path when you want to correct account data, ask about retention or understand which device details are connected with your access.

HANDLING YOUR DATA

Browse How nusa188 Handles Account Details

We keep the Privacy Policy practical by linking each data use to an account task. Phone verification helps confirm access, device signals help detect unusual sessions and payment references help reconcile wallet…

Account collection

We collect details you enter during account creation and phone verification, along with sign-in events needed to maintain access and connect a request to the correct account.

Cookie use

Cookies and similar browser storage can keep your session active, remember basic preferences and help us identify repeated access from the same device path.

Device signals

Our records may include device type, browser details, IP address and session timing. These signals help us examine unusual access without collecting your wallet PIN.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference lets us compare a wallet event with the account record and answer status questions.

Retention approach

We retain account, security and transaction records only as long as needed for the stated service purpose, dispute handling, security checks or duties required where local law permits.

Your contact rights

You can ask us to explain, correct or review personal data connected with your account. Send the request through support with enough detail to locate the record.

Find Answers About Privacy Policy

These Privacy Policy answers address the searches we hear most often before account access. They cover phone checks, wallet records, cookies, device data, retention and the route for correction requests, so you can decide what to share before continuing.

It covers account details, phone verification, device and session data, cookies, payment references, support requests, retention and the ways we use those records for access and security.

Yes. The Privacy Policy includes references linked with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity, such as status, time and matching details.

Phone verification helps connect account access with the correct account and supports security checks. We record its status rather than asking you to share a phone password or wallet PIN.

The policy can cover device type, browser details, IP address and session timing. We use these signals to understand access events and investigate activity that does not match your usual device path.

Use the account support route and say that your request concerns the Privacy Policy. Include the affected account detail and a useful date or reference, while leaving out passwords and wallet PINs.

Retention depends on the type of record and its purpose. Account, security and transaction details may remain while needed for service operations, disputes, security checks or duties where local law permits.

Yes. Ask through the privacy request path for details about cookies or browser storage connected with your access. These tools can support sessions, basic preferences and device-based security checks.

nusa188 Privacy Policy for Your Account

Check Privacy Support Through Your Account

Account access route

Wallet record request

Privacy change path

Browse How nusa188 Handles Account Details

Account collection

Cookie use

Device signals

Payment matching

Retention approach

Your contact rights

Find Answers About Privacy Policy

01 What does the nusa188 Privacy Policy cover?

02 Does the Privacy Policy include DANA and QRIS records?

03 Why does nusa188 need phone verification data?

04 What device data is covered by the Privacy Policy?

05 How do I request a correction to my account data?

06 How long does nusa188 keep personal data?

07 Can I ask what cookies nusa188 uses?

Related Pages