Reference

Privacy Policy for Your noz388 Account

Live Baccarat Table, Crash Skyrise Arena and QRIS account records each need clear handling, so our Privacy Policy explains what we collect, why we use it and how…

Account dataCookie choicesWallet recordsSecurity requests
noz388 Privacy Policy for Your noz388 Account
HELP WITH YOUR DATA

Get Privacy Policy Help Beside Account Support

A clear contact path matters when you cannot tell whether a phone check, cookie setting or wallet reference belongs to your account.

Account data request Ask for the personal data connected with your noz388 account through the account support…
Wallet record question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the date, amount…
Security concern Report an unexpected login, device session or account change through support as soon as…
YOUR DATA CONTROLS

What We Do With Account And Device Data

Privacy is handled through practical account controls rather than broad promises. We separate sign-in details from the payment references needed to reconcile DANA, QRIS or a bank transfer, and we limit internal…

Phone verification

Before account access or a sensitive data response, we may send a phone verification step to the number connected with your account. This helps us distinguish your request from an attempt to obtain another person’s account details.

Device sessions

When you move from a mobile browser to desktop, we record session and device signals used for account security. These signals help us spot unusual access around titles such as Live Baccarat Table without reading unrelated files on your device.

Cookie settings

Cookies can keep your sign-in path working, remember selected settings and help us understand whether a page loads correctly. You can manage browser cookie controls, although turning them off may require you to repeat account steps.

Payment references

For DANA, OVO, GoPay, QRIS and bank transfer events, we retain the reference needed to match a payment status with your account. We do not ask for your wallet PIN, card password or unrelated financial details.

Retention checks

We keep personal data only for the period needed for account service, security checks, dispute handling or legal duties. When you ask about deletion, we explain which records can be removed and which transaction references must remain.

Change requests

You can request access, correction or deletion through account support. We verify the request, confirm the scope in writing and tell you if a requested change affects phone verification, wallet matching or records linked to an open security matter.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the account questions you are most likely to ask before opening access or checking a wallet record. We keep the wording practical: what data is collected, how cookies work, what happens during phone verification and how to contact us. If your question concerns a particular DANA, QRIS, device or account event, include that detail in your request so we can identify the correct record.

The noz388 Privacy Policy covers data connected with your account, phone verification, device sessions, cookies, support messages, lobby activity and payment references. It explains why we use those details for access, security, support and legal duties, including records linked to DANA, OVO, GoPay and QRIS.

We may collect your account name, phone number, sign-in and device details, cookie settings, support messages, selected account activity and transaction references. We do not need your wallet PIN or banking password to match a DANA, QRIS, bank transfer or virtual account status.

Use the account support route and ask for a copy of the personal data linked to your account. Include your account phone or email, but leave out passwords and wallet credentials. We may complete phone verification before confirming the request or sharing account-specific details.

Yes. The Privacy Policy explains that cookies can keep a mobile sign-in path active, remember settings and help us identify page errors. You can change cookie controls in your browser. If cookies are blocked, you may need to repeat verification or sign-in steps.

You can ask us to correct inaccurate account data or delete information that no longer needs to be held. We verify your identity first, then explain any exceptions. Records connected to security checks, disputes or legal duties may need to remain for a stated period.

We use DANA and QRIS references to match a payment event with the correct account and status. The record may include a reference, date and amount status, but we do not request a wallet PIN. Ask support about an unfamiliar entry using the account route.

The policy is available for you to read before account access, while eligibility and access depend on local law. If a local requirement affects data handling, verification or retention, we explain the relevant step through account support and apply the rule to your request.