Reference

Privacy Policy for Your nix4d Account

Our Privacy Policy explains how nix4d handles the account, device and wallet details you provide when you open the lobby from Indonesia, including from Surabaya.

Account clarityWallet dataDevice controlsPolicy requests
nix4d Privacy Policy for Your nix4d Account
ACCOUNT HELP ROUTE

Get Privacy Policy Help Beside Your Account

A clear support path matters when a Privacy Policy question concerns your own record. Sign in first when possible, open the account support area, and include the phone number or transaction reference…

Policy questions Use the support area inside your signed-in account to ask how a data field is collected, used or retained. Include the page or account step involved so we can respond to the Privacy Policy question without exposing unrelated details.
Wallet records For DANA, OVO, GoPay, QRIS, bank transfer or virtual account concerns, attach the transaction reference rather than a password. We check the payment status against your account record and explain what information the check requires.
Access concerns If phone verification or a device sign-in raises a privacy concern, tell us which device path you used and when it happened. We can focus the response on account security, stored device signals and the requested correction.
HANDLING YOUR RECORD

What nix4d Does With Your Account Data

We keep this Privacy Policy practical by linking each category of information to an operating need. Account details support phone verification and sign-in; payment references help reconcile DANA, QRIS and bank activity…

Data collection

We collect details you enter during account opening, including contact information used for phone verification. We also receive activity records created when you sign in, select a wallet rail or request help with a payment status.

Cookies and devices

Cookies help keep the website session working, remember necessary preferences and identify a repeated sign-in path. Device signals can support security checks. You can manage browser cookie settings, though some account steps may then require another check.

Account security

Phone verification, sign-in records and device checks help us distinguish your account activity from an unfamiliar attempt. We do not ask for your DANA, OVO, GoPay or bank password through the account support area.

Payment matching

A wallet or bank reference lets us match a payment status to the correct account. For QRIS, virtual account and bank transfer records, we use the reference and status needed to investigate an incomplete or unmatched transaction.

Retention choices

We retain account and transaction records for as long as needed for the purpose described in this Privacy Policy, including security checks and unresolved support matters. When a record is no longer needed, our handling follows applicable retention requirements.

Request changes

Ask us to correct an inaccurate account detail or explain a data use through the signed-in support area. Include the affected field and your phone verification context; we may need to confirm account control before changing the record.

Privacy Policy Answers for Indonesia Accounts

These Privacy Policy answers focus on the questions we expect you to ask before opening or using an account from Indonesia. They cover the records created by phone verification, device access and local payment status. If your question concerns a specific DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, use the signed-in support area and provide that reference. Where access or eligibility is discussed, it depends on local law.

The nix4d Privacy Policy covers information you enter for an account, phone verification details, device and sign-in records, cookies needed for the website session, payment references and support messages. It also explains why we use each category, how retention works and how you can request a correction.

No. Our Privacy Policy distinguishes payment status information from wallet credentials. We may receive a DANA or QRIS reference, status and account-linked details needed to match activity, but the account support area should never request your wallet password or bank password.

Phone verification connects the account to a contact detail you control and helps us respond to access questions safely. Under this Privacy Policy, the verification record can support sign-in checks and account recovery questions, while a failed or incomplete step may keep account access pending.

The Privacy Policy treats necessary cookies as session tools that help the website remember your sign-in path and required preferences. On a mobile browser, clearing cookies can remove that session and trigger phone or device checks again. Browser controls remain available to you.

Yes. Use the signed-in support area and identify the account field you believe is wrong, such as a phone detail or payment reference. We may confirm account control before making a change, then explain whether the correction affects an open support or payment check.

We retain payment records for the period needed for the stated purpose, such as matching a DANA, GoPay, bank transfer or virtual account status, resolving support questions and applying security checks. The applicable retention period can depend on legal and operational requirements.

Sign in and open the account support area, then state whether you want access to a data detail, a correction, an explanation of use or a retention question. Add the relevant device path or transaction reference, but do not send wallet passwords or bank credentials.