Reference

Privacy Policy For Your Account

Our Privacy Policy explains how nabati bet handles the details you provide when opening an account, checking wallet status or contacting support.

Clear data purposesWallet record contextAccount access stepsCookie choices
Explore Our Lobby Read FAQ
nabati bet Privacy Policy For Your Account
HELP WITH PRIVACY

Three Ways To Ask About Data

A clear contact route helps you act on this Privacy Policy without searching through unrelated account pages. Tell us whether your question concerns sign-in records, a wallet reference, a cookie or a correction request, and include the account detail needed to locate it. We may ask for an account step or verification detail before discussing private records. That check protects your account while keeping the request connected to the right support case.

Team online

Account access request

Ask us to confirm which account details are linked to your sign-in path. We may request a verification step before sharing private records, so the response reaches the person who controls the account rather than an unverified contact.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the receipt detail through our support route. We can check the stored transaction reference and explain what account or status record it is connected to.

Correction request

Tell us which profile or contact detail needs correction and why it is no longer accurate. We will use the account record to locate the request, apply the permitted change and explain any detail that must remain for security.

DATA CARE

How We Handle Your Privacy Choices

Privacy work is tied to the account actions you can recognise, not to a vague promise about data.

Account details

We use your account and contact details to create the profile, send account-related replies and identify the correct record when you ask about Privacy Policy rights. We do not need unrelated profile details to process a focused data request.

Device and session data

Your browser or mobile device can provide session signals such as sign-in state, basic device type and error context. These details help us diagnose an access issue without treating a device signal as a complete identity check.

Cookies

Cookies can keep your account session active and help us understand whether a page or login step has failed. You can adjust cookie controls in your browser; clearing them may sign you out and remove saved session preferences.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be stored beside the relevant account event. We use that record to check status, reconcile a receipt and respond to a wallet question.

Account security

We may ask for phone verification before account access or before discussing sensitive records. Keep sign-in details private and contact us if an unfamiliar device or account change appears in your security history.

Retention and requests

We retain records only as long as needed for the stated account, security, support or legal purpose. Where local law permits, contact us to request access, correction or deletion and we will explain the next account step.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account questions we expect when you check nabati bet before opening an account. They explain the records connected to login, mobile cookies, local wallet references and support requests in plain terms. If your situation is different, use the support path rather than sending sensitive account details in an open message.

It covers account and contact details, phone verification, device and session signals, cookies, support messages and payment references. We use those records for account access, security, status checks and policy requests, subject to the limits and duties that apply where local law permits.

Those wallet names may appear in a transaction reference connected to your account. We use the reference to match a receipt or status question with the right account event. The policy does not treat a wallet name as permission to use your data for an unrelated purpose.

Where local law permits, you can ask which personal details are connected to your account and how they are being used. Send the request through our support route, describe the account step involved and complete any verification needed before private records are shared.

Contact us with the profile or contact detail that needs correction and explain what has changed. We may confirm your phone or account access first. After checking the record, we will apply the permitted change or explain why a particular field must remain unchanged.

Yes. Cookies can keep your mobile session connected from login through the lobby and help us identify a page error. You can manage them in your browser settings, but removing cookies may sign you out or require another account access step.

We keep each record for the account, security, support or legal purpose that requires it, then remove or restrict it when that purpose ends where permitted. A request about retention should identify the account record, such as a QRIS receipt or sign-in event.

Use our account support route and label the message as a Privacy Policy request. Include the type of concern, such as access, correction, cookie use or an unfamiliar wallet reference. Do not send a password; we will request an appropriate verification step if needed.

Related Pages

nabati bet Indonesia Access guide About Us sarangbola188 Bikini Paradise