Reference

csowin Privacy Policy for Your Account

Our csowin Privacy Policy explains what account, wallet and device details we collect, why we use them and how you can ask about your records.

Clear data purposesWallet status recordsPhone verificationIndonesia access rules
csowin csowin Privacy Policy for Your Account
CONTACT ROUTES

Reach Us About Your Privacy Policy

Questions about this Privacy Policy should reach the team through the account support route connected to your login and wallet status.

Account privacy request Use the support path beside your account area to ask for a copy of personal data, correction of an incorrect phone detail or clarification about information connected with your csowin login. We may ask for an account step that confirms the request belongs to you.
Wallet record question For DANA, OVO, GoPay or QRIS records, send the payment reference, date and wallet name through support. We use those details to locate the status without asking you to share a wallet PIN, password or full private banking credential.
Cookie and device help If a mobile browser keeps an old session or shows a cookie choice incorrectly, contact us with your device type and browser path. We can explain the relevant setting and the account effect without requesting access to unrelated files on your phone.
DATA HANDLING

Browse How We Handle Your Details

A useful Privacy Policy should tell you what happens after each account step, not only list broad categories.

Account details

When you create or verify an account, we may handle your phone number, chosen login details and verification outcome. These records let us connect your requests to the right account and help protect access when a new device or unusual login appears.

Payment matching

A DANA, OVO, GoPay or QRIS request can create a reference, amount, timestamp and status record. Bank transfer and virtual account references serve the same matching purpose. We use these records to reconcile activity, answer questions and investigate a disputed entry.

Cookies in browsers

Cookies can keep a session active, remember a preference or help us understand a failed account path. Clearing them may sign you out or remove saved choices. Your mobile or desktop browser provides controls for blocking, deleting or allowing cookies.

Account security

We use login activity, device signals and phone verification results to help detect access that does not match your usual account pattern. Never send us a password or wallet PIN. If your phone changes, contact support before asking us to alter account details.

Retention choices

We keep personal and transaction records only for the period needed for account operation, security checks, dispute handling and applicable obligations. When a record no longer serves those purposes, our retention process addresses it according to the relevant legal and operational requirement.

Requesting a change

You can ask about access, correction, deletion, restriction or another right available under applicable law by using account support. State the requested action and the phone number linked to csowin. We may verify your identity before changing or disclosing account information.

Ask About the csowin Privacy Policy

These Privacy Policy answers focus on the searches we hear from Indonesian account holders. They explain the data connected with login, wallets, cookies, devices and support requests, while keeping payment references separate from private credentials. If your situation is unusual, contact us through the account support route with enough detail to locate the record. Access depends on local law, and a request may require identity checks before we disclose or change personal data.

The csowin Privacy Policy covers account details, phone verification, login activity, device signals, cookies, support messages and payment-status references. It explains how we use those records for access, security, reconciliation and support, plus how you can ask about correction, deletion or another available right.

Yes. The Privacy Policy includes transaction references and status details connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use them to match a request or investigate a discrepancy, but we do not need your wallet PIN.

Use the support path connected with your account and request access to your personal data. Include the phone number linked to your login and describe the records you need, such as account details, cookie preferences or payment status. We may verify your identity before responding.

You can ask us to correct inaccurate account information through support. State which detail is wrong and provide the phone number linked to your account. For a wallet or bank record, add the transaction reference. We may request verification before making a change.

Our Privacy Policy treats cookies and device signals as tools for session handling, saved choices and access-security checks. Your mobile browser can block or clear them, although doing so may sign you out or remove preferences. Contact support if a cookie setting disrupts your login path.

We retain account, security and transaction records for the period needed to operate access, reconcile payments, answer disputes and meet applicable obligations. The exact period can vary by record type and legal need. When the purpose ends, our retention process addresses the data accordingly.

Send your Privacy Policy question through the account support route and identify the request type: access, correction, deletion, cookies or payment records. Do not send passwords or wallet PINs. If access is discussed, it depends on local law, and we may confirm your identity first.