Reference

macan123 Privacy Policy Explained

macan123 Privacy Policy tells you what account details we collect, why we use them, and how you can ask about changes before opening an account.

Account dataWallet recordsCookie choicesAccess requests
macan123 macan123 Privacy Policy Explained
ASK ABOUT DATA

Contact Us About Your Privacy Policy

A clear support route helps you act on the Privacy Policy without guessing which account step applies. We ask you to contact us from the signed-in account where possible, because that lets us compare your request with the phone verification status and the relevant wallet reference. You can still explain the issue when login access stalls, and we will direct the next identity check.

Team online

Account access

If you cannot enter your account, tell us the phone verification stage and the device path you used. We use those details to locate the privacy request without asking for a wallet password.

Wallet record

For a DANA, OVO, GoPay or QRIS record, include the transaction reference and date from your receipt. We can then separate payment matching from a request to change personal data.

Policy request

Ask us to explain, correct or remove data through the account support route. We may request a matching account detail before making changes, so another person cannot alter your record.

DATA HANDLING

Explore How We Handle Privacy Requests

The Privacy Policy is supported by operating steps rather than broad promises. We separate account identity, device signals and payment references, then use the smallest practical set for access, security and support.

Account details

We use your phone number and verification status to identify the account connected to a request. This helps us answer access questions without treating a DANA or QRIS reference as your full identity.

Device signals

A mobile browser may send session and device signals used for login continuity and security checks. We use these signals to assess unusual access, not to read unrelated files on your device.

Cookies

Cookies can keep a session active, remember a selected setting and support security checks. You can manage browser cookie controls, although changing them may affect account access or lobby continuity.

Account security

Phone verification is part of the account access path. Never send us a wallet PIN or password; when a request needs confirmation, we use account details that can be matched safely.

Retention

We retain records only while they support account operation, security, payment matching or a legal need. When a retention reason ends, handling follows the applicable removal or archival process.

Change requests

You can ask what data is linked to your account, request a correction or ask about removal through support. Include the affected account step so we can route the request accurately.

Browse Privacy Policy Answers

These Privacy Policy answers address the searches we hear most often before account creation. They cover the data connected to your phone verification, wallet activity, cookies, device access and requests sent through the macan123 account path.

It covers account details, phone verification, device and session signals, cookies, payment references and support requests. It also explains retention, security handling and ways to ask for correction or removal.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match account transactions, not to request your wallet PIN.

Phone verification helps connect a privacy request to the correct account and helps protect access. We may ask for a matching account detail when you request data changes or discuss a payment record.

Cookies can support login continuity, security checks and saved settings. You can adjust browser controls, but blocking some cookies may interrupt account access or require you to repeat a verification step.

You can contact us through the signed-in account support path and ask for correction, removal or a copy of linked data. We first match the request to your account and any retention need.

The policy covers practical session and device signals used for access continuity and security checks. It does not give us a reason to read unrelated files, messages or wallet credentials on your device.

Yes. Account access and eligibility depends on local law. We apply the Privacy Policy where local law permits, and our support route can explain which account step applies to your request.