Reference

bonge slot Privacy Policy For Your Account

bonge slot Privacy Policy explains how we handle the details connected to your account, phone verification and wallet activity before you enter the lobby.

Clear data purposesWallet record controlsPhone verification contextMobile and desktop access
bonge slot bonge slot Privacy Policy For Your Account
CONTACT ROUTES

Switch To Support For Privacy Requests

A privacy question should reach the same support route used when login or wallet status stalls. From your account area, send the request with your registered phone detail and the subject of the record you want checked; do not include a wallet password. We use the account step and payment reference to confirm ownership before discussing personal data.

Team online

Account data request

Ask us to locate the account details linked to your registered phone verification. We may request an account step or matching record before discussing, correcting or supplying personal data.

Wallet record check

For DANA, OVO, GoPay or QRIS questions, include the relevant transaction reference and date. We check the payment record without asking you to share a wallet password or security code.

Access concern

If a mobile browser or desktop session shows unexpected account access, contact support through the account area and describe the device path. We can review the access context and guide the next security step.

DATA PRACTICES

Browse How We Handle Your Details

We keep this Privacy Policy practical by linking each data use to an account action you can recognise.

Account details

We handle your registration details, phone verification result and account preferences so we can identify the correct account during access, support and a request to change personal data.

Cookies and browser storage

Cookies can keep a session path and help us recognise requested pages. You can clear or restrict them in your browser, though account access may ask you to authenticate again.

Security signals

We may use device, browser and connection signals to notice unusual access around your account. These signals support security checks and are not a substitute for your phone verification.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference records. We use those references to match a cashier event without requesting your wallet password.

Retention approach

We keep account, support and transaction records for operational, security or legal needs. When a record no longer serves one of those purposes, our process removes or restricts it.

Changes and contact

You can ask about access, correction or deletion through the account support route. Include your registered phone detail and request type so we can verify ownership before making a change.

Open Answers About Privacy Policy

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain what we collect, how wallet references work, how browser access is handled and which account step helps us respond to your request.

It covers account details, phone verification, device and browser signals, cookies, support messages and wallet references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us confirm that an account request belongs to you. We may use that step before discussing personal records, correcting account details or responding to an access request.

Yes. The policy covers browser storage and device or connection signals when you access the account from a phone or desktop. Clearing cookies may require another sign-in during your next session.

We use payment references and status details to trace a cashier event, but you should never send a wallet password or security code through support. DANA and QRIS credentials remain with their payment service.

Use the account support route and state whether you want access or correction. Add your registered phone detail and the relevant record, then we verify ownership before responding to the request.

We retain account, support and transaction records while they serve operational, security or legal needs. After that, our internal process removes or restricts the record rather than keeping it indefinitely.

Access and eligibility depends on local law. We apply this policy where local law permits, and a local rule may affect whether an account or a particular data request can be processed.