Reference

Privacy Policy for Your bomjudi Account

bomjudi Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account clarityWallet recordsPolicy access
bomjudi Privacy Policy for Your bomjudi Account
CONTACT YOUR WAY

Get Privacy Policy Help Through Account Support

A clear contact path helps when you want to ask about the Privacy Policy or correct a detail connected with your account.

Policy questions Ask how we collect, use or retain account data through the logged-in support route.
Wallet references If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account…
Access requests To request a copy, correction or removal where available, identify the account and describe…
DATA HANDLING

What Our Privacy Policy Keeps Clear

We keep this Privacy Policy practical: you should be able to see why a data point is needed and where to ask about it.

Account data

We use your account details to create access, complete phone verification and respond to requests made through the correct account path. If a field changes, contact support with the account identifier so we can compare the request with the record we hold.

Device signals

When you move from login to the lobby on a phone, tablet or desktop, we may record browser, operating system, session time and related technical signals. These details help investigate failed access and unusual sessions without treating your device as a separate account.

Cookies

Cookies can keep essential session choices working and help us understand whether a page request belongs to an active sign-in. You can manage browser cookie settings, though changing them may affect login continuity or the way policy pages load.

Wallet records

A DANA, OVO, GoPay or QRIS reference can be linked to your account activity when needed to check a payment state. We do not need your wallet password for that check, and support should never ask you to disclose a private security code.

Security steps

Phone verification before account access helps us distinguish your request from an unapproved attempt. If a session looks unusual, we may pause the conversation or ask for another account check before sharing details covered by this Privacy Policy.

Retention requests

We retain records only for the account, reconciliation, security or legal purpose that calls for them. Ask support what can be changed or removed, and we will assess the request against active obligations and where local law permits the action.

Privacy Policy Questions About bomjudi

These Privacy Policy answers address the account and device questions you are most likely to have before opening access. We explain the practical route for checking stored details, asking for a change, and understanding wallet records. If your situation is not covered, use the support path after login and refer to the relevant account step.

It covers account details, phone verification, sign-in sessions, device signals, cookies, wallet references and support requests connected with our service. It also explains why we use those records, how retention is assessed, and how you can contact us about access, correction or removal where local law permits.

Phone verification helps connect an account request with the person who controls the registered contact detail. We use it before account access or a sensitive request, so a support conversation about your account or Privacy Policy rights is not disclosed to an unrelated person.

Yes. The Privacy Policy covers transaction references and status records created when you use DANA, OVO, GoPay or QRIS through the account flow. We may also handle bank transfer and virtual account references for reconciliation, but support does not need your wallet password or security code.

When you sign in on a phone, tablet or desktop, technical records may include browser type, operating system, session time and related device signals. We use them to maintain access, investigate failed login steps and identify unusual activity, rather than to create a separate identity for every device.

Use the logged-in support route and identify your account, then state which detail is inaccurate or which record you want assessed. We may verify your phone before responding. We will review correction or removal requests against account needs, security duties and local legal requirements.

Retention varies by purpose. Account and verification records may be needed while access remains active, wallet references may support reconciliation, and some records may remain necessary for security or legal duties. Ask support about a specific record; we will explain the applicable basis where local law permits.

You can read this page before opening access and use the contact route shown on the site for a policy question. Do not send wallet passwords or security codes. If account-specific details are involved, we may need an account identifier and phone verification before discussing them.