Reference

Privacy Policy for Your nusa35 Account

Our Privacy Policy explains what we collect when you open a nusa35 account, sign in from a mobile device, or check wallet status through DANA, OVO, GoPay and…

Account dataWallet recordsCookie choicesAccess requests
Explore Our Lobby Read FAQ
nusa35 Privacy Policy for Your nusa35 Account
PRIVACY HELP PATH

Get Help With Account Privacy

A clear support path matters when your account record, wallet status or access request needs attention. Contact our support desk from the account help route and include the email or phone detail linked to your profile, plus the payment reference if your question concerns DANA, OVO, GoPay or QRIS. We use those details to locate the correct record without asking you to send a full password or private login code. Privacy requests are handled as account matters, and access depends on local law.

Team online

Account request

Use the account help route to ask what personal data we hold for your nusa35 profile. We may ask you to confirm the registered phone or email before releasing details, so the request reaches the correct account.

Wallet receipt

For a DANA, OVO, GoPay or QRIS record, include the transaction reference and date in your support message. We can use that information to check status while keeping your password, PIN and one-time code out of the request.

Access concern

If a new phone or browser triggers an account check, contact support through the same account route. We will ask for account details that help confirm ownership, and we will not ask you to disclose a private sign-in code.

SECURITY PRACTICE

Six Privacy Controls Behind Access

Privacy at nusa35 is connected to the practical steps you take from login through the lobby. We separate account identification from payment references, record security events when a device changes, and use…

Account identity

We use the phone or email attached to your account to identify your profile and complete a clear account step. Before discussing private records, support may ask you to confirm that same contact detail.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets us match a cashier event to your account. We keep the payment context needed for reconciliation and support, without requesting your wallet PIN or login password.

Device checks

When you move from mobile browser to desktop, or sign in from a new device, we may record the device type, time and security result. This helps us investigate unusual access without storing the contents of your device.

Cookie control

Cookies can preserve your session and remember necessary page settings. Our Privacy Policy explains their purpose, and you can manage browser cookie settings; disabling some cookies may require another sign-in or affect account access.

Retention period

We keep personal and payment records only while they support account operation, security checks, dispute handling or a legal requirement. When the reason ends, the record is deleted or changed so it no longer identifies you where feasible.

Change request

Ask support to correct an inaccurate profile detail, explain a stored record or request deletion where available. Include the registered contact detail and a precise request; we respond according to identity checks and local law.

Privacy Policy Answers for nusa35

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. We keep the wording practical: what data is collected, why a device check appears, how wallet references are used and where to send a request. The same process applies to your nusa35 account in Indonesia, where local law permits access.

The nusa35 Privacy Policy covers account details, sign-in events, device information, cookies, payment references and support requests. It explains why we use each category, how long records may remain, and how you can ask about access, correction or deletion where local law permits.

No. We use the payment reference and status needed to match a DANA, OVO, GoPay or QRIS transaction with your account. You should never send a wallet PIN, password or one-time code through support when asking us to check a receipt.

We record limited device details, such as device type, browser context and sign-in time, to identify unusual account access and support a security check. We do not use this process to read unrelated device content, and the Privacy Policy explains its retention purpose.

Send a request through the account help route using the phone or email connected to your nusa35 profile. Describe the records you want to access, and be ready to confirm account ownership. We handle the request according to the Privacy Policy and local law.

Yes. Contact support with the registered contact detail and identify the field that is inaccurate, such as a phone number or email address. We may verify ownership before making a change, then update the account record where the request is permitted.

We retain payment references for the period needed to match deposits, answer receipt questions, investigate disputes, protect account access or meet a legal requirement. After that purpose ends, we delete or anonymise the record according to the Privacy Policy.

Use the account support route for a Privacy Policy question, a data access request or a wallet record concern. Include your registered phone or email and, for DANA, OVO, GoPay or QRIS matters, the transaction reference rather than private login credentials.

Related Pages

nusa35 Indonesia About Us FAQ Access guide nusa35 Casino