Reference

ular288 Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open an account, verify your phone, enter the lobby and use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet details explainedAccount contact routeMobile access context

Browse Our Lobby Read FAQ

How DANA And QRIS Data Enters Our Policy

ular288 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers account details, phone verification, device signals, wallet selections and records connected with account activity. When you choose DANA, OVO, GoPay or QRIS, we may retain the payment reference and status needed to match a deposit request to your account; we do not

1
describe a wallet password as an account field we need to store. Bank transfer and virtual account references can also appear in the account record when you use those routes. We use access logs to investigate an interrupted login or a wallet status question, then retain
2
records only for the stated operational or legal purpose. Access depends on local law, and some requests may need identity checks before we disclose or change a record. The policy applies to our site and its mobile browser path, not to separate wallet providers’ own handling
3
rules.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY HELP ROUTES

Wallet Status Help Through Our Privacy Desk

A clear contact path helps when you want to ask what data we hold or why an account record appears. Send your account identifier through our support route and describe the request without sharing a wallet PIN. We can connect a privacy question with a payment receipt or status check while keeping the request focused on your personal data.

Team online

Account data request

Ask us to locate account details linked to your phone verification step. Include the account identifier and the relevant date so we can separate your request from another DANA, OVO or GoPay record.

Payment record question

If a QRIS, bank transfer or virtual account reference looks unfamiliar, send the receipt number rather than your wallet password. We use that reference to check the stored status and explain the record.

Correction or removal

Tell us which personal detail needs correction or removal. We may ask you to confirm account ownership before changing a phone, device or payment-related record, where local law permits.

SECURITY RECORD PRACTICE

How ular288 Protects Account Records

We keep this policy practical: you can see why account data is collected, how cookies support the mobile browser path and where to direct a change request.

Account opening

When you open an account, we record the details needed to create your account path and show access after phone…

Phone verification

A phone verification step links account access to the contact detail you provide.

Device signals

Our site may record browser, device and sign-in signals to identify repeated access or investigate a stalled login.

Cookies

Cookies can keep a session connected between login and the lobby on mobile.

Retention period

We retain account, payment-reference and security records for the purpose that requires them, then remove or restrict them when that…

Change requests

To request access, correction or removal, contact our support route with your account identifier and the requested action.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we expect before you open an account: wallet references, phone checks, cookies, device records and contact steps. If your question is not listed, use the privacy contact route with the smallest useful set of account details. Eligibility and access depend on local law.

It covers account details, phone verification, device and access signals, cookies, payment references and requests to access, correct or remove personal data connected with your account.

Our policy distinguishes payment references and status records from wallet passwords. Do not send a DANA or OVO password to support; we need the receipt or reference instead.

Phone verification helps connect an account to its contact detail and helps us check ownership before changing records. It can also support investigation of an unfamiliar sign-in.

We may retain a QRIS, bank transfer or virtual account reference and its status so we can match an account request. The separate payment provider follows its own privacy terms.

Yes, send a data access request through our support route with your account identifier. We may verify ownership before responding, and the available route depends on local law.

State the exact field or record you want changed or removed and provide your account identifier. We check the request, explain any retention duty and act where local law permits.

Cookies can keep a mobile browser session and policy choice connected. If you block them, login or saved choices may not work as expected; browser controls manage those settings.

ular288 Privacy Policy For Your Account

Wallet Status Help Through Our Privacy Desk

Account data request

Payment record question

Correction or removal

How ular288 Protects Account Records

Account opening

Phone verification

Device signals

Cookies

Retention period

Change requests

Privacy Policy Answers For Your Account

01 What does the ular288 Privacy Policy cover?

02 Does the Privacy Policy store my DANA or OVO password?

03 Why does ular288 need phone verification?

04 How are QRIS and bank transfer details handled?

05 Can I request a copy of my account data?

06 How can I ask for a correction or removal?

07 Do cookies affect Privacy Policy choices on mobile?

Related Pages