Reference

basoswin Privacy Policy: Your Account Data Explained

Our Privacy Policy explains what data we collect when you open an account, sign in, use DANA or QRIS, and contact support.

Account dataWallet recordsCookie choicesAccess requests
basoswin basoswin Privacy Policy: Your Account Data Explained
CONTACT PATHS

Get Privacy Policy Help Without Guesswork

A privacy question should not disappear inside a general payment query. We keep a clear route for requests about your account data, wallet records, cookies, or retention.

Data access request Ask us to identify the personal data linked to your basoswin account. Include your registered contact detail and the relevant account step, so we can check the request before responding.
Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, provide the transaction reference and date. We use those details to trace status without requesting your wallet password.
Correction request If your contact detail or account record needs correction, send the requested change through support. We may ask for an account verification step before editing data connected with access.
HANDLING DETAILS

How basoswin Handles Privacy Requests

Privacy controls work best when each request reaches the right record. We separate account identity, payment references, device events, cookie settings, and support conversations so a request can be checked with less…

Purpose-based data use

We use account and verification data to create access, protect sign-in, and answer account requests. DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references support payment matching rather than wallet-password collection.

Cookie controls

Cookies can keep your mobile browser session active and help us understand loading errors. You can manage browser cookie settings, although changing them may require another sign-in or affect parts of the account path.

Account security

Before discussing sensitive account data, we may check your registered contact detail and a recent account step. Keep your password private, and do not send wallet PINs or full payment credentials to support.

Retention approach

We retain records for the period needed for account operation, payment matching, security checks, dispute handling, or legal duties. When a record is no longer needed, our handling follows the applicable retention process.

Who receives requests

Privacy requests are handled by the support route connected with your basoswin account. Payment references may be checked with the relevant processing service, limited to resolving the stated wallet or transfer question.

Requesting a change

You can ask for access, correction, or another available privacy action by describing the record and account step involved. We verify ownership first, then explain the result and any local-law limits.

Privacy Policy Answers for Your Account

These Privacy Policy answers focus on the practical questions you may have before opening an account or sending a data request. They explain wallet records, mobile cookies, verification, retention, and the contact route in plain terms, while recognising that access depends on local law.

It covers account details, verification records, sign-in events, device data, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account use.

No. We use transaction references and status details to match a payment with your account. Do not send a wallet password, PIN, or full payment credential through support.

Use the available support contact linked with your account and ask for a data access request. Include your registered contact detail and the account step involved so ownership can be checked.

Device and cookie data can keep a mobile browser session active, identify loading problems, protect sign-in, and record basic account events. Browser settings may limit cookies and require another sign-in.

Yes, you can request a correction for an account record by contacting support and describing the field that needs change. We may verify ownership before editing data connected with account access.

We retain payment references for account operation, payment matching, security checks, disputes, or legal duties for the applicable period. The Privacy Policy explains that retention can depend on local law.

Yes. It applies when you sign in from a mobile browser, open the lobby, or check wallet status. Cookie settings, device events, and account verification are handled under the same policy.