Reference

bowototo Privacy Policy for Your Account

Our Privacy Policy explains how we handle the account details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Account dataWallet recordsCookie choicesSecurity requests
bowototo bowototo Privacy Policy for Your Account
HELP WITH YOUR REQUEST

Get Clear Privacy Support Near Login

A privacy question should not leave you searching through the lobby. Send your request through the account support channel linked near login or the cashier path, and include the email or phone…

Account access Use the support path beside login when you need a copy of your account data, a correction to your phone number or help confirming that a request came from the account holder.
Wallet records For DANA, OVO, GoPay or QRIS questions, share the transaction reference shown in your receipt. We can check the linked account record without requesting your wallet PIN.
Privacy contact Ask support to route a request about cookies, retention, deletion or data access to the privacy contact. We may verify your account before discussing personal records.
HOW WE HANDLE DATA

Keep Account Choices Visible And Practical

We explain our handling in operational terms so you can make a clear account decision. Login activity and phone verification help us detect unusual access, while cookie settings affect how the site…

Collected details

We may receive your name, phone number, email, login events, device signals and account activity when you create an account, verify access or contact us about Privacy Policy matters.

Cookies

Cookies can keep a session active and remember selected settings on your mobile browser. You can adjust browser controls, although changing them may require another login.

Account security

Phone verification and sign-in checks help protect the account. We will not ask for your wallet PIN or full payment credential when checking a DANA, QRIS or bank record.

Retention

We keep account and transaction records for operating the service, resolving disputes, checking security events or meeting legal duties, then assess whether continued storage is needed.

Your changes

You can ask us to correct inaccurate contact details or explain how a record is used. A request should come from the account contact so we can protect your data.

Policy contact

For access, deletion, cookie or retention requests, contact support through the account path. Include a clear request and avoid sending passwords, wallet PINs or secret codes.

Privacy Policy Answers Before Account Access

These answers address the searches we hear most often about the bowototo Privacy Policy. They explain what happens around account creation, wallet records, mobile access and requests for changes. If your question involves a specific transaction or device, use the support path near login and provide only the minimum details needed to locate your record.

The bowototo Privacy Policy covers account details, phone verification, login events, device signals, cookies, support messages and payment references. It explains why we use each category, how long records may remain and how you can ask for access, correction or deletion.

No. We may receive a transaction reference, amount status or date needed to match an account event, but we do not ask for or need your DANA, OVO, GoPay or QRIS PIN. Never send a wallet PIN through support.

Use the support route beside login and state that you want an account data copy under the Privacy Policy. Include the phone number or email attached to your account. We may verify ownership before releasing records connected with you.

Yes, you can ask us to correct inaccurate contact details through account support. We may request a phone verification step or another account check before changing the record, because the contact route protects sign-in and privacy requests.

Cookies can maintain your sign-in session and remember selected settings in a mobile browser. You can change cookie controls in your browser, but blocking required cookies may sign you out or prevent a privacy request from being completed.

Retention depends on the purpose of each record. We may keep account, payment-reference and security records for service operation, dispute handling or legal duties. When those needs end, we assess whether the record should be removed or de-identified.

You may ask support about deletion of eligible personal data. We first verify the account holder and check whether a record must remain for security, dispute handling or legal duties. Access depends on local law and the applicable request conditions.