Reference

Open macan123 Privacy Policy Before Account Access

Our Privacy Policy explains what we collect when you create an account, sign in on mobile, open Baccarat or Aviator, and use DANA or QRIS.

Account recordsWallet referencesCookie choicesAccess depends on local law
macan123 Open macan123 Privacy Policy Before Account Access
CONTACT ROUTES

Check Privacy Policy Help Paths

A clear contact route helps when you want to ask about a Privacy Policy record, correct an account detail, or understand a wallet entry. Start from the signed-in account help area and include your account identifier plus the relevant date or transaction reference. For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, we use that reference to locate the right record without asking you to resend a full wallet credential.

Team online

Account help

Use the signed-in help path for questions about your name, phone verification, account access record or a request to correct personal details.

Wallet status

Send the DANA, OVO, GoPay or QRIS reference shown in your cashier history. We use it to match the event and explain what data is stored.

Privacy request

Ask for a copy, correction or deletion assessment through account support. Include the email or phone attached to your account so we can verify ownership.

HANDLING DETAILS

Request Changes To Your macan123 Data

We keep this policy practical by linking each data action to a familiar account step: phone verification, sign-in, wallet selection or support contact.

Account security

Phone verification is connected to account access, and sign-in events can include device type, browser details and time so we can investigate an unfamiliar session.

Cookie control

Cookies help keep your session active and remember selected settings. You can manage browser cookie controls, though changing them may affect sign-in continuity.

Wallet minimisation

For DANA, OVO, GoPay and QRIS, we use route, reference and status details to reconcile an event rather than requesting your wallet password.

Device records

Mobile and desktop access may create security records containing browser type, operating system, sign-in time and unusual-session signals for account protection.

Retention checks

We keep account, support and transaction references for the stated operational, dispute and legal purposes, then delete, restrict or anonymise them when suitable.

Correction route

To request access or a change, contact account support with your attached phone or email and the specific record. We verify ownership before responding.

Find Privacy Policy Answers Before Joining

These Privacy Policy answers address the searches we hear before account creation: what is collected, how wallet records are matched, how cookies work, and how you can request a change. If your question is not listed, use the account help route with the smallest useful detail.

It covers account and phone details, sign-in and device records, cookies, support messages, and wallet or transaction references created through DANA, OVO, GoPay, QRIS, bank transfer or virtual account.

We use your phone number for account identification and the clear phone verification step before account access. It also helps support confirm that a Privacy Policy request belongs to you.

Our policy describes route, reference, amount and status records used to match a cashier event. Do not send a wallet password in support messages; we do not need it for a policy request.

Open the signed-in account help path and request a copy of your personal data. Include the attached phone or email, and we will verify account ownership before handling the request.

Yes. Send the specific incorrect detail through account support, along with your attached phone or email. We may ask for an ownership check before changing the account record.

Cookies can maintain your sign-in session and save selected settings. Your browser controls can restrict them, but doing so may interrupt account access or require you to sign in again.

Access and eligibility depends on local law. Our Privacy Policy explains handling for accounts reached where local law permits, including device, account, support and wallet records.