Reference

Privacy Policy For Your combat123 Account

combat123 Privacy Policy shows what we collect, why we use it and how you can request changes before opening an account.

Clear data purposesWallet record contextDevice access controlsChange request path
combat123 Privacy Policy For Your combat123 Account
HELP WITH PRIVACY

Reach Us About Your Data

A clear support route matters when a Privacy Policy question concerns your login, wallet status or a receipt. Start from the account support path and select the privacy request option, then include the phone or account detail needed to locate your record. We use the support channel displayed in your account for status checks and follow-up, so you do not need to send wallet passwords or full payment credentials.

Team online

Privacy request

Use the privacy option inside account support when you want a copy of your stored details, a correction to an account field or an explanation of a data purpose. Include your account phone reference so we can match the request without asking for your DANA, OVO or GoPay password.

Wallet status query

If a QRIS, bank transfer or virtual account receipt appears under the wrong status, contact us through the account support path. Share the transaction reference and date, not a wallet PIN. We can compare the payment record with your account while keeping sensitive credentials out of messages.

Login access help

A sign-in concern can involve device data, phone verification or an unfamiliar session. Choose account help from the support area and describe the device path you used, such as mobile browser or desktop. We use those details to check access events and respond through the displayed channel.

DATA CONTROL POINTS

What Our Privacy Process Covers

Privacy at combat123 is handled through practical account controls rather than vague promises. We separate login records from wallet references where the workflow allows, limit staff access to what a support case…

Account details

When you open an account, we use the details needed for phone verification and account access. Your phone reference helps us connect a login to the right account, while support notes remain tied to the case that created them. We do not need your wallet PIN for this step.

Payment references

A DANA, OVO, GoPay or QRIS transaction may create a reference, amount and status record in the account workflow. Bank transfer and virtual account checks can also show a BCA, BRI, Mandiri or BNI reference. These records help reconcile a receipt without storing wallet passwords.

Cookies and browser storage

Cookies can keep a session active, remember a selected language or support basic security checks. You can clear them in your mobile browser or desktop settings, although doing so may require another login. Our Privacy Policy treats these files as access tools, not as a reason to collect unrelated content.

Device security

We may log device type, browser signals, login time and session events to help identify an unfamiliar sign-in. If you move from mobile to desktop, those events can appear as separate access records. Tell support which device path you used when asking us to check a session.

Retention choices

We retain account, support and transaction references only while they serve account security, payment reconciliation or a legal need. When a purpose ends, records can be removed or changed into a form that no longer points directly to you. Ask support to explain the retention reason for a specific record.

Your requests

You can ask for access, correction, deletion where available, or clarification about how a record is used. Send the request through the account support path and identify the relevant login, receipt or message. We may ask for a safe account check before changing personal data.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account steps you are most likely to check before using combat123 from Indonesia. They cover phone verification, local wallet references, mobile browsers, cookies, retention and requests for a copy or correction. If your question involves eligibility, access depends on local law and the support path in your account can explain the next step.

The combat123 Privacy Policy covers account details, phone verification, login events, device signals, cookies, support messages and payment references. It explains why we use each category, how long operational records may remain and how you can request access or correction through the account support path.

Yes. Privacy Policy coverage includes references created when DANA, OVO, GoPay or QRIS is selected for a payment step. We may use the reference, status and timing to reconcile your account, but you should never send us a wallet PIN or password.

Your phone reference supports account verification, while device type, browser signals and login timing help us check unfamiliar access. These records are connected to security and account support. If a device entry looks wrong, describe your mobile or desktop path through account support.

You can request a copy of personal data linked to your account through the privacy request option in account support. Tell us whether you mean login records, support messages or payment references. We may complete a safe account check before releasing details to the verified account holder.

Send a correction request through the combat123 account support path and name the field or transaction reference that appears wrong. For QRIS, DANA, OVO or bank transfer matters, include the receipt date and reference, while keeping wallet credentials private.

We keep records while they support account security, payment reconciliation, support handling or a legal need. The period can differ by record type. You can ask why a particular login, receipt or message remains stored, and we will explain the relevant retention purpose.

Open the account support area and choose the privacy request route shown there. Include your account phone reference and a short description of the question. Do not include a wallet PIN, full password or unnecessary payment credentials; access depends on local law.