Reference

Privacy Policy for Your ulartoto Account

Clear control over your account data starts with our Privacy Policy. We explain what we collect when you create an account, verify your phone, open titles such as…

Data use explainedWallet records coveredMobile access clarifiedPrivacy requests accepted
ulartoto Privacy Policy for Your ulartoto Account
REQUEST SUPPORT

Get Help With Privacy Requests

A clear support route helps when you want to ask about account data, a wallet record or a device entry.

Account data request Open the support route from your signed-in account and ask which account details we hold. Include your account phone number so we can compare the request with the phone verification step before sharing personal data.
Wallet record query If a DANA, OVO, GoPay or QRIS record looks unfamiliar, mention the payment rail and approximate transaction date in your support request. We can use that context to locate the relevant account entry without asking you to send a wallet password.
Privacy change request For a correction or removal request, state exactly which detail needs changing and why. We may ask you to confirm account ownership through the existing login and phone verification path before applying any permitted update.
DATA HANDLING

Keep Wallet And Device Data Clear

Privacy depends on practical handling, not a vague promise. We separate account access records from the request itself, use device signals to spot unusual sign-ins, and keep payment references tied to the…

What we collect

We may receive your phone number, account details, verification result, login timestamps, browser type and device signals. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we also keep the payment reference needed to match account activity.

Cookies and sessions

Cookies can keep a signed-in session working and help us recognise a returning browser. On a mobile path, they may connect your login with the lobby request; clearing browser cookies can remove that session and require account access again.

Account protection

Phone verification is part of our account access checks. We may compare a new device or unusual login pattern with prior account activity before responding to a data request, helping prevent one person from receiving another person’s private details.

Retention choices

We retain account and payment records only for the period needed for the stated account, security, support or record-keeping purpose. When a request can be completed, we remove or restrict details that no longer need to remain available.

Access and correction

You can ask what personal details are connected with your account or request a correction through the signed-in support path. Tell us whether the issue concerns your phone record, device entry, cookie session or DANA, OVO, GoPay or QRIS reference.

Contact ownership

Privacy requests should come from the account support route so we can confirm ownership before acting. If you cannot sign in, explain that in the request and include the account phone number; we will outline the next verification step.

Privacy Policy Answers For ulartoto

These Privacy Policy answers focus on the account questions you may have before using ulartoto from Indonesia. We cover payment references, mobile sessions, phone verification, cookies, correction requests and access that depends on local law. If your question is not listed, use the signed-in support route and describe the exact account detail or device activity you want us to check.

The ulartoto Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, payment references and retention. It explains how we use those details for account access, security, support and records connected with DANA, OVO, GoPay, QRIS and bank rails.

We use your phone number for the account verification step and to connect a privacy request with the correct account. If you ask us to show, correct or remove data, the phone record helps us check ownership before we disclose or change anything.

Yes. The Privacy Policy covers references created when you use DANA, OVO, GoPay or QRIS, including the details needed to match an account action with a payment record. We do not need your wallet password to investigate a reference or status question.

Sign in, open the account support route and ask for the personal details connected with your account. Name the area you want checked, such as phone verification, device activity, cookies or a QRIS reference. We may request an ownership check before responding.

Yes. Send a correction request through the account support path and identify the inaccurate detail, such as a phone record or account entry. Explain the requested replacement clearly. We will check ownership and tell you whether the change can be made under the Privacy Policy.

Cookies can keep your mobile browser session connected to your account and remember that a verification step has been completed. If you clear cookies, the session may end and you may need to sign in again. The Privacy Policy explains their account and security purpose.

Yes. Access, eligibility and some privacy request outcomes depends on local law. We assess the request against the applicable rules and the account ownership check. Where local law permits, we explain what data can be accessed, corrected, restricted or removed.