Reference

maxim33 Privacy Policy For Your Account

maxim33 Privacy Policy explains how we collect, use and protect the details connected with your account, wallet status and access to our Indonesia lobby.

Clear data purposesWallet reference checksPhone verificationRequest a change
maxim33 maxim33 Privacy Policy For Your Account
HELP WHEN NEEDED

Privacy Questions Near Your Cashier

A direct support path helps when a privacy question appears beside a login or wallet status issue. Tell us which account step you reached, whether the matter concerns phone verification, a payment receipt or a data request, and include only the details needed to locate the record. Our support chat can explain the next step without asking you to post sensitive credentials in the conversation. If you are checking a QRIS or bank transfer reference, keep the receipt available while we match the request.

Team online

Account access

If phone verification or login access raises a Privacy Policy question, contact our support chat with your registered contact detail and a short description. We use that context to locate the right account path, while you should never send a password, one-time code or full wallet security credential.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, share the payment reference and status shown on your receipt. We can explain what operational data is being checked and help separate a cashier record from unrelated personal details.

Privacy requests

To ask for access, correction or removal of eligible account data, use the same support channel and write Privacy Policy request in your message. We may ask for an account step that confirms ownership before discussing records connected with your account.

DATA HANDLING

What We Protect Inside maxim33

Privacy is handled through ordinary account operations rather than hidden shortcuts. We connect a session to device and connection signals, keep wallet references for reconciliation, and use account security checks before discussing…

Account details

We use the contact and verification details you submit to create an account path, confirm that a request relates to you and send account-related replies. We do not need your password in a support message, and we ask you to keep one-time codes private.

Device signals

When you move from phone login to the lobby, we may record device, browser and connection signals linked with that session. These details help identify unusual access and protect the account; they are not a reason to collect unrelated files from your device.

Cookies

Cookies can keep a login path working and help us understand basic page function. You can manage them through your browser settings, although changing cookie controls may affect account access or the way a page remembers your session.

Payment references

A DANA, OVO, GoPay or QRIS reference can be retained with its status and time so we can reconcile a cashier request. Bank transfer and virtual account records serve the same operational purpose without requiring your wallet password or banking login.

Retention practice

We keep records while they support account operation, security checks, payment reconciliation, dispute handling or a legal requirement that applies to the service. When a record is no longer needed for those purposes, our process is to remove or anonymise it where practical.

Your request

You can ask what account data we hold, request a correction, ask about use or seek deletion where applicable. Send the request through support and identify the account safely; we may verify ownership before releasing or changing any record.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account questions you may have before using maxim33 from Indonesia. They cover the records created by login, phone verification and wallet activity, plus the practical route for asking us to explain or change a record. If your question concerns eligibility, access depends on local law and the location supported for your account.

It covers account details, phone verification, login and device signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains our purposes, retention approach, security checks and the way you can request access or correction.

Phone verification helps us connect an account request with the person who controls the registered contact path. It can support login security and ownership checks when you ask about account records. Never place your password or one-time code in support chat, even when asking about the Privacy Policy.

Yes. We may handle a DANA or QRIS reference, status and time when those details are needed to match a cashier request. The same approach applies to OVO, GoPay, bank transfer and virtual account records. We do not ask for your wallet password or banking login.

You can send an access request through our support chat and identify the account using a safe registered contact path. We may verify ownership before discussing records. Your request can cover account details, verification history, device signals, cookies or payment references held for operational purposes.

Message support with Privacy Policy request, describe the inaccurate field and provide the account contact path needed to locate it. For a payment mismatch, include the DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference shown on your receipt.

Retention depends on the reason a record exists. We may keep details while they support account operation, payment reconciliation, security checks, dispute handling or a legal requirement. When that purpose ends, our process is to remove or anonymise the record where practical.

You can ask us to delete eligible account data through support, and we will assess the request against the purpose and any applicable requirement to retain a record. Access to the account may depend on local law, and we will explain any part that cannot be removed.