Reference

bumi110 Privacy Policy for Your Account

Our Privacy Policy explains how bumi110 handles the details connected with your account, including phone verification, login activity and wallet records for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
bumi110 bumi110 Privacy Policy for Your Account
ACCOUNT HELP ROUTES

Where To Ask About Privacy Policy

A clear contact route matters when your account record or wallet status needs attention. Start with the account help link beside login, then describe the requested correction or access matter without sending…

Account help link Use the help route beside login to ask about stored account details, phone verification records or a Privacy Policy request. We may ask you to confirm the account before discussing personal data.
Cashier status path For DANA, OVO, GoPay, QRIS or bank transfer questions, share the transaction reference shown in your cashier history. We use that detail to separate a payment-status query from a personal-data request.
Receipt and access check If a receipt or login record looks unfamiliar, tell us through account help and include its date, device type and visible reference. Do not send a passcode, wallet PIN or complete payment credential.
DEVICE SECURITY LAYER

What Our Privacy Policy Does With Data

We keep this Privacy Policy practical by describing the records created during account access, payment checks and support contact.

Account data handling

We use your account details to create access, complete phone verification and connect your activity with the correct account. We do not need your DANA, OVO or GoPay wallet password to identify a payment record.

Cookies on your device

A session cookie can keep the account path working between login and the lobby on a phone or desktop. You can manage browser cookie settings, though removing essential cookies may interrupt account access.

Payment record checks

QRIS, bank transfer and virtual account references help us match a cashier event with your account. We use the visible status and reference needed for checking, rather than requesting your full wallet credentials.

Account security steps

Phone verification helps confirm that an account request belongs to you. If an unfamiliar login or account change appears, contact account help and avoid sharing passcodes, wallet PINs or complete card details.

Retention and deletion

We retain records only for the period needed for account administration, payment reconciliation, security checks or a legal duty. Ask through account help which record you mean and we will explain the applicable handling.

Changes to your data

You can request correction, access or clarification by using the account help route. Include the account identifier and the specific field or record; we may verify your identity before making or disclosing a change.

Privacy Policy Answers For bumi110

These Privacy Policy answers address the searches we hear before account access: what we collect, how local wallet records are used, how cookies behave and where to send a request. Read them with the full policy wording, especially when your account uses more than one payment rail.

It covers account details, phone verification, login activity, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

No. We use payment status and visible reference details to match a cashier event with your account. Do not send a DANA, OVO or GoPay password, PIN or complete credential.

Open the account help link beside login and describe the records you want to access. Include your account identifier, then complete any identity check we request before disclosure.

Yes. Send a correction request through account help and name the inaccurate field or record. We may verify your account first, then explain whether the change can be made.

Session cookies can keep your login path active on mobile or desktop. You can change browser settings, but removing essential cookies may interrupt access to your account and policy link.

Retention depends on the record and the reason it is needed, such as reconciliation, account security or a legal duty. Ask account help about a specific QRIS or bank reference.

Access and eligibility depends on local law. Where local law permits, use the account help route to ask about your data rights, account record or a policy-related request.