Reference

net33 Privacy Policy for Your Account

Clear Privacy Policy terms show how we handle your account details, device signals and payment records when you access Baccarat, Aviator or other lobby areas.

Account dataWallet recordsCookie choicesAccess requests
net33 net33 Privacy Policy for Your Account
PRIVACY SUPPORT

Check Privacy Policy Help Through Support

A direct support route keeps Privacy Policy questions tied to the right account rather than scattered across messages. When you contact us, use the email or support form shown on our site and include your account identifier without sending a password or wallet PIN. We can then match a request to the relevant login, device or payment record.

Team online

Privacy request

Ask which account details we hold, why they are used and how long they remain available. We will use the account path to locate the relevant record without asking for your wallet PIN.

Correction path

If your phone number, email or profile detail is wrong, tell our support team through the account help route. We may request phone verification before changing information linked to account access.

Payment query

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, send the receipt reference rather than private wallet credentials. This lets us check status while limiting sensitive details.

DATA PRACTICE

Protect Account Data Across Devices

Privacy Policy choices matter most when your account moves between a mobile browser and desktop.

What we collect

We may receive your name, contact details, phone verification result, login timestamps, browser type and device signals. These details help connect your account activity with the correct session and support request.

Why we use it

We use account and session details to provide access, identify failed logins, match payment references and respond to Privacy Policy questions. We do not need your DANA, OVO or GoPay PIN.

Cookies and sessions

Cookies can keep a signed-in session working and remember selected settings on your device. You can manage or delete them through browser controls, although some account access steps may then need repeating.

Account security

Phone verification supports account access, while login and device signals help us investigate unusual sessions. Never send a password, one-time code or wallet credential when asking about privacy.

How long we retain

We retain relevant account, support and transaction records only as long as needed for service operations, security review, dispute handling or legal obligations. Different record types can therefore have different retention periods.

Changing your details

Send a correction, access or deletion request through the support route with enough account context to locate it. We may verify your identity before changing or releasing details connected to your account.

Find Privacy Policy Answers Before Opening

These Privacy Policy answers address the account steps you are most likely to check before opening an account from Indonesia. We explain wallet records, device access, cookies, corrections and contact handling in plain language. If your question concerns a specific record, use the support path and include its reference without sharing secret credentials.

It covers account details, phone verification, login and device signals, cookies, lobby activity, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

No. Our Privacy Policy describes handling payment references and status details, not your DANA, OVO or GoPay PIN. Do not send wallet credentials to support when asking us to check a receipt.

We use your phone number for account identification and the phone verification step before access. It can also help us match a support request, correct a record or investigate an unfamiliar login.

Yes. The Privacy Policy allows you to ask what eligible account details we hold and how they are used. Contact support through the site route, provide account context and complete any identity check.

Yes. Send the correction through support and identify the affected account field, such as phone or email. We may verify your identity before changing details that control account access.

The Privacy Policy applies the same account rules on mobile and desktop. We may process browser, session and device signals so a login can be secured and a payment reference matched correctly.

Use the email or support form displayed on our site and describe the request clearly. Include a receipt reference or account identifier when useful, but never include a password, one-time code or wallet PIN.