Reference

nasa4d Privacy Policy for Your Account

Our nasa4d Privacy Policy explains how we handle your account details, phone verification, device signals and wallet records connected with DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record handlingRequest access or changesCookie choices

Explore Our Lobby Read FAQ

Open the Privacy Policy Before Account Access

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

This Privacy Policy covers data we receive when you create an account, complete phone verification, sign in, browse casino rooms such as Sic Bo or Fish Hunter, and use wallet steps linked to DANA, OVO, GoPay or QRIS. We may record account identifiers, transaction references, device

1
and browser details, security events, support messages and preference choices so we can provide account access, check wallet status and investigate unusual activity. We do not treat every data point as permanent: retention depends on its purpose, account status, security needs and applicable legal duties. Where
2
access or eligibility is discussed, it depends on local law. If a payment partner or bank transfer is involved, that provider may handle certain details under its own policy. Read this page together with any notice shown during registration or payment, then contact us before opening
3
an account if a point is unclear.

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

REQUEST HELP

Browse Support Paths for Privacy Questions

A privacy question should not leave you guessing about the next step. We keep the account-help route close to wallet and verification support so you can…

DATA CONTROL

Explore How We Handle Your Account Data

Our privacy process follows the actual account journey rather than treating every record the same way. Registration, phone verification, sign-in, wallet status and support contact can each create different data points.

Data we collect

We may receive your account name, phone contact, verification result, sign-in events, device details, wallet references and support messages. The exact fields depend on the step you take.

Why we use it

We use account and verification details to provide sign-in, match wallet status, protect the account and respond to privacy requests. We do not collect data without a stated operational purpose.

Cookies and devices

Cookies and similar device signals can keep a session working, remember selected settings and help detect unusual access. You can manage browser cookie controls, though some account steps may then work differently.

Account security

Phone verification, sign-in records and device checks help us identify unusual account access. Never share your password, wallet PIN or one-time code when asking us about privacy.

Retention choices

We keep records only for the period needed for the stated purpose, account security, dispute handling or applicable legal duties. When a record is no longer needed, we remove or de-identify it where practical.

Changes and contact

You can request access, correction or deletion through the available account-help contact route. We may verify ownership first and explain any limit where security or local law affects the request.

Check Privacy Policy Answers Before Joining

These Privacy Policy answers address the questions we expect you to ask before opening an account from Indonesia. They cover the records created by registration, phone verification, DANA or QRIS activity, cookies, account access and requests to change stored details. If your situation is not listed, use the privacy contact route rather than sharing sensitive credentials in a message.

It covers account registration, phone verification, sign-in events, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account steps.

Yes. The Privacy Policy explains that we may keep payment references, status details and timing linked with DANA or QRIS. The payment provider may separately handle data under its own policy.

Use the available privacy contact route from your signed-in account and identify the records you want. We may verify account ownership before sending a copy or describing the stored details.

You can ask us to correct inaccurate account details through the account-help route. We may require phone verification or another ownership check before changing information connected with sign-in or wallet status.

Cookies can support session continuity, saved settings and security checks. Your browser controls can restrict them, but the Privacy Policy explains that some sign-in or account functions may behave differently.

Retention varies by purpose. We consider account status, security needs, disputes and applicable legal duties, then remove or de-identify records when they are no longer needed where practical.

You can submit a deletion request through the available privacy contact route. We assess ownership, security needs and local legal duties, so some records may need to remain for a stated reason.

nasa4d Privacy Policy for Your Account

Browse Support Paths for Privacy Questions

Explore How We Handle Your Account Data

Data we collect

Why we use it

Cookies and devices

Account security

Retention choices

Changes and contact

Check Privacy Policy Answers Before Joining

01 What does the nasa4d Privacy Policy cover?

02 Does the Privacy Policy explain DANA and QRIS data?

03 How can I request my nasa4d account data?

04 Can I correct my phone or account details?

05 How does the Privacy Policy handle cookies?

06 How long does nasa4d retain account records?

07 Can I ask for deletion under this Privacy Policy?

Related Pages