Reference

koko110 Privacy Policy For Your Account

koko110 Privacy Policy sets out what we collect when you create an account, sign in from a phone, or connect DANA, OVO, GoPay or QRIS.

Clear data purposesWallet details explainedAccount access controlsIndonesia privacy contact
Explore Our Lobby Read FAQ
koko110 koko110 Privacy Policy For Your Account
PRIVATE HELP PATHS

Get Privacy Help Near Your Wallet

A clear contact route matters when a data question appears beside a payment receipt or a stalled login. From your account support path, tell us whether your request concerns phone verification, a DANA or QRIS reference, device access or a message sent to our team. We ask for enough detail to locate your account, not your wallet password. If you are contacting us from Yogyakarta or elsewhere in Indonesia, include the relevant date and account step so we can separate a privacy request from a payment-status question.

Team online

Account support path

Use the support route connected to your account when you want to ask what personal data we hold. Include your registered phone number and the specific request, while leaving out your DANA, OVO or GoPay password.

Cashier reference check

For a privacy question about QRIS, virtual account or bank transfer records, share the receipt reference and approximate time. We use that narrow detail to locate the transaction without asking you to send a full wallet statement.

Access correction request

If your name, phone detail or device record needs correction, identify the account step that shows the issue. We may ask for phone verification before changing account data, helping keep another person from altering your record.

DATA HANDLING

What We Protect And Retain

We keep this policy practical by linking each data action to an account task. Registration details support phone verification; device signals help us spot unusual sign-in activity; payment references help reconcile DANA…

Account details

We may hold the phone number and registration details you provide for account creation and verification. These fields help us distinguish your account from another sign-in and let support respond to a request about the correct record.

Device signals

A mobile browser or desktop browser can send technical signals such as session data and browser type. We use them to maintain sign-in continuity and identify unusual access, rather than to request the password for your wallet.

Wallet references

DANA, OVO, GoPay and QRIS may appear through a transaction reference or status record. For bank transfer and virtual account checks, we keep the payment detail needed to match your request without treating it as your wallet login.

Cookies and sessions

Cookies can keep your account session working and remember necessary browser settings. You can adjust cookie controls in your browser, although turning off necessary cookies may interrupt phone verification or return you to the login screen.

Security access

We use account checks before discussing private records or changing registered details. Keep your phone verification code private, sign out on shared devices, and contact support if a login appears that you did not make.

Retention requests

You may ask why a record remains, request a correction, or ask whether deletion is available. We assess the request against the original account or payment purpose and applicable requirements, then reply through the contact route linked to your account.

Privacy Policy Answers For koko110

These Privacy Policy answers address the account questions we expect before you open access. They cover wallet references, browser use, phone verification, retention and requests made from Indonesia. If your situation is not listed, use the account support path and describe the exact screen or payment reference involved. Access and eligibility depends on local law, so our reply may vary by your location and the request you make.

The koko110 Privacy Policy covers registration details, phone verification, sign-in and device records, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, virtual account and bank transfer. It explains why we use each category and how you can ask about your own data.

No. Our Privacy Policy does not require your DANA, OVO or GoPay wallet password. We may use a transaction reference, amount and status supplied through the payment process to match a receipt or account request. Never send a wallet password or verification code to support.

Phone verification connects an account request to the correct registered detail and helps prevent another person from changing private data. We may ask for this step before discussing an account record or correcting a phone number. The process remains subject to where local law permits.

When you sign in through a mobile browser, we may receive technical details such as browser type, session identifiers and device signals. These support account continuity and unusual-access checks. We do not need access to unrelated files, contacts or your wallet password for this purpose.

Use the account support path and state whether you want access to a record or correction of a specific field. Include your registered phone number and the screen or account step involved. We may verify ownership first, then assess the request where local law permits.

We retain payment references only for the period connected with account support, reconciliation, security or applicable requirements. A QRIS receipt, virtual account reference or bank transfer detail may therefore remain after the original action. Ask support why a particular record is still retained.

You can request deletion through the account support route, and we will assess which records can be removed. Some account, security or payment records may need to remain for an applicable purpose. We will explain the result and any required phone verification where local law permits.

Related Pages

koko110 Indonesia Liga 1 Over Under FAQ Komodo Gold Reels Access guide