Reference

kabehjitu Privacy Policy: Know Your Data Choices

Our Privacy Policy explains how we collect, use and protect the account details connected with Blackjack, Pyramid Bonanza, Mobile Legends and other lobby areas.

Account dataWallet recordsDevice choicesCookie controls
kabehjitu kabehjitu Privacy Policy: Know Your Data Choices
CONTACT PATHS

Reach Support About Your Privacy Policy

A clear contact path helps you act on the Privacy Policy without guessing where to start. Use the support route inside your account when you need a copy of your stored details, want to question a wallet record or need help with a phone-verification entry. Include the account identifier and the relevant date so we can locate the request without asking for unnecessary payment credentials.

Team online

Account help

Open the account support route for a Privacy Policy request, then identify the account email or phone number linked to your access. We use those details to confirm the request belongs to you.

Wallet records

For a DANA, OVO, GoPay or QRIS privacy question, share the transaction reference and date rather than a wallet password or full security code. Our support path checks the related account record.

Access concerns

If phone verification or a device check blocks your privacy request, tell us which step stopped and whether you used mobile or desktop access. We will explain the next account-security step.

DATA HANDLING

Check What We Store And Why

Privacy works best when each record has a clear purpose. We separate account information, payment references, support messages and technical security logs so a request can be handled with limited access.

Account details

We may store your name, phone number, email address and phone-verification result to create and protect your account. We use these fields for account access and related support, not as a public profile.

Payment references

A DANA, OVO, GoPay or QRIS record can include a reference, amount status and time without exposing your wallet password. Bank transfer and virtual account matching follows the same limited-purpose approach.

Cookies and devices

Cookies and device signals can keep a session active, remember selected settings or flag unusual login patterns. You can review cookie controls in your browser, while disabling them may affect account access.

Account security

Phone verification, login records and device checks help us investigate access that does not match your usual pattern. We do not ask for your wallet PIN or full authentication secret through support.

Retention approach

We keep each category only for the period needed to provide the requested account service, investigate a security event, reconcile a payment record or meet a legal requirement.

Change requests

You can ask us to correct inaccurate account details, explain a stored record or request deletion where permitted. We may verify your phone or account identifier before making a change.

Find Answers About Privacy Policy

These common Privacy Policy questions focus on the account steps and local wallet records you are most likely to check before opening an account. If your situation is not covered, use the account support path and include only the information needed to identify your request.

The kabehjitu Privacy Policy covers account details, phone verification, device and cookie signals, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create and protect the account, complete the phone-verification step before access, and investigate sign-in issues. We do not request a wallet PIN through the Privacy Policy support route.

Yes. The Privacy Policy explains that DANA and QRIS references may include a transaction identifier, status and time so we can match account activity and answer payment-status questions without storing wallet secrets.

You can contact account support to request the account data we hold about you. Include your account email or phone number, and we may verify ownership before preparing the requested copy.

Send a correction request through the account support path and identify the inaccurate field, such as an email or phone number. We may ask for a verification step before changing the record.

We retain payment references only as long as needed for account service, reconciliation, security checks or legal duties. The Privacy Policy distinguishes transaction references from wallet passwords and authentication secrets.

You may request deletion of eligible personal data through account support. We assess the request under applicable requirements because some records may need to remain for security, reconciliation or legal duties.