Reference

nirmalabet Privacy Policy for Your Account Data

Our Privacy Policy shows how we handle the details connected with your nirmalabet account, from phone verification to DANA and QRIS payment records.

Account dataWallet recordsCookie choicesAccess requests

Explore Our Lobby Read FAQ

Browse how Privacy Policy covers your data

nirmalabet Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect details needed to create and protect your account, including your phone number, verification status, sign-in events, device signals and support messages. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may retain payment references and status records so we

1
can match activity to your account and investigate a receipt question. We use cookies and similar storage to keep sessions working, remember selected settings and understand which pages load correctly. We do not ask for data beyond the stated account, payment, security and support purposes. You
2
can request access, correction or deletion through our account support route. Some records may remain when required for security, dispute handling or legal duties. Access depends on local law and is provided where local law permits.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATH

Reach us about your Privacy Policy

A clear support path helps when a data question sits beside an account or wallet issue.

Account data request Tell us which account detail you want to access or change, such as your phone verification record, and we will use the account support route to identify the request.

Wallet record question Include the DANA, OVO, GoPay or QRIS reference shown in your account so we can connect your payment-status question with the correct privacy request.

Access problem If your phone verification blocks account access, explain the step that failed and the device you used; we will separate access help from any Privacy Policy request.

HANDLING DETAILS

Explore account security and data choices

We keep this policy practical by linking each data choice to a real account step. Phone verification helps us distinguish your sign-in from an unfamiliar attempt, while device and session records help…

Account security

We use phone verification, sign-in records and device signals to help protect account access. If a sign-in looks unusual, those records can support an access check before details are changed.

Cookies and sessions

Cookies can keep your session active and remember settings on a mobile browser. You can manage browser storage through your device settings, although some account steps may then need repeating.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a receipt or status question. We use those references for account support rather than unrelated purposes.

Data retention

We retain account, security and payment records only for the period needed for the stated purpose, dispute handling or legal duties. Our support route can explain why a particular record remains.

Request a correction

If your phone number or verification detail is wrong, contact support from the linked account and describe the correction. We may ask for account checks before changing protected details.

Request deletion

You can ask us to remove eligible account data through support. We will explain what can be deleted and what must remain for security, payment matching or legal duties.

Check Privacy Policy answers before opening

These Privacy Policy answers cover the practical questions that arise before you open an account or connect a local wallet. We keep the wording tied to your account journey, from phone verification and cookie settings to payment references and requests for access or correction. If your situation is not listed, use the support path with the relevant account detail.

It covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number for account creation, verification and access checks. It helps us connect a support request to the correct account when you ask about data or a wallet record.

Yes. It covers cookies and session data used when you open the lobby in a mobile browser, including pages such as Baccarat, Super Bingo or Mega Fishing.

Sign in and contact support through the account area. State that you want an access request, identify the relevant phone number or record, and complete any account check we require.

Yes. Send a correction request through the linked account support route, explain which detail is wrong, and provide the updated value. We may verify ownership before changing protected account data.

We keep payment references for the period needed to match receipts, resolve disputes, protect account access or meet legal duties. Support can explain the reason for a specific retained record.

Account access and eligibility depends on local law. We provide access where local law permits, and you should check the rules that apply to your location before opening an account.

nirmalabet Privacy Policy for Your Account Data

Reach us about your Privacy Policy

Explore account security and data choices

Account security

Cookies and sessions

Payment references

Data retention

Request a correction

Request deletion

Check Privacy Policy answers before opening

01 What does the nirmalabet Privacy Policy cover?

02 Why does nirmalabet collect my phone number?

03 Does the Privacy Policy cover mobile browsing?

04 How can I request my nirmalabet account data?

05 Can I ask nirmalabet to correct my data?

06 How long are payment records kept under the Privacy Policy?

07 Can I use nirmalabet where I live in Indonesia?

Related Pages