Reference

mabar88 Privacy Policy For Your Account

The mabar88 Privacy Policy explains what we collect when you open an account, sign in on mobile, or check wallet status through DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests

Browse Our Lobby Read FAQ

How Wallet Records Enter This Policy

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

Our Privacy Policy covers details you provide during account creation, including contact details used for phone verification before account access. It also covers records created when you select DANA, OVO, GoPay or QRIS, such as a reference, amount, status and time connected with your request. Bank

1
transfer and virtual account references may be retained so we can match a receipt to the correct account and investigate a stalled status. Device and browser details can help us recognise a sign-in session and protect the account from unusual access. We apply this policy to
2
the mabar88 service for Indonesia where local law permits; where access or eligibility is discussed, it depends on local law. If you use a shared phone in Makassar or elsewhere, sign out after checking your wallet status and avoid saving login details in the browser.

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

PRIVACY HELP ROUTE

Contact mabar88 About Your Data

A clear support path matters when a Privacy Policy question involves your account or a wallet receipt.

Account access Ask us to explain account data linked to your phone verification step, including what we need before access and how to request a copy of the details held for your account.

Wallet receipt For a DANA, OVO, GoPay or QRIS query, provide the reference and status shown in your account rather than private wallet credentials, so our team can trace the record safely.

Policy request Use the same support route to ask for correction, deletion or clarification. We may request an account check first so a change is made for the right person.

HANDLING YOUR DETAILS

Account Security From Login To Retention

We keep the Privacy Policy practical by connecting each data use to an account step. Phone verification helps us confirm account access, cookies help remember suitable session settings, and security checks help…

Phone verification

Before account access, we use the phone verification step to connect the request with the correct account. This helps prevent one person from changing another person’s stored details.

Mobile sessions

When you sign in through a mobile browser, session and device signals may be recorded for security. Clearing browser data can remove local preferences without deleting account records.

Cookies

Cookies can keep a session active, remember language or support essential account functions. You can manage browser cookie settings, although some policy-related account actions may then need another sign-in.

Payment matching

A QRIS, DANA, OVO or GoPay reference helps us match a payment status with your account. We do not need your wallet password to check that operational record.

Retention

We keep account, verification and payment records for the period needed for service operation, dispute handling or legal duties. The policy explains the reason and context for each retention need.

Change requests

You can ask us to correct inaccurate details, explain a data use or remove eligible records. Send the request through support and be ready to confirm account ownership.

Privacy Policy Answers For Your Account

These Privacy Policy questions cover the account, device and payment records you are most likely to ask about before opening access. If your situation is not listed, our support route can explain the relevant policy step without requiring you to share a password.

It covers account details, phone verification, sign-in and device signals, cookies, payment references, support requests, retention and your available requests for access, correction or deletion.

Phone verification connects an account access request to the correct account and helps protect stored details. We may use that check when you ask us to change or disclose account data.

Yes. The policy includes operational records such as a DANA or QRIS reference, status, amount and time, along with comparable records for OVO, GoPay, bank transfer and virtual account requests.

We may receive session, browser and device signals needed for account access and security. These signals help identify unusual sign-ins; they do not give us your phone password or wallet security code.

Contact support through the account help route and clearly ask for an access request. Include the account phone detail you can safely confirm, because we may verify ownership before responding.

You can request correction of inaccurate details or removal of eligible records through support. Some payment, dispute or legal records may need to remain for the period stated in the policy.

Yes. Where access or eligibility is discussed, it depends on local law. Our Privacy Policy applies to the service for Indonesia where local law permits, and support can clarify a location-specific request.

mabar88 Privacy Policy For Your Account

Contact mabar88 About Your Data

Account Security From Login To Retention

Phone verification

Mobile sessions

Cookies

Payment matching

Retention

Change requests

Privacy Policy Answers For Your Account

01 What does the mabar88 Privacy Policy cover?

02 Why does mabar88 need phone verification?

03 Does the Privacy Policy include DANA and QRIS records?

04 What device data can mabar88 see on mobile?

05 How do I request my mabar88 data?

06 Can I ask mabar88 to correct or remove data?

07 Does access under this Privacy Policy depend on location?

Related Pages