Reference

Privacy Policy For Your nix288 Account

nix288 keeps your Privacy Policy questions close to the account steps you use for DANA, OVO, GoPay and QRIS.

Clear data purposesPhone verificationCookie choicesRequest access
nix288 Privacy Policy For Your nix288 Account
HELP WHEN NEEDED

Privacy Policy Support Paths

A clear contact route matters when your account details or payment record needs attention.

Account access If phone verification blocks access, contact us through the account support path and describe…
Wallet record For a DANA, OVO, GoPay or QRIS record, share the payment rail, reference and…
Data request To ask about access, correction or removal, label your message as a Privacy Policy…
SIX CONTROL POINTS

What Your Privacy Policy Covers

We handle privacy through practical controls rather than broad promises. Account creation starts with a phone verification step, and sign-in records help us identify unusual device behaviour.

Collected details

We may collect your phone number, verification result, account settings, device signals and activity needed to operate your account.

Account security

Phone verification helps connect access to the correct account, while device and session signals can highlight unusual sign-in behaviour.

Cookie controls

Cookies can remember selected settings and help essential account pages function between visits.

Payment matching

A payment reference lets us connect a DANA Fast Transfer, QRIS or bank transaction to the account that initiated it.

Retention period

We keep personal and transaction records while they support account security, payment checks, dispute handling or a legal requirement.

Policy changes

If this Privacy Policy changes, we will update the policy page and identify the revised subject in clear language.

Privacy Policy Questions About nix288

These Privacy Policy answers focus on the searches we expect you to make before opening or using an account. They explain account data, wallet references, cookies, device checks and the route for asking us to inspect or change a record. If your question concerns eligibility, access depends on local law, and the support path can confirm what applies to your account.

The nix288 Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages and payment references. It explains why we use each category, how we protect account access, how long records may remain and how you can request access or correction.

We use your phone number for account creation and the verification step before account access. It helps us connect a sign-in attempt to the right account and investigate access problems. We do not need your password or wallet secret in a support message.

Yes. The Privacy Policy includes payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match a transaction, check a status or resolve a mismatch without treating the payment record as a public profile.

On mobile, cookies can keep selected settings and help account pages continue between visits. Your browser lets you remove or restrict them. Some restrictions may interrupt saved preferences or sign-in continuity, while the Privacy Policy request route remains available through your account support path.

You can request access or correction by using the support contact connected to your account and marking it as a Privacy Policy request. Include the record or date you mean. We may verify account ownership first, then explain what we can provide or amend.

We retain account and transaction records while they support security, payment matching, dispute handling or a legal requirement. After that need ends, we remove the record or reduce its identifying detail where practical. The period can depend on the type of record and local law.

Use the support route shown with your signed-in account and describe the Privacy Policy question, device and approximate time when relevant. Eligibility and access depend on local law. We can then confirm the applicable account path without asking you to send unnecessary private credentials.