Reference

Privacy Policy For Your nuansa4d Account

nuansa4d Privacy Policy shows how we collect, use and protect the account details connected with your lobby access, DANA, OVO, GoPay and QRIS activity.

Account dataWallet recordsCookie choicesAccess requests
nuansa4d Privacy Policy For Your nuansa4d Account
CONTACT ROUTES

Where To Ask About Privacy Policy

A clear support route helps when you want to ask about a record, correct an account detail or understand a wallet status entry.

Account support path Use the signed-in support route for a Privacy Policy question, correction request or access request. Include your account phone number and the relevant date so we can identify the right record without requesting your password.
Wallet record check For DANA, OVO, GoPay or QRIS entries, send the transaction reference shown beside the wallet status. We compare that reference with the account record before discussing a deposit or withdrawal detail.
Security concern If a sign-in or device record looks unfamiliar, contact support through your account as soon as you can. We may ask you to complete phone verification before changing access details or discussing stored account data.
DATA HANDLING

What We Keep And Why

We keep this policy practical: each data category has a service reason, a security reason or a legal reason.

Account details

We use your account name, phone contact and verification status to connect the correct person with the correct sign-in. Before changing access details, we may ask you to repeat the phone verification step.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can produce reference numbers and status records. We use them to reconcile your request, investigate a mismatch and respond to a privacy question.

Device signals

Your browser, device type and session timing may be recorded when you sign in from mobile or desktop. These signals help us identify unusual account access without treating a device signal as your password.

Cookie choices

Cookies can keep a session active, remember a language or privacy choice and help a page load as expected. You can manage browser cookie settings, although removing some cookies may affect the account access path.

Retention process

We retain each category only while it supports account service, security checks, dispute handling or a legal requirement. When a record no longer needs that purpose, our handling follows the applicable retention process.

Change requests

You can ask us to correct account data, explain a stored record or provide a copy where local law permits. Send the request through account support and identify the phone contact tied to your account.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the requests we expect when you are deciding whether to open an account or checking an existing record. We keep the route tied to your account so a request about a QRIS entry, mobile sign-in or game history reaches the correct data set. Access and eligibility depends on local law, and we will explain the next step where local law permits.

The nuansa4d Privacy Policy covers account details, phone verification, sign-in records, device signals, cookies, support requests and payment references. It also explains how activity connected with titles such as Limbo Quick Arena may be handled for account service, security or legal duties.

We use your phone number to create and protect the account, complete the clear phone verification step and connect support requests with the correct record. If you ask for a data change, we may use that contact to confirm that the request is yours.

Yes. The Privacy Policy covers references and status details created when you use DANA or QRIS, along with OVO, GoPay, bank transfer and virtual account routes. We use these records to reconcile account activity and respond to a specific transaction question.

You can request access to the data connected with your account through the signed-in support path. Include your account phone contact and the categories you want checked. We assess the request under applicable requirements and respond where local law permits.

Cookies may remember a session, language selection or privacy choice when you move between account pages on mobile or desktop. You can adjust them in your browser. Removing necessary cookies may interrupt sign-in or require you to repeat an account step.

Retention varies by category and purpose. We may keep account, security, wallet and support records while they are needed for account service, dispute handling, security checks or legal duties. A specific retention request can be sent through account support.

Contact us through the account support route and identify the record, such as a QRIS reference, device entry or phone detail. We may request phone verification before making a correction, then assess the change where local law permits.