Reference

Privacy Policy for macanempire Account Access

Our macanempire Privacy Policy shows how we handle the details connected with VIP Baccarat, Galactic Gems, Mobile Legends and your wallet activity.

Clear data choicesWallet record contextPhone verificationIndonesia access
macanempire Privacy Policy for macanempire Account Access
PRIVATE HELP ROUTE

Privacy Questions Around Wallet Records

A direct support path helps when you want to understand a payment record, phone check or device entry rather than guess what a status means.

Account data request Ask what account details we hold, including the phone verification record connected with your macanempire access. We will use the account contact you provide to locate the request.
Wallet record question For DANA, OVO, GoPay, QRIS or bank transfer records, share the reference and date rather than sensitive wallet credentials. We use those details to trace the relevant entry.
Access and correction If your name, phone detail or account record needs correction, contact our support route beside the cashier path. We may ask for an account check before making a change.
DATA HANDLING

Data Choices Across Your Account

We keep privacy practical by connecting each data choice to a visible account action. Your sign-in, phone check, wallet reference and browser session have different purposes, so we explain them separately instead…

Account details

We use the contact details you submit to create access, complete a phone verification step and respond to a privacy request. We do not ask for unrelated personal details to browse the account area.

Payment references

A DANA, QRIS, OVO, GoPay, bank transfer or virtual account reference helps us match a requested transaction with its status. It is handled as a record, not as your wallet password.

Cookies and browser

Cookies and similar browser storage can keep your session connected, remember a practical setting and help identify repeated security events. You can manage browser permissions, though some account steps may then need repeating.

Session security

We examine sign-in time, device type and security signals to spot unusual access. If a session does not match your usual account pattern, we may request another account check before access continues.

Retention period

We retain account, support and payment records only while needed for service history, transaction matching, dispute handling or legal duties. A deletion request is assessed against those separate reasons.

Changes and contact

To request access, correction or deletion, contact our support route with your account contact and a clear request. We may confirm ownership first, then explain the action and any local-law limit.

Privacy Policy Questions From Indonesia

These answers address the account questions we hear before access is opened. They cover the records created by phone verification, mobile browsing and local payment references, while keeping the focus on how you can ask about or change your personal data.

It covers account details, phone verification, device and browser signals, cookies, support requests, payment references and retention. It also explains how to ask for access, correction or deletion where local law permits.

We use your phone detail to create and protect account access, complete the account step before entry and connect support requests with the right record. A phone check may be required when security signals change.

Yes. The policy covers references, timestamps and status details created during DANA or QRIS requests, as well as OVO, GoPay, bank transfer and virtual account activity.

You can contact our support route with the account contact used for access and ask for a data summary. We may confirm account ownership before disclosing records linked to that request.

Send a correction request through the privacy support path and describe the field that is wrong. Include your account contact, but never include a wallet password or one-time security code.

You may ask us to delete eligible personal data. We first separate records that can be removed from those needed for transaction matching, dispute handling, account security or legal duties.

Mobile browsing can provide device type, browser and session security signals, just as desktop access can. Those details help keep your login connected and identify unusual access; handling still follows this policy.