Reference

bento124 Privacy Policy For Indonesia

bento124 Privacy Policy explains how we handle the account, wallet and device data connected with your access to our Indonesia lobby.

Account dataWallet recordsCookie choicesPhone verification
bento124 bento124 Privacy Policy For Indonesia
CONTACT PATHS

Get Privacy Policy Help Near Account Support

A clear contact route helps when you need to ask about a data record, cookie choice or account detail. Start from the account help route and include the phone number or email linked to your account, without sending a wallet password or full banking credential. Our support team can direct a Privacy Policy request to the right review path, including a payment receipt or status reference when your question concerns DANA, QRIS, OVO or GoPay.

Team online

Account help

Use the account help route when you want to ask what personal data is linked to your bento124 account. Include your registered contact detail and a short description of the request; we will ask for only the checks needed to locate the correct record.

Cashier status

For a Privacy Policy question about a wallet or transfer record, share the payment reference rather than your password. Our cashier path can help identify whether the record relates to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Security concern

If you suspect another device has entered your account, contact support through the account route promptly. Tell us the device type, approximate sign-in time and affected account step so we can review session activity without asking you to reveal secret credentials.

DATA PRACTICES

How bento124 Applies Privacy Policy Controls

We keep the Privacy Policy practical by connecting each data use to an account or security task.

Account collection

When you create an account, we collect the details needed to identify the account and complete phone verification before access. This can include your contact detail and sign-in record. We do not ask you to place a wallet password in a support message.

Device signals

A mobile browser or desktop session may send device, browser, IP and session signals. We use these details to recognise unusual sign-ins, keep the lobby connected after login and investigate an access issue without treating your device as a permanent identity.

Cookie choices

Cookies and similar storage can keep your session active, remember selected settings and help us detect account misuse. You can manage browser cookie controls on your phone or desktop. Blocking some cookies may require another sign-in or limit a requested account function.

Wallet references

DANA, OVO, GoPay and QRIS may provide a reference, amount and status tied to a transaction request. Bank transfer and virtual account records can serve the same reconciliation purpose. We use these references to match status, not to request your private wallet credential.

Security checks

Phone verification, sign-in records and unusual-device checks help us protect your account. If a request involves changing account data or discussing a payment record, we may ask you to confirm the registered contact detail before we disclose or amend anything.

Retention requests

We retain data while it supports account operation, security review, payment reconciliation, dispute handling or a legal duty. You can ask what we hold, request a correction or ask about deletion through support. Some records may remain where a valid legal or security reason applies.

Privacy Policy Questions For Your Account

These Privacy Policy answers cover the account steps and data questions you are most likely to have before opening access. They also explain how payment references, device sessions and contact requests fit together. If your situation is different, use the account help route and give us enough detail to find the relevant record without sharing a password.

The bento124 Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages, payment references and security records. It applies when you open an account, sign in, use the lobby, contact support or check a DANA, OVO, GoPay, QRIS or transfer status.

We use phone verification to connect the account to a confirmed contact route before access and to help detect unusual sign-ins. It also gives support a safer way to locate your account. Access depends on local law, and we do not need your wallet password for this check.

Yes. The Privacy Policy covers transaction references and status details created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer or a virtual account. These records help us reconcile a request and investigate a receipt without storing your private wallet credential.

We use device and session signals to keep your sign-in connected, identify unusual access and investigate account problems. Cookies can remember settings and session state. You can adjust browser controls on a phone or desktop, although blocking some cookies may require another sign-in.

Yes. Send a correction request through account help using the contact detail registered to your account. Explain which record is wrong and provide the accurate detail. We may verify the request before changing it, especially where the record relates to phone access or a payment status.

You can ask which data we retain and request deletion through support. We assess the request against account security, payment reconciliation, dispute handling and legal duties. Some records may need to remain for a valid reason, and we will explain the applicable reason where we can.

Use the account help route and state that your request concerns the Privacy Policy. Include your registered contact detail, the affected account step and, for wallet matters, the payment reference. Do not send passwords, full banking credentials or private wallet access codes.