Reference

Privacy Policy For Your Account

ronaldo slot Privacy Policy explains what we collect when you open an account, use the mobile lobby, or connect DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsCookie choicesPolicy requests
ronaldo slot Privacy Policy For Your Account
CONTACT ROUTES

Ask About Your Privacy Policy

A clear request path helps when you need to ask about the Privacy Policy, an account record or a wallet reference.

Account request Ask us to explain the account details connected with your phone verification step. We may ask you to confirm the account route before discussing records, so private details are not disclosed through an unverified request.
Wallet query For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, include the payment reference and date shown in your account. We use those details to locate the relevant entry without asking for your wallet PIN.
Privacy request Send a request to access, correct or remove eligible personal records through the support path inside your account. We will explain any identity check and any record that must remain for a lawful account or payment purpose.
DATA PRACTICE

What Your Privacy Policy Covers

We handle this policy area through practical account controls rather than vague statements. Phone verification helps us match you to the right account, while device and session signals help detect unusual login…

Data we receive

We may receive your account contact details, phone verification result, device session markers and support messages. Payment records can show a DANA, OVO, GoPay or QRIS reference, while bank transfer entries may show the selected bank route.

Cookie controls

Cookies and device storage can keep your login session open and retain settings between pages. You can adjust browser controls, although blocking required cookies may interrupt the account path or return you to the phone verification step.

Account security

We use account checks, session signals and phone verification to reduce unauthorised access. Never send your password or wallet PIN in a support request. If a login looks unfamiliar, contact us through the account help route before continuing.

Payment records

A receipt reference helps us match the correct wallet or bank entry without storing your wallet PIN. This can include QRIS, DANA, OVO, GoPay, virtual account, BCA, BRI, Mandiri or BNI details supplied during the payment step.

Retention approach

We retain personal records only while they support account access, payment reconciliation, security checks, dispute handling or a legal duty. When a purpose ends, we remove or anonymise the relevant record where local rules allow that action.

Change requests

You can ask us to correct account details, explain a data use, provide an eligible copy or delete eligible records. Include your account contact route, and we will verify the request before making a change or explaining a necessary exception.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account actions you are most likely to take from Indonesia. They explain how we connect phone verification, device sessions, local wallet references and support requests without turning a policy question into a general lobby description. If your case is not covered, use the account support route and quote the relevant receipt or account step.

It covers account details, phone verification, device and session signals, cookies, support messages, and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use. It also explains retention, security checks and how to request access, correction or deletion.

Phone verification helps us connect you with the correct account and reduce mistaken or unauthorised access. It can also support a request about a wallet status or receipt. We use the verification result for account protection rather than asking you to send a wallet PIN.

Yes. The Privacy Policy covers payment references supplied during a DANA or QRIS step, as well as OVO, GoPay, bank transfer and virtual account entries. These records help us match a receipt or status question to the right account without needing your wallet password.

Cookies and device storage can keep your session active and retain selected settings while you move from login to the lobby. If you block required cookies, the account path may stop or ask for phone verification again. Your browser controls can manage optional cookie use.

You can ask for an eligible copy or correction through the support route inside your account. Include the account contact route and describe the record, such as a phone detail or QRIS receipt reference. We verify your request first and explain any lawful limitation.

We keep records while they are needed for account access, payment matching, security checks, support, dispute handling or a legal duty. When the purpose ends, we remove or anonymise the record where local rules allow. The retention period can differ by record type.

Sign in and use the support route near your account, then state whether you need access, correction, deletion or an explanation of data use. Include a matching account or receipt reference, but do not send your password, wallet PIN or full payment credentials.