Reference

Open macan33 Privacy Policy Before Account Access

macan33 Privacy Policy explains what we collect when you create an account, verify your phone, enter the lobby, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesPrivacy requests
macan33 Open macan33 Privacy Policy Before Account Access
CONTACT ROUTES

Ask About Your Privacy Policy Request

A clear contact path helps when you want to ask about stored data, a wallet receipt or an account-access record.

Account privacy request Use the support path connected to your account to ask for a copy, correction…
Payment record question For DANA, OVO, GoPay, QRIS or bank transfer records, attach the payment reference with…
Access and cookie help If a privacy notice does not load on your phone, tell us the device…
SECURITY PRACTICE

Explore How Account Data Stays Protected

Privacy is handled through account controls rather than a single statement. We separate phone verification from payment references, limit internal access to the records needed for a task, and use session and…

Data we receive

We receive the details you enter for an account, the phone verification result, device and session signals, and transaction references returned by DANA, OVO, GoPay, QRIS or bank rails.

Cookie controls

Cookies help keep your session open and remember policy choices. You can review cookie controls in your browser settings, although blocking required cookies may interrupt login or policy access.

Account security

Keep your phone, password and verification messages private. If a login looks unfamiliar, use the account support path and identify the affected session without sharing your password.

Retention approach

We retain account, security and payment-reference records for the operational, dispute or legal purpose that applies. When that purpose ends, records are removed or changed into non-identifying data.

Changing your details

Request a correction through account support and name the field that needs changing. We may ask for phone verification before changing identity or payment-linked details on your profile.

Who handles requests

Our account support path receives privacy questions, access requests and correction requests. Give us a clear description and registered phone number, while keeping wallet PINs and passwords out of the message.

Find Privacy Policy Answers Before Joining

These questions cover the points Indonesian customers usually check before opening an account. If your situation is different, use the account support path with the smallest amount of detail needed to locate your record, and keep passwords and wallet credentials private.

The macan33 Privacy Policy covers account details, phone verification, device and cookie signals, payment references, security logs, retention practices and requests to access or correct personal data.

No. We use payment references and status details for DANA, OVO, GoPay, QRIS, bank transfer or virtual account matching. You should never send a wallet PIN or full payment credential.

Phone verification helps connect an account request to the person controlling the registered number. We may also use it before changing identity or payment-linked details, so account records are not altered casually.

Use the account support path and ask for a personal-data copy. Include your registered phone number and a specific request, but leave out your password, verification code and wallet credentials.

Yes. Send a correction request through account support and identify the inaccurate field. We may request phone verification before changing profile or payment-linked data, particularly where the change affects account security.

Cookies support session continuity and remember your policy choices. Browser controls let you adjust them, but blocking required cookies can interrupt login, account verification or access to the Privacy Policy.

Yes. Requests and account access depend on local law. We handle privacy requests where local law permits and may retain or limit certain records when an operational, dispute or legal purpose requires it.