Reference

mhabet77 Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, use DANA or QRIS, and contact support.

Clear data purposesWallet record handlingMobile access detailsPolicy contact route

Browse Our Lobby Read FAQ

How DANA and QRIS Data Is Used

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

Our Privacy Policy covers the account details you submit, device and sign-in records, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, and virtual account deposits. We use payment references to match a transaction with your account, check its status, resolve a

1
receipt question, and complete required account controls. Bank details such as BCA, BRI, Mandiri, or BNI may appear in a transfer record, but we use them for the stated transaction purpose. We keep records for as long as needed for account administration, security, dispute handling, and
2
legal duties. We do not ask for a wallet PIN in support messages. Access to mhabet77 and related processing depends on local law, and you should stop using the service if local rules do not permit access.

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

CONTACT PATH

Privacy Help Beside Your Account

A clear contact route helps when you need a copy, correction, or explanation of personal data. Use the support path shown inside your signed-in account and include the phone number or account reference connected to your request. We can then check the relevant wallet receipt, login event, or cookie question without asking you to send a password or wallet PIN.

Team online

Account request

Ask us to confirm the data connected with your account, explain its purpose, or correct a phone detail after we verify that the request comes from you.

Wallet record

For a DANA, OVO, GoPay, QRIS, or bank transfer question, share the receipt reference through the account support path rather than sending private wallet credentials.

Access concern

If a mobile login or privacy page does not load, tell us your device path and the visible error. We will use that detail to locate the access issue.

SECURITY RECORDS

What Our Privacy Process Covers

We handle privacy through practical account controls rather than vague promises. A phone verification step can connect an account action to you, while sign-in and device records help us identify unusual access.

Account data

We collect details needed for account creation, phone verification, sign-in support, and requested wallet actions. We use those details for the purpose shown at the relevant account step.

Cookie choices

Cookies can keep your session active and remember basic page settings on a mobile browser. You can manage browser cookie controls, although some account pages may then require another sign-in.

Security checks

Login time, device details, and verification events can help us investigate an unfamiliar account action. Never place a password, wallet PIN, or one-time code in a support message.

Retention period

We retain account, payment-reference, and support records only for account operation, security review, dispute handling, and legal duties that still require them.

Request a change

You can ask us to correct account data or explain its use through the signed-in support route. We may verify your account before changing or releasing records.

Policy contact

For a Privacy Policy question, include your account reference, the relevant date, and the data concern. We use those details to direct the request to the right support queue.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the questions you may have before opening an account or connecting a local wallet. We keep the wording practical: what data is used, how you can ask for a change, what cookies do on mobile, and how local access rules affect processing. For a case tied to your account, use the support path displayed after sign-in.

It covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity.

We use the reference to match a deposit or status enquiry with your account, check a receipt, and resolve a payment question. We do not need your wallet PIN for that process.

Yes. Send the request through the signed-in support route with your account reference and the data concerned. We may verify your identity before providing a copy or making a correction.

Cookies can maintain a signed-in session and remember basic browser settings. You can change cookie controls in your mobile browser, but restricted cookies may require you to sign in again.

We keep them for the period needed to operate your account, protect access, resolve disputes, and meet legal duties. The period can differ by record type and the reason for retention.

Yes. Contact support through your account and mention the date, device path, and account action. We can explain the relevant purpose after confirming that the request belongs to you.

Yes. Account access and related data processing depends on local law. If access is not permitted where you are, do not open an account or submit personal details.

mhabet77 Privacy Policy for Your Account

Privacy Help Beside Your Account

Account request

Wallet record

Access concern

What Our Privacy Process Covers

Account data

Cookie choices

Security checks

Retention period

Request a change

Policy contact

Privacy Policy Answers for Indonesia

01 What does the mhabet77 Privacy Policy cover?

02 Why does mhabet77 record my wallet transaction reference?

03 Can I request a copy or correction of my account data?

04 How does this Privacy Policy handle mobile cookies?

05 How long does mhabet77 keep payment and support records?

06 Can I ask why my data was used for a security check?

07 Does access to mhabet77 depend on local law?

Related Pages