Reference

navibet Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an account, check wallet status or access the lobby from a phone or desktop.

Account dataWallet recordsDevice choicesYour requests
navibet navibet Privacy Policy for Your Account
HELP CHANNELS

Reach Support About Your Privacy Policy

A clear contact route helps you ask what we hold, why we use it or how to correct an account detail.

Account request Send a privacy question through the account support route and include your registered phone…
Wallet query If your request concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account references…
Access concern When a phone or desktop session displays the wrong privacy choice, tell us the…
CONTROL CHECK

Check How navibet Handles Your Data

The policy gives you a practical view of data handling from the first phone verification step through account closure or a later request.

Collection

We collect details you enter for account access, plus technical signals from the device path you use. A phone verification event helps us associate access activity with the account you asked to open.

Purpose

We use account and transaction references to provide the requested account flow, check wallet status and respond to support questions. We do not describe these records as permission for unrelated contact.

Cookies

Cookies can keep a selected setting available between visits and help us see whether a policy page loads correctly. Your browser controls provide a way to manage cookie behaviour.

Account security

Login events, phone verification and device signals can help us identify unusual access. If you change phones, review your account access details and contact support when a record looks unfamiliar.

Retention

We keep records for the period needed for the stated purpose, account support and applicable requirements. The retention approach can differ by record type, so ask us about a specific item.

Your changes

You can ask us to correct inaccurate account details, explain a data use or address a policy concern. Include your registered contact detail and the change you want assessed.

Search Your Privacy Policy Questions

These answers address the questions we expect you to ask before opening an account or sending a privacy request. They point back to the policy text and the account details we need to identify your record.

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

We use the phone verification record to connect an account access request with the correct account and help assess unusual login activity. The policy explains this purpose and related handling.

Yes. It explains how references linked to DANA, OVO, GoPay and QRIS may be handled, along with bank transfer and virtual account details needed to check a transaction status.

Use the support route beside account access and provide your registered email or phone, then describe the correction. We assess the request against the record and the policy’s stated purposes.

You can ask us to clarify the account, device, cookie or transaction records connected with you. Include enough account detail for identification, and we will explain the applicable handling.

Retention depends on the record type, its stated purpose and applicable requirements. The policy sets out the approach, while support can address a specific account or transaction record you identify.

Account access and related processing apply where local law permits. If you are unsure about access from your location, check the policy and contact support before opening an account.