Reference

nicebet Privacy Policy For Your Account

Our Privacy Policy explains how we collect, use and protect the details connected with your nicebet account, including phone verification, device signals and wallet activity.

Clear collection rulesWallet record controlsCookie choicesAccount contact path
nicebet nicebet Privacy Policy For Your Account
CONTACT DATA CARE

Get Privacy Help Through Your Account

A direct support route helps you ask what data we hold, why a record appears, or how to correct an account detail. Open the account help panel while signed in and include the phone number or transaction reference linked to your request. Our support chat can check wallet status without asking you to send a password or full payment credentials.

Team online

Account help panel

Use the signed-in account help panel for a Privacy Policy question, correction request or access request. Include your registered phone number and the relevant date so we can locate the correct record.

Support chat

Our support chat can explain a DANA, OVO, GoPay or QRIS record and direct your privacy request to the right team. We will not ask for your password, one-time code or complete wallet credentials.

Receipt reference

Keep the receipt or bank transfer reference when you contact us about personal data. A reference from QRIS, BCA, BRI, Mandiri or BNI helps us separate your request from another account.

DATA HANDLING PRACTICE

What We Protect Inside nicebet

Privacy controls work alongside the account steps you already use: phone verification, sign-in and wallet status checks.

Account details

We may handle your phone number, profile entries, sign-in events and verification result to create and maintain your account. We use these details for account access, support responses and security checks rather than unrelated messages.

Wallet references

A wallet or bank record can contain a rail name, reference number, amount and status. We use that information to match your request to the correct account and investigate a receipt, reversal or pending result.

Cookies

Cookies can retain a session preference, language setting or security state on your device. You can manage browser permissions, although removing necessary cookies may require you to sign in again.

Device security

We may record device type, browser details, approximate network data and access time when checking unusual sign-in activity. These signals help protect your account without giving support your password or private wallet code.

Record retention

We retain account, support and transaction records only for the period needed for service administration, dispute handling, fraud checks and applicable legal duties. When a record is no longer needed, our handling process removes or separates it.

Change requests

Ask us to correct an inaccurate phone number, profile detail or contact preference through the account help panel. We may confirm account ownership before making a change, so one person cannot alter another person’s records.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the questions you may have before opening or continuing a nicebet account. We explain account records, wallet references, cookies, correction requests and access limits in plain terms. If your question concerns a specific transaction, use the account help panel with its receipt reference. Access remains subject to local requirements and depends on local law.

The nicebet Privacy Policy covers personal data connected with your account, including phone verification, sign-in events, device signals, support messages and payment references. It also explains cookies, retention, security checks, correction requests and the circumstances in which we may share records.

We use your phone number to create or locate your account, complete the clear phone verification step and help prevent mistaken access. Support may confirm ownership before changing a phone detail. We do not ask you to place a password or one-time code in chat.

Yes. The Privacy Policy covers DANA and QRIS references linked to your account, along with OVO, GoPay, bank transfer and virtual account records. We use rail name, reference, amount and status to match a request, investigate delays and maintain required transaction records.

You can request a correction through the signed-in account help panel. Tell us which phone number, profile detail or contact preference is inaccurate, and provide the relevant account reference. We may verify ownership first, then confirm whether the requested change was applied.

Cookies can keep your session, language setting and security state available while you move between account pages. Browser controls let you remove or restrict them. If necessary cookies are blocked, you may need to sign in again or repeat a device check.

We keep account, support and transaction records for the period needed to operate the account, handle disputes, check unusual activity and meet applicable legal duties. The period can differ by record type. You can ask support which category applies to a particular request.

Yes. Send an access request through the account help panel and identify the record or period you want us to locate. We may ask for account verification before responding. Access or eligibility depends on local law, and some records may require lawful redaction.