Reference

slot988ular Privacy Policy, Clearly Explained

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

Account dataWallet statusCookie choicesSecurity steps
slot988ular slot988ular Privacy Policy, Clearly Explained
CONTACT ROUTES

Reach Support About Privacy Choices

A clear support route helps when you want to ask about the Privacy Policy, correct an account detail or check why a wallet reference is connected…

Policy questions Send your question through the account support route and mention Privacy Policy, cookies, account…
Wallet references If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account data…
Access concerns When a sign-in or phone verification concern affects your privacy request, tell us the…
DATA PRACTICES

Explore How We Handle Your Records

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

Account creation

When you open an account, we collect the details needed to create and protect that account.

Cookies and browser use

Cookies can remember a session, language choice or security setting in your browser.

Wallet records

A DANA, OVO, GoPay or QRIS reference can appear in account records when you check a payment status.

Account security

We use phone verification, sign-in signals and account activity records to identify access that does not match your usual pattern.

Retention periods

We retain different records for different periods because account, payment, security and legal needs are not identical.

Changes and requests

Where local law permits, you can ask us to correct inaccurate account data, explain a processing purpose or address an…

Browse Privacy Policy Answers Before Access

These Privacy Policy answers focus on the account questions you may have before opening access from Indonesia. We explain the records connected with phone verification, browser use and local wallet references, along with the practical route for asking about your data. If your circumstances involve eligibility or regional access, that access depends on local law.

The slot988ular Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It explains why we use those records for account access, security, wallet status checks and legal duties, plus how you can ask about eligible data requests.

We collect the details needed to create and protect your account, including your phone number and verification record. We may also keep sign-in activity, device signals and support messages. We use these records for account administration and security, not as public profile content.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS when we check a recorded status or investigate a receipt. Bank transfer and virtual account references can be handled similarly. We do not need your wallet PIN for those checks.

Cookies may keep a session active, remember a browser preference or support a security check. If you move between a phone browser and desktop, device signals can help identify unusual access. You can manage cookie behaviour through your browser settings, subject to account functions that need security cookies.

Where local law permits, you can ask what eligible account data we hold or request a correction. Use the support route shown after sign-in, identify the record or phone number involved and complete reasonable verification. We may limit a request where retention is required for security or law.

Retention depends on the record type and purpose. Account, payment, security and legal records can require different periods. We remove, anonymise or restrict records when they are no longer needed for those purposes, while a valid legal or security requirement may require continued retention.

Use the account support route for a Privacy Policy concern and describe whether it involves cookies, phone verification, wallet references, correction or access. Include a transaction reference when relevant, never send a password or wallet PIN, and expect reasonable checks before account details are discussed.