Reference

Open nexus888 slot Privacy Policy

nexus888 slot Privacy Policy explains how we use account, device and wallet details while you access Live Baccarat Turbo, Sumatra Tiger Slots or the lobby from Indonesia.

Account clarityWallet data scopePolicy contact
nexus888 slot Open nexus888 slot Privacy Policy
CONTACT THE TEAM

Switch to the right privacy contact

A clear contact path matters when your account record or wallet reference needs attention. Use the support route shown inside your signed-in account and include the email or phone detail attached to…

Account privacy request Ask us to explain the personal details connected with your account, including phone verification records and sign-in activity. Send the request through the signed-in support path so we can check account ownership before discussing data linked to your profile.
Wallet record question For a DANA, OVO, GoPay or QRIS reference, include the transaction date, amount shown in your account and the wallet rail used. We can use that context to locate the relevant payment record without requesting your wallet password.
Access or correction If your account details need correction or you cannot reach the policy page, contact support from the account route and describe the issue. We may ask for a phone verification step before changing or disclosing personal account data.
DATA HANDLING

Explore the controls behind this policy

Privacy work is part of the account path, not a separate promise detached from the lobby.

Account data

We collect details you submit for account creation, phone verification and support contact. These records help us recognise your account when you move from sign-in to the lobby or ask why a wallet status has not matched the reference you supplied.

Device records

A browser or phone can create session, device and security records around sign-in. We use these signals to identify unusual access and protect pages such as Fishing War Mobile Play, without treating your device as a public identity.

Cookies

Cookies can keep a session open, remember a policy-page visit or support security checks between account steps. You can manage cookies in your browser, although blocking some may prevent the account path from working as intended.

Account security

Phone verification is an account access step, not a request to publish your number. We may compare sign-in context with account details before discussing personal records or changing account data connected with wallet activity.

Retention questions

We keep records only as needed for the stated account, security, support or transaction purpose and for duties that apply where local law permits. Ask support what record category your request concerns and which retention rule applies.

Change request

To request correction, access or another available change, use the signed-in support route and identify the account detail involved. We may verify ownership first, then explain the next step and any legal reason a request cannot be completed.

Ask before opening your account

These Privacy Policy questions focus on the decisions you make before using an account from Indonesia. We answer them in practical terms: what we collect, why a payment reference appears, how device records work and where to send a request. If your situation depends on local law, the available action can vary by location and account status.

The Privacy Policy covers account details, phone verification, device and session records, support messages, cookies and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains how to ask about access, correction and retention.

We use phone verification to confirm account ownership during access and certain support requests. It helps us avoid discussing account or wallet records with the wrong person. We do not ask you to place your phone number in a public message or open chat.

Yes. The policy covers payment references that reach your account through QRIS, DANA, OVO, GoPay, bank transfer or virtual account steps. We use the reference and related account context to investigate status questions, rather than requesting your wallet password.

Cookies can support sign-in sessions, policy-page access and security checks on your browser or phone. You can control them through browser settings. If you block required cookies, some account steps may stop working or ask you to sign in again.

Where local law permits, you can request access to or correction of personal details connected with your account. Contact support through the signed-in route, identify the record involved and complete any ownership check needed before we discuss or change it.

Send a retention question through the account support path and mention the type of record, such as a phone verification entry, support message or payment reference. We will explain the applicable handling period or limitation where local law permits.

If the policy page does not load on your phone or desktop, use the account support route and state the device and browser path you tried. We can help locate the page and handle a privacy request after confirming account ownership.