Reference

Read ular288 Privacy Policy Clearly

Our Privacy Policy explains what data we collect when you open an account, sign in from a mobile browser, or use DANA, OVO, GoPay and QRIS.

Account data explainedWallet records addressedCookie choices coveredRequest path included
ular288 Read ular288 Privacy Policy Clearly
CONTACT PATHS

Browse Privacy Help From Your Account

Privacy questions should reach the support route connected to your account, because the team may need to confirm which profile or payment reference you mean. Start with the account help link, include the email or phone number attached to your profile, and describe whether your request concerns cookies, a device record, wallet status or data correction. We use that context to avoid sending account details to the wrong person.

Team online

Account help route

Open the support link beside your account controls and state your Privacy Policy question. Include your registered contact detail, but never send a password, one-time code or full wallet PIN.

Payment receipt check

For DANA, OVO, GoPay, QRIS or bank transfer records, include the transaction reference and date. We can then match the request without asking you to repeat unrelated account details.

Change request path

Ask us to correct, access or remove eligible account data through support. We may confirm your phone verification before discussing profile details or applying a requested change.

DATA CONTROLS

Switch Through Your Privacy Choices

We treat privacy as an account process rather than a footer link. Our handling follows the data purpose shown in this policy: account access, payment reconciliation, device protection and support response.

Account data

We may keep your submitted contact details, phone verification result and account activity needed to maintain your profile. We use these records for the stated account purpose rather than unrelated messages.

Cookies

Cookies can remember session settings and help us identify a valid sign-in on your browser. You can adjust cookie controls in your browser, though some account functions may then need repeated sign-in.

Device signals

When you sign in from a phone or desktop, technical signals such as browser type, device details and session timing can help us spot unusual access and protect your profile.

Payment matching

DANA, OVO, GoPay, QRIS and bank transfer references help us match an account transaction. We retain the record needed to resolve status questions, not a wallet PIN or one-time code.

Retention

We keep records only for the period needed for account operation, security checks, payment reconciliation and legal duties. Ask support about a specific record and we will explain its applicable retention reason.

Your request

You can request a copy, correction or eligible removal of your data through account support. Tell us the exact request and registered contact detail so we can verify ownership before replying.

Ask About ular288 Privacy Policy

These Privacy Policy answers cover the account actions you are most likely to take before opening or using your profile. They explain what may be collected, why a payment reference appears, how mobile browsing is treated, and how to contact us. If your question concerns eligibility, remember that access depends on local law.

It covers account details, phone verification, browser and device signals, cookies, payment references, security checks, retention and requests to access, correct or remove eligible data.

We use the verification status to protect account access and connect support requests to the correct profile. We do not need your one-time code or wallet PIN for a privacy request.

Yes. It explains that DANA and QRIS records may include a reference, status and time so we can reconcile an account transaction and answer a payment-status question.

The browser may provide device type, browser version and session timing. Cookies can retain settings, while security checks may use technical signals to identify unusual account access.

Use the account support route and ask for a data copy. Include your registered email or phone number, then complete any ownership check needed before we discuss profile records.

Yes. Send a correction request through support and identify the field that is wrong. We may confirm phone verification before changing contact, profile or payment-related account records.

Contact support with the specific record or account detail you mean. We will assess whether removal is available and explain any retention needed for security, reconciliation or legal duties.