Reference

Privacy Policy for sukaspin Indonesia

Our Privacy Policy explains how sukaspin handles your account, device and wallet details when you create access, choose DANA or QRIS, and enter the lobby.

Account dataWallet detailsCookie choicesPrivacy requests
sukaspin Privacy Policy for sukaspin Indonesia
PRIVACY HELP PATHS

Get Privacy Help Near Account Access

You can ask us about personal data without leaving the account route. Tell us whether your request concerns login details, a wallet reference, a cookie setting, or a stored device signal, and…

Account access Use the account help path when you need to correct your phone detail, ask how sign-in data is used, or report an unfamiliar device connected with your sukaspin access.
Wallet records For a privacy question about DANA, OVO, GoPay or QRIS, send the visible payment reference and your account detail; we use those fields to locate the matching status record.
Receipt checks If a bank transfer or virtual account receipt is attached to the wrong account, contact us through the payment status route so we can check the record before making a correction.
YOUR DATA CONTROLS

Your Security Choices Inside sukaspin

Privacy protection works best when your account steps and device choices are clear. We separate essential account records from optional cookie preferences, limit access to payment references, and use verification checks when…

Account creation

We collect the details needed to create your account and complete phone verification before access. Keeping your phone detail current helps us connect a privacy request with the correct account.

Device signals

Your browser and device may send session signals used to spot unusual sign-ins. We do not treat a device signal as a wallet password, and you can ask us about a recorded access event.

Cookie settings

Essential cookies support sign-in and policy access, while other cookies may remember preferences. You can clear browser data or adjust available cookie settings, though sign-in may need verification again.

Wallet protection

DANA, OVO, GoPay and QRIS references are used to match payment status, not to obtain your wallet password. We may retain a reference and amount status needed for account records.

Retention period

We retain account, security and payment records only as long as needed for stated purposes, account support, dispute checks or legal duties. Ask us which retention rule applies to your record.

Change requests

To request access, correction or deletion, contact us through account help and identify the affected record. We may verify your account before changing data, especially for payment or sign-in details.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the questions we expect before you open an account or ask for a record change. They focus on sukaspin account access, local wallet references, cookies, device signals and the request path available where local law permits.

It covers account details, phone verification, device and session signals, cookies, payment references and support records handled through sukaspin. It also explains your available access, correction and deletion requests.

We use your phone detail to create and protect account access, complete verification, and connect a privacy request with the right record. We do not use it to obtain your DANA or OVO password.

We may retain the QRIS reference and payment status needed to match a transaction with your account. The same approach applies to DANA, GoPay, bank transfer and virtual account records.

Contact us through account help and state that you want a copy of your Privacy Policy data record. Include your account detail, then complete any identity check needed before release.

Yes. Send a correction request through account help and identify the field, such as your phone detail or payment reference. We may verify account ownership before updating the record.

Essential mobile cookies support sign-in and policy access, while other cookies may remember preferences. Clearing browser data can remove those settings and may require phone verification when you return.

Use the account help path and describe the unfamiliar sign-in or device signal. We can check the related session record, explain the available action, and apply changes where local law permits.