Reference

bento 123 Privacy Policy Explained

bento 123 Privacy Policy shows how we handle the data linked to your account, mobile browser, phone verification and wallet activity.

Account dataWallet recordsCookie choicesAccess requests
bento 123 bento 123 Privacy Policy Explained
CONTACT ROUTES

Browse Support Options For Privacy Questions

A clear contact route helps when you want to ask about the Privacy Policy, correct account data or understand a wallet record.

Policy question Use the support path from your account area and name the Privacy Policy section…
Data correction Tell us which account detail needs changing and why it is inaccurate.
Wallet record For a DANA, OVO, GoPay or QRIS question, share the transaction reference and date…
DATA PRACTICES

Explore How We Handle Your Data

Privacy choices work better when you know what happens behind each account step.

Account creation

When you open an account, we collect the details needed to create your profile and begin phone verification.

Device signals

A mobile browser or desktop session may provide device, browser and security-event data.

Cookie choices

Cookies can keep your session working and help us remember selected settings.

Payment matching

Transaction references help us connect a payment receipt with DANA, QRIS, bank transfer or virtual account activity.

Retention period

We retain account, security and transaction records only for the period needed for the stated purpose, dispute handling and applicable…

Request handling

You can ask for access, correction or clarification through our account support path.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers address the searches we hear before an account is opened in Indonesia. They cover the data connected with sign-in, phone verification, mobile browsing and local wallet records. If your situation is not listed, use the account support path with a clear question and a transaction reference only when it is relevant.

It covers account details, phone verification, device and browser signals, cookies, security events, support records and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect the right person with an account and supports security checks during sign-in or data changes. We use the phone detail for those stated account purposes, where local law permits.

Yes. When you use a phone browser, we may receive browser, device and security-event signals needed for session protection. Your browser settings can control some cookies, but sign-in may be required again.

You can request access through the account support path. Include the profile detail needed to locate your account, avoid sending passwords or wallet PINs, and expect a verification step before release.

Send the correction request through account support and identify the inaccurate field. We may verify your phone or account details first, then apply the available change where local law permits.

We may retain transaction references, status and receipt details needed for account support and reconciliation. Do not send a DANA or QRIS PIN; the Privacy Policy does not require it.

Ask through the account support path and name the record type, such as a sign-in event or payment reference. We can explain the applicable retention purpose and any local-law condition.