Reference

Privacy Policy For Your selow 188 slot Account

selow 188 slot Privacy Policy sets out how we collect, use and protect the details connected with your account, wallet status and lobby access.

Clear data purposesWallet record controlsPhone verificationCookie choices
selow 188 slot Privacy Policy For Your selow 188 slot Account
PRIVACY HELP PATH

Where To Ask About Your Policy Data

A clear contact route matters when you want to understand a record linked with your account.

Account contact path Use the support contact option inside your account area for Privacy Policy questions, data…
Wallet record check If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account…
Login recovery route When a privacy request follows a failed login, tell us which device path you…
DATA CONTROL DETAILS

Six Practical Privacy Controls We Use

Privacy is handled through ordinary account controls rather than broad promises. We separate access checks from payment references, limit internal use to a stated purpose and keep a record of requests that…

Account details

We use your phone number and account credentials to create an access path, support phone verification and protect the account from an unknown login. If a detail changes, contact us through the signed-in support path so we can confirm the request before editing it.

Payment references

A DANA, OVO, GoPay or QRIS reference helps us match a wallet event with your account. For bank transfer and virtual account records, we use the relevant reference and status details, not an open-ended request for unrelated personal data.

Device signals

The mobile path from login to the lobby may provide device, browser and connection signals used for account security. We use these signals to spot an unusual access pattern, and they can help us investigate why phone verification appeared on your device.

Cookie choices

Cookies can keep a verified session available and help us understand whether a security step completed. Your browser controls can limit or remove cookies, although changing them may require another login or phone verification before account access continues.

Retention period

We keep account, contact and transaction records only for the period needed to provide the requested service, protect account integrity or meet a legal duty. When a retention need ends, we delete, anonymise or restrict the record where our process allows.

Change requests

You can ask us to correct an inaccurate name, phone detail or account record through the support contact path. We may request a phone verification step or a matching receipt reference, then explain what we changed or why a legal record must remain.

Privacy Policy Questions About Your Account

These Privacy Policy answers address the account and wallet questions you are most likely to ask before opening access or contacting us. We keep each answer tied to a practical action: check your account path, protect a receipt reference, adjust browser cookies or request a data change. Where a legal condition affects access, it depends on local law.

The Privacy Policy covers account details, phone verification, device signals, cookies, payment references and support messages connected with your access. It also explains why we use those records, how we protect them, how long we retain them and how you can request a correction or data access.

These wallet names appear because a payment reference can be linked with your account status. We use the reference to identify a transaction or receipt question, while avoiding unnecessary personal details. Bank transfer and virtual account references are handled in the same purpose-based way.

Open the support contact path after login and ask for an account data access request. Tell us which account and phone number the request concerns, but do not send a full password or complete wallet credentials. We may confirm ownership before releasing private account details.

Yes. Send a correction request through the signed-in support route and identify the inaccurate account detail, such as a phone number or name. We may use phone verification or a matching account record to confirm the request, then explain the change or any reason a record must remain.

Cookies can support a verified login session, remember a security step and help us detect unusual device activity. You can manage cookies through your browser settings. Removing them may sign you out or cause another phone verification step when you return to your account.

We retain each record for the period needed for its stated purpose, account security, request handling or a legal duty. Payment references may need to remain for account reconciliation. When the reason ends, we delete, anonymise or restrict the record where our process allows.

Yes. Access and eligibility depend on local law, and our Privacy Policy applies where local law permits. If a legal rule affects a request or account action, we will use the support contact path to explain the relevant limitation without asking for unrelated personal details.