Reference

ular288 Privacy Policy For Your Account

ular288 Privacy Policy explains what we collect when you open an account, connect DANA or QRIS, and enter the lobby from a mobile browser.

Account dataWallet recordsDevice checksPolicy requests
ular288 ular288 Privacy Policy For Your Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact route helps you ask about the Privacy Policy without explaining your request at the cashier. Use the support path shown in your account area, include the phone number linked to your account, and tell us whether your question concerns login, a wallet reference or device data. We may ask for account details before discussing private records.

Team online

Account support path

Open the support link beside your account and state that your request concerns the Privacy Policy. Include your registered phone number and the subject of your request so we can locate the correct account record without asking you to send wallet credentials.

Wallet record request

If your question concerns DANA, OVO, GoPay or QRIS data, mention the payment rail and the date shown in your account history. We use that reference to check the relevant record while avoiding requests for your wallet PIN or full authentication details.

Device access question

For a mobile browser concern, tell us the device type, sign-in time and message displayed on screen. We can then separate a Privacy Policy request from a routine access issue and explain which account data may have been used during the check.

DATA PRACTICES

How We Handle Your Private Data

We keep the Privacy Policy practical by linking each data use to an account action.

Account collection

When you open an account, we collect the details needed for account access and phone verification.

Wallet references

Payment data is handled as transaction references rather than as a request for your wallet PIN.

Cookies and sessions

Our browser session may use cookies or similar storage to keep sign-in state, remember essential choices and protect account access.

Security checks

We may compare sign-in time, browser details and device signals when an account action looks unusual.

Retention requests

We retain account and payment references only as long as needed for the stated service, security work and applicable record…

Changes and access

You can ask to see, correct or clarify personal data connected with your account through the support path.

Privacy Policy Questions For Indonesia

These Privacy Policy answers focus on the account steps you are most likely to meet in Indonesia. They explain wallet references, mobile access, verification and requests for changes without replacing the full policy text. If your situation is not covered, use the account support path and include the relevant record.

The ular288 Privacy Policy covers account details, phone verification, sign-in records, device signals, cookies, support requests and payment references. It explains why we use those records for access, security, wallet matching and retention, including activity linked to DANA, OVO, GoPay and QRIS.

Your phone number connects the account to the verification step before account access. We use it to locate the correct record and protect sign-in activity. If you ask about your Privacy Policy data, we may confirm account control before discussing details linked to that number.

We do not ask you to send a DANA or QRIS PIN for a Privacy Policy request. We handle relevant payment references and status details so an account record can be matched. Keep wallet authentication private and use the account support path for payment-data questions.

You can ask what personal data is connected with your account by using the support path shown in your account area. Include your registered phone number and, if relevant, a wallet or bank-transfer reference. We may verify account control before responding, and the response depends on local law.

Cookies or similar browser storage can keep an essential session, remember choices and support account security. If you clear them on your mobile browser, you may be asked to sign in and complete phone verification again. This does not change the Privacy Policy request process.

Send a correction request through the account support path and describe the record that needs attention. Your registered phone number helps us identify the account, while a payment reference can locate a wallet entry. We verify account control before changing data and explain any limits required by local law.

Retention depends on the purpose of the record, such as account security, support, payment matching or required record duties. Ask about a particular account or transaction reference through support. We will explain the applicable retention response rather than applying one fixed period to every record.