Reference

syair sdy vip Privacy Policy

syair sdy vip Privacy Policy gives you a clear view of how we collect, use and protect details linked to your account, wallet status and device access.

Account dataWallet recordsCookie choicesPrivacy requests
syair sdy vip syair sdy vip Privacy Policy
PRIVACY HELP DESK

Contact Us About Your Privacy Choices

A direct privacy question should not become a wallet-status problem.

Account message Use the support message route after login to ask about stored contact details, phone…
Cashier question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, mention the date, amount…
Access request When you cannot reach the account, use the available account-support route and state the…
DATA CARE ROUTINE

Check How We Handle Account Data

Privacy work is part of the account flow rather than a separate promise. We record enough activity to identify a sign-in, connect a wallet reference to the right…

Collected details

We may hold your name, contact route, phone verification result, login timestamps, device signals and payment references.

Cookie controls

A mobile browser can store session cookies so you do not repeat every step between login and the lobby.

Account security

Phone verification can be required before we discuss private records or restore account access.

Payment matching

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain reference details needed to match a cashier…

Retention period

We keep account and transaction records for as long as operational, security or legal needs require.

Request changes

Ask us to access, correct or remove eligible personal details through account support.

Ask About Privacy Policy And Access

These Privacy Policy answers focus on the questions that arise before account opening or during a wallet and device check. We explain what may be collected, why phone verification can appear, how cookies affect a mobile session and which route to use when you want a correction. If your situation involves Indonesia eligibility, access depends on local law, so contact us through the account support path for a case-specific response.

It covers personal details, phone verification, login events, device signals, cookies, support messages and payment references connected with your account. It also explains how we use, retain, secure and amend those records when you contact us.

DANA and QRIS can create transaction references linked to an account request. We use those references to match a cashier event, investigate a status question and reduce mistaken account records without requesting your wallet PIN.

We may collect your name, email or phone route, verification result, login timestamps, device signals and transaction references. The exact fields depend on the account step you complete and the service access available where local law permits.

Yes. Send an account-support request stating the field that needs correction and the contact route linked to your account. We may complete phone verification before changing private details, and we will handle the request under applicable requirements.

Cookies can keep a mobile session active between login and the lobby and help us detect unusual sign-in activity. You can clear or restrict them in your browser, but the next account step may require another sign-in.

We retain payment references, login events and related account records while operational, security or legal needs require them. After that need ends, handling follows the applicable retention process rather than an indefinite storage rule.

Use the support message route connected to your account and identify the record or question. Include only the relevant email, phone detail or transaction reference; never send a password, wallet PIN or complete payment credential.