Reference

nos4d Privacy Policy for Your Account Data

Our nos4d Privacy Policy explains what we collect when you create an account, verify your phone, use DANA or QRIS, and open the lobby from a mobile device.

Account dataWallet recordsDevice choicesPolicy requests
nos4d nos4d Privacy Policy for Your Account Data
CONTACT PATH

Privacy Help For Login And Wallet Questions

A clear contact path helps when you want to ask about your personal data rather than a game or wallet result. Start from the support route linked to your account or login screen, include the phone number or account detail used for verification, and describe the request plainly. We use that context to find the right record without asking you to send a full payment password.

Team online

Account access

If you cannot reach your account, use the support route shown at login and mention your verified phone detail. We can explain the identity check needed before discussing account data.

Wallet records

For a DANA, OVO, GoPay or QRIS data question, include the transaction reference and approximate date. We use those details to locate the relevant wallet record and avoid broad requests.

Data requests

To ask for a copy, correction or deletion review, contact us through the account support path. We may ask for a verification step so another person cannot request your data.

SIX DATA PRACTICES

Six Data Practices Behind Your Account

We apply this policy through ordinary account operations: phone verification before account access, device checks during login, wallet matching after a receipt arrives and controlled retention for records we still need.

Collection

We collect details you provide during account creation, such as your phone contact, plus technical data from the device and browser used to sign in or open the lobby.

Phone checks

Phone verification connects an account request to the person attempting access. We use the result to protect account data and may request the check again after unusual device activity.

Cookie use

Cookies can keep your login session available, remember basic page choices and help us identify technical faults. You can manage cookie settings through your browser on mobile or desktop.

Account security

Login events, device signals and wallet references help us identify access that does not match your account pattern. Never send your password or one-time code through a support message.

Retention

We retain account, payment and support records only while needed for account operation, dispute handling, legal duties or security checks. When no longer needed, records are removed or separated from active use.

Your request

You can ask what data we hold, request a correction, question its use or ask about removal through the account support path. We verify ownership before making a change.

Privacy Policy Questions Indonesian Accounts Ask

These Privacy Policy answers cover the practical searches we hear before an account is opened: payment records, device access, cookies, retention and changes to personal data. If your situation is not listed, use the support route connected to your login so we can check the correct account.

It covers account details, phone verification, login and device data, cookies, lobby activity, wallet references and support messages connected with your account, including access where local law permits.

Yes. We may retain payment references, status and receipt details from DANA, QRIS, OVO, GoPay, bank transfer or virtual account use so a wallet event can be matched correctly.

Phone verification helps connect the account to the person requesting access. It also gives us a practical check before we disclose account data or change details after an unusual login.

We may process device type, browser details, session events and technical signals used during login. This helps keep the account page working and identify access that does not match your normal pattern.

Cookies can preserve a login session, remember basic choices and help diagnose page errors. Your browser controls whether cookies remain, though changing them may affect account access or page settings.

Retention depends on why the record exists. We keep account, wallet and support data while needed for operation, disputes, legal duties or security checks, then remove it or separate it from active systems.

Use the support route connected to your account or login screen, state whether you want a copy, correction or removal, and provide the verified account detail needed to confirm ownership.