Reference

Explore bingkaibet Privacy Policy for Indonesia

Our Privacy Policy shows how we handle the account details behind your lobby access, including phone verification and payment status for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice choicesPrivacy requests
bingkaibet Explore bingkaibet Privacy Policy for Indonesia
CONTACT ROUTES

Reach us about your privacy record

A direct support route helps when you want to ask what account data we hold or why a wallet reference appears in your account history. Sign in first when possible, then send the request through the account support path so we can match it to the correct phone-verified account. Our 24/7 Support route can also help when access or payment status prevents you from reaching the request area.

Team online

Account privacy request

Sign in and send a privacy question from the account support path. We use your verified account details to locate the right record before discussing DANA, OVO, GoPay or QRIS references.

Wallet record question

If a bank transfer, virtual account or QRIS reference looks unfamiliar, include its date and status in your request. We can check the account record without asking you to share a wallet password.

24/7 Support route

When login trouble blocks the privacy form, use the available 24/7 Support path and explain that the request concerns personal data. We may ask for account details to confirm ownership.

ACCOUNT SAFEGUARDS

Check account data and device controls

Privacy is managed through practical account steps rather than broad promises. We separate account access, payment reconciliation and support handling, while using device and session signals to identify unusual sign-in patterns.

Data we receive

We receive details you submit during account creation and phone verification, plus sign-in events, device signals and payment references. These details help connect your request to the correct account without requiring wallet credentials.

Cookie choices

Cookies and similar device storage can keep your session available and help us understand basic page use. You can adjust browser controls, though some account or privacy-request steps may then need another sign-in.

Account protection

Phone verification is part of account access, and unusual device or session behaviour may trigger an ownership check. We use this step to reduce the chance of discussing private records with the wrong person.

Payment matching

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we use transaction references and status details to reconcile your account. We do not need your wallet password to answer a payment-data question.

Retention approach

We keep personal data only for the period needed to provide account access, resolve requests, prevent misuse and meet applicable record duties. When a record is no longer needed, our handling follows the relevant deletion process.

Changes and corrections

You can ask us to correct inaccurate account details, explain a data use or clarify a cookie choice through the account support path. Include the phone-verified account reference so we can process the request safely.

Find answers about Privacy Policy access

These Privacy Policy answers focus on the account and wallet questions you may have before opening an account. We keep the process tied to your verified account, the device you use and the payment reference involved, so you know what to include when contacting us.

It covers data collected through account creation, phone verification, sign-in, device use, support requests and payment references. It also explains cookies, retention, corrections and how to contact us about your records.

Yes. We may process DANA and QRIS transaction references or status details to match activity with your account. The same approach can apply to OVO, GoPay, bank transfer and virtual account records.

Phone verification helps connect account access and privacy requests to the correct person. It can also support an ownership check when a new device, unusual session or request involving private data appears.

Yes. Send a correction request through the account support path and identify the phone-verified account. Tell us which detail is inaccurate and, where useful, include the relevant wallet or transaction reference.

Cookies can keep your session active and help us understand basic page use. Browser controls may limit them, but you might need to sign in again before reaching account or privacy-request areas.

We retain data for the time needed to provide account access, handle support, prevent misuse and meet applicable record duties. The exact period can depend on the type of record and local requirements.

Access depends on local law and is available where local law permits. If your location or eligibility affects an account request, contact support so we can explain the applicable account steps.