Reference

ibcmax Privacy Policy, Clearly Explained

ibcmax Privacy Policy sets out how we collect, use, protect and retain data when you open an account, sign in, use the lobby or contact support.

Account dataWallet recordsDevice controlsPolicy access
Explore Our Lobby Read FAQ
ibcmax ibcmax Privacy Policy, Clearly Explained
CONTACT ROUTES

Get Privacy Policy Help Through Support

A clear support route helps when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record.

Policy questions Send a Privacy Policy question through the support path linked to your ibcmax account. We use your account identifier and the subject of your request to route the query, while asking you to leave passwords and one-time codes out of the message.
Data correction If your phone number, email address or verification detail needs correction, tell us which field is wrong and why. We may ask you to complete an account check before changing it, helping prevent another person from taking over your profile.
Wallet records For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, include the payment reference and date. We compare that reference with our account record and explain the status without requesting your wallet PIN or private login code.
DATA PRACTICES

How ibcmax Handles Privacy Details

We separate account operation from the data needed to answer a specific request. The lobby may receive device and sign-in signals so the account path works on mobile or desktop, while payment…

Account data

We use your account details to create access, complete phone verification, respond to support and connect activity with the correct profile. We do not need your wallet PIN or one-time code in a support message, so keep those private whenever you contact us.

Payment references

A DANA, OVO, GoPay or QRIS record can include a reference, amount, status and time needed for account reconciliation. Bank transfer and virtual account records follow the same purpose: matching a payment event without storing more wallet data than required.

Cookies and sessions

Cookies and browser storage help keep your signed-in session, remember selected settings and support security checks. If you clear them, you may need to verify your account again before reaching the lobby or viewing a saved payment status.

Device security

We may record device type, browser details, sign-in time and security signals when you access the account from a phone or desktop. These records help us investigate unusual access and protect your profile without giving support your private device passcode.

Retention

We retain account, support and payment records for as long as needed for the purpose described in this policy, account security, dispute handling or legal duties. When a record is no longer needed, we assess it for deletion or a form that no longer identifies you.

Your requests

You can ask what personal data we hold, request a correction, ask about deletion eligibility or object to a use where applicable. Send the request from your account route and identify the relevant record; we may verify ownership before making a change.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the account and wallet questions you are most likely to have before opening access or contacting us. We explain the practical steps for Indonesian account holders, including phone verification, mobile sessions and payment references. If your situation is not covered, use the support path with the smallest useful amount of detail. Eligibility depends on local law, and our team can clarify how the policy applies where local law permits.

The ibcmax Privacy Policy covers account details, phone verification, sign-in signals, cookies, support messages and payment references. It explains why we use those records for access, security, reconciliation and service contact, plus how you can ask about, correct or remove eligible data.

We collect the details needed to create and secure your account, such as contact data, phone verification status and sign-in records. If you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may also retain the payment reference and status.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use these details to match an account event and check status; do not send us your wallet PIN or one-time code.

We use device and browser signals to keep your session working, support security checks and investigate unusual sign-ins. Cookies can remember session settings. Clearing browser storage may sign you out or require phone verification before you return to the account area.

You can contact support from the account path and ask what eligible data we hold or request a correction. Name the field or record, such as a phone detail or payment reference. We may verify account ownership before sharing data or applying a change.

We keep personal data for the period needed to operate the account, protect access, answer disputes, reconcile payments or meet legal duties. The exact period depends on the record and purpose. When retention is no longer needed, we assess deletion or de-identification.

Where local law permits, you can ask whether eligible data may be deleted. Some records may need to remain for account security, payment reconciliation, dispute handling or legal duties. Send the request through support with your account identifier, not your private sign-in codes.

Related Pages

ibcmax Indonesia Access guide Goal Mobile Play ibcmax Casino Esports Free Fire