Reference

Open simbolwin Privacy Policy Clearly

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

Account dataCookie choicesPayment recordsPolicy requests
simbolwin Open simbolwin Privacy Policy Clearly
CONTACT PATHS

Reach Us About Privacy Policy

A clear support route helps you ask about a Privacy Policy point without sending sensitive details through an open message. Start from the account help path, describe the record or device concern, and include only the account details needed to locate it. For a wallet question, keep the payment receipt reference ready; we use that reference to check status without asking you to disclose a password.

Team online

Account help

Use the account help path when you need to ask what personal details are linked to your account or why phone verification is required before access.

Wallet status

For DANA, OVO, GoPay or QRIS questions, share the transaction reference through support so we can match the payment record without requesting your wallet password.

Policy requests

Ask us to correct, explain or remove eligible account data through the policy request path. We may verify account ownership before making a change.

DATA PRACTICES

Explore Privacy Controls Behind Your Account

Privacy choices work best when they are connected to the account actions you actually take.

Data we collect

We use account details you submit, phone verification status, support messages and transaction references.

Cookie choices

Cookies can keep your session active, remember selected settings and help us detect security issues.

Account security

Before account details are disclosed or changed, we may confirm ownership through the registered account path.

Payment handling

DANA, OVO, GoPay and QRIS references are used to trace a cashier status, while bank transfer and virtual account details…

Retention approach

We keep records for as long as needed for the stated service purpose, account protection, dispute handling or applicable legal…

Change requests

You can ask us to explain, correct or request deletion of eligible personal data through support.

Browse Privacy Policy Questions

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet record is checked. If your question is not covered, use the support path with a short description and avoid sending passwords, wallet PINs or unnecessary identity documents.

It covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It also explains purposes, retention, security checks and how to request an eligible change.

Phone verification helps us confirm account ownership before access and before certain data changes. We use its status as an account-security signal, and access depends on local law.

Yes. The Privacy Policy explains that DANA, OVO, GoPay and QRIS references may be used to trace payment status. We do not need your wallet password to check a receipt reference.

Send a correction request through the account help or policy request path. Tell us which detail is wrong and provide the registered account contact so we can verify ownership first.

You can request deletion of eligible personal data through support. We assess the request against account security, dispute handling and applicable legal duties before confirming what can be removed.

Retention varies by the record’s purpose, such as account protection, payment reconciliation or legal duties. When a record is no longer needed, our internal process moves it toward deletion or restricted handling.

Use the policy request path and describe the browser, device or cookie concern without sending a password. We can explain the relevant data use after confirming the account contact.