Reference

Open bentogel Privacy Policy Before Access

Our bentogel Privacy Policy explains what we collect when you create an account, verify your phone, use the mobile lobby, or connect DANA and QRIS.

Account dataWallet detailsDevice cookiesContact choices
bentogel Open bentogel Privacy Policy Before Access
CONTACT ROUTES

Ask Support About Your Privacy Choices

A direct request helps us locate the right account record without exposing details in a public message.

Support chat Ask us to explain a Privacy Policy point, confirm which account details we hold…
Data request form Send an access, correction, deletion, or objection request through our contact form.
Cashier status path When a wallet reference appears in a privacy question, choose the cashier help path…
DATA PRACTICE

Explore How bentogel Handles Your Records

Privacy depends on practical controls, not a broad promise. We separate account credentials from payment-status references where our systems allow, restrict internal access by work need, and use account checks before discussing…

Account security

We use your phone verification and sign-in checks to reduce unauthorised account conversations. Never send a one-time code, wallet PIN, or password to support; our team does not need those secrets to process a privacy request.

Cookie controls

Our mobile browser path may store cookies for session continuity, language, and security signals. You can clear or block them in your browser settings, but the lobby may ask you to sign in again afterward.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account records are used to match payment status with the correct account. We do not ask you to provide a wallet secret when checking a receipt.

Retention period

We keep personal records for as long as needed for account administration, security checks, payment disputes, or legal duties. When a record no longer serves one of those needs, we remove or anonymise it.

Correction requests

If your phone number, email address, or account detail is inaccurate, contact us from the account route and identify the field to change. We may request a verification step before applying the correction.

Deletion requests

You can ask us to delete eligible personal data through support chat or the contact form. Some records may remain temporarily when needed for security, payment reconciliation, disputes, or legal requirements.

Check bentogel Privacy Policy Answers

These Privacy Policy answers cover the account actions you are most likely to take before using bentogel in Indonesia. They address phone verification, wallet references, cookies, data requests, retention, and local access wording so you know which route to use when a question arises.

It covers personal data connected with your account, phone verification, sign-in, mobile browser activity, cookies, payment-status references, support requests, retention, and requests to access, correct, or delete eligible records.

Phone verification helps us confirm that an account-access request belongs to you and reduces mistaken disclosures. We may use that check before discussing account data or changing a phone number.

Yes. We may retain a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference and its status to match a cashier event with your account. We do not need your wallet PIN.

Use support chat or our contact form from the signed-in account route where possible. State that you are making a data access request and provide enough account detail for us to verify the correct record.

You can request a correction or deletion through the same contact routes. We assess the request against account security, payment reconciliation, disputes, and legal retention needs before confirming what can change.

Cookies may support login continuity, language preferences, and security signals when you use the mobile browser path. Browser controls let you clear or block them, though another sign-in may be required.

Account access and eligibility depend on local law. Where local law permits, we handle data for the purposes described here, limit internal access by work need, and respond to verified privacy requests.