Reference

mabes369 Privacy Policy For Your Account

Our Privacy Policy explains how mabes369 handles the details you provide when opening an account, confirming your phone and using DANA, OVO, GoPay or QRIS.

Clear data purposesWallet detail handlingAccess request pathCookie choices

Explore the lobby Read FAQ

How DANA And QRIS Data Is Used

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

We use account details to create your mabes369 profile, complete phone verification and protect the sign-in path. When you choose DANA, OVO, GoPay or QRIS, we receive payment references and status details needed to match a cashier action to your account; we do not need your

1
wallet password. Bank transfer and virtual account records are handled for reconciliation, support checks and withdrawal verification. Device, browser, IP and session records help us detect unusual access and keep login events traceable. Cookies can remember session choices and measure page use, and you can control
2
them through your browser settings. We may share necessary records with payment and security service providers only for these operating purposes. Where local law permits, you can ask what we hold, request a correction or ask about deletion. Some records may remain when a legal, fraud-prevention
3
or accounting need requires retention.

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

CONTACT PRIVACY

Privacy Questions Through Account Support

A direct support route helps you ask about the Privacy Policy without sending sensitive wallet credentials.

Account support chat Use the support chat shown after login to ask about collected data, cookie choices or a Privacy Policy request. We will first match your contact details with the account record.

Cashier privacy route If your question concerns DANA, OVO, GoPay, QRIS or a bank transfer reference, start from the cashier support path. Do not send a wallet PIN or password in your message.

Access request Ask for a copy, correction or deletion review through support using your registered phone or email. We record the request, check account ownership and reply about the next available step.

CONTROL YOUR DATA

Privacy Controls For Login And Wallets

We keep this Privacy Policy connected to practical account actions: phone confirmation, browser sessions, wallet references and support requests.

Account details

We use your registered contact details to create the account, send account messages and confirm that a privacy request comes from you. Keep your phone number current so ownership checks can work.

Phone verification

Phone verification connects a real account step to your login request. We retain the verification result and related security event, while your message should never include a one-time code after use.

Device sessions

Our records can include browser type, device signals, IP address and session time. These details help identify unusual sign-ins whether you use an Android browser, iPhone browser or desktop.

Cookies

Cookies can keep your login session active and remember selected settings. You can remove or block them through browser controls, although some account access steps may then need to run again.

Retention choices

We keep personal and payment records only for the operating, security and accounting purposes described in this Privacy Policy. Ask support which records remain and why a removal request may be limited.

Policy changes

When this Privacy Policy changes, we update the page and identify the revised section. You can contact support to ask how a change affects your account, wallet references or stored device records.

Privacy Policy Questions Indonesian Customers Ask

These Privacy Policy answers focus on the account actions you are most likely to take: registration, phone confirmation, wallet payments, mobile access and requests for your personal records. If your question is not listed, use the account support chat and quote the relevant section title.

It covers account details, phone verification, device and browser records, cookies, payment references, retention, security use and the steps available when you request access, correction or deletion.

No. The Privacy Policy describes payment references and status details used to match DANA, OVO, GoPay or QRIS activity. Do not send a wallet PIN, password or one-time code to support.

Device, browser, IP and session details help us recognise unusual login activity, investigate account access and protect phone verification. The same records can apply on a mobile browser or desktop.

Use the support chat linked from your account and identify yourself with the registered phone or email. We verify account ownership, record the request and explain the available response.

Yes, where local law permits. Send the requested correction or deletion through account support. Some payment, security or accounting records may need to remain for a stated operating reason.

Cookies can preserve a login session and remember selected settings. Browser controls let you block or remove them, but doing so may require another login or repeat an account step.

The policy is written for your account activity in Indonesia, while access depends on local law. Where local law permits, the contact, access and correction choices described here are available.

mabes369 Privacy Policy For Your Account

Privacy Questions Through Account Support

Privacy Controls For Login And Wallets

Account details

Phone verification

Device sessions

Cookies

Retention choices

Policy changes

Privacy Policy Questions Indonesian Customers Ask

01 What does the mabes369 Privacy Policy cover?

02 Does the Privacy Policy store my DANA or QRIS PIN?

03 Why does mabes369 collect device and browser data?

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

05 Can I ask for correction or deletion under this Privacy Policy?

06 How do cookies affect my mabes369 account access?

07 Does the Privacy Policy apply across Indonesia?

Related Pages