Reference

nau4d Privacy Policy For Your Account

DANA, OVO, GoPay and QRIS records are explained clearly in the nau4d Privacy Policy, alongside the account details used to open the casino, slots and sports areas.

Account dataWallet recordsCookie choicesPrivacy requests
nau4d nau4d Privacy Policy For Your Account
REQUEST HELP DIRECTLY

Privacy Help Beside Your Account Route

A clear support route matters when a privacy request concerns a login, wallet reference or phone number.

Account privacy request Use the support path attached to your account when you want to ask what…
Wallet record question Include the relevant DANA, OVO, GoPay or QRIS reference when your request concerns a…
Cookie and device query Tell us whether you used a mobile browser or desktop browser when asking about…
SIX DATA CONTROLS

Six Ways We Handle Privacy Requests

Privacy is handled through practical account steps rather than broad promises. We connect a request to the profile details you provide, check that the request concerns your account…

Data collected

We may handle your name, contact detail, phone verification result, account activity, payment references and technical signals such as browser…

Cookie choices

Cookies and similar storage can help keep an account session active and remember selected settings.

Account security

Phone verification, session checks and unusual-access checks help us protect account data.

Retention period

We retain account, support and payment references only for the period needed for the stated service, security, dispute and legal…

Payment matching

A Bank BCA Deposit reference, bank transfer detail or virtual account event may be matched with your profile to identify…

Change or deletion

Ask through account support to correct a phone number, contact detail or other personal data.

Privacy Policy Questions About nau4d

These answers address the searches we receive about the nau4d Privacy Policy, from wallet references to mobile browsing. If your situation is unusual, send the account context through support so we can identify the relevant record and explain the next step.

It covers account and contact details, phone verification, payment references, device and browser signals, cookies, retention, security checks and privacy requests. It also explains when data may be shared for a requested service or where local law permits.

Yes. The Privacy Policy explains that DANA and QRIS activity can produce a payment reference, amount, status and timestamp linked to your account. OVO, GoPay, bank transfer and virtual account records follow the same account-matching purpose.

Phone verification helps connect account access to the contact detail you provide and supports security checks. It can also help us identify the correct profile when you ask about a correction, cookie setting or payment record.

You can send a data-access request through the support route attached to your account. Include the phone or email detail used during account access. We may verify the request first, then explain which records can be supplied under local law.

Open account support and state the field that needs changing, such as a phone number or contact detail. Add the current account identifier and the corrected value. We will check ownership before applying or explaining the requested change.

Retention depends on the record and its purpose. Payment references may be kept for account matching, security, disputes or legal duties, while device and cookie records may follow a different period. Ask support for the applicable explanation for your request.

Send a deletion request through account support and identify the profile concerned. We assess it under the Privacy Policy and local requirements. Some payment, security or legal records may need to remain for the period required by law.