Reference

Privacy Policy for Your solusiwin Account

solusiwin Privacy Policy explains how we handle the details linked to your account, including phone verification, device access and wallet records for DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record contextAccount request path
solusiwin Privacy Policy for Your solusiwin Account
HELP WITH DATA

Ask About Privacy From Your Account

A direct account path makes privacy questions easier to send without exposing details in a public message.

Account privacy request Use the support path inside your account to ask what personal details are connected to your profile. Include your account identifier and the specific request, such as access, correction or removal, rather than sending wallet credentials.
Payment record question If a DANA, OVO, GoPay or QRIS record needs clarification, send the payment reference shown in your cashier history. We use that reference to check status while avoiding a request for your wallet password or full security code.
Login and device concern When a phone check or unfamiliar device session concerns you, contact us through the account support route before trying repeated logins. Tell us the device path and time shown on screen so we can focus on the relevant access record.
DATA HANDLING

How We Manage Account Privacy

Privacy decisions affect practical moments, from the first phone verification to a payment receipt check after a QRIS scan.

Account details

We use the information attached to your account to provide login protection, process account requests and connect support replies to the correct profile. Phone verification is an account step, not a reason for us to ask you to publish personal details in chat.

Wallet references

A wallet or bank record can include a method label such as DANA, QRIS, BCA, BRI, Mandiri or BNI. We use payment references to reconcile account activity and support questions, while your wallet password remains outside our request path.

Cookies and sessions

Cookies and session data help remember an authenticated browser path and keep account pages connected during a visit. On a shared device, sign out after checking your account and clear the browser session if you do not want it retained locally.

Device protection

Login activity can be associated with device and session signals so an unusual access pattern can receive closer attention. If you move from mobile browser to desktop, use your normal account path and contact support when a session does not look familiar.

Retention choices

We retain account and transaction records only for the operational, dispute and legal purposes described in the current Privacy Policy. A deletion or correction request can be assessed against those purposes, with the result explained through your account contact path.

Requesting changes

You can ask us to access, correct or clarify personal details by sending a focused request through account support. State the affected field and why it appears incorrect; we may need account verification before changing a phone or payment-linked record.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account questions we expect before you open access or connect a local wallet. They explain the practical route for checking data, cookies, device sessions and payment references. If a question concerns eligibility, access depends on local law, and the current policy remains the controlling text for your account.

The solusiwin Privacy Policy covers account details, phone verification, device sessions, cookies, payment references, retention and privacy requests. It also explains how we use information for account support and status checks involving DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect an account request to the correct person and supports login protection. We may use the verified phone detail when checking an account change or unusual session; access and eligibility still depends on local law and the current policy terms.

Open the support route from your account area and state whether you want access, correction or clarification. Name the affected field, such as a phone detail or payment reference. We may ask for account verification before releasing or changing information.

Yes. The Privacy Policy covers payment references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. These records help us trace a receipt or status question; they do not require you to send a wallet password or full security code.

Cookies and session data can keep your signed-in account path working and help recognise a browser session during account activity. If you use a shared phone or computer, sign out and clear local browser data after your visit to reduce access through that device.

Use account support and describe the device type, approximate time and screen path linked to the unfamiliar session. Avoid sending passwords or security codes. We can focus the request on the relevant login record and explain the next account-protection step.

You can submit a deletion request through the account support path. We assess it against the retention purposes stated in the Privacy Policy, including transaction or dispute records that may need to remain. We will explain the outcome and any remaining record category.