Reference

miliarbet Privacy Policy for Your Account

miliarbet Privacy Policy explains how we handle the details you provide when opening an account, checking a wallet status, or entering the lobby where local law permits.

Account dataWallet recordsDevice controlsPolicy access
miliarbet miliarbet Privacy Policy for Your Account
CONTACT ROUTE

Privacy Help Beside Your Account Path

A clear contact path matters when a login record or wallet reference needs checking.

Account privacy request Use the support link inside your account and state whether you need access, correction or removal of a specific personal detail.
Wallet record check For DANA, OVO, GoPay or QRIS questions, share the transaction reference rather than sending a full wallet password or unrelated account material.
Device access concern If a mobile or desktop session looks unfamiliar, sign out, change your account password and tell support which device path needs checking.
SECURITY LAYERS

Six Ways We Handle Account Data

We keep this Privacy Policy practical by connecting each data category to an account task you can recognise.

Purpose-led collection

We collect account, verification, device and payment-reference details for access, security, support and record matching. We do not need your wallet password to investigate a DANA or QRIS reference.

Cookies and sessions

Cookies and similar browser storage can keep a session active and remember basic access choices. You can clear them through your browser settings, though sign-in preferences may need to be entered again.

Account security

Phone verification is required before account access, while sign-in records and device signals help us investigate unusual activity. Never place a password or one-time code in a support message.

Retention approach

We keep records only for the operational, dispute, security or legal purpose that requires them. When a purpose ends, the relevant record is removed, anonymised or restricted where applicable.

Your control request

You can ask us to access, correct or remove personal details by using the account support route. Include the affected identifier so we can verify the request before making a change.

Policy changes

When this Privacy Policy changes, we update the policy area and its effective wording. Check the page before opening an account or returning from a Semarang or Makassar mobile connection.

Privacy Policy Questions You May Search

These answers address the account and payment questions we expect you to ask before sharing details with miliarbet. Each answer points back to a practical action, from checking browser storage to requesting a correction through the account support route.

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

Phone verification helps confirm that the account access request belongs to you and supports security checks. We use the result for the stated access purpose, not as permission for unrelated data use.

Yes. The policy covers session details, device signals and browser storage used during mobile access. You can clear cookies in your browser settings, then sign in again when needed.

We use payment references and status details to match a transaction with your account or answer a support question. We do not ask you to send a wallet password or private security code.

Yes. Use the support link shown in your account, identify the record you want to access or correct, and complete the identity check needed to protect your account from an unauthorised request.

Retention depends on the purpose: access, security, dispute handling or a legal need. When that purpose ends, we remove, anonymise or restrict the relevant record where applicable.

You can return to the Privacy Policy page through the miliarbet policy area before account access. Eligibility and access depends on local law, so check the current wording for your region.