Reference

kombo 99 Privacy Policy Explained

Our Privacy Policy explains what we collect when you open an account, check DANA or QRIS status, and move between the lobby and Live Blackjack Table.

Account dataWallet recordsCookie choicesSecurity checks
kombo 99 kombo 99 Privacy Policy Explained
CONTACT WHEN NEEDED

Privacy Help Beside Your Account

A direct support path helps you act on this Privacy Policy without searching through unrelated account screens. Start from the support chat linked to your account area and include the email or phone used for access, the affected device and the request you want handled. We may ask for a transaction reference, but never ask you to send a wallet password or one-time security code. Your request can concern a data copy, correction, deletion, cookie choice or an explanation of a DANA, OVO, GoPay or QRIS record.

Team online

Account privacy request

Send a privacy request from the support chat inside your account area. Include your registered phone or email, the exact record you are asking about and a safe way for us to reply. We use the account step to reduce the chance that another person receives your personal data.

Wallet record query

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, share the transaction identifier and date through support chat. We compare it with the account record and payment status, while keeping wallet passwords, card secrets and one-time codes out of the conversation.

Access and cookie help

For cookie choices, device access or a sign-in concern, tell us whether you are using a mobile browser or desktop browser. We can explain which data supports account security and which browser setting affects a saved session, without asking you to disclose your password.

DATA HANDLING PROMISE

Inside Our Privacy Controls

Privacy work is practical: we separate account identification, wallet references, browser signals and support content so each request can be handled for a clear reason.

Account data collected

When you open an account, we may collect your name or chosen account label, phone number, email address, verification result and sign-in events. These fields let us identify the correct account, answer a privacy request and detect an unusual access attempt before account-linked data is disclosed.

Payment references

A DANA, OVO, GoPay or QRIS action can create a reference number, amount status and timestamp in our records. Bank transfer and virtual account steps can create similar reconciliation data. We use these items to match receipts and resolve status questions, not to read your private wallet credentials.

Cookies and devices

Our browser may store a session cookie and device signals that keep your account path working between login and the lobby. You can clear cookies in your browser settings, although doing so may sign you out or require phone verification again. We explain any necessary cookie use when it affects access.

Account security

We monitor sign-in events, device changes and verification steps to protect your account. If access looks unusual, we may pause a sensitive action and ask you to confirm the registered phone or email. Never place a password or one-time code in support chat, even when asking about this Privacy Policy.

Retention and deletion

We keep account, payment and support records for as long as needed to provide the requested service, investigate security events or meet applicable legal duties. When a retention reason ends, eligible data can be deleted or separated from your account. A deletion request may therefore receive a reasoned scope response.

Changes to your data

You can ask us to correct an outdated phone number, email address or account detail through the support route. We verify the request before making a change, record what was adjusted and explain any field that must remain for transaction or security records. Access remains subject to local law.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account, device and wallet questions you may have before opening an account or contacting us. We keep the route practical: identify the account, describe the data request and use support chat when a record needs checking. Where access or eligibility is discussed, it depends on local law, and a payment reference does not give us access to private wallet credentials.

It covers account details, phone verification, sign-in events, device and cookie signals, support messages, payment references and records needed for security or legal duties. It also explains your request rights, retention approach and contact route when you want a copy, correction or deletion of eligible data.

No. When you use DANA, OVO, GoPay or QRIS, we handle transaction references and status results needed to match an account action. We do not ask for wallet passwords or one-time codes in support chat, and those secrets should never be sent to us.

A session cookie can keep your sign-in path active while you move from account access to the lobby. Device signals may help identify an unusual sign-in. You can clear cookies through your mobile browser settings, but this may sign you out and trigger phone verification again.

Open support chat from your account area and ask for a personal data copy. Include the registered phone or email and describe the records you need, such as sign-in events or a QRIS receipt. We verify account control before sending account-linked data to the correct person.

Yes, you can ask us to correct inaccurate account details or delete eligible data through support chat. We first confirm the request belongs to you. Some payment, security or legal records may need to remain for a defined period, and we explain that scope in our reply.

We retain payment references, account records and support content only while needed for the requested service, security checks or applicable legal duties. A DANA, OVO, GoPay, QRIS, bank transfer or virtual account record may therefore remain after a transaction while its reconciliation or retention reason continues.

Use the support chat connected to your account and label the request as a Privacy Policy concern. Tell us whether it involves account data, cookies, device access or a payment reference. Do not include your password or one-time code. Account access and eligibility depend on local law.