Reference

mitrabet Privacy Policy For Your Account

mitrabet Privacy Policy sets out what we collect when you open an account, sign in from a mobile browser, or use DANA and QRIS.

Account detailsWallet recordsDevice signalsData requests

Browse Our Lobby Read FAQ

How Privacy Policy Covers Wallet Records

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

Our Privacy Policy applies to information you provide during account creation, including your phone details and verification data, plus records created when you select DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use these records to match an account action with the correct

1
wallet status, investigate an incomplete cashier step and protect access from unusual devices. A mobile browser may send device and connection signals; a desktop session can create a separate sign-in record. If you connect from Jakarta or elsewhere in Indonesia, location and eligibility handling depends on
2
local law. We keep only the data needed for the stated purpose, account administration, dispute handling or a lawful request, then remove or restrict it according to our retention process. You can ask what we hold and request a correction through the support path.

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

REQUEST HELP

Privacy Questions Through Account Support

A clear support route helps when you want to ask about a Privacy Policy record rather than a cashier result.

Account access If sign-in stalls after phone verification, tell us which device path you used and the account detail connected to it. We use that context to locate the privacy request without asking for your full wallet credentials.

Wallet records For a DANA, OVO, GoPay or QRIS record, include the payment name and relevant date. We can explain the data held for that event, while you should never send a wallet PIN or one-time code.

Correction requests Ask us to correct an inaccurate phone detail, verification entry or contact record through account support. We may ask for an account step that confirms the request belongs to you before changing stored data.

HANDLING YOUR DATA

What Our Privacy Process Keeps Clear

We keep the policy practical by linking each data use to an account action you can recognise.

Account details

We may store your phone detail, account identifiers and verification results so we can connect a sign-in request with the right account. We do not need your wallet PIN to handle ordinary account support.

Device signals

A mobile browser or desktop session can provide connection, browser and device signals. We use these details to recognise access patterns, investigate account protection events and distinguish a fresh sign-in from an existing session.

Cookies

Cookies and similar storage can preserve a session choice, remember a language setting or help us understand whether a page request completed. You can manage browser storage, although some account steps may then need repeating.

Wallet matching

When you select DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we retain the transaction reference and status needed to match the account action and respond to a payment query.

Retention

We retain records for the period needed for account administration, security checks, dispute handling or legal duties. When a purpose ends, we delete, anonymise or restrict the record under our internal process.

Your request path

You can ask what personal data we hold, request a correction or raise a deletion question through account support. We may verify your account step first, then explain any legal reason a record must remain.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening an account. We keep the wording tied to real actions, including phone verification, mobile access, payment records and requests sent through account support.

The mitrabet Privacy Policy covers account details, phone verification, device and connection signals, cookies, wallet records, support requests, retention and the ways you can ask to access or correct personal data.

We use your phone detail to create and identify the account, complete the stated verification step and connect support requests with the correct record. We do not ask you to send a wallet PIN.

Yes. The Privacy Policy covers records linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account actions, such as a reference, selected rail, status and related account event.

A mobile browser or desktop session may provide browser, device, connection and session signals. We use them for access continuity, account protection and investigation of unusual sign-in activity, as described in the policy.

Use the account support route and state that you are making a Privacy Policy data request. Include your account phone detail and the records you seek; we may verify ownership before responding.

Yes. You can request correction of an inaccurate account, contact or verification record through support. Tell us what is wrong and what should replace it, then complete any ownership check we require.

We keep each record only while needed for its stated account, security, dispute or legal purpose. After that period, we delete, anonymise or restrict it according to the applicable process and local law.

mitrabet Privacy Policy For Your Account

Privacy Questions Through Account Support

What Our Privacy Process Keeps Clear

Account details

Device signals

Cookies

Wallet matching

Retention

Your request path

Privacy Policy Answers For Indonesia

01 What does the mitrabet Privacy Policy cover?

02 Why does mitrabet need my phone detail?

03 Does the Privacy Policy cover DANA and QRIS records?

04 What device data can mitrabet collect?

05 How can I request a copy of my personal data?

06 Can I ask mitrabet to correct my data?

07 How long does mitrabet keep Privacy Policy records?

Related Pages