Reference

ibc88 Privacy Policy For Your Account

The ibc88 Privacy Policy explains how we collect, use and protect the details connected with your account, wallet activity and device access.

Account dataWallet recordsDevice accessPolicy requests
ibc88 ibc88 Privacy Policy For Your Account
CONTACT YOUR WAY

Get Privacy Help Near The Cashier Path

A clear contact route helps you ask about the Privacy Policy without placing sensitive details in the wrong message.

Live chat Use live chat from the signed-in account when you need to ask how we use phone verification data, a device signal or a DANA, OVO, GoPay or QRIS payment reference. We can keep the conversation connected to the correct account without asking you to post a password.
Account form The account contact form gives you a written path for Privacy Policy questions, access requests and correction requests. Include the email or phone detail attached to your account, the subject of your request and a safe way for us to reply. Do not attach unnecessary identity documents.
Payment context When your question concerns a bank transfer, virtual account or QRIS receipt, share only the reference details needed to locate the event. Our support team can check status and explain which data is retained while keeping your login secret and wallet credentials private.
DATA HANDLING

What We Do With Your Account Details

The Privacy Policy is built around the information needed to operate an account and respond to a real request.

Account records

We use your account contact details to create and maintain access, send service messages and connect a support request with the right account. Phone verification is handled as an access step, not as a reason to request unrelated personal details. Keep your sign-in information private and contact us if it changes.

Payment records

A DANA, OVO, GoPay or QRIS reference can show that a payment event was submitted and help us compare its status with a bank transfer or virtual account record. We retain the operational record needed for reconciliation, support and applicable legal duties, without asking you to send a wallet password.

Device signals

When you move from phone login to the lobby, we may process browser type, device characteristics, IP-related signals and session times. These details help detect unusual access and protect the account. They are not used as a request for permission to read unrelated files, contacts or messages on your device.

Cookies

Cookies can preserve a sign-in session, remember selected settings and help us understand whether a page request completed. You can adjust cookie controls in your browser. If you block necessary cookies, the account path may ask you to authenticate again before showing wallet status or account support.

Retention periods

We keep each category only for the period needed for its stated purpose, account security, dispute handling or a legal requirement. Retention can differ between account details, payment references, security logs and support messages. Ask support to explain the category linked to your request rather than sending a full account history.

Your requests

You can contact us to ask for access, correction, deletion where available, or an explanation of how a specific detail is used. We may verify that the request comes from the account holder before changing records. If a request cannot be completed, we will explain the relevant security or legal reason.

Privacy Policy Answers For ibc88 Accounts

These Privacy Policy answers address the account and payment questions we hear most often from people using ibc88 in Indonesia. They explain what to prepare, which contact path to use and how local payment references or device activity fit into our handling of account data. If your situation is different, send a focused request through live chat or the signed-in contact form. Access depends on local law.

It covers details you provide for an account, phone verification, support conversations, payment references and device or session signals. It also explains cookies, retention, security use and request paths. The policy applies to the account services we provide where local law permits and does not require unrelated personal details.

Phone verification helps connect access to the correct account and gives us a security check when an account session changes. We may use the result to investigate unusual login activity or support a recovery request. Do not send your verification code to support; we will not need your private code.

Yes. The policy covers payment references and status details created when you use DANA, OVO, GoPay or QRIS. We may also process bank transfer and virtual account references to reconcile a transaction, answer a receipt question or meet a legal duty. Wallet passwords are not needed for support.

Where local law permits, you can request access to the personal details connected with your account. Use signed-in live chat or the account contact form, state that you are making a Privacy Policy access request and provide the account contact detail needed for verification. We may ask a safe identity check.

Send a correction request through the account contact form or live chat, describing the specific field that is inaccurate and the correct value. We may verify account ownership before changing it. For a payment reference, include only the relevant DANA, OVO, GoPay, QRIS, bank or virtual account detail.

You may ask about deletion where local law permits, but some records can need to remain for security, dispute handling or a legal requirement. Tell support which category you mean, such as account details, a device signal or a payment reference. We will explain any limit rather than silently ignoring the request.

Contact us through signed-in live chat or the account form and name the browser, device path or cookie question. We can explain how session cookies and security signals relate to access. You can also change browser cookie settings, although blocking necessary cookies may require another login step.