Reference

nemo4d Privacy Policy, Made Clear

nemo4d Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests

Browse Our Lobby Read FAQ

Know What Your Account Shares

nemo4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy separates account details from activity records so you can understand why each type is handled. When you create an account, we may receive your phone number, sign-in details and verification information needed to protect access. We record payment references from DANA, OVO, GoPay,

1
QRIS, bank transfer or virtual account steps, but we do not ask you to send a wallet password through support. Device data can include browser type, operating system, IP address and sign-in time. We use it to detect unusual access, keep sessions working and connect your
2
request to the right account. Game activity such as Blackjack, Bingo or Fish Hunter may appear in account records when needed for service checks. Access and eligibility depends on local law. This policy explains storage, sharing, cookies, retention and the ways you can ask us to
3
correct or remove eligible details.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH PRIVACY

Get Answers Through Your Account Path

A clear contact route helps when you need a copy of your data or want to question a wallet record.

Data access request Ask us what account, device and payment-reference details we hold by sending a request through your account support path. We may ask for verification before releasing records.

Correction request If your phone number or account detail is wrong, tell us which field needs changing. We compare the request with your verified account step before applying an update.

Wallet record query For a DANA, OVO, GoPay or QRIS status concern, include the transaction reference and date. We use the payment trail to check the record without requesting your wallet PIN.

HOW WE HANDLE DATA

Privacy Choices That Follow Your Login

Privacy controls should fit the way you actually use an account. We keep the policy linked from the account access area so you can check it before entering the lobby or connecting…

Account protection

We use phone verification before account access and may compare sign-in device details with earlier sessions. This helps us identify unusual entry without asking you to share your password.

Cookie controls

Cookies can remember your session and selected settings on a mobile browser or desktop. You can adjust browser permissions, though blocking required cookies may interrupt account access.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a cashier event to your account. Wallet PINs and banking passwords should never be sent to us.

Retention periods

We retain account, security and transaction records only for the period needed for service operation, dispute handling, fraud checks or legal duties. Deletion timing can differ by record type.

Correction requests

You can ask us to correct inaccurate profile details through the account support route. Include the affected field and verified phone number so we can confirm the request belongs to you.

Policy contact

Questions about this Privacy Policy can be sent through support with the subject and account phone number. We may request identity proof before discussing personal records.

Privacy Policy Answers Before Access

These Privacy Policy answers cover the questions we expect before an account is opened or a wallet is connected. They explain the data path in plain terms, while the full policy remains the place to check the current wording for your account and region. If your request concerns a specific record, include its date and reference where available.

It covers account details, phone verification, device signals, cookies, game activity records, payment references and support requests connected with your use of nemo4d. Access depends on local law.

We use the phone number to create and verify your account, help protect sign-in and connect support requests to the correct profile. Keep it current so account checks can be completed.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay and QRIS, plus bank transfer and virtual account steps. We use these records to match payment status to your account.

You can request access through the account support path. State the records you want, add your verified phone number and complete any identity check required before we disclose personal details.

Send a correction request through support and identify the inaccurate field, such as your phone number or profile detail. We compare the request with your verified account before making a change.

We may record browser type, operating system, IP address, session time and similar access signals. These details help keep login sessions secure and investigate unusual account entry.

Use the account support route and mention cookies or retention in your request. We can explain the relevant record category, while browser settings let you manage optional cookie activity.

nemo4d Privacy Policy, Made Clear

Get Answers Through Your Account Path

Privacy Choices That Follow Your Login

Account protection

Cookie controls

Payment matching

Retention periods

Correction requests

Policy contact

Privacy Policy Answers Before Access

01 What does the nemo4d Privacy Policy cover?

02 Why does nemo4d need my phone number?

03 Does the Privacy Policy cover DANA and QRIS records?

04 Can I ask nemo4d for my stored account data?

05 How do I correct details under this Privacy Policy?

06 What device details can nemo4d collect?

07 How can I ask about cookies or retention?

Related Pages