Reference

Privacy Policy For Your kribo88 Account

kribo88 Privacy Policy explains what we collect when you open an account, use a mobile browser, check wallet status, or contact support, and why each detail is needed.

Account recordsWallet referencesCookie choicesAccess requests
kribo88 Privacy Policy For Your kribo88 Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

Privacy questions should not slow down your account path. We keep the support route close to account access so you can ask what a record means, why a verification step appeared, or how a payment receipt is matched. Include the phone number or account detail connected to your request, but do not send a wallet password or full payment credentials. We use the details you provide to locate the case and respond through the support path shown in your account area.

Team online

Account request

Ask us to explain an account record or phone-verification detail through the support path beside your account area. We may ask for enough account information to confirm that the request concerns you before discussing stored data.

Receipt question

If a DANA, OVO, GoPay or QRIS reference appears in a privacy query, attach the receipt number and date rather than wallet credentials. We use that reference to locate the record and clarify its handling.

Access change

For a copy, correction or deletion request, state the exact account detail and preferred outcome. We assess the request under local requirements, confirm your identity, then explain the next step where local law permits.

DATA CONTROL

What You Can Control In Privacy Settings

We treat Privacy Policy requests as account tasks, not as a reason to collect extra details. Our handling covers the records created during login, phone verification, mobile browsing, wallet checks and support…

Data collected

We may hold your account contact, phone-verification result, login events, device and browser signals, payment reference, support messages and choices made during cookie consent. We collect these categories for access, security, payment matching and support handling.

Cookie use

Cookies and similar browser storage can keep your session connected while you move from login to the lobby on mobile. They can also help us remember a privacy choice. You can clear browser storage, though this may require another account login.

Account security

Phone verification helps connect account access with the contact detail you supplied. We also examine login timing, device signals and unusual account changes. Never share a password, wallet PIN or verification code in a support request.

Retention timing

We keep records while they support account operation, payment reconciliation, security checks or a legal requirement. When a purpose ends, we remove or anonymise the relevant record unless another valid reason requires continued storage.

Your request

You may ask for access, correction, deletion or an explanation of processing through the account support path. Include a clear request and the contact detail used for the account so we can check identity before responding.

Policy contact

For a Privacy Policy question, use the support route shown beside your account area and identify the relevant date, device path or payment reference. We will explain what we can do under local law and what confirmation is needed.

Privacy Policy Questions For kribo88

These Privacy Policy answers cover the account moments that most often raise questions: opening access, using a phone, checking DANA or QRIS status, changing stored details and asking for a copy. We keep each answer tied to the way our account path works, while legal rights and eligibility remain dependent on the rules that apply to you in Indonesia.

It covers data created when you open or access an account, complete phone verification, browse on mobile, check a wallet reference, use cookies or contact support. It explains purposes, retention, security handling and the routes available for access or correction where local law permits.

We use the verification result to connect account access with the contact detail you supplied and to reduce unauthorised changes. It is not a request for your wallet PIN or verification code. If the detail is wrong, ask for a correction through the account support path.

Yes. We may store a payment reference, date, amount status or reconciliation result linked to DANA, OVO, GoPay or QRIS. These records help us identify a receipt or status issue; they do not give us your wallet password or private wallet credentials.

Use the support route shown beside your account area and ask for an account-data access request. Name the contact detail connected to the account and describe the records you want. We may verify your identity before providing a response, where local law permits.

You can request a correction when an account contact detail, phone-verification result or support record is inaccurate. Tell us what appears wrong and what it should say. We will check the account record, update it when appropriate and explain any legal reason for keeping an older entry.

Retention depends on the purpose. We keep account, device, payment-reference or support records while they are needed for access, reconciliation, security or a legal duty. After that, we remove or anonymise them unless another valid requirement applies. You may ask why a record remains.

Yes, you can ask for deletion through the account support path, and we will assess the request under the rules that apply to your account. Some records may remain for security, payment reconciliation or legal duties. We will explain the result and any reason for continued retention.