Reference

Privacy Policy For Your sakurawin Account

The sakurawin Privacy Policy explains what we collect when you open an account, enter the lobby, or check DANA, OVO, GoPay and QRIS status.

Account recordsWallet activityCookie choicesPolicy requests
sakurawin Privacy Policy For Your sakurawin Account
HELP WHEN NEEDED

Get Policy Help Beside Account Support

A clear contact route matters when a privacy question appears beside a login or wallet issue.

Account contact Use the support contact attached to your sakurawin account for a Privacy Policy request.
Wallet status check If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account…
Policy request Ask for access, correction, deletion review or a plain explanation through our policy contact…
DATA HANDLING

Keep Control Of Account And Device Data

Privacy work is part of the account path rather than a separate promise. We record the practical events needed to protect sign-in, connect a wallet reference to the…

Account details

When you open an account, we handle the contact details and account fields you submit.

Device sessions

A phone or desktop session can create technical records such as login time, browser details and security signals.

Cookies

Cookies and similar storage can remember a session, support account security and keep policy choices available on the same device.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can leave a reference, amount status or matching record in…

Retention period

We retain records only for the operational, security and legal reasons described by the Privacy Policy.

Changing your data

If your phone number, email or account detail changes, contact us through the account support route before relying on a…

Privacy Policy Answers For sakurawin

These Privacy Policy answers focus on the decisions you make before opening an account: what we collect, why a wallet reference appears, how device access works and how to ask for a change. If your question is not covered, use the policy contact route with the account detail you can safely share. Account availability depends on local law.

It covers account details, phone verification, device sessions, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, account security and the steps for requesting access or correction.

We use your registered phone or email to create and protect the account, confirm an account access step and respond to a policy request. It also helps us avoid sending account or wallet details to the wrong person when a request comes from an unrecognised session.

Yes. The policy covers payment references and status records connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account steps. We use those details to reconcile an account action and investigate a status question without treating them as your complete profile.

A mobile or desktop session may provide technical details such as browser type, login time and security signals. These records help us protect account access and investigate a failed session. The Privacy Policy explains their purpose, and browser cookie controls can affect the login path.

Use the policy contact route connected to your account and state whether you want access, correction, deletion review or an explanation. Include your registered phone or email, but never send a password or one-time code. We may verify the account before releasing or changing records.

Retention depends on the reason a record is needed for account security, payment reconciliation, support or legal duties. Closing an account does not necessarily remove every transaction or access record immediately. The Privacy Policy explains the relevant period and lets you ask about a specific record.

Yes, you can read the policy and send a request from the same mobile path used for account access, including from Makassar. Cookie or session controls may affect the page, and account eligibility depends on local law. Use the support contact route if the policy page does not load.