Reference

nex55 Privacy Policy For Your Account

nex55 Privacy Policy explains how we collect, use and protect the details connected to your account, including phone verification, device access and wallet records.

Account clarityWallet record careClear contact routeDevice-aware security
nex55 nex55 Privacy Policy For Your Account
CONTACT YOUR WAY

Get Privacy Help Near Account Access

A direct support path helps when you need a Privacy Policy answer rather than a general account reply. Tell us which account step or wallet record concerns you, and include only the details needed to locate it. We can help you understand a phone verification request, a QRIS status reference or a device sign-in question without asking you to send a password. Use the support route shown on nex55 while access depends on local law.

Team online

Policy questions

Ask our support desk how the Privacy Policy applies to your account details, phone verification or device sign-in. Include your registered contact and a short description, but never send your password or a full wallet PIN.

Wallet records

For a DANA, OVO, GoPay or QRIS record, share the transaction reference and displayed status through the account support path. We use that reference to find the relevant entry without requesting unnecessary payment credentials.

Access concerns

If a login check appears after a device change, tell us the device type and approximate time. We can explain the security reason and the next account step while keeping your sign-in secret private.

DATA HANDLING

What We Keep And Why It Matters

Privacy Policy choices are easier to assess when each data use has a clear reason. We separate account setup, wallet matching, security checks and policy requests instead of treating every record as…

Account setup

We use the details you enter during account creation to establish your profile and complete the clear phone verification step before account access. This helps us connect future sign-ins and wallet references to the correct account.

Payment matching

When you use QRIS, DANA, OVO or GoPay, we keep the payment reference and status needed to match the account record. Bank transfer and virtual account entries follow the same matching purpose, not an open-ended collection.

Cookie controls

Cookies and similar browser signals can remember session choices and help us spot an unusual sign-in. You can manage browser cookie settings, although turning them off may interrupt the account path or require another verification step.

Security checks

A change from mobile browser to desktop, a new device, or repeated failed sign-ins can trigger an extra check. We use those signals to protect access and do not need your password to explain why a check appeared.

Retention purpose

We retain account, payment and support records only for the period needed for account operation, dispute handling, security work or applicable legal duties. When a record is no longer needed for those purposes, our process addresses its removal or restriction.

Change requests

To ask for correction, access, restriction or removal of personal details, contact support through the account path. State the request clearly, and we may verify ownership before changing a phone detail or releasing account-linked records.

Privacy Policy Answers For nex55

These Privacy Policy answers address the searches we expect before an account is opened. They cover the records created by local wallets, the device path used for access and the practical steps for making a data request. If your question concerns a specific transaction or sign-in, use the support path with its reference rather than sending sensitive credentials.

The nex55 Privacy Policy covers account details, phone verification, device and browser signals, cookies, payment references, support requests and retention. It explains why we use each category for access, wallet matching, security, dispute handling or applicable legal duties.

Yes. Privacy Policy covers the reference, amount and status connected with DANA, OVO, GoPay and QRIS activity, along with bank transfer and virtual account records. We use those details to match a payment and answer a status question without requesting your wallet PIN.

Phone verification is an account security step before access. It helps connect the person signing in with the correct account and can reduce confusion after a device change. The Privacy Policy describes this use, while your verification code and password should remain private.

Contact our support desk through the account support path and state whether you want access to, correction of, restriction on or removal of a personal detail. We may confirm account ownership first, then assess the request under applicable rules and the Privacy Policy.

We keep account, payment and support records for the period needed to operate the account, resolve disputes, protect access or meet applicable legal duties. The Privacy Policy does not treat every record alike, and records no longer needed are addressed through our retention process.

You can adjust cookie settings in your browser. Some session functions may stop working or ask for another sign-in check when cookies are disabled. The Privacy Policy explains that cookies support session continuity and security signals, not that they replace your account choices.

Access and eligibility depends on local law, including the rules applicable to your location. Our Privacy Policy applies where local law permits, but a request may require additional checks when Indonesian legal requirements or payment-record duties affect the account.