Reference

apollo 68 slot Privacy Policy For Wallet Data

apollo 68 slot Privacy Policy explains how we collect, use and protect details connected with your account, DANA, OVO, GoPay or QRIS activity.

Account clarityWallet contextCookie choicesSecurity requests
apollo 68 slot apollo 68 slot Privacy Policy For Wallet Data
PRIVACY HELP DESK

Get Clear Answers About Your Data

A privacy question should not require you to search through account screens.

Live chat request Use live chat for a Privacy Policy question about account access, phone verification, cookie…
Account email path The support email linked from our account area is suitable for a copy request…
Wallet status check If a DANA, OVO, GoPay or QRIS reference appears incorrectly, contact support with the…
ACCOUNT DATA PRACTICE

What You Receive From Our Privacy Process

We handle this policy area through ordinary account controls rather than broad data collection. Phone verification helps us connect a request to the correct account, while sign-in records help us investigate access…

Account details

We use your phone number and submitted account details to create access, complete phone verification and answer account requests. If a detail changes, ask us to correct it through support. We may request an account check before changing information tied to your login.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a wallet or bank status with your account question. We use the reference for that operational purpose and do not ask you to place a password, PIN or full credential in a support message.

Device records

When you sign in on a mobile browser or desktop, we may record device and browser signals such as session timing and security events. These signals help us investigate unusual access; they are not a request to install a separate application on your device.

Cookies and storage

Cookies and similar browser storage can keep a session available and remember selected settings. You can adjust browser permissions or ask support about a cookie question. Removing storage may require you to sign in again, but it does not erase account records by itself.

Retention choices

We keep personal records for as long as needed for account operation, security checks, payment reconciliation or a dispute. When a record is no longer needed for those purposes, our process removes or separates it according to the applicable retention need.

Your requests

You can ask for access to personal data, a correction, an explanation of use or a question about deletion. We may need to verify your identity and clarify the scope before acting, then respond through the contact route connected with your account.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions that arise while opening an account, signing in from a phone and checking a local wallet record. We keep each response tied to a practical action, so you know which information may be used and which contact route can help. If a question concerns eligibility or access, where local law permits, support can explain the next available step without asking you to share unnecessary credentials.

The Privacy Policy covers account details, phone verification, sign-in and device signals, cookie storage, payment references and support messages. It explains why we use each category, how retention works and how you can ask for access, correction or clarification through our support channels.

We use your phone number to create and identify your account, complete the phone verification step and connect a privacy request with the correct record. If you contact us about DANA or QRIS status, verification helps us discuss your account without revealing details to another person.

Yes. The Privacy Policy covers references and status details connected with DANA, OVO and GoPay when they are used to trace an account question or payment record. We use those references for matching and support, not as permission to collect unrelated wallet content.

A mobile browser or desktop session may create records such as sign-in time, browser details and security events. We use these signals to identify unusual account access and troubleshoot a session. We do not require a separate application installation to use the account path.

You can request access to personal data or ask us to correct an inaccurate detail through live chat or the account support email. Include your registered phone number, but never include a password, wallet PIN or full payment credential. We may verify your identity first.

We retain records while they are needed for account operation, security investigation, payment matching or a dispute. After that need ends, records are removed or separated through our retention process. Support can explain the purpose and status of a particular record when you ask.

You can adjust cookie permissions in your browser or contact support with a question about stored session settings. Removing cookies may sign you out or reset preferences, but it does not automatically delete account data. We can explain which browser setting relates to your request.