Reference

Your Privacy Policy for DANA Access

Our Privacy Policy explains how solusiwin handles the account and wallet details you provide before you enter the lobby.

Clear data purposesWallet record contextAccount request pathIndonesia access wording
solusiwin Your Privacy Policy for DANA Access
CONTACT ROUTES

Three Ways To Ask About Your Data

A clear contact route helps when a privacy question appears beside a login or wallet issue.

Account access Ask through the account support route when you need to confirm the phone verification record, correct a contact detail, or understand why a sign-in event appears in your account history.
Wallet records For DANA, OVO, GoPay or QRIS questions, share the relevant receipt or status reference without sending a wallet password. We use the reference to locate the payment record linked to your account.
Privacy request Request a copy, correction, restriction, or removal review through our privacy contact path. We may verify account ownership first so another person cannot obtain or alter your personal record.
DATA PRACTICES

Six Privacy Controls Behind Your Account

We keep the Privacy Policy practical by linking each data type to an account task. Login records help us trace access, wallet references help us resolve payment status, and device signals help…

Account records

We use your account and phone verification details to create the sign-in path, confirm ownership during support, and connect the correct profile to lobby and wallet records.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a receipt or status event to your account without treating the payment reference as your password.

Device signals

When you open the lobby on a mobile browser or desktop, we may record browser, device and login signals for access checks. These signals help us investigate unusual sign-in patterns.

Cookies

Cookies can keep a session active, remember necessary settings, and help us understand whether a page request belongs to the same visit. Your browser controls can remove or restrict them.

Storage periods

We retain account, support and payment records only for the period needed for the stated purpose, account safety, dispute handling, or a legal record requirement. You can ask why a record remains.

Security requests

Contact us when a phone number, login detail, or wallet reference looks wrong. We verify the account owner before changing data, disclosing records, or processing a deletion request.

Seven Answers About Privacy Policy

These Privacy Policy answers address the searches we hear most often before account creation. They cover account data, wallet references, cookies, device behaviour, retention, and the route for requesting changes. If your situation is specific, contact us through the privacy path and include only the details needed to identify the record.

The Privacy Policy covers data collected during account creation, phone verification, login, support contact, device access, cookies, and wallet activity. It also explains how DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be connected to your account record.

Phone verification helps us confirm account ownership during sign-in and support requests. We may use the verified contact detail to locate your profile or protect it from an unauthorised change. The Privacy Policy explains this purpose and the request path for correcting the record.

Yes. The Privacy Policy covers payment status and receipt references created through QRIS, DANA, OVO and GoPay, along with bank transfer and virtual account records. These references help us investigate a mismatch, but you should never send a wallet password through support.

When you use a mobile browser or desktop browser, we may receive device, browser, session and login signals connected to the access request. We use them for account protection and troubleshooting. The Privacy Policy explains the purpose without treating those signals as your account password.

Cookies can support session continuity, necessary settings and page-request checks. Your browser can remove or restrict cookies, although some account functions may not work as expected afterward. The Privacy Policy describes why a cookie may be used and how browser controls affect it.

You can contact us to request access, correction, restriction, or removal where the request is allowed. We first verify account ownership, then assess the record, its purpose, and any retention requirement. The Privacy Policy contact route is the right place to begin.

Retention depends on the purpose of the record, account safety needs, dispute handling, and applicable legal requirements. The Privacy Policy does not treat every record alike. Ask us about a specific phone, login, QRIS, or bank reference so we can explain its status.