Reference

kebo88 Privacy Policy for Your Account

Our Privacy Policy explains how kebo88 handles the details you provide during account creation, phone verification and wallet activity.

Account dataCookie choicesWallet recordsContact steps
kebo88 kebo88 Privacy Policy for Your Account
ACCOUNT HELP PATH

Contact Us About Privacy Choices

A clear contact route matters when your account data needs attention.

Privacy request Send a request through the support path beside login, identify the account record you…
Wallet record For DANA, OVO, GoPay or QRIS data, include the payment reference and date rather…
Access concern If phone verification or a device session looks unfamiliar, contact support from the account…
SECURITY BY DESIGN

Security From Login Through Retention

We treat the Privacy Policy as an operating rule, not a footer link. Account access begins with the details you submit and the phone verification step, while device and session records help…

Data collection

We collect details you enter for an account, phone verification results, device signals, session events and payment references. We use each category for a stated account, security, support or legal purpose.

Cookie choices

Cookies and similar device storage can help keep a session available and remember selected settings. You can manage browser permissions, though refusing some storage may affect login or policy preference handling.

Account security

Never place a password, wallet PIN or one-time code in a support message. Phone verification and session checks help us discuss protected account details with the right account holder.

Payment separation

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help identify transaction status. We do not need your private wallet credential to investigate a receipt or account match.

Retention rules

We keep account and support records only while they serve the stated purpose, protect the service, resolve a dispute or meet an applicable legal duty. Removal timing can depend on the record type.

Change requests

Ask for access, correction or a privacy preference change through the support route beside login and the cashier area. Add your account identifier so we can verify the request without exposing data.

Privacy Policy Questions Before You Join

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening access. We keep the route practical: check the policy, complete phone verification, and use the support path beside login when a personal-data request needs a direct answer. Access remains where local law permits.

It covers data you provide for account creation and phone verification, device and session details, support messages, cookies, and payment references linked to DANA, OVO, GoPay, QRIS or bank routes.

Phone verification helps connect account access with the correct account holder and supports security checks. We use the result for access and protection purposes, and you should not send verification codes to support.

Yes. The policy includes payment references and status records connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. Wallet PINs are not needed for support matching.

Use the support route shown beside login and the cashier area, write Privacy Policy in the subject, and include your account identifier. We may complete account checks before discussing protected records.

You can request a correction through the same support path. State which account detail is inaccurate and provide the replacement detail carefully; we may verify ownership before changing the record.

Cookies or related device storage can keep login preferences and session settings available on your phone. Browser controls can limit them, but some account or preference functions may then require repeated steps.

Retention depends on the data type and its purpose. We keep records while needed for account support, security, dispute handling or an applicable legal duty, then assess whether continued storage is needed.