Reference

Privacy Policy for Your bom89 Account

Our Privacy Policy explains how bom89 handles the details you provide when you open an account, verify your phone, access the lobby, or use DANA, OVO, GoPay and…

Account detailsWallet recordsDevice accessYour contact choices
bom89 Privacy Policy for Your bom89 Account
CONTACT ROUTES

Get Privacy Policy Help Directly

A clear contact route helps when you want to ask about the Privacy Policy, correct account data or understand a wallet record. We can match your request using the phone number connected to your account and a recent reference, without asking you to send a wallet password. For access questions, eligibility depends on local law, so our team may ask for the country connected to your request before explaining the available path.

Team online

Account message

Send a message through your signed-in account when you want us to locate a phone verification event, correct a profile detail or explain why a particular data field appears in your account record.

Email request

Use the contact email shown on our bom89 site for a Privacy Policy request. Include your account phone number, the subject of your request and a safe reply address; never include your DANA, OVO or bank password.

Payment status

If your question concerns QRIS, GoPay, DANA, OVO or a bank transfer reference, share the transaction date and reference only. We use those details to find the record while keeping your wallet credentials outside our support process.

DATA PRACTICES

Six Privacy Checks Behind Your Access

We apply the Privacy Policy to practical account events rather than treating data as a vague promise.

Collection

We collect details you enter during account creation, such as your phone number, plus login events, device type, browser signals and support messages. We collect only the fields needed to provide account access, address requests and connect a payment reference to the correct account.

Wallet matching

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may store the amount status, reference and time supplied by the payment flow. We use these records to confirm status and answer receipt questions, not to request your wallet password.

Cookies

Essential cookies keep your signed-in path working and help preserve security settings between pages. You can adjust browser cookie controls, but blocking required cookies may interrupt login or require you to verify your phone again on the next account visit.

Account security

We use phone verification, session checks and device signals to reduce account access by the wrong person. If a sign-in looks unusual, we may pause a step and ask for account confirmation before showing personal details or payment status.

Retention

We keep account, support and payment-reference records only for the period needed to provide the service, resolve a dispute or meet a legal duty. When a record no longer serves one of those purposes, our process removes it or separates it from direct account identity.

Changes and access

You can ask us to access, correct or delete eligible personal data by contacting support from your account or the contact email on bom89. We may verify your identity with the account phone number before making a change or disclosing stored details.

Privacy Policy Answers for bom89

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They cover what we collect, how payment references are handled, how to request a correction and what happens when you access bom89 from a phone or desktop. Where access is discussed, it depends on local law.

It covers account creation, phone verification, login events, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect account access, how long records may remain and how you can request access, correction or deletion where applicable.

No. Our Privacy Policy separates wallet credentials from the account record. For DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, we may retain a reference, status and time so we can match a payment question, but your wallet password stays with the payment service.

Phone verification connects the person completing the account step with the account record and helps us respond to access requests. It also supports checks when a new device or unusual session appears. We may ask for the same phone detail before changing personal data.

Send a request from your signed-in account or use the contact email shown on bom89. Tell us which detail is wrong and provide the account phone number for matching. We may ask for an additional confirmation before changing profile, security or payment-reference data.

You can request deletion of eligible personal data through account support or our contact email. We first check whether a record is still needed for an open dispute, account security or a legal duty. If retention is required, we will explain that reason and the remaining handling.

On a phone browser, essential cookies help keep the login path and security checks connected while you move through the account. Browser controls can block cookies, but doing so may interrupt access or require phone verification again. We do not describe a separate mobile app in this policy.

Use the signed-in account message route or the contact email displayed on our site. Include your request type, account phone number and a safe reply address, but do not send a wallet password. Access and eligibility depends on local law, and we may verify identity before replying.